Case study · 2026
Process Processor
The starting point
Why do we sometimes take in a question from a digital service more easily than the same question from an advisor?
In many organizations, the process problems are already known. The people working in the process usually see the waiting times, the duplicated work and the unclear responsibilities. Yet the problems are hard to discuss openly. Advice from a colleague or a consultant can be perceived as criticism of the person, the team or earlier decisions.
I wanted to explore whether a digital service could create a more neutral space for reflection.
The hypothesis
If people describe their process step by step and are met with consistent, neutral questions, they can discover for themselves what would be hard to hear as direct advice.
The role of the AI is not to present a verdict. It helps the user structure their experience, spot contradictions and articulate opportunities for improvement.
The solution
Process Processor guides the user through a structured analysis of a work process. The service helps identify, for example:
- unclear responsibilities
- unnecessary handovers
- waiting times
- manual duplicated work
- information gaps
- steps without a clear purpose
- potential improvements and automations
The design principle
The service should not replace the advisor's judgment. It should lower the threshold to the honest analysis that has to come before the advice.
The important part is that the analysis happens together with the user. The tool does not observe the organization from the outside and hand out grades.
Process Processor grew out of the same principle that shapes my advisory work: do not start with the tool. Start by understanding the work, the people and the decisions behind the process. Only then can you tell whether the answer is changed ways of working, clearer responsibilities, automation or AI.