Most firms I talk to have already blamed the wrong thing. Usually it’s a person, or “we just need to hire more help.” Neither is what’s actually going on.
When a firm grows, the work doesn’t break all at once. It bleeds quietly. A client question that should take two minutes takes two hours because the answer is buried in a folder no one can find. Billable time gets burned hunting through manuals and case files instead of doing the work itself. New hires ask the same questions again and again because the knowledge was never written down anywhere they could find it on their own.
None of that shows up as one dramatic failure. It shows up as everyone being a little more tired than they should be, a little more behind than they should be, and nobody quite able to point to why.
Why “hire more people” usually doesn’t fix it
Picture a small firm where every new client file gets built the same slow way. Someone digs through old emails to find the right template, copies data by hand from one system into another, and asks around to figure out who’s supposed to sign off next. Now add a new hire to help with the volume. That person doesn’t get relief from the mess. They get trained into it. They learn the same workaround everyone else learned, because the workaround is the only process that exists. Headcount went up. The bottleneck didn’t move.
That’s not a real client of mine, it’s a pattern I’ve seen play out the same way across a lot of firms, which is exactly why it’s worth naming plainly. Hiring adds hands. It doesn’t add a system. If the system is the problem, more hands just means more people working around the same broken thing.
What the system actually is
By “system” I don’t mean software. I mean the actual path a piece of work takes from the moment it enters your firm to the moment it’s done: who touches it, in what order, where it waits, and where the knowledge to move it forward actually lives. Most of the time that knowledge lives in a person’s head, or scattered across old emails and a folder structure nobody agreed on. It was never designed. It just accumulated, one workaround at a time, while the firm was busy doing the actual work.
That’s not a criticism. It’s what happens to every growing firm that doesn’t have someone whose job is to step back and look at the whole thing. Everyone inside it is too busy running the process to see the shape of it.
What I actually look for
A workflow bottleneck audit starts by mapping one important workflow end to end, not the whole firm at once. I find the delays, the handoffs that aren’t clearly owned by anyone, and the steps that only work because one specific person remembers how they go. Then I leave you with a prioritized plan for fixing them, in order of what will actually move the needle first.
What I’ve seen work best is picking the one workflow that causes the most quiet frustration, the one people mention almost as a joke because they’ve stopped expecting it to change, and starting there. Fixing that one thing usually tells you more about the rest of the firm than trying to map everything at once ever would.
The honest version
If work inside your firm feels harder to manage than it should, the bottleneck usually isn’t your people. It’s your system. Your team is probably working hard and working around a lot to get things done anyway. That’s worth fixing before it’s worth hiring around.
If you’re not sure whether what you’re dealing with is a people problem or a system problem, that’s a fair thing to bring to the audit call. Fifteen minutes is usually enough to tell the difference.
Find out if it’s your people or your system.
Fifteen minutes to look at the workflow that’s actually slowing you down.
