Organization Design

Process Design and Where the Handoffs Leak

Find where a repeating process actually loses time and quality — which is almost never inside the steps and almost always at the boundaries between them — and fix it with a map you can build in a day rather than a transformation programme.

  • Intermediate
  • 12 min total
  • 13 chapters

What decision this helps you make: Which handoffs to remove, which waits to attack, and whether the right move is to redesign the process, automate it, or simply give one person end-to-end ownership of it.

What this topic is

A process is a repeating sequence of steps that turns a request into a finished outcome — a customer onboarded, an invoice paid, a candidate hired, an incident resolved. A handoff is the moment the work passes from one person or team to the next. Process design is the practice of deciding what the steps are, who does them, and how many boundaries the work has to cross on its way through. The core finding, which is close to universal, is that the time and the quality are lost at the boundaries rather than inside the steps.

Why it matters

A process runs hundreds or thousands of times a year, so every defect in it is paid repeatedly and compounds. Yet nearly all improvement effort goes into making individual steps faster, which is where almost none of the elapsed time sits. Measure a typical business process end to end and you will usually find that the work itself accounts for a small single-digit percentage of the calendar time, and everything else is the work sitting somewhere waiting for a person who does not know it has arrived.

Who should learn it

Any manager who owns something that repeats — onboarding, order-to-cash, hiring, support escalation, claims, procurement — and anyone who has been asked to make one of those things faster without adding people.

What you will understand

  • The three things that leak at every handoff, and which one is usually the largest
  • Flow efficiency: how to compare touch time against elapsed time in an afternoon
  • Why first-pass quality compounds across steps, and what that does to a five-step process
  • When to remove a handoff, when to automate it, and when to give one person the whole thing

Prerequisites

Common misconception

"Our process is slow because the teams involved are under-resourced, so we need more people in the slowest step." Measure it and the slowest step is usually not slow. Take a process that takes eleven working days end to end: the actual hands-on work often adds up to a few hours, and the remaining time is queueing — the request sitting in an inbox, a shared queue, or a status of "awaiting review" while the person who will do it is busy with something else. Adding people to a step reduces the time that step takes and leaves untouched the ninety-plus percent of elapsed time that was never work at all. That is why so many resourcing fixes deliver a process that is measurably faster inside and takes the same eleven days.