Went live too soon
Straight from pilot to production, without proper testing. The first error is immediately visible to a customer.
Between “it works in the demo” and “it's part of the day-to-day work” lies the part where things usually go wrong. We help you make that transition, with attention to privacy, security, human oversight, testing, and working agreements people actually follow.
Next step: document working agreements with the team leads.
Six patterns. They rarely cost you the technology, but they do cost you trust.
Straight from pilot to production, without proper testing. The first error is immediately visible to a customer.
It’s unclear who can make decisions, check, and make changes. So everyone does it differently.
Personal data or confidential information that hasn't been properly protected. Difficult to fix after the fact.
Answers are blindly accepted without validation. Until one is wrong.
User feedback isn't collected, so no one knows where the friction is.
Knowledge and administration are in the hands of the enthusiast. If they leave, everything comes to a standstill.
Data sovereignty, privacy by design and security to the standard. See data sovereignty.
Human review and explanation for decisions that affect people.
Testing, validation, and monitoring of output and performance — including after launch.
Roles, responsibilities, and escalation documented. See AI governance.
Ongoing insight into usage, quality, and impact, rather than a one-off measurement after the fact.
Regularly evaluate and adjust based on data and feedback.
Six steps. Step four is where most engagements get stuck—and where we put in the most time.
Every point has an owner. Without an owner it's not an agreement but an intention.
| Control | Status | Owner |
|---|---|---|
| Data classification and DPIA | ready | Privacy |
| Access management and permissions | ready | IT |
| Model selection and documentation | ready | Project management |
| Test plan and validation criteria | in progress | Process owner |
| Check for bias and errors | in progress | Project management |
| Human review in place | in progress | Process owner |
| Logging and audit trail | to be scheduled | IT |
| User training and adoption plan | to be scheduled | Team leadership |
| Incident procedure and escalation | to be scheduled | Executive team |
| Evaluation and metrics | to be scheduled | Process owner |
Likelihood versus impact. Start with the top right; leave the bottom left for later or never.
| Low likelihood | Medium likelihood | High likelihood | Very high likelihood | |
|---|---|---|---|---|
| Very high impact | 2 | 3 | 4 | 4 |
| High impact | 1 | 2 | 3 | 4 |
| Medium impact | 1 | 1 | 2 | 3 |
| Low impact | 1 | 1 | 1 | 2 |
De Frisse Blik shows where you stand with data, AI and governance—and which step makes the most sense to take first.
Ask your question about AI, the AI Act, integrations or digitalization. The answer comes from the pages of this site, with references to where it can be found.
Also good to know: frequently asked questions · security and data · terms and conditions · partners · research and figures · templates · what's changing · where you start
An AI pilot only adds value if the source data are reliable, someone is accountable and the output is used in the actual workflow.
Start with a concrete business problem and a measurable outcome, not with an AI tool. Arrange data, ownership, risk and human control before you scale up.
We connect analysis, business intelligence, data and execution so you don't get stuck in advice or loose tooling.
A concrete analysis, priorities, decision criteria, an executable next step and visibility into what needs to be built, integrated or secured next.
Right for Dutch SMB organizations that want to solve a concrete process, knowledge, data or AI problem. Not for organizations looking only for a generic tool demo or unproven AI promise.
Price and scope depend on the chosen next step. View the current fixed packages and pricing logic at pricing for digitization.
We work step by step, make assumptions and ownership explicit, use only the minimum necessary data, and maintain human control over decisions and execution.
No. The preference is one clearly defined problem with a measurable outcome, then scale up.
The current pricing and package logic is on the pricing page; custom work is only chosen if the scope really requires it.
By defining the problem, owner, success metric and stop criteria in advance, and doing readback and verification after each step.
We map your current process, systems, exceptions and costs. Only then do we advise whether an off-the-shelf solution, a custom integration or another approach makes sense.
This page supports the following concrete solutions.
Choose the next step that fits what you are viewing now.
Bedrijfsgeheugen gebruikt noodzakelijke cookies voor een goede werking van de site. Met jouw toestemming gebruiken we ook analytische cookies (Google Analytics) om te meten hoe de site wordt gebruikt en die te verbeteren. Je keuze wordt onthouden en je kunt 'm altijd wijzigen. Meer weten? Zie onze privacyverklaring.Met jouw toestemming meten we met Google Analytics hoe de site wordt gebruikt. Zonder toestemming meten we niets. Privacy