You Don't Need a Law Firm COO Yet: 5 Structural Changes to Make First
As law firms grow, one solution tends to surface repeatedly:
"Maybe it's time to hire a COO."
On the surface, it seems like the logical next step. The partners are overwhelmed, staff members have constant questions, projects are delayed, and leadership feels stretched thinner each month. Bringing in an experienced operations leader appears to be the answer.
Sometimes it is.
But in many firms, hiring a COO doesn't solve the underlying problem—it simply gives someone new the responsibility of managing it.
Before adding another executive position, it's worth asking a different question:
What structural problems are we expecting a COO to solve?
In my experience working with law firms, most operational strain doesn't begin with a lack of leadership. It begins with a lack of operational architecture.
Here are five structural changes every firm should evaluate before deciding that a COO is the next step.
1. Clarify Who Actually Owns Decisions
One of my favorite questions to ask during firm assessments is remarkably simple:
"Who owns this decision?"
More often than not, the response isn't immediate. Not because leadership doesn't care about the answer. Because ownership has never been intentionally defined.
Many firms operate under assumptions instead of clearly established authority. Team members know who typically makes a decision, but they don't know who actually owns it. When uncertainty arises, the safest option becomes escalating the issue to a partner.
Eventually, leadership becomes the default destination for every question.
The result isn't stronger oversight. It's decision congestion.
Before hiring a COO, map out who owns recurring operational decisions across your firm. When ownership becomes visible, decisions begin moving through the organization without requiring constant executive involvement.
2. Document Responsibilities Before Expanding Leadership
When firms begin feeling overwhelmed, one of the first assumptions is that everyone simply has too much work.
Sometimes that's true. More often, responsibilities have become blurred over time.
Tasks gradually shift between employees without anyone updating expectations. Processes evolve, temporary solutions become permanent, and eventually several people believe they're responsible for the same task, or no one believes they are.
This creates duplicated effort, inconsistent results, and unnecessary frustration. Adding another executive to oversee unclear responsibilities rarely eliminates confusion. It often inherits it.
Instead, take time to document:
- What each role owns
- What each role supports
- What requires partner approval
- What can be completed independently
Clear responsibility reduces management far more effectively than additional management layers.
3. Build Systems That Don't Depend on Leadership Memory
Many firms unknowingly rely on leadership's memory as part of their operational process.
Partners remember:
- Which client prefers phone calls.
- Which vendor should be contacted first.
- Which filing process differs from the standard workflow.
- Which employee usually handles certain exceptions.
None of this information lives inside a system. It lives inside people. While this works during periods of stability, it becomes increasingly fragile as firms grow.
Every vacation, resignation, promotion, or unexpected absence creates operational risk. Strong firms build systems that preserve knowledge rather than expecting individuals to remember it indefinitely. A COO should spend time improving operations—not reconstructing institutional knowledge that was never documented.
4. Measure Operational Health, Not Just Productivity
Many firms track performance. Fewer measure operational health.
Productivity metrics answer questions like:
- How many files were opened?
- How many calls were completed?
- How many cases closed this month?
Operational metrics answer different questions.
- Where do decisions consistently stall?
- Which processes require repeated partner involvement?
- Which tasks experience the highest rework?
- Which teams rely most heavily on interruptions?
Those measurements reveal structural weaknesses long before financial reports do. When firms only measure output, they often mistake operational friction for employee performance. Sometimes the issue isn't the people.
It's the system asking people to compensate for invisible gaps.
5. Design Escalation Paths Before Creating New Leadership Roles
Every organization experiences problems. Healthy organizations don't eliminate problems. They eliminate confusion about what happens next.
When employees don't know where decisions belong, every issue eventually lands on a managing partner's desk. Not because the issue required executive involvement. Because no alternative path existed.
Effective operational structure creates intentional escalation paths.
Employees know:
- What they own.
- What requires consultation.
- When leadership becomes involved.
- Who has authority before the issue reaches a partner.
This creates confidence throughout the organization while protecting leadership's capacity for strategic work. A COO shouldn't become the firm's newest escalation point. They should help strengthen the system that determines where decisions belong in the first place.
Hiring a COO Isn't the First Milestone, It's Often the Second
None of this suggests that hiring a COO is the wrong decision. Many firms absolutely benefit from experienced operational leadership.
The question is whether the firm has built a structure capable of supporting that role. A COO cannot permanently solve unclear ownership. They cannot single-handedly define responsibilities that have never been documented. They cannot remove every bottleneck if authority still flows back to the same people.
Operations leaders amplify structure. They rarely replace it.
Final Thoughts
One of the biggest misconceptions in law firm operations is that growth problems always require additional people. Often, they require better architecture. The strongest firms aren't the ones with the most leadership positions.
They're the ones where decisions move intentionally, responsibilities are visible, and systems continue functioning without constant executive intervention.
Before hiring your next operational leader, take a closer look at the structure already supporting your firm. You may discover that what feels like a staffing problem is actually an architectural one. And when the architecture improves, growth becomes something your systems can sustain—not something your leadership has to carry alone.
About Legacy Contracts
At Legacy Contracts, we partner with managing partners and law firm leaders to identify the invisible operational structures that shape how firms make decisions, delegate responsibility, and grow sustainably. Through operational assessments and strategic consulting, we help firms build systems that reduce leadership dependency and create long-term stability.










