Tell Us
Participants describe a recent episode.
Operational Reality Mapping
Map how work actually gets done.
Operational Reality Mapping is an evidence-led, behaviourally informed diagnostic that reconstructs how a critical job actually gets done, compares that reality with organisational intent, identifies sources of operational friction and discovers the highest-value Assurance Points for intervention.
AI can extend discovery, analysis and structure where appropriate; it is not the primary value proposition.
Illustrative
Operational Reality Map
Stated Reality
Formal route
Reported Reality
Described route
Operational Reality
Observed route
WaitsHidden approvalsWorkaroundsReworkInformal handoffsA Potential Assurance Point
You already have policies, processes and technology.
In a complex organisation, the way work is designed and the way work actually gets done are rarely identical.
Real work may depend on personal judgement, undocumented workarounds, hidden approvals, fragmented systems and increasingly AI agents.
Complexity is not something you need to remove before mapping can help. Complexity is what we map.
Three realities
Compare intent, belief and evidence
01
Stated Reality
Where it comes from
Policies, procedures and process maps
What it reveals
What the organisation has designed and documented
02
Reported Reality
Where it comes from
Interviews and descriptions of recent work
What it reveals
What participants believe and describe happens
03
Operational Reality
Where it comes from
Permitted evidence, traces and observation
What it reveals
What the evidence shows actually happens
Each lens is useful. Divergence between them is where operational risk tends to accumulate.
The gaps between these states can create delay, rework, error, non-compliance and operational risk.
Not how is this process supposed to work—what does it actually take to get the job done?
What gets mapped
One bounded job-to-be-done
The unit of analysis is a job travelling through the organisation—not necessarily a department or system.
Illustrative workflows
- Onboarding a supplier
- Approving a procurement package
- Responding to a regulatory requirement
- Approving a contract
- Producing a board submission
- Processing a customer exception
- Moving an initiative from concept to execution
Illustrative examples, not client case studies.
The map may examine
Outcome, trigger, actors, stages, decisions, approvals, handoffs, responsibilities, artefacts, systems, dependencies, exceptions, waiting, rework, controls and evidence.
Methodology
From scope to intervention
- 01
Scope
Select a bounded, strategically meaningful workflow and establish the intended outcome, boundaries, stakeholders and success criteria.
- 02
Understand
Review relevant policies, procedures, process maps, responsibilities, approval rules, templates and governance documents.
- 03
Discover
Conduct high-value human interviews and broader AI-assisted discovery using questions about recent, real examples of work.
- 04
Reconstruct
Gather permitted evidence, trace recent cases and, where feasible, follow a live case through an Operational Drill.
- 05
Map
Combine intended, reported and evidence-backed operational reality into one coherent view.
- 06
Diagnose
Examine clarity, ownership, handoffs, incentives, capacity, systems, social norms and sources of truth.
- 07
Prioritise
Identify the small number of moments where drift could materially threaten the intended outcome and intervention is possible.
- 08
Intervene
Recommend the smallest intervention likely to improve reliability before proposing major redesign or new technology.
Behavioural discovery
Ask about the last real example.
Episodic questions reveal hidden dependencies, adaptations and tribal knowledge that abstract descriptions often miss.
Tell us about the last time you did this.
What happened next?
Who did you contact?
What were you waiting for?
How did you know that was the correct document?
What did you do when the expected process did not work?
Who do experienced people call that a new joiner would not know to call?
What would happen if you followed the written process exactly?
Evidence Ladder
From recollection to observed work
Show Us
Evidence makes the route more tangible.
Let Us Observe
The work is followed as it happens.
The objective is to shadow the work, not continuously monitor an individual.
Operational friction
A diagnostic lens, not a predetermined verdict
Understanding and information
- — Clarity
- — Knowledge and findability
Ownership and coordination
- — Ownership
- — Authority
- — Coordination
- — Handoffs
Behavioural conditions
- — Capacity and attention
- — Incentives
- — Risk and psychological safety
- — Social norms and tribal knowledge
Process and technology
- — System friction
- — Process friction
Operational truth and AI alignment
- — Source-of-truth failure
- — AI-agent alignment
An engagement follows evidence; it does not assume that every form of friction is present.
Minimum Effective Intervention
Identify the smallest intervention, at the highest-leverage moment, that materially improves the probability of the intended outcome.
- 01Remove unnecessary friction
- 02Improve the default
- 03Adjust the choice architecture
- 04Improve information, framing or salience
- 05Prompt or nudge
- 06Check or verify
- 07Escalate or require approval
- 08Redesign only where evidence justifies it
Potential deliverables
Outputs that make reality usable
01
Operational Reality Map
02
Friction Heatmap
03
Assurance Point Register
04
Minimum Effective Intervention Roadmap
A facilitated engagement may also include an Executive Operational Reality Brief, Intended Workflow Map, Responsibility Reality Map and Evidence Register, depending on scope.
A typical bounded engagement can be completed in approximately three to five weeks, depending on scope, evidence availability and organisational complexity.
Path to continuous assurance
Discover → Design → Deploy → Assure → Learn
Discover
Map divergence.
Design
Define priority interventions.
Deploy
Place them in work.
Assure
Identify future drift.
Learn
Improve continuously.
This implementation path is distinct from the continuous Operational Assurance Model: it describes how mapping can move towards operational practice.
Begin with one workflow
Choose one important workflow. Map its reality.
Start with a job that matters: recurring enough to observe, important enough to improve and bounded enough to understand.