“The team is handling it” can sound reassuring while hiding an important question: who makes the next move?
A handoff example
Imagine a designer finishes a draft and marks the task “done.” The launch is still waiting because nobody has been asked to approve it. A better handoff names the reviewer, describes the decision needed and gives a date for the response. The designer’s work is complete; the project’s next move is now visible.
Write the outcome before the activity
“Prepare onboarding emails” describes work. “New customers receive a clear first-week sequence” describes the result. A short outcome statement helps the team decide which tasks matter and when the work is actually finished.
Assign one next-action owner
Several people may contribute, but one person should keep the next action moving. In a task detail, record the owner, the specific action and the due or review date. If the action depends on somebody else, make that dependency explicit rather than leaving it in chat.
Review at the handoff
At the next check-in, ask whether the decision happened, not whether everyone was busy. A short update may be enough; another meeting is not always necessary.
- Outcome: what will be true when this is done?
- Owner: who moves the next step?
- Review: when will the team know whether it moved?
Start with one stalled handoff and give it a clear owner today.