Procedure-Work Mismatch¶
Core Idea¶
A system's prescribed model of how work happens — procedures, checklists, regulations — diverges systematically from how work is actually done, and because the gap is often load-bearing for performance, the question is how it is managed, not whether it can be eliminated.
How would you explain it like I'm…
Grandma's Real Recipe
The recipe says cook for ten minutes, but Grandma knows the real oven runs hot, so she takes the cookies out early and they come out perfect. The written rule and what you really have to do aren't quite the same. People who do the job every day quietly fix the gap so things still work.
Rules Versus Real Work
Procedure-Work Mismatch is when the official instructions for a job — the rules, checklists, and step-by-step guides — don't match how the job actually gets done in real life. The instructions imagine perfect tools, perfect inputs, and no surprises, but real work has broken equipment, weird cases, and time pressure. The people doing the job fill the gap using know-how that isn't written down anywhere. Often nobody is to blame — the rules just fall behind as tools and demands change. The surprising part is the gap is usually helpful: many systems only work because workers quietly bridge it, which is why 'working strictly to rule' on purpose actually slows everything down.
Work-as-Imagined vs. Work-as-Done
Procedure-Work Mismatch is the structural pattern in which a system's prescribed model of how work happens — formal procedures, regulations, checklists, runbooks, role definitions — diverges systematically from how the work is actually performed under real conditions. The prescription describes a clean, deterministic workflow against an idealized set of constraints; the enactment confronts variable inputs, unreliable equipment, time pressure, exceptional cases, and the unwritten know-how operators developed precisely because the prescription doesn't survive contact with reality. The signature commitment is a layered representation: there's the work, and there's a separate authoritative description of the work that the institution has invested with control authority, and the two slowly drift apart. Crucially the divergence is usually nobody's fault — procedures lag changes in equipment and demand while workers patch the gap informally. And the gap is usually load-bearing: many systems work because operators silently bridge it, so suppressing the informal adaptation without fixing the procedure degrades performance, which is exactly what a 'work-to-rule' slowdown demonstrates.
Procedure-Work Mismatch is the structural pattern in which a system's prescribed model of how work happens — formal procedures, standard operating procedures, regulations, checklists, runbooks, role definitions — diverges systematically from how work is actually performed under real conditions. The prescription describes a clean, deterministic workflow against an idealized constraint set; the enactment confronts variable inputs, unreliable equipment, time pressure, exceptional cases, and the unwritten know-how operators have developed precisely because the prescription does not survive contact with reality. Hollnagel's 'work-as-imagined versus work-as-done' is the canonical articulation, but the pattern recurs whenever a system uses an explicit normative artefact to govern a class of work and that artefact is built at a different granularity than the work itself. The signature commitment is layered representation: there is the work, and there is a separate, authoritative description of the work that the institution has invested with control authority, and the two slowly diverge. The divergence is not necessarily anyone's fault — procedures lag changes in equipment, inputs, regulation, and demand; workers patch the gap through informal adaptation; the institution keeps auditing, training, certifying, and litigating against the formal model, so the two views coexist for a long time, often without trouble, until an incident, audit, or workforce change exposes the gap. A subtle structural fact is that the gap is usually load-bearing: many systems work because operators silently bridge the prescription-enactment gap, so suppressing the informal adaptation without fixing the procedure typically degrades performance — the work-to-rule slowdown is precisely the experiment of removing the gap-bridging adaptation. The mismatch is therefore not simply a defect but a feature of how layered normative systems function, and the question is how it is managed, not whether it can be eliminated.
Broad Use¶
- Aviation and nuclear: Checklists confront edge cases the writers never anticipated; "what the book says vs. what we do" is institutionally recognized.
- Medicine: Clinical guidelines and surgical timeouts confront nursing workarounds and clinicians' adaptation of electronic workflows.
- Finance operations: Settlement and compliance procedures are where most operational-risk events originate.
- Software and DevOps: Runbooks are why engineers say "the docs are always lying"; blameless postmortems surface enacted reality.
- Public administration: Case-handling procedures confront how caseworkers actually triage — "street-level bureaucracy."
- Law: Written law confronts customary practice; administrative law codifies the gap after the fact.
Clarity¶
Separates is the procedure right? from is the work right?, so an incident can be placed in the right cell rather than collapsing to "people aren't following the rules."
Manages Complexity¶
Compresses safety, compliance, and operational-risk events to one frame: identify the prescription, the enacted practice, and whether the gap is harmless adaptation, latent risk, or active failure.
Abstract Reasoning¶
A large load-bearing gap yields a brittleness signature — excellent routine performance, concealed fragility to anything that disrupts the informal layer: rapid onboarding, work-to-rule, or literal automation.
Knowledge Transfer¶
- Aviation → medicine: Crew Resource Management transferred from cockpit incidents to operating-theatre teamwork and ICU rounding.
- Nuclear → software: Operating-experience programs are the ancestor of blameless postmortems and shared incident databases.
- Street-level bureaucracy → system design: "How much discretion to leave" becomes a design parameter for caseworker decision-support.
Example¶
A barcode-scan medication workflow is bypassed by nurses batch-scanning at the cart under a full ward; the ward runs on time only because they bridge the gap, and a strict scanner lockout collapses throughput while delivering none of the safety the documented path promised.
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Procedure-Work Mismatch is a kind of Formal vs. Informal Structures — Procedure-work mismatch (work-as-imagined vs work-as-done) is the official-vs-actual divergence specialized to a prescriptive work artefact and its enacted practice, with the gap often load-bearing. is-a the formal/informal-structures distinction applied to procedures. Clean fit.
Path to root: Procedure-Work Mismatch → Formal vs. Informal Structures → Formalization → Transformation
Not to Be Confused With¶
- Procedure-Work Mismatch is not Impedance Mismatch because the mismatch is a representational divergence often load-bearing, whereas impedance mismatch is pure transfer-efficiency loss to be eliminated.
- Procedure-Work Mismatch is not Normalization of Deviance because the mismatch is broad and morally neutral, whereas normalization of deviance is the specific harmful drift of acceptable practice toward unsafe.
- Procedure-Work Mismatch is not Implicit Knowledge because the mismatch is the structural gap that tacit knowledge bridges, whereas implicit knowledge is the know-how itself.