Why the partner becomes the bottleneck in a small firm

Why does the principal end up as the constraint?

Because judgement, authority and client relationships all sit in one place, and nobody ever wrote down which decisions actually require them. In a firm of two or three, routing everything through the owner is cheaper than documenting anything. The habit is sensible at the start and survives well past the point where it works.

Three forces keep it in place. Clients ask for the principal by name, so the principal answers. The principal's name is on the engagement and the practising certificate, so the principal signs off. And the principal is usually the fastest person in the building at the actual work, so delegating feels slower in the moment than doing it.

There is also a piece of plain arithmetic behind it. When everything must pass through a single point, waiting time does not rise gently as that point gets busier, it rises sharply. A principal who is booked most of the day will have a queue behind them that is far longer than their diary suggests. This is not a character flaw, it is what happens to any system with one gate.

What are the signs it is already happening?

The reliable signs are all about waiting rather than workload. A busy firm has work moving. A bottlenecked firm has work parked.

• Matters, jobs or files sit in "waiting on you" for longer than the work itself takes.
• Nobody can send a quote, an engagement letter or an invoice without your review.
• Your team saves up questions and delivers them in batches shaped around your diary.
• Clients routinely wait days for an answer that takes four minutes.
• The admin you do happens after six or on a Sunday, because the working day belongs to other people.
• A week of leave takes a fortnight of preparation and produces a fortnight of backlog.
• New enquiries go cold and you find out about it later, if at all.
• The process lives in your head and gets re-explained rather than read.
• Staff have stopped asking and started guessing, or stopped guessing and started waiting.

The sharpest test takes a fortnight. Keep a running list of every interruption, one line each, and mark it: (a) genuinely needed my professional judgement, (b) needed a rule that somebody else could have applied, (c) needed nothing but a status update or a signature. Category (a) is your actual job. The size of (b) and (c) is the size of the bottleneck.

What does the bottleneck actually cost?

Four things, and only one of them shows up in the accounts. The other three are the expensive ones.

Capacity. The firm cannot take on more work than its slowest gate allows. Revenue plateaus and the cause looks like a marketing problem, so firms spend money on more enquiries that then queue behind the same person.

Response time. Professional work is often won by whoever replies first with something credible. Slow replies lose work that never appears in any report, because a prospect who chose someone else rarely tells you why.

Development. Your people do not grow, because the decisions that would have trained them keep coming back to you. Firms in this state tend to lose good juniors and then conclude that good juniors are hard to find.

Key person risk. A practice that cannot run for two weeks without one person is fragile in the ordinary case of illness or leave, and it is a genuine problem in any sale, merger or succession conversation. Whatever the practice is worth, it is worth less when it is one person's memory.

Then there is the personal cost, which is usually what makes someone finally act: the highest-paid person in the firm spends their evenings on its lowest-value tasks.

Why doesn't hiring on its own fix it?

Because hiring adds capacity below the constraint, not at it. If every piece of work still needs your approval before it moves, a new staff member increases the volume arriving at your desk. The queue gets longer, and the new hire's first experience of the firm is waiting.

Hiring works when the new person absorbs decisions, which means the decisions have to be written down and handed over. Firms that skip that step tend to hire twice, conclude that delegation does not work, and take the work back.

What should you fix first?

Separate the judgement from the routing, then attack the routing. Judgement is what clients pay for and it should stay with you. Routing, chasing, assembling and updating are pure overhead, and they are what actually fills the queue.

1. Log a fortnight. Every interruption, one line, marked (a), (b) or (c) as above. Two weeks is enough to see the pattern and short enough that you will finish it.
2. Rank by frequency, not by irritation. The thing that annoys you most is rarely the thing costing the most hours.
3. Write the rule for the top three category (b) items. A rule is one paragraph: what the situation is, what to do, and the exceptions that come back to you.
4. Change the default from "ask me" to "do it and tell me." Name the exceptions explicitly so nobody has to guess where the line is.
5. Replace blank pages with drafts. Approving a prepared draft is a much smaller call on your attention than composing one from nothing. This applies to acknowledgements, quotes, status emails and reports alike.
6. Automate the assembly, not the decision. Getting the file open, the record created, the numbers pulled and the draft written is machine work. Deciding whether to send it is not.
7. Review after thirty days. Look at which drafts you changed and why, then fold that back into the rule. Two rounds of this and the rule is usually better than the original instinct.

The aim is not to remove the principal from the decisions the firm is paid for. It is to stop the principal from also being the postal service.

What to do next

Take the single item you touched most often in your fortnight log and write the rule for it this week. Change the default, tell the team, and see what breaks. If the routing and assembly around that item is still manual after the rule exists, that is the first thing worth automating, and it is usually a small build rather than a project. It is where Shift starts with a new firm: one workflow, the one costing the most hours, before anything else gets discussed.