Map your business processes
Org charts show who reports to whom. They do not show how work actually moves. This programme maps your real processes end to end and connects every step to the roles, tasks and tools that run it.
03DiscoveryAvailable now · 48h post-ingestion
The org chart is a map of accountability, not a map of work.
Ask an executive how the organisation is structured and you will get a confident answer. Ask how a customer complaint actually travels from first contact to resolution, every handoff, every approval, every system touched, and the room goes quiet. That silence is normal. Work flows horizontally through organisations that are drawn vertically, and almost nobody owns the horizontal view.
The process documentation most companies hold describes how work was designed to run, usually years ago, by someone who has since left. The real process has grown workarounds, side channels and quiet heroics that never made it into the manual. The gap between as-documented and as-run is where cost hides, and it is precisely where naive automation goes wrong.
Automate a step without seeing the whole flow and you have not removed the bottleneck. You have moved it.
AI raises the stakes on this old problem. Automate a single step without seeing the whole flow and you have not removed the bottleneck, you have moved it downstream to a team that never saw it coming. The value of AI in operations is decided at the level of the flow, not the step, which means you cannot make good automation decisions from an org chart or a tool list. You need the process as it actually runs, confirmed by the people who run it.
That is the discipline of this programme: capture the real flows, connect every step to the roles, tasks and tools that carry it, and score AI exposure per step so the automation case is visible end to end before anyone builds anything.
What this programme does.
We capture your core processes as they actually run, not as they were documented years ago: every handoff, every approval, every system touched, confirmed by the people who do the work.
Each process step is linked into the graph, so AI exposure, tool dependencies and capacity all become visible per process, and any change you model shows its downstream effects.
From kickoff to landed.
Available now · 48h post-ingestion
Your structure and core processes go in
You provide the structure, departments and the names of your core processes. That is genuinely all: the engine drafts the step-by-step maps for confirmation.
The engine drafts every flow
Each process is drafted end to end: handoffs, approvals, systems touched, and the roles and tasks connected at every step, ready for the people who actually run it.
Process owners confirm reality
An hour with each process owner turns the draft into the as-run truth: workarounds included, dead steps removed, the quiet heroics finally on the map.
Exposure and bottlenecks, per step
Automation potential scored per step and rolled up per process, with bottleneck analysis showing where work queues, who it waits on, and which steps AI removes.
What you get.
Living documents, not slideware: every deliverable stays connected to the graph and updates as the analysis moves.
Living process maps
Every core process, step by step, connected to roles, tasks and tools.
Bottleneck analysis
Where work queues, who it waits on, and which steps AI removes.
Process-level AI exposure
Automation potential scored per step, rolled up per process.
What you need.
- Your structure and departments
- Names of your core processes: the engine drafts the steps for confirmation
- An hour with each process owner to confirm the drafts
The questions teams ask about this programme.
How is this different from process mining software?+
Process mining reads system logs, so it only sees the steps that touch instrumented systems, and it takes months to deploy. This programme captures the whole flow, including the human steps and workarounds logs never see, drafts it in days, and has the people who run the process confirm it. You get the as-run truth without a mining infrastructure project.
How much time does this take from our people?+
About an hour per process owner to confirm the drafted maps. The engine does the drafting; your people do what only they can do, which is say how the work actually runs.
Our processes are not documented at all. Can we still run this?+
Yes, and undocumented is often easier than badly documented. The engine drafts the steps from the process names, your structure and its own process library, and the owners correct the draft. Confirming a proposal is far faster than writing from a blank page.
Do the maps go stale like our old documentation did?+
No. The maps live in the Human Layer Graph, connected to the roles, tasks and tools at every step. When the graph changes, the process view changes with it, and any change you model shows its downstream effects across the flow.
Where should we start?+
Three to five core processes in one department is the proven starting shape: big enough to see real bottlenecks and automation potential, small enough to confirm in a week. Expand from there once the value is visible.
Programmes compound.
Each programme deepens the same graph the next one runs on: nothing is re-gathered, nothing starts from zero.
The natural next step · Programme 06 · TransformCreate a rightsizing plan mapped to your processes
Once you can see how work actually flows, capacity decisions can finally be grounded in real workflows instead of benchmark ratios.
View programmeExplore next
Discovery
See how AI changes your roles, tools and processes.
Read moreSee how AI has impacted your roles
Role-by-role exposure, task by task
Read moreFind which tools and SaaS AI has disrupted
Your stack, scored against the AI market
Read moreThe Company Brain: Where AI Compounds
Everyone in your organisation is using AI, and none of it makes the organisation smarter. Every session works from its own private context, so only the person learns. The organisations getting real returns have one connected model of how the work runs, and it is the only asset in the AI stack that appreciates.
Read moreWhere to Start: The Clean Baseline Your AI Transformation Is Missing
Almost every organisation is somewhere in the AI shift, and almost none can describe where. AI lands at task level while most orgs deploy at macro level, and that mismatch is what turns speed into dirty data. Why the baseline comes before the tool decision.
Read moreEngagements
How an engagement runs, week by week.
Read more
Start with this programme, on one department.
See your organisation as flows of work, not boxes on a chart, before you redesign anything.