When work in a small business stalls, it is almost never stalling in the middle of somebody doing the work. It is stalling in the cracks between people. The handoffs. Sales to delivery. Owner to manager. Team to client. Service person to admin. Week to week.
Handoffs are where work dies. And because they are the spaces between the things, they are also where most owners are not looking.
The shape of a handoff problem
A Santa Cruz owner tells me the intake is slow. We trace it. The actual conversation with the client takes 15 minutes. The form they fill out takes another 5. So far, 20 minutes.
Then comes the gap. The form lands in somebody's inbox. The person who processes it does not see it right away. When they do, they have questions for the client but they ping the salesperson instead, who is with another client. The salesperson responds 18 hours later. The processor asks the follow-up. The client answers in two days. By the time the intake is actually ready to move forward, five days have passed, and the work that was supposed to happen took 20 minutes.
The math is always like this. Work is fast. Handoffs are slow. The handoff stretched a 20-minute task into a week.
Why handoffs fail
A few specific ways they break.
Nobody owns the handoff. The salesperson thinks it is the operations person's job once the form is submitted. The operations person thinks the salesperson is supposed to set them up. The work sits while both assume the other is handling it.
The handoff is verbal or informal. Something was mentioned in passing, in a hallway, on Slack, inside a longer message. It never made it into a system. A week later, nobody remembers it.
The information transferred is incomplete. The handoff happens, but the receiving person does not have what they need to act. They have to go back for more context, which adds another handoff, which adds another delay.
The receiving person has no trigger. The work lands in their inbox, but their inbox has 200 other things. Nothing tells them "this is yours now, start the clock." It blends in and sits.
The Lean lens
Lean manufacturing has a concept here that is useful. Work-in-progress inventory, or WIP. Every piece of work sitting in a handoff waiting for the next person is inventory. Inventory costs money to hold. It ages. It gets lost. It hides problems.
The goal in Lean is to shrink WIP. Move pieces of work through the system faster by making handoffs smaller, clearer, and more reliable. The faster the handoff, the less WIP sits around getting stale.
In a small Santa Cruz business, you can usually spot the WIP by asking a simple question. Where in our process does work usually sit waiting for somebody. Almost always, those are handoffs that are not working.
What a good handoff looks like
A handoff is basically a promise being made between two parts of the operation. The promise includes four things.
Who is handing off and who is receiving. By name. Not "someone on ops."
What is being handed off. A specific piece of information or work product, complete and ready to be acted on.
What the receiving person is expected to do next. "Book the intake call" or "produce the proposal draft" or "respond to the client with next steps."
When. The expected timeline for the next step.
If a handoff has those four, it works. If any of them is missing, it breaks about a third of the time, and over a year that adds up to a lot of stalled work.
Where to start
Pick the one handoff that causes the most friction in your business. For most owners I work with, it is one of three.
Sales to delivery. The moment a client or customer commits and the real work begins. If this handoff is fuzzy, onboarding is always rough, and the client's first impression of the delivery team is confused.
Owner to team. The moment you assign something to somebody else. If this is fuzzy, things do not get done, or they get done in a way that surprises you, and you keep reclaiming the work because it is easier than fixing the handoff.
End of day to start of next day. Especially in service businesses with shifts. The handoff from Thursday's team to Friday's team. If this is fuzzy, small issues carry over into bigger ones, and nobody feels like they can start fresh.
Pick one. Write out what a clean handoff in that spot would actually look like. Four lines. Who, what, next action, when. Put it into a simple shared tool or form. Try it for two weeks.
The common mistake
The most common mistake is relying on memory and goodwill across handoffs. "We all just communicate well." This works until the day somebody is out, somebody is tired, or the volume goes up. Then the informal system breaks and nobody knows why Friday got messy.
The fix is not to add bureaucracy. It is to add the minimum structure that makes each handoff unambiguous. A template, a field in your project tool, a specific channel for a specific kind of work. Small design. Big payoff.
Monday action
Walk one recurring piece of work from start to finish in your head. A client from first inquiry to first invoice paid. For each transition between one person or stage and another, ask: Is this clean.
Find the sloppiest one. That is where you start.
Write the four-line clean handoff for that transition. Talk to the two people involved. Agree on it. Run it for two weeks.
If you want help mapping the handoffs in your business and finding the ones quietly bleeding time, a Flow Check is a two-week diagnostic that often starts exactly here. You come out with a clear map of where work is waiting and which one fix will loosen the whole system.