There is a particular kind of frustration that happens when a managing partner knows the firm should be producing more consistent results, but can't seem to get everyone to operate the same way. One employee completes a task correctly every time. Another handles the same task differently. One attorney follows the established process. Another has developed their own version. A client receives one experience from one member of the team and a noticeably different experience from another.

The natural response is often to address the people involved. Someone needs additional training. Someone needs to pay closer attention. Someone needs to follow the process. Someone needs to be held more accountable. Sometimes, that assessment is correct.

But when inconsistency continues across people, departments, or situations, it is worth asking a different question:

1. What if the inconsistency isn't primarily a people problem?
2. What if the system is producing inconsistent results because consistency was never actually designed into it?

Consistency Is Not the Same as Compliance

Law firms often use the words consistency and compliance interchangeably, but they describe two different things.

Compliance asks:

Did the person follow the instruction?

Consistency asks:

Does the system reliably produce the intended outcome?

That distinction matters.

A firm can have written procedures, checklists, training materials, and documented expectations while still producing inconsistent results.

Why? Because documentation alone does not create structure. If an employee has to interpret what a procedure means, determine when an exception applies, decide who needs to be consulted, or figure out what happens when something falls outside the normal workflow, the system is still relying on individual judgment to fill the gaps.

And individual judgment will naturally vary. That doesn't necessarily mean the employees are careless or incapable. It means the operating structure has left room for different interpretations.

The Same Process Can Produce Different Outcomes

Imagine a law firm has a process for handling a new client intake. The documented process says the intake should be completed, the necessary information should be collected, the matter should be entered into the appropriate system, and the next step should be assigned.

On paper, that sounds clear.

But what happens when the intake is incomplete?

What happens when the client provides conflicting information?

What happens when the person responsible for the next step is unavailable?

What happens when the matter doesn't fit neatly into the normal intake process?

What happens when someone isn't sure whether the issue belongs with an attorney, paralegal, intake coordinator, or managing partner?

Those moments are where operational consistency is actually tested. The standard process may be clear when everything goes according to plan.

The real strength of a system becomes visible when something doesn't. If every employee responds differently when uncertainty appears, the firm doesn't have one operating process. It has several individual interpretations of the same process.

Where Inconsistency Actually Comes From

Inconsistency can enter a law firm's operations through several places.

Unclear ownership

When no one clearly owns a task or outcome, employees may make different assumptions about who is responsible. One person takes initiative.

Another waits. Someone else escalates the issue.

The result is inconsistency that appears to be a performance problem but may actually be an ownership problem.

Undefined authority

Employees may know what they are responsible for but not know what they are authorized to decide. That creates hesitation, unnecessary escalation, and different approaches to similar situations. One employee makes the decision independently. Another asks for approval.

A third waits until leadership becomes involved.

Again, the outcome varies, not necessarily because the employees are different, but because the decision structure is unclear.

Undocumented exceptions

Most firms have exceptions. The problem isn't that exceptions exist. The problem is when employees encounter the same exception repeatedly but there is no shared understanding of how it should be handled.

The exception then becomes dependent on whoever happens to encounter it.

Individual workarounds

Workarounds are often created because someone is trying to keep the firm moving. They may even be effective in the moment. But when one person's workaround becomes another person's normal process, the firm can gradually develop multiple ways of accomplishing the same thing.

Eventually, nobody is quite sure which way is the way.

Invisible knowledge

Some of the most important operational information inside a law firm may never have been formally documented. It lives inside experienced employees. They know which attorney prefers what. They know which client needs a different communication style. They know what happens when a particular provider doesn't respond. They know who to ask when something unusual occurs. That knowledge is valuable.

But when the system depends on a particular person knowing it, consistency becomes dependent on that person remaining available.

Why More Training Doesn't Always Fix Inconsistency

Training is an important part of employee development, but it can become an easy answer to a structural problem.

When an employee produces an inconsistent result, the response may be:

"We need to train them better."

Then the firm trains them. A few weeks later, the same problem appears again. Another training is provided. Then another reminder. Then a meeting. Then additional oversight. Eventually, leadership begins spending more time monitoring the process than improving it.

This creates a cycle:

Inconsistency → correction → temporary improvement → inconsistency → more correction.

The problem is that the intervention is happening at the individual level while the source of the inconsistency may exist at the structural level. If the process itself remains unclear, training employees to memorize the process will only take you so far.

The more useful question becomes:

What would make the desired outcome easier to reproduce regardless of who is performing the work?

