Your Biggest Operational Risk Might Be Your Most Loyal Employee

Every law firm has one.

Or, at least, most firms that have been around long enough do.

The employee who's been there since almost the beginning.

They've worked for the managing partner for 20 years.

Maybe 25.

They've survived office moves, technology changes, partner departures, new hires, bad years, great years, and probably more than a few firm crises.

They know everything.

Ask why a process works the way it does, and they know.

Ask about a client from 2009, and they remember.

Can't figure out something in the practice management system?

Ask them.

Need to know why the firm handles a particular situation in a strangely specific way?

They know the story.

These employees can be extraordinarily valuable.

They can also become one of the biggest operational risks in a law firm.

The difference isn't how long they've been there.

It's what they've done with those years.

Loyalty Is Valuable. It Isn't a Performance Metric.

Let me start by making something very clear.

I value loyalty.

In a world where people change jobs frequently, there's something incredibly valuable about an employee who has invested 10, 15, 20, or even 30 years in one organization.

I've worked with long-tenured employees who are absolute gold.

They understand the firm's history.

They have deep client relationships.

They know the personalities.

They've seen what has worked and what hasn't.

They provide context a new employee—or a Fractional COO like me—simply doesn't have.

I listen to those people.

Their perspective matters.

But tenure can't become a substitute for performance.

And loyalty can't become immunity from change.

Meet the Legacy Employee

I think of these long-tenured team members as legacy employees.

Not simply because they've been around a long time.

It's because they've become deeply woven into how the organization functions.

Sometimes that's wonderful.

Other times, you start hearing things like:

"We've always done it this way."

Or:

"We tried that before."

Or my personal favorite:

"That might work somewhere else, but it won't work here."

Then comes the ten-minute explanation of why the new idea is doomed before we've even tried it.

Sometimes they're right.

That's important to acknowledge.

Someone who has worked inside a firm for 20 years knows things I don't know when I walk through the door.

Maybe there really is a reason a particular approach failed previously.

Maybe there's historical context leadership has forgotten.

Maybe the proposed solution genuinely doesn't fit the practice.

I want that information.

What I don't want is for history to become an automatic veto on the future.

"We've Always Done It This Way" Is Information, Not an Argument

Whenever I hear:

"We've always done it this way,"

my next question is:

"Why?"

Sometimes there's a fantastic answer.

Great.

Keep doing it.

But sometimes the answer is essentially:

Because we do.

That's not strategy.

That's habit.

And habits become particularly difficult to challenge when the person defending them has been with the organization longer than almost everyone else.

Their tenure gives their opinion weight.

Again, that's not necessarily bad.

The problem begins when that weight becomes enough to stop change entirely.

Legacy Employees Can Become Organizational Gravity

This is how I think about it.

A deeply tenured employee can create organizational gravity.

They aren't necessarily trying to sabotage anything.

They may genuinely believe they're protecting the firm.

But every proposed change gets pulled back toward what feels familiar.

New software?

"The old system works fine."

New reporting structure?

"We've never needed that."

New workflow?

"We tried something like that before."

New manager?

"I've always gone directly to the managing partner."

Eventually, implementing even relatively straightforward changes becomes exhausting.

Leadership spends so much energy overcoming resistance that it becomes tempting to simply leave things alone.

And slowly, the organization gets pulled back toward the status quo.

Institutional Knowledge Isn't Always an Asset

Law firms love talking about institutional knowledge.

And they should.

Institutional knowledge can be incredibly valuable.

But I see a dangerous version of it all the time.

One person knows how the process works.

One person knows the history.

One person has all the passwords.

One person knows the workaround.

One person knows which client expects what.

One person knows how to fix the weird issue that happens every six months.

And almost none of it is documented.

Leadership says:

"We could never survive without her. She knows everything."

That's usually meant as a compliment.

I hear it as a risk assessment.

Because if your organization can't function without one employee, you don't have institutional knowledge.

You have institutional dependency.

If It's Only in Someone's Head, the Firm Doesn't Own It

This is one of my biggest frustrations when I encounter it.

An employee has accumulated 20 years of knowledge.

But very little of it has been transferred into:

• documented processes

• SOPs

• training materials

• shared systems

• cross-training

• institutional resources

The employee knows it.

The firm doesn't.

That's an important distinction.

Because what happens when that employee retires?

Takes an extended leave?

Gets sick?

Or simply decides tomorrow that they're ready for something different?

