Diagnostic methodology

Map how work actually gets done.

Operational Reality Mapping is an evidence-led, behaviourally informed diagnostic for understanding how an important workflow actually operates.

It establishes a clear view of Operational Intent, reconstructs Operational Reality, identifies the material Execution Gaps between them and locates the Assurance Points where proportionate intervention could improve the intended outcome.

Humans and AI agents may both participate in the same operational system. The method examines how the work operates—not merely which actor performs each task.

Core relationship

Operational Intent

compared with

Operational Reality

reveals the Execution Gap

The purpose

Make the Execution Gap visible.

Organisations usually have strategies, policies, procedures, controls and process maps describing how work should happen.

But work is performed under real conditions. People and AI agents interpret information, make decisions, cross organisational boundaries, manage exceptions and adapt when the intended process does not fit the situation.

Operational Reality Mapping makes those conditions visible before the organisation prescribes a solution.

It is most useful when an important workflow is:

  • underperforming
  • delayed or repeatedly reworked
  • contested or poorly understood
  • dependent on undocumented knowledge
  • crossing multiple functions or systems
  • exposed to regulatory, financial or operational risk
  • incorporating AI agents or automation
Do not begin by asking how the process is supposed to work. Begin by asking what it actually takes to produce the outcome.

Intention and reality

Compare what should happen with what actually happens.

Operational Intent and Operational Reality are compared to reveal the Execution Gap.

Operational Intent

What the organisation wants to happen.

Informed by

  • strategy and intended outcomes
  • policies and procedures
  • process and control design
  • responsibilities and authority
  • risk and regulatory requirements
  • expected evidence of successful execution

Compare

The Execution Gap

Material divergence between Operational Intent and Operational Reality.

Operational Reality

What actually happens during execution.

Reconstructed from

  • participant accounts of recent work
  • documents, artefacts and communications
  • permitted records and system traces
  • decisions, approvals and handoffs
  • exceptions, workarounds, waiting and rework
  • observation of work where appropriate

Operational Intent and Operational Reality must remain distinct.

Documentary evidence helps establish the intention. Participant accounts, operational evidence and observation help reconstruct the reality.

No single source is treated as automatically complete. The method triangulates available evidence to build a credible, bounded account of how the workflow operates.

Not every difference represents failure. Operational Reality may include legitimate judgement, authorised exceptions and useful adaptations. The concern is material divergence that is invisible, unmanaged or threatens the intended outcome.

Evidence-led discovery

Reconstruct reality from recent, real work.

Operational Reality cannot be established from a process map alone.

The method combines documentary review, participant experience, operational evidence and—where feasible—direct observation of work.

Three levels of evidence: Tell us, Show us, and Let us observe.
  1. 01

    Tell us

    Participants describe a recent, specific example of the work.

    Purpose

    Reveal remembered decisions, dependencies, informal coordination and adaptations.

  2. 02

    Show us

    Permitted artefacts and evidence make the route of the work more tangible.

    Purpose

    Validate handoffs, approvals, information sources, waits, exceptions and rework.

  3. 03

    Let us observe

    Where appropriate, the workflow or a live case is followed as it happens.

    Purpose

    See conditions and behaviours that may not appear in documents or recollection.

These are complementary evidence sources, not distinct versions of reality.

The objective is to understand the work, not to monitor an individual continuously.

Ask about the last real example

Move from abstract descriptions to actual episodes.

General questions often produce an idealised description of a process. Episodic questions reveal the decisions, dependencies, workarounds and operating conditions that shape real execution.

  • Tell us about the last time you performed this work.
  • What happened next?
  • Who did you need to contact?
  • What were you waiting for?
  • How did you know which information or document to use?
  • What happened 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?

A concise selection—not an exhaustive interview script.

The unit of analysis

One bounded job-to-be-done.

Operational Reality Mapping follows a meaningful job from trigger to outcome. The unit of analysis is the work travelling through the organisation—not necessarily a department, system or process owner.

  1. 01Trigger
  2. 02Activity
  3. 03Decision
  4. 04Handoff
  5. 05Completion
  6. 06Outcome

The map may examine

  • intended outcome
  • trigger and completion criteria
  • human and AI actors
  • stages and activities
  • decisions and approvals
  • responsibilities and authority
  • handoffs and dependencies
  • documents, data and systems
  • waiting and rework
  • exceptions and adaptations
  • controls and required evidence
  • operating conditions affecting behaviour

Illustrative workflows—not client case studies

  • 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

Methodology

