Spot friction before new tools are introduced
Many digital problems sit in the workflow, not in the tool. Information is searched, copied, forwarded, and maintained twice. I make visible where time and quality are lost and where AI or automation genuinely fits.
What it is about
This stays close to concrete daily reality, without heavy organisational consulting. I take one task that regularly creates effort today and answer three questions: what happens, what does it cost, and what could become easier?
Typical starting situations
Too many manual steps.
Information spread across emails, files, chats, and folders.
Status reports rebuilt again and again.
Decisions take longer than needed.
Knowledge disappears after meetings or handovers.
How it works
Pick a task. A real routine that occurs often and creates noticeable effort.
Make the current flow visible. Steps, people, media breaks, data sources, and error sources.
Estimate the effort. Frequency, time, rework, and waiting times.
Derive levers and define a test. A concrete proposal, small enough to test and relevant enough to matter.
Outcome
A clear sketch of the workflow
Visible friction points
A rough effort estimate
Prioritised improvement levers
A concrete next test step
Suitable formats
Process review: focused look at one workflow. Duration: 60 to 120 minutes plus a short review.
Impact Day: analyse a routine, rebuild it, and calculate the difference in time, effort, and value. Duration: one working day or two compact sessions.
Workflow prototype: a first usable flow, e.g. with Microsoft 365, Power Automate, or AI support. Duration: 1 to 3 weeks to the first test.
Method
A real task, visible proof, clear anchoring. I start with a concrete task, check the difference in everyday work, and secure the result so it can keep being used.
Next steps
A good fit after this: Impact Day or Implementation and prototyping.
Other formats