You've sacked this person three times. The problem keeps coming back.

So you let them go. Hired someone better. Trained them properly this time.

Six months later. Same problems. Different name on the desk.

You do it again. Tighter process. Better handover notes. Clearer expectations. The new person is sharp, experienced, comes recommended.

Four months in. Jobs going out wrong. Clients not called back. Paperwork late.

At some point you start wondering if it's you. If your expectations are unreasonable. If there's something about this role that just attracts the wrong people.

It's not you. It's not them. It's the gap between them and the person before them in the chain. And the person after them. And the system they're all trying to work inside.

The problem that wears a name tag

When something goes wrong, the first question is always "who." Who dropped it. Who didn't follow up. Who forgot.

It's natural. Find the person, fix the person, move on. If the person can't be fixed, replace them.

But some problems don't live inside a person. They live between people. In the space where one person's work ends and another's begins. In the translation from one system to another. In the moment where context evaporates because it was never written down, never attached to the job, never passed along in a way the next person could use.

That's a Broken Handoff. One of the most expensive frictions in any business, because it gets misdiagnosed every time. You think you've got a people problem. You've got a process problem. You replace the person. The process stays broken. The problem comes back wearing a new name tag.

The Handoff Trace

Here's a diagnostic you can run on any job, order, or project that recently went wrong. Fifteen minutes, a piece of paper, and the willingness to be honest about what you find.

Step 1. Pick one thing that went wrong recently. A job that was late. An order with the wrong spec. A client who got incorrect information. Something specific and recent enough that people remember the details.

Step 2. Trace it from the very beginning. Who started it? A client call, a quote request, a purchase order? Start there and follow it through every person who touched it.

Map it as a chain:

Step 1: [Who] did [what] using [what system/format]
   ↓
Step 2: [Who] received it as [what format] and did [what]
   ↓
Step 3: [Who] received it as [what format] and did [what]
   ↓
Step 4: [Who] received it as [what format] and did [what]
   ↓
(continue until the job was complete or the mistake happened)

Step 3. At each transition, where the work moved from one person to the next, ask three questions:

1. Did information change format? Verbal to written. Email to spreadsheet. Handwritten note to typed entry. One system to another.
2. Did anyone re-enter data that already existed somewhere? Same client details, job specs, or quantities typed into a different system.
3. Did someone have to ask "what's the status?" or "what did they mean by this?" Any moment where context was missing and someone had to chase it down.

Step 4. Count three things:

• Transitions: How many times did the work move from one person to another?
• Format changes: How many times did information change shape?
• "I didn't know" moments: How many times was someone missing context they needed?

Step 5. Write up your results:

Job/Project: _______________
What went wrong: _______________

The chain:
  Step 1: _______________
  Step 2: _______________
  Step 3: _______________
  Step 4: _______________
  (add more as needed)

Total transitions:          ___
Total format changes:       ___
Total "I didn't know" moments: ___

Where it actually broke: Between Step ___ and Step ___

Each transition is a failure point. Each format change is a place where information degrades. Each "I didn't know" moment is a gap where context leaked out.

What the trace reveals

Think of it like photocopying a photocopy. First copy is fine. Second is slightly fuzzy. By the fifth, you're squinting.

That's what happens to job information as it moves through hands and systems.

A client says "I need it by the 15th, same spec as last time." That goes into an email. The email gets summarised on a job card. The job card goes to the workshop. The workshop sees "same as last time" and interprets it based on what they remember. Which might not be what the client remembers.

Three transitions. Two format changes. One "I didn't know" moment waiting to happen.

The mistake shows up at step five. But it started at step two, where the context began leaking.

Why replacing the person never works

The coordinator you sacked wasn't bad at their job. They were sitting at the point in the chain where information was thinnest.

They had to take a half-complete email, a verbal instruction from the boss, and a scribbled note from a client meeting. Turn all of that into a job the workshop could execute perfectly. When they got it right, nobody noticed. When they got it wrong, everyone noticed. And it always looked like their fault, because their name was on the job card.

But the real failure happened upstream. In the meeting where nobody took proper notes. In the quoting system that doesn't connect to the job system. In the assumption that "they'll know what I mean."

You replaced the person standing in the gap. The gap didn't move.

The pattern hiding in your operation

Think about how work flows through your business.

A quote becomes a job. A job becomes a schedule. A schedule becomes a delivery. A delivery becomes an invoice. An invoice becomes a payment.

At every one of those transitions, information has to survive the move from one person, one system, one format to the next. At every transition, something can get lost, changed, or misunderstood.

The businesses that run smoothly aren't the ones with the best people. They're the ones with the fewest transitions. Or the ones where transitions are clean. Information flows in one format, through connected systems, with context attached.

The businesses that feel chaotic. Where the same mistakes keep happening. Where you keep blaming people but the problems persist. Those are the ones with too many transitions, too many format changes, and too many gaps where context disappears.

The person was never the problem

I spent seven years inside a 400-person regional business. Every time there was a recurring failure, the first instinct was the same. Find the person. Fix the person. Replace the person.

And every time, the same problems came back. Because nobody traced the handoff. Nobody counted the transitions. Nobody asked "where did the information actually degrade?"

Once you trace it, you can't unsee it. The break is obvious. Sitting in the gap between step two and step three, where a phone call became a sticky note, where a sticky note became a misremembered instruction, where a misremembered instruction became a wrong delivery.

The person at the end of that chain didn't fail. The chain failed.

Follow the trace

Run the Handoff Trace on one thing that went wrong last month. Just one.

Count the transitions. Count the format changes. Count the "I didn't know" moments. You'll find the break point. And it won't be where you expected.

Found something? Most owners do. The Handoff Trace covers one dimension. The Clarity Conversation covers all six. Four hours, $2,000, and you walk away with a scored friction map, the cascade, and a clear picture of what to fix first.