Skip to main content

Process Mapping

What happens when teams improve the process they imagine instead of the work people actually do?

Problem: Queues, workarounds, and handoff failures remain hidden.

Question: What happens from trigger to outcome in real work today?

Decision: Establish a validated as-is map before selecting a control or redesign.

This method produces an evidence-backed current-state map that practitioners recognize as true.

Inputs​

  • A process boundary, start trigger, and stopping outcome.
  • Access to the people and agents that perform, receive, or inspect the work.
  • Real cases, artifacts, timestamps, system traces, observations, and known exceptions.
  • The approved governing standard or setpoint, recorded separately from observed practice; otherwise an explicit NONE APPROVED state.
  • An owner who can resolve disputed observations without converting the map into policy.

Map Reality​

  1. Set the boundary. Name the trigger, first included action, intended output, customer or receiver, and final included action. Output: a one-sentence scope.
  2. Follow real cases. Observe representative work and collect artifacts rather than reconstructing the process from memory. Output: an evidence trail for each sampled path.
  3. Record the flow. Capture actors and agents, inputs and outputs, actions, handoffs, decisions, queues, controls, and interfaces in the order observed. Output: the main path with responsible actors.
  4. Expose variation. Add rework, delays, workarounds, exceptions, escalation paths, and differences between documented, standardized, and observed practice. Do not rewrite the governing contract to match what happened. Output: alternate paths and visible practice-to-standard variance.
  5. Attach measures. Add observed volume, elapsed time, waiting time, error or rework signals, and other measures already supported by evidence. Mark unknowns instead of guessing. Output: a measured as-is map.
  6. Validate with practitioners. Walk the map from trigger to output with the people who do and receive the work. Resolve disagreements against evidence and record remaining unknowns. Output: a dated validation and named validators.

Do not simplify away a queue, exception, or local workaround merely because it should not exist. Mapping describes current truth; Process Modelling proposes a different future.

As-Is Map Output​

Boundary:
Governing standard or setpoint: APPROVED NAME | NONE APPROVED
Trigger:
Outcome and receiver:
Actors and agents:
Inputs and outputs:
Main sequence:
Handoffs and interfaces:
Decisions and rules observed:
Queues and delays:
Controls and evidence:
Observed departures from the governing standard:
Exceptions, rework, and workarounds:
Observed measures:
Unknowns:
Validated by / date:

Use the simplest notation the practitioners can review. A wall of notes, a table, or a flow diagram can be enough. The map is successful because it is evidence-backed and usable, not because it uses specialized software.

Checks​

  • Every step is inside the declared boundary and has an actor or unresolved owner.
  • Every handoff names what moves and who receives it.
  • Decisions show the observed rule, including inconsistent rules.
  • Queues, exceptions, and rework remain visible.
  • Measures distinguish observed values from unknowns or estimates.
  • The governing standard is named separately from observed controls; absence is explicit rather than replaced with a post-hoc target.
  • Practitioners can trace at least one real case through the map without inventing a missing step.

Failure Modes​

  • Procedure theatre: mapping the written procedure rather than observed work.
  • Happy-path map: omitting queues, exceptions, and recovery.
  • Premature design: rewriting the flow while evidence is still being gathered.
  • Ownerless handoff: drawing a connection without naming sender, receiver, and transferred output.
  • False precision: adding durations or failure rates that were not observed.

Proof Of Done​

A practitioner unfamiliar with the drawing can follow a real case from trigger to output, locate its decisions and delays, and identify which observations remain uncertain. The validators agree that the map represents current work rather than desired work.

Changes my mind: a new observation or trace shows that a material path, actor, control, or exception is missing or misrepresented.

Supplementary Demonstration​

This LeanOhio demonstration shows a practical facilitated mapping session. Use it to observe elicitation and group validation, not as a mandatory notation.

Source Trail​

  • ISO 9001 process approach — primary guidance for defining processes through inputs, outputs, interactions, responsibility, risks, controls, and evaluation.

Context​

  • depends-on Performance Reality — distinguish observed measures from desired targets.
  • depends-on Standards — keep the governing contract distinct from the reality being observed.
  • pairs-with Process Modelling — use the validated map as the starting constraint for intended design.
  • applies-to Work Charts — inspect how work and responsibility move between people and agents.
  • contrasts-with Business Process Reengineering — map what exists before deciding the structure must be replaced.

Questions​

Next question: Which observed constraint must the intended process preserve, remove, or test?

  • Which disputed step needs another observation before modelling begins?