Ask anyone why a request took three weeks and you rarely hear that the work itself was hard. You hear that it was waiting: for a signature, for finance to look at it, for someone to notice it had arrived. The work is quick. The handoffs are slow.
That gap is where most process delays live, and it is almost invisible. Each person does their part reasonably fast, yet the whole process crawls, because nobody owns the space between the steps.
Why handoffs fail
- Nobody knows where the work is. A request sits in someone’s inbox and everyone else assumes it is moving.
- Ownership is vague. "Finance will approve it" is not the same as "Ada in finance owns this stage".
- There is no expected time. Without a target, a stage that should take a day quietly takes a week.
- The next person is not told. Work finishes, but nobody tells the next owner it is their turn.
- Parallel work is serialised. Steps that could happen at the same time wait in a line out of habit.
A practical fix in five steps
- Map the stages once. Write down every stage the process passes through, in order. Do it once, properly, instead of re-explaining it each time.
- Give every stage a single owner. A named person or a named department, never "the team". Ownership is what makes a stage move.
- Set a target time per stage. Even a rough target turns a vague delay into a visible one. A stage that is overdue becomes a conversation, not a mystery.
- Make the handoff automatic. When a stage is signed off, the next owner should know immediately, without anyone forwarding an email.
- Let stages run in parallel. If legal and IT do not depend on each other, let them work at the same time and rejoin when both are done.
Make it visible to everyone
The single biggest improvement is visibility. When anyone involved can see where a process is right now, who has it and how long it has been there, the chasing stops. People stop asking "any update?" because the answer is on screen.
Where to start
Pick the one process people complain about most, usually onboarding, approvals or purchasing. Map its stages, name the owners, set rough targets, and track the next five runs. The bottleneck will show itself within a week.