Why Work Gets Stuck in Your Business (The 5 Handoffs to Check First)
Why does work get stuck in your business?
Work gets stuck at the moment it changes hands. Most of the delay in a small business sits in the gaps between people: the hours and days where a task is finished by one person and hasn't yet been picked up by the next. Five of those gaps appear in almost every business, and you can check all five this afternoon.
Who is this for?
You run a business that already sells. There are two or three people around you: a virtual assistant, a contractor, maybe someone part-time on delivery or on calls. Money comes in every month. Nothing is on fire.
And still, things take a strange amount of time. A client asks where their thing is and you have to go looking. You open a thread from nine days ago and find your own message sitting at the bottom of it, unanswered, with three people each waiting on one of the others. This article is for that week.
Key takeaways
- Work stalls between people far more often than inside a task.
- A handoff holds together when it has three parts: a named owner on each side, a trigger that starts it, and an agreed definition of "done".
- The founder's inbox is the most expensive handoff point in most small businesses, because everything queues behind one person's attention.
- You can find your slowest handoff in about twenty minutes, using three deliverables that ran late.
- Automation makes a clean handoff faster and a vague handoff messier.
- Fix the handoff before you change the tool. A tool records a decision that already exists.
- Five handoffs cover most of it: sale to delivery, decision to action, person to person, work to client, person to tool.
Table of contents
- What does a handoff actually look like?
- The 5 handoffs where work gets stuck
- How do you find which handoff is failing?
- What does the research say about handoff delays?
- What should you fix first, once you've found it?
- Where does AI belong in a handoff?
- Frequently asked questions
- Recommended tools and resources
- Where to explore next
- Final summary
What does a handoff actually look like?
A handoff is the moment work stops belonging to one person and starts belonging to another. A closed call becomes an onboarding. An approved draft becomes a scheduled post. A supplier's quote becomes a purchase order.
Three things have to be true for that moment to hold. Someone is named on each side. Something triggers it, a status change, a file landing in a folder, a message in one agreed place. And both people use the same definition of finished.
Take one away and the work still moves, most of the time, because somebody chases it. That chasing is the cost. It rarely appears in any report, and it's the reason a five-person business can feel busier than a twenty-person one.
Flavie spent 17 years inside businesses before House of Her, and that's where this way of looking comes from: a decision never lived in isolation. A system affected a process. A process affected a team. A team affected the customer. When something stalls, the cause is almost never sitting where the complaint is.
The 5 handoffs where work gets stuck
Step 1: Sale to delivery
What you promised on a call lives in that call. The client remembers one version, you remember another, and the person who has to deliver it wasn't there.
Here's the difference in practice. The vague version: "Great, we'll get started next week." The written version: one paragraph, sent to the client and to whoever delivers, naming what gets built, what's excluded, and the first date something is due. Same conversation, five extra minutes, and the delivery person stops guessing.
Step 2: Decision to action
Work sits because one person has to approve it, and that person is you. Nobody is blocked by difficulty here. They're blocked by permission.
This is the handoff that quietly sets the size of your business. Every task that needs your yes joins the same queue, and that queue moves at the speed of your worst day. Writing down which decisions actually need you is usually the single highest-value hour available to a founder.
Step 3: Person to person
Two people, one shared inbox, and no rule about who answers what.
A founder of a small B2B company showed Flavie her inbox in a session in April 2026. Purchase orders had been missed. Suppliers were waiting on replies nobody had sent. Invoices had gone missing inside the thread. Two people, both working hard, both assuming the other had it. The fix started by splitting the inbox into three named jobs, sales, purchasing and finance, each with an owner.
Step 4: Work to client
The work is finished and the client doesn't know. It sits in a folder, or in a draft, or in someone's "I'll send it tonight".
This one is easy to miss because internally the task looks done. From the client's side, nothing has happened. Delivery isn't complete until it has been returned, received and confirmed, and that last step needs a name on it like any other.
Step 5: Person to tool
You automated something. It runs. Nobody reads what it produces.
A form fills a spreadsheet nobody opens. A reminder fires into a channel nobody watches. An assistant drafts replies that sit unsent. The automation is working exactly as built, and the handoff on the far side of it was never designed. Every automation creates a new handoff, from the machine back to a human, and that one needs an owner too.
How do you find which handoff is failing?
Do this now, it takes about twenty minutes and needs no tool.
Pick the last three things that went out late. Take them in the order they happened, so you don't unconsciously pick a story. For each one, write the date it was promised and the date it actually landed.
Now fill the gap between those two dates with who was holding it, hour by hour where you can, day by day where you can't. You're looking for the stretches where the answer is "nobody" or "I'm not sure". Those stretches are your handoffs, and the longest one is what to fix this month.
Most founders find the same thing: the work itself took two days, and the calendar took eleven. Nine days of waiting, spread across two or three changes of hands.
What does the research say about handoff delays?
There's real data on this, and it comes with limits worth naming.
Gartner surveyed marketing leaders between July and August 2023, 329 of them plus 78 leaders from other functions, and published the results in May 2024. It found that 84% reported high "collaboration drag" from cross-functional work: too many meetings, too much feedback, unclear decision-making authority. It also found that businesses with high collaboration drag were 37% less likely to exceed their revenue and profit targets.
The limits matter. That sample is marketing leaders, largely in organisations far bigger than yours. The 37% figure is a correlation across a survey population, so it describes an association and carries no promise about what happens in your business. And "collaboration drag" is self-reported, which measures how work feels to the people inside it.
What the study is good for: it confirms that unclear ownership and unclear decision rights are a recognised, measured pattern in larger companies too. Your version of it has fewer people and shorter threads. The shape is the same.
What should you fix first, once you've found it?
Fix the naming before you fix anything else, because it's free.
For your slowest handoff, write four lines somewhere both people can see: who hands over, who receives, what starts it, and what "done" means. Four lines. No document, no software, no process map.
Then leave it alone for two weeks and watch whether that stretch shortens. If it does, you've found a handoff that was missing a definition. If it doesn't, you've found one that's missing capacity, and that's a different conversation about hiring or scope.
Resist the urge to redesign everything at once. Five handoffs rewritten in one weekend will all be half-followed by Wednesday. One handoff, held for a month, changes what people expect of each other.
Where does AI belong in a handoff?
On the trigger and the record, once a human has decided what the handoff is.
An assistant that watches a folder and posts "the file landed, it's yours now" removes a chase. One that reads a finished call and drafts the written paragraph from Step 1 removes a blank page. One that checks every Friday which items have sat in the same status for eight days gives you the twenty-minute audit above, on its own, every week.
What it can't do is decide who owns the work. That's a business design question and it stays with you. Point any tool at an undefined handoff and it will move confusion faster, which is worse than slowly. The order is roles first, tools second, every time.
Frequently asked questions
What does it mean when work gets stuck in a business?
It means work is waiting rather than being done. In most small businesses the waiting happens between people, at the points where a task changes hands and nobody is clearly responsible for picking it up.
How many handoffs should a small business have?
As few as the work allows. Every change of hands adds a place to wait, so combining two roles into one owner often does more for speed than any tool. Five or six named handoffs is common in a business with two or three people helping.
Why does work get stuck even when everyone is working hard?
Because effort and flow are different things. Two people can each work a full day on their own tasks while a third item sits untouched between them, waiting on a decision neither of them owns.
Is this a people problem or a system problem?
Usually a system problem wearing a people problem's clothes. If the same handoff fails with two different people in the seat, the definition is what's missing.
How do I know if I'm the reason things stall?
Count how many open items need your approval before they can move. If that number is higher than what you can clear in a normal day, you're the queue.
Should I write a process document for each handoff?
Start with four lines: who hands over, who receives, what triggers it, what "done" means. A longer document is worth writing once those four lines have held for a month.
What's the difference between a handoff and a workflow?
A workflow is the whole path work takes. A handoff is one joint in that path. Fixing a joint is cheaper and faster than redesigning the path.
Can automation fix a broken handoff?
Automation makes a clear handoff faster. On an unclear one it increases volume without adding clarity, so define the handoff first and automate second.
How long before I see a difference?
Two weeks is enough to tell whether one rewritten handoff shortened the wait. Anything shorter measures novelty rather than the change.
Where should I start if several handoffs look broken?
With the one carrying the most money or the most client contact. Fix it alone, hold it for a month, then take the next.
Recommended tools and resources
- A shared status board (Notion, Trello, ClickUp, a spreadsheet). Its job is to show who holds each item right now, which is the one question a handoff needs answered.
- Separate inboxes by function, rather than one shared mailbox. Sales, purchasing and finance each behaving like a named job removes most "I thought you had it" exchanges.
- A weekly stale-item check. Anything in the same status for more than eight days gets read out loud. A calendar reminder does this as well as software.
- One written page per handoff, four lines long, stored where both people already look.
- A decision list, naming which approvals genuinely need the founder. Everything absent from that list moves without you.
- A book worth the time: The Goal by Eliyahu Goldratt, for the habit of looking at where work waits rather than where people are busy.
Where to explore next
- How to Delegate Without Losing Control
- How to Know What to Fix First in Your Business
- 7 Signs Your Business Has Outgrown Its Systems
- How to Organise a Business That Still Depends on You
- Hire vs Automate: How to Tell Which One Your Business Actually Needs
- Where AI Doesn't Belong in Your Business
Final summary
Work gets stuck where it changes hands. The doing is usually quick, and the calendar fills up with waiting: a promise nobody wrote down, an approval that only you can give, a shared inbox with no owner, a finished file nobody sent, an automation nobody reads.
Take three late deliverables, map who was holding them and when, and the longest silence tells you which handoff to rewrite. Four lines, one handoff, one month. That's the whole method, and it costs nothing to start.
Want to see where your work actually stops?
If you've read this and already know which handoff is costing you, and you'd rather have someone map it with you than map it alone, book a call and we'll look at it together.