Twenty years of knowledge can walk out the door.

That shouldn't be possible.

Sometimes Knowledge Becomes Job Security

This is uncomfortable to talk about, but I've seen it.

Sometimes an employee resists documenting what they know because their knowledge has become part of how they protect their position.

If I'm the only person who knows how to do this...

If everyone has to come to me...

If the managing partner can't function without me...

Then I'm indispensable.

And if I'm indispensable, I'm safe.

I understand the psychology.

But it's terrible organizational design.

No healthy company should depend that heavily on one person.

And ironically, hoarding knowledge doesn't make someone more valuable in my eyes.

It makes the organization more vulnerable.

The Most Valuable Employees Multiply What They Know

The employees I value most don't protect their knowledge.

They multiply it.

They document.

They train.

They mentor.

They build systems.

They create backups.

They make sure someone else understands what they understand.

That doesn't make them less valuable.

It makes them more valuable.

Because now they aren't simply capable of doing the work.

They're capable of building an organization that can do the work.

That's a much higher-level contribution.

The best legacy employees don't protect institutional knowledge.

They multiply it.

Then There's the Shadow Organizational Chart

This is another dynamic I encounter frequently.

A law firm grows.

The managing partner realizes they can't manage everyone directly anymore.

So leadership positions are created.

Maybe there's an office administrator.

A director.

A COO.

A department head.

On paper, the organizational structure makes sense.

Except for one person.

The legacy employee.

They've reported directly to the managing partner for 20 years.

And they have absolutely no intention of changing that now.

So technically, they report to the new leader.

In reality?

They continue walking straight into the managing partner's office.

"I've Always Reported to the Managing Partner"

This creates more problems than people realize.

The new manager can't truly manage.

The legacy employee knows they can bypass the chain of command.

The managing partner continues getting dragged into operational issues they were specifically trying to delegate.

Other employees notice that the organizational structure apparently applies differently depending on who you are.

And eventually, the org chart becomes theoretical.

That's not harmless.

If you hire someone to lead, you have to let them lead.

And that means even your longest-tenured employees need to respect the structure.

Loyalty should earn trust.

It should not earn veto power—or a permanent exemption from accountability.

Longevity Can Create Informal Power

Every organization has formal authority.

Titles.

Reporting relationships.

Decision rights.

But organizations also have informal authority.

And legacy employees can accumulate a tremendous amount of it.

They know the owner.

They've been around longer than the managers.

Everyone knows the owner trusts them.

They may not have a senior title, but people understand that their opinion carries weight.

Again, that can be incredibly useful.

But leadership needs to be conscious of it.

Because informal power can quietly undermine formal leadership if it isn't managed appropriately.

The New Leader Has Almost No Chance If the Owner Doesn't Back Them

I've seen this happen.

A firm hires someone specifically to introduce structure and change.

The legacy employee resists.

They go around the new leader and directly to the owner.

And the owner allows it.

At that moment, the new leader's authority is effectively gone.

The message to the organization is clear:

The new structure applies until someone sufficiently important doesn't like it.

You cannot ask someone to lead while simultaneously allowing employees to bypass them whenever they're uncomfortable.

If leadership wants change, leadership has to support the people responsible for implementing it.

"We Tried That Before" Doesn't Mean We Should Never Try Again

This one deserves special attention.

Long-tenured employees have seen initiatives come and go.

They've seen new consultants.

New software.

New leadership ideas.

New strategic plans.

Some of them failed.

That history matters.

But context changes.

Technology changes.

People change.

The firm changes.

Execution changes.

Something that didn't work eight years ago may work beautifully today.

Or perhaps the idea was fine and the implementation was terrible.

"We tried it once" shouldn't permanently close the door.

The better question is:

"What happened last time, and what can we learn from it?"

That's how institutional knowledge should support innovation rather than block it.

Change Is Particularly Hard When You've Mastered the Current System

I also have empathy for why this happens.

Imagine you've spent 20 years becoming exceptionally good at operating within a particular system.

You know every shortcut.

Every exception.

Every workaround.

Every personality.

You've built enormous competence around the current way of doing things.

Then someone like me walks in and says:

"We're going to change it."

That's uncomfortable.

Suddenly, expertise you've accumulated for decades may feel less relevant.

A new system puts everyone back into learning mode.

I understand why someone might resist that.

But organizations can't stop evolving simply because change makes experienced employees uncomfortable.

