Actual-vs-Documented Process Map¶
Artifact — instantiates Informal Structure Mapping
Places the official process and the observed process side by side in one artifact so mismatches and practical dependencies can be pointed at and discussed concretely.
Most arguments about "how the process really works" go nowhere because the two sides are picturing different things and neither can see the other's picture. Actual-vs-Documented Process Map is the artifact that ends that stalemate: a single two-lane diagram with the official procedure rendered in one lane and the observed procedure — reconstructed from real cases — rendered directly beside it, step aligned to step. Its defining move is deliberately narrow. It does not mine, judge, or decide; it renders. It puts the written model and the lived model in one frame so a mixed room can stop trading anecdotes and instead point at a specific divergence — the step that isn't in the manual, the approval that happens off-book, the handoff that everyone reorders under pressure — and talk about that concrete thing.
Example¶
A retail bank believes its mortgage-underwriting workflow is well documented: intake, automated credit pull, income verification, decision, funding. Loans keep slipping their close dates anyway. An analyst builds the actual-vs-documented map. In the official lane sits the five-step SOP. In the observed lane, reconstructed from a dozen real files, sits what actually happens: between "automated credit pull" and "income verification" there is an unwritten "senior underwriter pre-check" that catches thin-file cases before they enter the queue, and the documented single "decision" step is really two — a soft decision, then a compliance sign-off that a specific reviewer does by email, never in the loan system.
Laid side by side, the divergence is impossible to argue with. Nobody had to accuse anyone of anything; the map simply shows an extra step the SOP omits and an approval that lives outside the system of record. That picture — official on the left, real on the right, the gaps flagged between them — becomes the shared object the next conversation is about.
How it works¶
What distinguishes this from either lane on its own is the disciplined alignment of the two:
- Build the documented lane straight from the SOP, policy, or workflow diagram — the official sequence, verbatim, with nothing added.
- Build the observed lane from a handful of real case walkthroughs, tracing what actually happened in each rather than what should have.
- Align step to step, anchoring on shared milestones so the two lanes read across, and mark every divergence type explicitly: an inserted step, a skipped step, a reordering, or an out-of-band approval.
- Withhold judgment on the artifact itself — divergences are flagged, not labeled good or bad. The map's job is to make the gap legible; interpreting and disposing of it happen elsewhere.
Tuning parameters¶
- Swimlane granularity — activity-level or task-level detail. Finer detail exposes more real divergence but makes the artifact harder to read at a glance.
- Alignment anchor — align the lanes by process step or by handoff between roles. Handoff-anchored maps foreground coordination gaps; step-anchored maps foreground missing or reordered work.
- Number of case traces — one representative walkthrough or several. More traces reveal how much the "actual" path varies, at the cost of a busier picture.
- Divergence notation — how richly inserted / skipped / reordered / off-book steps are marked. Richer notation is more informative but risks looking like an indictment.
- Freshness — a dated snapshot or a periodically re-drawn artifact; a map is only as true as its last case sample.
When it helps, and when it misleads¶
Its strength is that it turns a vague dispute into a shared object. A room that cannot agree on "how underwriting works" can agree on a diagram where the extra pre-check step is right there in the observed lane, and that shared object is what every downstream mapping and repair move builds on. It is also politically light: it describes, it does not accuse.
Its central limitation is that a map is a simplification of a moving reality — the divergence between work-as-imagined and work-as-done is real and worth showing, but the observed lane is only ever a sample of it.[n1] Pick one "actual" path and you can hide the variation that is the whole point; freeze the artifact and it quietly rots as the real process drifts. The classic misuse is treating the drawn observed lane as the truth rather than a traced sample, and then defending the picture instead of the practice. The discipline that guards against this is to build the observed lane from several traces, date the artifact, and keep it explicitly a description to be interpreted — never a verdict.
How it implements the components¶
This artifact fills the representational core of the archetype — the two models it holds in one frame:
formal_structure_map— the documented lane is the official record: the SOP, policy, or workflow diagram rendered verbatim as the comparison baseline.actual_practice_trace— the observed lane is the reality reconstruction: what real cases actually did, traced beside the official version so the two read across.
It stops at rendering. It does not explain why the two lanes differ (formal_informal_gap_diagnosis) — that cause analysis is Shadow Process Audit — nor decide what to do about a divergence (formalization_or_repair_decision), which belongs to Workaround Review.
Related¶
- Instantiates: Informal Structure Mapping — supplies the side-by-side artifact that makes the formal/actual gap discussable.
- Consumes: Process Mining Review or Workflow Ethnography can supply the observed-process lane where the analyst does not trace cases by hand.
- Sibling mechanisms: Informal Leader Mapping · Organizational Network Analysis · Process Mining Review · Shadow Process Audit · Workaround Review · Workflow Ethnography · Communication Pattern Review
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: The mechanism places the official process and the observed process side by side in one artifact so mismatches and practical dependencies can be pointed at and discussed concretely, so its operative form is a static or prospective information artifact.
Independent corroboration: The frozen evidence defines Actual-vs-Documented Process Map as 'Places the official process and the observed process side by side in one artifact so mismatches and practical dependencies can be pointed at and discussed concretely', so its operative form is Representation, Specification & Plan.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: The explicit comparison of work-as-documented with work-as-actually-performed is a characteristic human-factors, resilience-engineering, and safety-investigation practice.
Related originating lineages:
- Accounting & Auditing — Control walkthroughs and tests of whether prescribed procedures operate in practice contribute the assurance use case.
- Ethnography & Qualitative Methods — Direct walkthroughs and attention to situated practice contribute the method for discovering work that procedure documents omit.
- Organizational & Management Science — Business-process mapping and operational improvement contribute the aligned lane-by-lane representation.
Review resolution: The defining operation is an engineering process comparison between observed and prescribed flows. Audit, ethnography, and organizational analysis supply evidence and interpretation, making the generalized page a cross-disciplinary synthesis with engineering primary.
Attribution caveat: The artifact resembles management process mapping, but its work-as-imagined versus work-as-done distinction has a particularly strong safety-engineering lineage.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The distinction between work-as-imagined (the process as designed and documented) and work-as-done (how it actually unfolds under real constraints), central to Erik Hollnagel's resilience-engineering / Safety-II writing. The artifact exists precisely to hold both in one view rather than letting the imagined version stand in for the done one. ↩