Handoff material should include approaches already tried and found unsuccessful
Aliases: failed-attempt record · negative knowledge · attempt history
What it is
Negative knowledge in handoffs records approaches that did not meet the goal, together with their conditions, observations, and stopping rationale. A handoff containing only the current solution makes excluded paths look unexplored and invites recipients to repeat experiments or reintroduce known risks.
Why it happens
Final artifacts preserve successful paths, while failed attempts remain in personal memory or scattered conversation. A recipient cannot distinguish never tried from failed under particular conditions. Capturing approach, context, evidence, and conclusion narrows the search space. A bare “does not work” label instead turns a contingent result into an apparent prohibition.
Studying it
Compare handoffs containing current state alone with those including failed attempts. Measure duplicated experiments, exploration coverage, solution time, and outcome quality. Code whether records include conditions and evidence, and test whether they wrongly suppress reasonable retries after circumstances change.
Where it stops holding
Not every minor probe warrants retention; exhaustive failure logs create search cost. Failure may be specific to an old version, dataset, or permission state, and cheap reversible approaches can reasonably be retried. Records should bound the evidence rather than elevate judgment into policy.
Applying it
- Capture the approach, test conditions, observations, stopping reason, and conditions for retry.
- Link failures to logs, prototypes, or data instead of conclusion labels alone.
- Select failed attempts by risk and repetition cost rather than listing every action.
- Ask recipients to reassess changed conditions and append evidence from any retry.
Related
Cards in the same group
- V4.05.1Asynchronous handoffs require written context because questions cannot be answered immediately
- V4.05.3Unrecorded tacit rationale is a major source of handoff loss
- 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