Why handoffs, not tasks, are where work actually breaks
Ask most operations leaders where their process is slow, and they'll point to a task: a form that takes too long to fill in, a report that takes a day to generate, an approval that requires too many clicks. Tasks are visible. They have an owner, a start, and an end. It's natural to look there first.
But when we trace actual work across the tools a team uses — the moment a deal moves from Sales to Onboarding, or a ticket moves from Support to Engineering — the time lost rarely lives inside a task. It lives in the gap between two tasks, where nobody is officially responsible for the clock.
The handoff is nobody's job
A task has an owner by definition: someone is doing it. A handoff, by contrast, is the moment one owner stops and another hasn't started yet. In well-instrumented teams we've worked with, this gap regularly accounts for more elapsed time than every task in the process combined.
In one case we traced, a ticket spent eleven minutes total being actively worked on, and four days sitting at a single handoff waiting for someone to notice it had arrived.
That's not a rare outlier. It's close to the median pattern we see when a team measures handoffs for the first time.
Why this is so easy to miss
Handoffs are invisible for a structural reason: they usually cross a tool boundary. The sending team's tool shows the case as "done" the moment they hand it off. The receiving team's tool doesn't show it at all until someone opens it. The gap in between exists in neither system's reporting — it only becomes visible when you stitch the two timelines together.
This is also why fixing individual tasks so often disappoints. A team spends a quarter shaving twenty minutes off a report-generation step, only to find total cycle time barely moves — because the four-day handoff gap next to it was never touched.
What to measure instead
Instead of starting with "which task is slow", start with "which handoff has the largest gap between when work leaves one team and lands with the next". That reframing alone tends to point operations teams at a different, and more fixable, set of problems — often a notification that doesn't fire, a queue nobody is assigned to monitor, or a manual step that only one person on a team knows how to do.
We built Adesion around this idea specifically: not to add another dashboard of task-level metrics, but to make the handoffs themselves visible, so teams stop optimising the part of the process that was never actually the problem.