A handoff must transfer context, not just an object
Aliases: handoff context · handoff communication · context transfer
What it is
A contextual handoff transfers not only files, tickets, or objects but also current goal, known constraints, attempted options, unresolved judgment, and the reason for the next step. A recipient needs more than what they received; they need why it is in its present state.
Why it happens
Objects preserve results, while critical judgment often lives in memory, temporary discussion, and failed attempts. Object-only transfer makes the recipient repeat exploration, revive excluded options, or reverse a decision without risk knowledge. Structured context restores common ground, though unprioritised volume transfers reading burden.
Studying it
- Paradigms: have recipients continue the same task from object-only versus contextual packages.
- Variables: goal, constraints, failed options, open issues, reconstruction time, questions, and recovery quality.
- Methodological caution: longer documentation is not necessarily effective; test recipient explanation of next step and risk.
Where it stops holding
Emergency handoffs cannot document all history, so prioritise risk, current state, and contact. Sensitive material must be minimised by access, not spread through handoff.
Applying it
- Use a stable skeleton: goal, state, tried/untried, rationale, risk, next step, and contact.
- Accumulate it during work and ask the recipient to restate gaps.
- Link evidence and discussion to the object.
- Verification: sample repeated failed attempts and first questions after transfer; recurrence shows missing context.