Unrecorded tacit rationale is a major source of handoff loss
Aliases: missing decision rationale · tacit knowledge loss · rationale gap
What it is
Tacit rationale loss occurs when a handoff transfers a conclusion but not the evidence, tradeoffs, or exceptions that produced it. The recipient knows what was selected but not why, or which changed conditions should trigger reconsideration, encouraging either rigid reuse or accidental violation of a key constraint.
Why it happens
Experienced practitioners compress cues into judgment and prioritize progress over articulating reasoning. Artifacts retain visible outcomes while tradeoffs remain in memory. After transfer, recipients infer intention from the result and may confuse hard constraints, preferences, and temporary compromises. The mismatch often appears only in a boundary case.
Studying it
Decision-reconstruction interviews can compare prior owners' and recipients' accounts of evidence, constraints, alternatives, and exceptions. Give recipients new edge cases and observe when they retain or revise the earlier choice. Retrospective accounts can rationalize after the fact, so triangulate them with contemporaneous artifacts and action traces.
Where it stops holding
Not all expert judgment can be fully verbalized, and demanding exhaustive justification creates burden and plausible-sounding retrospective stories. Low-consequence, reversible choices need only light records. Sensitive rationale may require abstraction or restricted access rather than permanent verbatim storage.
Applying it
- Attach goals, evidence, hard constraints, tradeoffs, and reconsideration triggers to consequential decisions.
- Separate facts, assumptions, preferences, and temporary compromises.
- Prioritize rationale capture for high-impact or hard-to-reverse choices.
- Test transfer with a new edge case and ask the recipient to justify retaining or changing the choice.
Related
Cards in the same group
- V4.05.1Asynchronous handoffs require written context because questions cannot be answered immediately
- V4.05.2Handoff material should include approaches already tried and found unsuccessful
- V4.05.4Handoff content should accumulate during work rather than be reconstructed at transfer time
- V4.05.5A handoff is complete only when the recipient confirms it through read-back