The Handoff Problem

Most solo operators obsess over the tasks in their business. They document what needs to be done, they optimise how it gets done, and they measure whether it got done.

None of that matters if the handoff is broken.

Here's a concept I picked up from Sam Corcos (CEO of Levels) in his interview with Tim Ferriss, and it changed how I think about process performance: if you complete a task but don't communicate that it's done, you haven't completed the task.

Think about that for a second. You've done the work. The deliverable exists. But the next person in the chain doesn't know it's ready. So they wait. Or they chase. Or they assume it's not done and work around it. The process stalls — not because anyone failed at their job, but because the handoff between jobs didn't happen.

Corcos doesn't treat communication as a separate KPI in his business. It's not a line item on a position description. It's embedded into how every task is performed. The task isn't done until the next person knows it's done and has what they need to pick it up.

You might be thinking this is a team management problem. It isn't — or at least, it's not exclusively one.

If you're a solo operator, you're still working within processes that involve other people. Suppliers, clients, contractors, partners. Every one of those relationships has handoff points, and every one of those handoff points is a place where time gets wasted.

Here's a real example. I've been working with a marketer, and part of his process requires me to complete a foundations document before he can build a strategy for ads and content. I finished the document. But if I don't tell him it's done, he's stuck. He either waits or follows up, and either way, the process slows down — not because of his capacity or mine, but because of a communication gap between two completed actions.

Now multiply that across every stakeholder interaction in your business. The cumulative drag on your cycle time is significant.

Listen to the podcast episode for this newsletter issue here: The Handoff Problem: Why Work Falls Through the Cracks | Lone Wolf Unleashed

When you tighten up handoffs, you reduce cycle time. That's not a productivity hack — it's a structural improvement. The same work gets done in less time, which means you're freed up sooner, and in delivery processes, your cashflow improves because the gap between doing the work and getting paid for it shrinks.

One of my clients runs a claims advocacy business. As he's been documenting his processes, he's realised he can now communicate to his clients — with precision — exactly what they need to do and when they need to do it. That's not just good service. It speeds up his side of the process too, because he's not waiting on incomplete or late information. Both parties win.

When you document your processes (and if you haven't, that's step one), don't just map the tasks. Map the handoffs. For each transition between tasks — especially where another person is involved — ask:

Who needs to know this task is complete?

What do they need from me to start their part?

How will I communicate it — and is that the fastest, clearest channel available?

When is the expectation set — do they know upfront how and when I'll hand off to them?

That last point is easy to overlook. Setting the expectation at the start of a working relationship about how handoffs will happen saves an enormous amount of friction later. It's the difference between a supplier who chases you three times and one who knows exactly when and where to look for what they need.

Bringing someone into your business only saves time if the communication overhead of managing them is less than the time you were spending on those tasks yourself. If you haven't built clear handoff protocols into your processes before you hire, you'll end up in daily standups, constant check-ins, and the slow erosion of trust — not because your new hire is underperforming, but because neither of you has a shared understanding of how work moves between you.

Build the communication channels before you need them. Make handoff expectations part of how people work, not something bolted on after things start falling through the cracks.

This also applies in reverse. If your suppliers or clients aren't communicating handoffs back to you, that's costing you time. It's worth having a direct conversation about it. Not every process improvement requires a new tool or a redesigned workflow — sometimes it's just saying, "Here's how I'd like us to handle handoffs, and here's what I'll commit to on my end."

Communication isn't a soft skill that sits alongside the work. It is the work. And the sooner it's treated that way, the sooner your processes stop bleeding time at every junction.

Enjoy this post, refer new subscribers and get the Time Flux Method - what I use to help people save 2+ hours a day.