The market won't allow it.

Your Most Loyal Employee Shouldn't Become Your Least Coachable Employee

This is where leadership has to draw the line.

Tenure deserves respect.

Experience deserves respect.

Institutional knowledge deserves respect.

But none of those things mean someone becomes uncoachable.

Everyone in a healthy organization should remain capable of:

• receiving feedback

• learning

• adapting

• using new technology

• respecting leadership structures

• changing processes when there's a better way

That includes the person who's been there for 25 years.

Maybe especially that person.

Because other employees are watching.

The Best Legacy Employees Are Incredible

I don't want this article to leave the impression that long-tenured employees are inherently difficult.

They're not.

Some of the best people I've ever worked with are legacy employees.

And when they're good, they're extraordinarily good.

They can tell me why something exists.

They can help me avoid mistakes.

They know which changes will create unintended consequences.

They understand the firm's culture.

They know the clients.

And instead of using that knowledge to resist change, they use it to help us implement change intelligently.

Those employees become my partners.

They're often the people I rely on most.

The Difference Is Whether They Protect the Past or Help Build the Future

That's ultimately the distinction.

A great legacy employee can say:

"Here's why we historically did it this way. But I understand why we need to change."

They can help translate between the old organization and the new one.

They can mentor newer employees.

They can identify what should be preserved.

They can help leadership understand what needs to evolve.

Their longevity becomes an enormous strategic advantage.

They don't protect the past simply because it's familiar.

They help determine which parts of the past deserve to come with us.

The Goal Isn't to Become Indispensable

I hear people describe employees as "indispensable" all the time.

Usually, it's intended as the highest possible compliment.

Operationally, I'm not sure it is.

I don't want any organization to have one person it literally cannot function without.

Instead, I want great employees to make themselves promotable.

Document what you know.

Develop the person behind you.

Build systems.

Create backups.

Transfer knowledge.

Then move into higher-value work.

If the organization can function without you doing your old job every day, that's not evidence that you're less valuable.

It's evidence that you've successfully built something.

Leadership Has a Responsibility Here Too

Legacy-employee problems aren't always created by the employee.

Owners contribute.

Sometimes significantly.

If you've allowed someone to bypass managers for 15 years, don't be shocked when they're resistant to a new reporting structure.

If you've praised someone for being "the only person who knows how everything works," you've reinforced dependency.

If you've allowed "we've always done it this way" to end every conversation, you've taught the organization that resistance works.

Leadership has to own its part.

Then it has to reset expectations.

Loyalty Should Earn Trust, Not Veto Power

Your long-tenured employees have earned something valuable.

Trust.

Their history matters.

Their opinions should be heard.

Their knowledge should be respected.

But trust doesn't mean they get to decide whether the firm changes.

It doesn't mean new leaders can't manage them.

It doesn't mean processes don't need to be documented.

And it doesn't mean every new idea can be dismissed because the firm tried something vaguely similar in 2014.

Loyalty should earn trust.

Not veto power.

The Real Question

Look at your longest-tenured employees.

Then ask:

If this person left tomorrow, what would happen?

Would you lose valuable history and experience but continue operating effectively?

Or would significant parts of the business stop functioning because no one else knows what they know?

If it's the latter, that's a risk.

Then ask another question:

When the firm changes, does this person help move everyone forward?

Or do they consistently pull the organization back toward the way things have always been?

That's the difference between institutional knowledge that strengthens your firm and institutional dependency that limits it.

The Best Legacy Is a Firm That's Stronger Because You Were There

Twenty years at a company should mean something.

It should mean you've accumulated enormous knowledge.

Built relationships.

Developed expertise.

Helped shape the culture.

But the greatest legacy isn't becoming the one person the firm can't survive without.

It's leaving behind:

• stronger systems

• documented knowledge

• better-trained people

• future leaders

• a more capable organization

The best legacy employees don't make themselves the center of the organization.

They make the organization better.

And that's the kind of loyalty every law firm should want.

Long-tenured employees can be one of a law firm's greatest competitive advantages—but only when institutional knowledge becomes institutional strength rather than organizational dependency.

I help law firms build clearer reporting structures, document critical processes, strengthen accountability, transfer institutional knowledge, and implement change without losing the people and history that made the firm successful in the first place.

Because the goal isn't to erase what made your firm successful.

It's to make sure the past doesn't prevent you from building what's next.