Soft Handoffs
Passing work between people without losing intent, context, or the original argument — the silent muscle of long-lived teams.
Most team friction shows up at the edge: a ticket moves from one desk to another and half the context evaporates. A soft handoff is a small block of text — three paragraphs, perhaps — that says what the work is, why it matters, and what it would look like if it succeeded.
It costs twenty minutes to write. It saves twenty hours of misalignment.
When to use it
- Cross-functional tickets, design-to-engineering transfers.
- Whenever a meeting ends with “I’ll send you a note.”
When to avoid it
- Tasks small enough to fit in a single conversation.
A template that holds
Three short paragraphs: what this is, why it matters, what success looks like. Not “what I did” — “what I’m asking you to do.” A soft handoff is forward-facing. It describes the destination, not the journey that got us here. The reader should be able to pick up the work without needing to ask the author a single clarifying question.