Process Maps
A step-by-step map of each analysed workflow: who does it, what information moves through it, and where it breaks down.
Proof
Makes the real workflow visible before any redesign begins.
Phase Two begins here. Six to eight weeks to find the workflow worth changing and design exactly what the new version looks like — AI role, human role, review points, and exception handling — before anyone builds anything.
Not every manual, repetitive, or painful task is an AI problem. And knowing that a workflow needs AI is not the same as knowing how to change the work. Both questions need answering before a pilot can begin.
This service runs two stages inside one engagement. Stage One goes deep on two to three candidate workflows — maps every step, scores every pain point, and sorts everything into three categories: what AI can genuinely help with, what should be fixed without AI, and what is not worth solving right now.
Stage Two takes the selected workflow and redesigns it completely: what AI does, what people own, where review happens, what good output looks like, and how exceptions are handled. The result is a complete workflow specification — the design brief for anyone who builds or pilots the tool. This service produces the design. Not the build.
Stage One selects and maps. Stage Two redesigns. The output is a workflow specification complete enough for an internal team or implementation partner to build from.
This layout is for explaining a service as a repeatable operating shape: who it is for, how the work moves, and what the client leaves with.
The data layer, governance layer, and literacy layer have been assessed. The business knows where its foundations sit. Now the question is where to apply AI first and what the new process should look like.
Leadership has identified two or three processes causing friction. Stage One validates which is the right one to change and whether AI is actually the correct solution — or whether the process just needs to be fixed.
An internal team or implementation partner will run the pilot. They need a complete, unambiguous specification to work from — not a concept or a slide deck.
Identify two to three candidate workflows with leadership. Define scope and selection criteria, then map each workflow end-to-end: every step, every decision point, every handoff, and everywhere things go wrong.
Weeks 01–02Score every pain point against AI fit, business impact, data availability, and owner readiness. Produce the AI Opportunity Shortlist, Process-Improvement-First List, and Deprioritised List. Select the one workflow to redesign.
Weeks 03–04Design the AI role — what it does, what it produces, its operating limits. Design the human role — what people own, what they review, and what they decide. Map the redesigned workflow with roles clearly separated.
Weeks 05–06Document every review point, quality standard, exception path, and failure mode. Present the complete workflow specification to leadership and confirm it is sufficient to brief whoever builds or runs the pilot.
Weeks 07–08A step-by-step map of each analysed workflow: who does it, what information moves through it, and where it breaks down.
Makes the real workflow visible before any redesign begins.
The specific pain points where AI fits, ranked by usefulness and readiness.
Identifies where AI can genuinely help.
The pain points that should be fixed with a better process, template, checklist, or system — not AI. Often the most valuable output.
Prevents tool-first waste by identifying what AI should not touch.
What is not worth solving now and why.
Makes the no-list explicit and defensible.
The new process for the selected workflow, with AI steps and human steps clearly separated.
Shows exactly how the work changes before anything is built.
What AI does in the new workflow and what people own, review, decide, and escalate.
Keeps judgement and accountability explicit from day one.
What good output from this workflow looks like in plain English, and the specific tests that would confirm the redesigned workflow is working.
Gives staff, builders, and leadership the same standard.
A clear view of whether the workflow is ready to pilot and what would need to be true before a build begins.
Creates the bridge to Service 07.