Motion without throughput
Busy rooms can still stall when work waits on approvals, missing data, or "I thought you had it." That is the coordination tax — hidden labour that does not show on utilisation charts. Activity is not progress. When jobs take twice as long as they should, list the waits rather than the tasks. The waits are where margin leaks.
Hiring and buying often follow busyness without actually fixing throughput. You add salary and subscriptions to a situation that still has no single queue and no named owners at handoffs.
Diagnose one slow job
Pick a job that embarrassed you — late to the customer, late to invoice, late as a board story. Timeline it: where did it sit? Who was supposed to act? Was the truth in email, a spreadsheet, or a meeting? Each wait needs an owner or a system fix, not another all-hands.
Common waits include approvals stuck in a founder inbox, data being re-keyed because systems disagree — as covered in when CRM and finance disagree — and priority being decided verbally every morning, which is the territory of the meeting that replaced the system.
Fixes that actually move throughput
One queue for open customer work — visible, aged, and owned. Decision rights with thresholds so exceptions do not all route to the same person, the subject of the founder bottleneck piece. Remove duplicate checks where two people verify the same fact because neither trusts the system.
If the busyness is login fatigue, tool stack heavier than the work covers it. If it is thread-chasing, email is not a workflow is the relevant read. If you are planning to hire your way out of it, hiring will not fix a broken handoff explains why that rarely works.
Measure what matters
Track cycle time for one job type — quote to cash, order to ship — not hours logged. If cycle time flatlines while headcount rises, you are paying the coordination tax in cash. A systems review gives you an external mirror when you need one.
The busy trap for leadership
Founders interpret busy as demand and hire or buy — sometimes correctly. Often they fund activity that masks stalls: more people in handoffs, more tools logging the same fact, more meetings updating status verbally. Ask whether throughput rose, not whether everyone looked stressed.
Publish one queue visible to leadership — aged work, not utilisation percentages. When the queue grows while headcount grows, the problem is system and ownership, not effort. Pair that view with hiring will not fix a broken handoff.
WIP limits — maximum open jobs per person or team — expose stalls faster than busyness metrics. You do not need fancy software. You need a number the room respects and reviews weekly.
Run a quarterly pass on handoffs that still use email or verbal priority. Each one is coordination tax you have normalised. A process audit helps when the map is too messy to fix in one ops meeting.
Stop rewarding visible busyness in stand-ups. Ask "what unblocked the queue" rather than "what kept you busy." Culture follows what leadership praises. One honest metric on the wall beats ten motivational posters.
Book — Teesside and the North East. Process audit to map the waits, and build when the fix is thin and owned.