PHASE 02
WORK BREAKS BETWEEN
PEOPLE, NOT INSIDE STEPS.
When you look at a completed process map, the delay is almost never inside the boxes. It is in the arrows between them, and the arrows are the part nobody designed.
The gap is the failure point
People are generally good at the work they were hired to do. An acquisitions person is good at a seller conversation. A project manager is good at running a job. Failures inside a step are usually skill or capacity problems, and they are visible, so they get addressed.
Failures between steps are different. They are nobody's job by definition, which is precisely why they persist.
The pattern is always the same. Person A finishes and believes they are done. Person B is unaware anything is waiting, or is aware and believes A is still working on it, or received it and does not consider it complete enough to start. The work sits. Neither person is failing at their job. The gap belongs to no one, so no one is watching it.
Ask your team where things get stuck and they will name the gaps immediately. I never know when it is ready for me. I have to go ask whether they finished. I get it and half the information is missing so I have to go back. Everyone knows. Nobody owns it.
Define done
Most handoff failures collapse into one root cause: done means something different to each person, and nobody ever wrote it down.
A lead is qualified. What does that mean. To the person who took the call it might mean the seller sounds motivated. To the person who has to make an offer it means motivation, timeline, condition, who else must sign, mortgage status and a reachable phone number. When those two definitions differ, work bounces back and forth, and each bounce costs a day and some goodwill.
The fix is unglamorous and durable. For each stage, write down what must be true before it moves. Specific, checkable, no adjectives.
Bad: the lead is properly qualified. Good: reason for selling captured, timeline captured, condition notes recorded, all decision-makers identified, mortgage status noted, best contact number confirmed. That second version can be checked by someone other than its author, which is the entire test.
The rest of the material, including Ben's published resources, lives on the main site.
One owner per stage
Every stage has exactly one name on it. Not a department, not a pair, not whoever is available.
Shared ownership sounds collaborative and behaves like no ownership. Two people responsible for follow-up means each of them assumes, reasonably, that the other one has the ones they did not touch. This is not a character flaw. It is what any sensible person concludes when responsibility is ambiguous and everyone is busy.
One owner does not mean one person does all the work. It means one person is accountable for the work moving, and that when it stops, there is no question whose phone rings.
Write it down somewhere everyone can see. If you cannot name the owner of every stage in your main process from memory, neither can your team, and that ambiguity is currently costing you work.
Make the handoff itself an event
The third ingredient. Even with a definition of done and a named owner, work sits if the next person does not know it is their turn.
A handoff needs to be a thing that happens, not a state someone eventually notices. In practice that means one of three arrangements.
A push
Completing the step notifies the next owner directly. Best for anything time-sensitive, and the most common thing automation gets used for.
A shared queue
Work lands in one visible place the next owner checks on a known rhythm. Works when volume is steady and the rhythm is genuinely kept.
A standing moment
A short daily or weekly point where work is passed explicitly. Lowest tech, and it works, provided it actually happens every time.
What does not work is a stage change in a system nobody watches, or a convention that the next person will see it. Those are hopes with a process diagram drawn around them.
Escalation and the owner as bottleneck
One handoff deserves separate treatment, because in most small businesses it is the largest single source of waiting: the handoff to you.
If your map shows work stopping repeatedly at an approval or an answer only you can give, the constraint is not your team's capability. It is that decision rights were never defined, so everything comes to you by default.
Two things fix most of it. Write down what each role decides without asking — with real thresholds, not vague authority. And write down what genuinely must escalate, which is usually a much shorter list than current practice implies.
Then hold the line. The hard part is not the document. It is that when somebody brings you a decision that is inside their authority, you have to hand it back, every time, including the week you are busy and it would be faster to just answer.
Frequently asked
Questions people actually ask
How do I know where my handoff problems are?
The process map shows them as waits, and your team can name them in under a minute if you ask what they are usually waiting on. The two sources almost always agree.
What if two people genuinely share a stage?
Then split the stage or assign the ownership by a clear rule — territory, alternating days, source. Ambiguous shared ownership is the specific condition that drops work, and any explicit rule beats it.
Is a checklist really the answer?
For definition of done, largely yes, and the reason is that it can be verified by someone who did not do the work. The sophistication people reach for instead usually adds interface without adding clarity.
How detailed should a definition of done be?
Detailed enough that a new hire could check it without judgment calls. If the criteria need interpretation, they will be interpreted differently, which puts you back where you started.
My team resists this as bureaucracy. What do I say?
Frame it the way they already experience it. This is so you stop having to chase people for information you need, and so nobody gets blamed for a thing that was never theirs. The people doing the work usually feel the pain of ambiguity more than the owner does.
Make your next move
A year from now, what will you be glad you started today?
You don't need another promise that everything will be easy. You need something useful to learn — and a next step you're willing to take.