Pattern · Foundational
Invisible Handoff
Responsibility or information moves between people or teams without an explicit, observable acceptance event.
Brilliant QuestPublished 9 October 2026Updated 2026-10-09
Illustrative structure
Team A
Acceptance?
Team B
Common indicators include…
- “I thought they had it.”
- Email chasing and duplicate follow-up
- Work waiting unnoticed
- Status meetings used to discover status
Why it may happen
Sending is treated as equivalent to acceptance. Teams have locally reasonable definitions of “done”, but no shared event marks the transfer of responsibility.
What it can cost
Work can wait between queues while each team believes it has completed its part. Chasing and repeated status checks consume time without improving the underlying handoff.
Questions worth asking
- What observable event proves that responsibility has transferred?
- Who owns the item until the receiving team accepts it?
- What happens when a handoff is rejected or incomplete?
Possible interventions
- Define readiness criteria and an explicit acceptance event.
- Make pending and rejected handoffs observable.
- Assign ownership while work is between teams.
Verification required
This is an explanatory pattern, not a finding about your organisation. Establish whether it is present through a real example, records and the people involved; retain contradictory evidence.