Tool-Mismatch Postmortem¶
Retrospective review — instantiates Tool-Repertoire Bias Counterbalancing
After a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion.
A Tool-Mismatch Postmortem is a backward-looking review triggered by a specific failure in which the tool "succeeded" on its own terms while the underlying problem was not solved. Its defining move is retrospective outcome adjudication: it compares what actually happened against the original problem-first need — not against the tool's native metrics — to establish whether the failure was really a tool/problem mismatch rather than poor execution, and then converts that finding into a concrete change to the repertoire. It is the only mechanism in the archetype that runs after the fact and whose deliverable is a durable modification: a training update, a procurement request, an interface change, a new referral partner. It closes the loop the rest of the pattern opens.
Example¶
A precision-parts manufacturer keeps shipping a bracket that passes every inspection yet fails in the field. The quality tool — a coordinate-measuring machine — reports each unit in spec; by its own metric, quality is excellent. After the third field return, an engineer convenes a Tool-Mismatch Postmortem.
The review sets the tool's verdict beside the real need: "the bracket must survive vibration in the customer's assembly for its service life." The measuring machine grips dimensions superbly and dynamic fatigue not at all — it was never able to see the failure mode. The initial reflex on the floor had been "operator error, retrain the line," but the postmortem's outcome check shows execution was fine; the tool simply could not represent the property that mattered. That reframing is the payload. The finding routes into the repertoire: add a vibration-fatigue test to the qualification suite, update inspector training to flag fatigue-sensitive parts, and open a procurement request for the missing rig. The mismatch becomes a permanent capability, not a recurring surprise.
How it works¶
- Trigger on masked failure. The postmortem fires when a tool-native success coincides with a real-world failure — the signature of mismatch — rather than on every bad outcome.
- Adjudicate outcome against need. It reconstructs the case and compares the realized result to the original problem-first statement, explicitly distinguishing mismatch (the tool couldn't grip what mattered) from execution (the tool was fine, the doing was poor).
- Convert finding into repertoire change. A confirmed mismatch is not merely documented; it is routed into a specific, owned update — training, procurement, interface, partnership, or method — so the same gap cannot recur unaddressed.
Tuning parameters¶
- Trigger sensitivity — which failures convene a postmortem. Broad triggers catch more mismatches but tax the team; narrow triggers reserve the ritual for consequential cases and risk missing slow patterns.
- Attribution rigor — how hard the review works to separate mismatch from execution. High rigor prevents both scapegoating operators and excusing real errors; low rigor collapses into blame or hand-waving.
- Loop-closure strength — whether findings must land as owned, dated repertoire changes or may end as recommendations. Strong closure actually expands capability; weak closure produces reports that change nothing.
- Blamelessness — how firmly the review separates cause-finding from fault-finding. A blameless stance surfaces honest accounts; a punitive one drives the real mismatch underground.
When it helps, and when it misleads¶
Its strength is that it is the archetype's learning engine: it catches the most insidious failure — the tool that reports success while the problem festers — and turns it into a lasting change in what the organization can do. Done well it drives double-loop learning, altering the repertoire and assumptions rather than just retrying the same tool harder.[n1]
Its failure mode is the reflex it must fight: the pull to explain failure as poor execution rather than tool/problem mismatch, because blaming the operator is easier and threatens no cherished tool. A postmortem captured by that reflex retrains people to run a mismatched tool more diligently — entrenching the bias it was meant to break. It can also degrade into a report-generating ritual whose findings never close into change. The guarding discipline is to force the outcome comparison against the original need, to hold the mismatch-versus-execution distinction explicitly, and to require every confirmed mismatch to exit as an owned repertoire change.
How it implements the components¶
outcome_validity_check— its analytic core: adjudicating the realized outcome against the original problem-first need rather than the tool's native success metric, and distinguishing mismatch from execution.repertoire_refresh_loop— it converts each confirmed mismatch into a concrete, owned update to training, procurement, interfaces, or partnerships, closing the learning loop.
It diagnoses a past failure and pushes the resulting change, but it does not maintain the living catalog of tools those changes land in — that map is tool_repertoire_map, held by its nearest twin, the Tool Repertoire Inventory: the postmortem generates the reason to refresh, the inventory is the artifact that gets refreshed. It also does not keep the ongoing register of misfit cases (non_grippable_residual_register, the Residual Case Log).
Related¶
- Instantiates: Tool-Repertoire Bias Counterbalancing — supplies the after-the-fact learning that turns recurrent mismatch into repertoire change.
- Consumes: Residual Case Log supplies the recurring misfits that warrant a postmortem; Tool Repertoire Inventory receives the resulting updates.
- Sibling mechanisms: Tool Repertoire Inventory · Residual Case Log · Representation Fit Scorecard · Problem-First Intake Template · Affordance Blind-Spot Walkthrough · Alternative-Tool Red Team · Borrow-or-Refer Protocol · Favored-Tool Pause Rule
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Tool-Mismatch Postmortem operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it after a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion.
Independent corroboration: The frozen evidence defines Tool-Mismatch Postmortem as 'After a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Both independent reviews identify organizational management as the historical home of the operation—After a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion.. The retained alternates document formative adjacent traditions; the reach field, not the origin field, carries later applicability.
Related originating lineages:
- Education & Pedagogy — Education, assessment, and instructional practice supplies a parallel or contributing lineage for the mechanism's defining operation: after a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion.
- Engineering & Design — Engineering design, reliability, and systems-safety practice supplies a parallel or contributing lineage for the mechanism's defining operation: after a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: after a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion.
Review resolution: Both blind reviewers independently place the defining operation—After a tool-native success masks a real-world failure, reconstructs the mismatch and feeds it back into training, procurement, and repertoire expansion.—in organizational management. Their queued differences are secondary: alternate_origin_disagreement, origin_mode_disagreement. Reviewer A contributes no unique alternate; reviewer B contributes ['education_pedagogy', 'engineering_design']. I preserve the full evidence-supported union of 3 alternate domain(s), without a numeric cap. origin_mode=convergent reflects the reviewers' evidence about historical construction, while domain_reach=universal separately reflects present-day portability. The affirmative encyclopedia-synthesis finding is preserved, and confidence=medium uses the more conservative reviewer level.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
[n1] Double-loop learning — Chris Argyris's distinction between single-loop learning (correcting actions within existing assumptions) and double-loop learning (questioning the assumptions and frames themselves). A postmortem that changes the repertoire, not just the effort, is doing the double loop. ↩