From scope to proportionate intervention.

  1. 01

    Scope the workflow

    Select one important, recurring and bounded job-to-be-done. Define its intended outcome, boundaries, stakeholders and success criteria.

  2. 02

    Establish Operational Intent

    Review the relevant strategy, policies, procedures, controls, responsibilities, authority, regulatory requirements and expected evidence.

  3. 03

    Gather evidence of execution

    Use interviews, AI-assisted discovery, permitted artefacts, operational records, system traces and observation to examine recent, real examples of the work.

  4. 04

    Reconstruct Operational Reality

    Build an evidence-led map of the route work actually takes, including decisions, handoffs, dependencies, waits, exceptions, workarounds and rework.

  5. 05

    Identify and diagnose the Execution Gap

    Compare Operational Reality with Operational Intent. Determine which divergence is material and investigate the conditions producing it.

  6. 06

    Design the assurance response

    Identify priority Assurance Points and recommend the Minimum Effective Interventions most likely to improve the intended outcome.

Operational Reality Mapping is diagnostic. Recommended interventions must be implemented and evaluated before their effectiveness can be established.

Operational conditions

Understand why divergence occurs.

The purpose is not simply to find where reality differs from intention. It is to understand the conditions producing the difference.

01

Clarity and information

  • unclear requirements
  • information that is difficult to find
  • conflicting or outdated sources
  • loss of context
02

Ownership and coordination

  • unclear ownership or authority
  • hidden approvals
  • fragmented handoffs
  • cross-functional dependencies
  • waiting between actors
03

Behavioural conditions

  • workload and attention
  • incentives and competing priorities
  • social norms and tribal knowledge
  • risk perception and psychological safety
  • habitual workarounds
04

Process and technology

  • unnecessary process friction
  • system limitations
  • fragmented tools or data
  • poorly configured automation
  • misaligned AI-agent instructions or permissions

The diagnostic follows the evidence. It does not assume that every type of friction is present or that every workaround should be removed.

Where intervention matters

Locate the moments with the greatest assurance value.

An Assurance Point is a designed moment where human or AI activity can be compared with Operational Intent and, where necessary, guided, corrected, verified or escalated.

Operational Reality Mapping identifies the small number of moments where material divergence could threaten the intended outcome; relevant evidence is available; an intervention is operationally possible; and the value of intervention is proportionate to its burden.

A seven-moment workflow with Assurance Points only at the decision, exception and approval moments.
  1. 1Trigger
  2. 2Prepare
  3. APDecide
  4. 4Handoff
  5. APException
  6. APApprove
  7. 7Outcome

Assurance Points are selective. They are not checkpoints at every stage.

Explore Assurance Points

Proportionate response

Intervene only as much as the evidence requires.

The Minimum Effective Intervention is the smallest practical intervention, applied at the highest-leverage moment, likely to materially improve the probability of the intended outcome.

The response should not automatically be more training, another approval, new software or wholesale process redesign.

Depending on the evidence, the intervention may

  • remove unnecessary friction
  • improve clarity or information
  • change a default
  • prompt or guide an actor
  • introduce verification
  • clarify authority
  • restrict an action
  • require approval or escalation
  • redesign the workflow where lesser intervention is unlikely to be sufficient

Start with the least burdensome response justified by the evidence.

Explore the Principles of Operational Assurance

Potential deliverables

Outputs that make reality usable.

  1. 01

    Operational Intent Map

    A clear representation of the intended outcome, workflow, requirements, authority and expected evidence.

  2. 02

    Operational Reality Map

    An evidence-led reconstruction of how the workflow actually operates.

  3. 03

    Execution Gap and Assurance Point Register

    A prioritised record of material divergence, contributing conditions and the moments where assurance may add value.

  4. 04

    Minimum Effective Intervention Roadmap

    A sequenced set of proportionate interventions, owners, evidence requirements and measures.

Optional outputs may include

The outputs depend on scope and evidence availability.

  • Executive Operational Reality Brief
  • responsibility and authority map
  • operational friction analysis
  • evidence register
  • human–AI interaction map
  • implementation priorities

A typical bounded engagement may be completed in approximately three to five weeks, depending on scope, evidence availability and organisational complexity.

A bounded diagnostic

Evidence before transformation.

Operational Reality Mapping is

  • an evidence-led diagnostic
  • focused on one bounded job-to-be-done
  • behaviourally informed
  • applicable to human and AI-enabled work
  • designed to identify material Execution Gaps and Assurance Points
  • intended to support proportionate action

Operational Reality Mapping is not

  • a certification
  • a formal audit opinion
  • continuous employee surveillance
  • a guarantee that an intervention will work
  • conventional process mapping alone
  • a predetermined technology or transformation programme

What happens next

Use the map to design assurance where it matters.

Operational Reality Mapping provides the diagnostic foundation.

Its findings can be used to design Assurance Points, implement Minimum Effective Interventions and establish continuous Operational Assurance around the material moments in the workflow.

  1. 01

    Operational Reality Mapping

    Reveal the Execution Gap.

  2. 02

    Assurance design

    Define Assurance Points and proportionate interventions.

  3. 03

    Continuous Operational Assurance

    Observe, compare, assure and adapt during execution.

Explore the Operational Assurance Model

Begin with one workflow

Choose one job that matters. Map its reality.

Start with a workflow that is recurring enough to examine, important enough to improve and bounded enough to understand.

Map the Reality of This Workflow