That's a systems question.

Accountability Should Make Consistency Easier

This is where accountability becomes more useful than simply measuring whether someone made a mistake.

Structural accountability asks whether the system makes responsibility visible.

Who owns the task?

Who owns the outcome?

What does "complete" actually mean?

What happens when something goes wrong?

Who has authority to resolve it?

When should the issue be escalated?

What information needs to be documented?

What happens next?

When these questions are answered within the workflow itself, employees have less room to interpret the process differently.

The goal isn't to eliminate judgment. The goal is to give judgment a structure.

That distinction is important in law firms because no operational system can account for every possible circumstance. A strong system doesn't attempt to predict everything. It establishes enough clarity that people know what to do when the predictable happens, and where to go when it doesn't.

Consistency Does Not Mean Everyone Does Everything the Same Way

There is another misconception worth addressing.

Designing for consistency does not mean turning a law firm into a rigid machine. Law firms deal with clients, opposing counsel, courts, providers, attorneys, employees, and circumstances that rarely behave exactly the same way twice.

There will always be judgment.

There will always be exceptions.

There will always be situations where the process needs to adapt.

The goal isn't uniformity. The goal is predictable structure with room for appropriate judgment. A consistent firm is not one where every employee behaves identically. It is one where employees understand the standards, ownership, authority, and decision paths that guide their work—even when circumstances change.

A Useful Test for Your Law Firm

If you're experiencing inconsistent results, don't begin by asking:

"Who isn't doing this correctly?"

Start with:

"What does the system require this person to know, decide, remember, or interpret in order to get this right?"

Then ask:

"Would another person reasonably make the same decision?"

If the answer is no, you may have identified a structural gap.

From there, look at five things:

1. Ownership

Is it clear who is responsible for the outcome?

2. Authority

Is it clear who can make the necessary decisions?

3. Process

Is there a defined path for completing the work?

4. Exceptions

Is there guidance for what happens when the normal process doesn't apply?

5. Visibility

Can leadership see where the process is breaking down without personally managing every step?

These five areas can reveal whether your firm is dealing with an employee performance issue or an operational design issue. Sometimes it will be the former. But sometimes the employee is simply operating exactly as the system allows.

The Goal Isn't More Control. It's More Clarity.

When inconsistency appears, the instinct to intervene is understandable.

Managing partners are responsible for protecting the firm's clients, reputation, employees, and profitability. When something isn't working, someone has to address it. But sustainable law firm management requires looking beyond the immediate correction. If every inconsistency requires leadership intervention, leadership eventually becomes part of the process.

And when leadership becomes part of every process, the firm becomes increasingly dependent on leadership to maintain consistency. That may work for a period of time. It becomes much harder to sustain as the firm grows. The objective isn't to make leadership better at catching inconsistencies. It's to build a firm where fewer inconsistencies require leadership intervention in the first place.

Consistency Is a Design Outcome

A law firm's employees are not operating independently of the system around them. They are responding to the information, authority, expectations, workflows, technology, documentation, and leadership patterns available to them.

If those structures are clear, consistent outcomes become easier. If those structures are unclear, employees will naturally fill the gaps themselves.

And when multiple people fill the gaps differently, inconsistency becomes inevitable. This is why consistency should be treated as an operational outcome, not simply an employee characteristic.

You can ask people to be more consistent. Or you can examine whether the system gives them a reasonable path to consistency. The second approach is harder at first. It also tends to be more sustainable.

Before You Correct the Person, Examine the System

The next time your law firm produces an inconsistent result, pause before assuming the solution is another reminder, another training session, or another conversation about performance.

Ask what the system is teaching people to do.

Ask where interpretation is required.

Ask where authority becomes unclear.

Ask whether ownership changes depending on who is handling the work.

Ask whether the process accounts for exceptions.

And most importantly, ask:

If another person had to perform this same work tomorrow, would the system give them a reasonable chance of producing the same result?

If the answer is no, you may not have an accountability problem. You may have a design problem. And design problems can be changed.

Explore the Legacy Resources

Legacy Contracts approaches law firm operations from the belief that sustainable accountability is not created through constant oversight. It is created through intentional structure.

Our resources are designed to help managing partners examine the systems behind delegation, decision ownership, accountability, workflow, and operational consistency, and begin identifying where the firm's current structure may be creating unnecessary friction.

If you're ready to move from identifying operational problems to understanding the structure behind them, explore the Legacy Resources.

[Explore Legacy Resources]