The 3 criteria we use to qualify a process for a pilot.
The honest answer: there are hardly any criteria. What we really ask for is a bounded scope and about two hours of your time. In return, within 48 hours of the intake you see a completely new process working, built on your own situation.
One thing up front, because it is often misunderstood: we do not rebuild your current process. We identify how the work runs today, and design a completely new process for it. We show that new process concretely and working, so you don't have to believe in a concept — you can look at a result.
A bounded scope
You pick one bounded process: something comes in, steps happen, something goes out. Multiple process owners or departments involved? No problem, as long as the edges are clear. The only thing that doesn't work is "everything at once". A bounded scope makes the result concrete, measurable and easy to discuss internally.
60 minutes to identify the current process
One conversation of an hour. Together we capture how the work really runs today: the steps, the rules, the exceptions, the systems. That is all the preparation we ask of you. No working groups, no documentation project, no weeks of workshops.
Time to go through the demo, live
Within 48 hours of the intake, the new process is up and running in a simulation environment. We ask you to go through that personal demo together, live, and evaluate it: is it right, what does it deliver, and what would you change. Your judgement on a working result, not on a presentation.
Really there is only one criterion: two hours of your time, and the willingness to think about a bounded scope.
Help choosing that scope?
The best first candidates are processes that recur often and are full of routine work. Think of:
- Handling applications or intakes: copying data, checking, requesting documents
- Completing files before an assessment or delivery
- Drafting quotes from standard data and templates
- Checks and verifications that are done by hand today
- Status updates and feedback to clients or chain partners
Torn between two processes? Bring both to the conversation; we'll choose together.
Why we keep the bar this low
Because concrete works and abstract doesn't. Talking about processes and AI in general terms almost never leads to a next step. We'd rather invest time and energy in you, so there is something working to decide on. And the first project does more than show what we can do: it shows your organisation that process change is enjoyable, moves fast and replaces no one's work.
Arjan van Unen — CMO, Model My Context