Practice AreasPersonal InjuryImmigrationEstate PlanningBusiness TransactionsCriminal DefenseNiche Firms
Diagnose
Legal DesignLive Events
Connect
The TeamBlogBook a Strategy Call →
Operations · Capacity

Hiring Won’t Fix Your Bottleneck

You already have staff. The work still runs through you. That is not a headcount problem — it is the predictable output of handing people a system nobody designed.

HIRETHE BOTTLENECKLFA / FIG.03HEADCOUNT →QUESTIONS AIMED AT YOU ↑HIRE 101HIRE 202HIRE 303HIRE 404DESIGN05DESIGN DROPS THE LOADMORE PEOPLE, MORE QUESTIONSFig. 03 — Headcount rises, owner load rises with it — until the system is designed

The bottleneck is not a staffing shortage. You have staff. You hired the people. And the work still routes through your desk every single day.

So you try delegating. It holds for about a week. Then the questions start coming back — what stage is this in, who owns it, is this ready to send, what does done look like. You answer them, one by one, and quietly conclude that you have the wrong people, or that you are simply bad at letting go.

Neither is true. Delegation broke because there was nothing designed to hand off to.

More people on an undesigned system just creates more questions aimed at you.

Law Firm Architects · Operating Philosophy

01You Cannot Hand Off a Vacuum

Handing someone work is not delegation. Delegation is handing someone a defined piece of the system — a stage with a beginning, an owner, and an end. If none of that exists, you have not delegated anything. You have simply moved the ambiguity to another desk, where it sits until it turns back into a question for you.

Your team is not underperforming. They are doing exactly what an undesigned firm forces capable people to do: check with the only person who holds the whole picture.

Every one of those gaps is a doorway back to your desk. Hiring adds people. It does not close doorways.

Key Takeaway

Adding people to an undesigned firm does not divide the work. It multiplies the questions — and every one of them lands on you.

02The Math Runs Backward

This is the part that blindsides owners. You assume the fifth hire relieves the load the fourth one created. In an undesigned firm, the opposite happens. Each new person is another node with no map, another set of judgment calls with no criteria, another source of “quick questions” that were never quick.

Capacity does not scale with headcount. It scales with structure. Until the structure exists, hiring is just a more expensive way of being the bottleneck.

Hire Into Chaos

  • People wait on your answer
  • Work starts by accident
  • Done is a judgment call
  • Handoffs are verbal
  • Capacity flatlines

Hire Into Design

  • People read the next move
  • Work starts on a trigger
  • Done is written down
  • Handoffs are confirmed
  • Capacity compounds

03Design the Thing You Are Handing Off

Before you post another job listing, build the thing a hire is supposed to step into. That is not a ninety-page manual. It is three fields, applied to every stage of your highest-volume case type.

Entry Trigger

The specific event that moves a case into this stage. Without it, work starts whenever someone happens to notice. With it, the stage starts itself.

Role Owner

One role — not one name, not a committee — accountable for the stage. When ownership is shared, it is not owned.

Exit Condition

What must be true before the case leaves. This is the field that lets staff close a stage without you. Skip it and you are re-hired, every day, as the firm’s approval mechanism.

3
Fields Per Stage
1
Case Type To Start
0
New Hires Required

04Fix the Design, Then Hire

An undesigned system breaks good people. It also breaks the next good person you hire, at exactly the same seam, for exactly the same reason. Design the stages first and the hire lands into something real — a lane they can run without checking in, a definition of done they can meet without asking, an exit they can execute without you.

Do that, and the next hire actually adds capacity instead of adding questions. Skip it, and you will keep paying salaries to protect a bottleneck that was never made of people.

OperationsDelegationCapacitySystems
LB
Luis Barés
Founder · Law Firm Architects

Luis designs law firm operating systems — the people, process, and technology architecture that lets a firm grow without running on burnout. He writes The Blueprint every week.

Ready When You Are

Ready To Design Your Firm?

If your team keeps handing the work back, we’ll help you design the system they were supposed to be handed in the first place.

Book Your Free Strategy Call →