How to Design Decision Pathways That Remove the Managing Partner as the Default
There is a particular kind of operational bottleneck that can be difficult to see from inside a law firm. The managing partner is involved in almost everything. Not necessarily because they want to be. Not necessarily because their team is incapable. And not necessarily because they have intentionally created a culture where every decision must come through them.
It often happens gradually.
An employee encounters something they haven't handled before, so they ask the managing partner. A decision gets made, and everyone moves forward. The next time something similar happens, another question comes back to leadership. Eventually, the managing partner becomes the person everyone consults whenever there is uncertainty.
At some point, the firm may still describe itself as delegated and collaborative, while the managing partner has quietly become the default decision-maker. This is where law firm delegation often breaks down. The problem isn't always that work hasn't been delegated. The problem is that decision ownership hasn't been designed.
The Managing Partner Shouldn't Be the Firm's Default Escalation Path
Managing partners are often expected to be the final safety net. When something is unclear, they know what to do. When a client situation becomes complicated, they know what to do. When an employee needs an exception, they know what to do. When two people disagree about responsibility, they know what to do. That expertise is valuable.
But a firm cannot scale effectively if the answer to every difficult question is simply:
"Ask the managing partner."
At first, this can feel efficient. The managing partner has the experience. They can make the decision quickly. The employee doesn't have to spend an hour trying to figure something out. The matter gets resolved. But there is a hidden cost.
Every decision that returns to leadership reinforces the idea that leadership is responsible for resolving it. The managing partner becomes faster at answering questions while the organization becomes less capable of answering them independently.
This creates a cycle:
Uncertainty → escalation → leadership decision → temporary resolution → another similar situation → escalation again.
The firm is solving individual decisions without solving the structure surrounding those decisions. That is the difference between decision-making and decision architecture.
Decision Pathways Create a Different Kind of Delegation
Delegation is often discussed as the transfer of work. But effective delegation also requires the transfer of appropriate decision-making authority.
If someone is responsible for completing a task but doesn't know what they are authorized to decide, the work hasn't been fully delegated. They have been given responsibility without enough authority to carry it.
This is where decision pathways become useful.
A decision pathway answers a basic question:
When this situation occurs, how should the decision move through the firm?
That doesn't mean creating a complicated approval tree for every possible scenario. It means identifying recurring decisions and determining where they belong.
For example:
- What can an employee decide independently?
- What requires supervisor approval?
- What should be escalated to an attorney?
- What genuinely requires managing-partner involvement?
- What circumstances change the normal decision pathway?
- What information should accompany an escalation?
These questions turn delegation from a general expectation into something operational. Instead of saying: "Use your judgment." The firm can define what judgment actually looks like within a particular role.
Start With the Decisions That Keep Coming Back
If you want to reduce managing partner overload, don't begin by trying to map every decision in the firm. Start with the ones that repeatedly return to leadership. Look at the questions your managing partner answers over and over.
What are employees asking?
What situations consistently require approval?
What exceptions keep appearing?
What decisions cause people to pause because they aren't sure who has authority?
What issues could probably be resolved without leadership involvement if the boundaries were clearer?
This is often where the firm's existing decision architecture becomes visible. You may discover that the managing partner is not actually needed for many of the decisions currently reaching their desk. The organization simply hasn't established another clear place for those decisions to go.
That distinction matters. Because if the problem is capacity, you may need more people. If the problem is authority, you need more clarity. Adding another employee to a poorly designed decision structure doesn't necessarily solve the problem. It can simply create another person who eventually asks the managing partner the same questions.
Build Decision Pathways Around Authority, Not Hierarchy
One of the easiest mistakes to make is assuming that decision ownership should always follow organizational hierarchy. The person with the highest title isn't necessarily the person who needs to make every decision. Instead, decision authority should reflect the nature of the decision.
Consider four basic categories.
1. Independent Decisions
These are decisions someone should be able to make without asking for permission.
The criteria should be clear enough that the employee understands the boundaries of their authority.
2. Conditional Decisions
These can be handled independently when certain conditions are met but require escalation when those conditions change.
This category is particularly useful because not every situation requires a rigid yes-or-no rule.
3. Escalation Decisions
These are situations where another level of expertise or authority is genuinely required.
The important part is defining when escalation should happen rather than leaving employees to guess.
4. Leadership Decisions
These are decisions that genuinely belong with firm leadership because they affect strategy, risk, finances, firm-wide policy, or other areas that require that level of authority.
The goal isn't to eliminate managing-partner involvement. The goal is to make managing-partner involvement intentional. That is a very different objective.
A Decision Pathway Needs More Than a Name
Simply assigning someone as the "owner" of a decision isn't enough. A usable decision pathway should answer several questions.
What is the decision?
Be specific.
"Client issues" is too broad. "Whether a client communication requires attorney review before being sent" is much easier to operationalize.
Who owns the decision?
There should be a clear person or role responsible for making it.
What authority does that person have?
Can they decide independently? Do they need certain information first? Are there defined limits?
When does the decision escalate?
This is one of the most important pieces. People shouldn't have to guess when something has become "too complicated."
Where does the decision go next?
If escalation is necessary, the pathway should identify the next appropriate level rather than simply saying, "Ask someone else."
These details transform a vague delegation structure into an actual operating mechanism.
The Goal Isn't to Remove the Managing Partner From Decisions
The phrase "remove the managing partner as the default" can sound like the managing partner shouldn't be making decisions. That isn't the goal. Managing partners should absolutely be involved in decisions that require their authority, expertise, or strategic perspective.
The problem is when their involvement is caused by ambiguity rather than necessity. There is a meaningful difference between:
"This decision requires the managing partner." and: "Nobody knows who else can make this decision." The first is intentional leadership.
The second is an operational gap. A healthy law firm doesn't eliminate leadership involvement. It creates enough clarity that leadership can spend its attention where it has the greatest value.
Decision Architecture Is Part of How a Firm Scales
This becomes increasingly important as a law firm grows. When a firm is small, informal decision-making can work surprisingly well. Everyone may know each other. The managing partner may be aware of most active matters. Communication can happen quickly. But growth changes the equation.
More employees create more communication pathways. More clients create more exceptions. More work creates more decisions. More specialization creates more areas where not everyone has the same knowledge. Eventually, the informal structure that worked at five people may become the bottleneck at fifteen. This is one reason firms can experience a strange form of growth strain.
The firm has grown, but the decision architecture hasn't. The result is often increased managing-partner involvement rather than increased organizational capacity. If the firm wants to scale, it cannot simply increase the amount of work being completed. It also has to increase the number of decisions the organization can make without requiring constant leadership intervention.
Start Designing With One Question
If your managing partner is currently the default decision-maker, don't begin by asking:
"How do we get everyone to stop bothering the managing partner?"
That frames the people as the problem.
Instead, ask:
"What decisions are currently reaching the managing partner that should have a different pathway?"
That question changes the conversation.
It allows you to look at the structure rather than blame the people operating inside it. Then begin identifying the recurring decisions. Map who currently makes them. Identify who could reasonably own them. Define the boundaries of that authority. Determine when escalation is appropriate. And document the pathway in a way that the people responsible for using it can actually understand.
You don't need to redesign the entire firm overnight. One decision pathway can reveal another. One clarified authority boundary can remove dozens of unnecessary interruptions. One recurring question can expose a larger structural gap.
The Firm You Want Requires Decisions to Have Somewhere to Go
A law firm's operational structure isn't only made up of workflows, procedures, and task assignments. It is also made up of where decisions go.
When authority is unclear, decisions gravitate upward. When decisions consistently gravitate upward, leadership becomes the bottleneck. And when leadership becomes the bottleneck, growth eventually becomes more difficult than it needs to be.
The solution isn't to tell employees to be more independent. It isn't to tell the managing partner to delegate more. And it isn't necessarily to hire another layer of management. The first step is understanding the architecture that already exists. Then, where necessary, redesigning it.
Because the objective isn't to create a firm where the managing partner makes fewer decisions simply for the sake of making fewer decisions.
The objective is to create a firm where the right decisions are made by the right people, with the right authority, at the right point in the workflow. That is what intentional decision architecture makes possible.
A Practical Starting Point
Take the last ten decisions your managing partner had to make that interrupted their normal workflow.
Write each one down.
Then ask:
- What was the decision?
- Why did it reach the managing partner?
- Who could reasonably own this decision?
- What information would they need to make it confidently?
- What boundary would require escalation?
- Where should the decision go the next time this situation occurs?
You may find that the managing partner is carrying decisions that were never intentionally assigned to them. And that is an important distinction.
Because you cannot redesign what you haven't first identified.
The Managing Partner Shouldn't Have To Be The System.
The firm should have a system that allows the managing partner to lead.
Legacy Contracts helps law firms identify the operational structures behind recurring bottlenecks, unclear authority, and leadership dependency. Explore the Legacy Resource Library for practical tools and frameworks designed to help you build greater operational clarity.
Ready to map where decisions actually belong in your firm? Explore the Decision Architect Workbook and begin turning recurring decision-making patterns into intentional pathways.
