FIELD NOTE |
January 8, 2026
Redundancy Isn’t Inefficiency
Efficiency removes what appears unnecessary under the conditions we already know. Redundancy preserves capacity for conditions we don't.
Organizations are taught to be suspicious of redundancy.
Two systems doing similar things? Consolidate them.
Two people who understand the same process? Clarify ownership.
Extra capacity? Improve utilization.
A manual path beside an automated one? Eliminate it.
There are good reasons for this. Duplication can be expensive, confusing, and genuinely wasteful. I've spent plenty of my career removing it.
But redundancy and waste are not the same thing.
Optimization works partly by identifying what appears unnecessary under known conditions. The problem begins when we mistake not necessary right now for not valuable to the system.
A second pathway looks unnecessary while the primary pathway works. Extra capacity looks idle until demand changes. Overlapping expertise looks inefficient until the person with singular knowledge leaves.
Efficiency asks how little a system needs when things go as expected.
Resilience asks what it needs when they don't.
More than one possibility has to remain alive
There is another function of redundancy that gets less attention.
If every resource is committed to current execution, every role is fully utilized, every process has one approved path, and every technology has to justify itself through immediate efficiency, where exactly is the new thing supposed to come from?
Real experimentation contains redundancy almost by definition.
For some period of time, an old way and a new way may coexist. Two teams may approach the same question differently. Someone may investigate an idea that produces nothing useful. A prototype may duplicate functionality that already exists because the point isn't yet efficiency.
The point is learning.
Resilience and experimentation can look like different problems, but structurally they require something similar: the system has to contain more possibility than today's operating conditions strictly require.
Eventually some paths should disappear. Redundancy doesn't mean preserving everything forever.
It means allowing multiple possibilities to exist long enough to discover which future is worth building.
Sometimes execution is really escalation
I've seen another version of this in organizations that have optimized away too many alternate paths.
The normal process works until something falls outside it.
Then a manager resolves the exception. A director negotiates between teams. An executive makes a call because the system itself cannot.
From the outside, this can look like strong execution. Things keep moving. Leaders are responsive. Problems get solved.
Look more closely and the organization may be borrowing flexibility from hierarchy.
The manager becomes the alternate path. The director becomes the integration layer. The executive becomes the exception-handling system.
If ordinary work repeatedly requires extraordinary intervention, escalation isn't merely a leadership behavior.
It's information about the architecture.
Somewhere, the system needs flexibility it doesn't otherwise contain.
Capacity that looks unused may already be doing work
We tend to recognize capacity when it is visibly producing something.
But some capacity does its most important work by remaining available.
It absorbs an unexpected customer issue without derailing everything else. It gives someone enough time to notice a pattern rather than simply process the next task. It allows one team to help another without abandoning its own commitments. It gives the organization somewhere to put an opportunity it didn't predict.
That can look inefficient on a utilization report.
But 100 percent utilization leaves very little room for reality.
Adaptation rarely announces itself as a planned project. It arrives as interruption.
When every person, system, and process is optimized for maximum utilization, interruption has nowhere to go.
People can become the redundancy
Organizations often discover key-person dependency at the moment someone leaves.
The response is usually documentation: write down the process, record the walkthrough, move the files into the shared drive.
Documentation matters.
It also captures only part of what the person was holding.
Experienced people know which rule matters in which circumstance. They know when a dashboard is wrong, which customer exception is genuinely risky, who needs to be consulted before a change, and what happened the last time the organization tried something similar.
Much of that knowledge is relational and contextual. You can document the decision someone made without transferring the judgment that made the decision possible.
That takes shared experience. People need opportunities to work alongside one another, encounter exceptions, understand the reasoning behind decisions, and develop judgment while the person with the expertise is still available.
A person is not a database. Knowledge transfer isn't simply an exercise in recording what someone knows. It's creating the conditions for other people to learn how to use it.
A person becoming indispensable can be flattering to the person and dangerous to the system.
Often it means several interfaces have collapsed into one human being.
They aren't only doing their job. They're translating, remembering, routing, reconciling, noticing, and absorbing ambiguity for everyone around them.
No single point of failure.
If you have two jobs that matter, you need two people who know enough about each other's work to cover them.
Instead, organizations often have one person doing two jobs.
That can look efficient for a surprisingly long time—right up until something changes.
The answer isn't to make every person interchangeable. Expertise is valuable precisely because it isn't generic.
Shared capacity means allowing knowledge to cross-pollinate before a crisis forces the transfer. Paired work, shared relationships, overlapping context, clear standards, and time for someone else to practice can make an organization less dependent on heroic memory without pretending everyone knows the same things.
Standardization can create capacity. Automation can create capacity. Clear ownership can create capacity.
None of them eliminates the need for slack.
In a young team, stable standards can be one of the best gifts we give people because they reduce unnecessary cognitive load. The point isn't to make every path identical. It's to make the stable parts stable enough that people have somewhere to stand when reality changes.
Ask what the redundancy is doing
None of this means more redundancy is always better.
Multiple systems can create conflicting sources of truth. Overlapping ownership can make accountability disappear. Too many paths can create cognitive load instead of resilience. Capacity can sit unused because nobody made the difficult decision to stop funding it.
Some redundancy really is waste.
But before removing it, I want to know what function it is performing.
Does it create a fallback?
Does it distribute knowledge?
Does it absorb variation?
Does it preserve a choice?
Does it create room to experiment?
Or is it simply duplication whose purpose disappeared years ago?
Those questions lead to a different kind of optimization.
The goal isn't to make everything redundant. It's to decide deliberately where the system should be lean and where it needs room.
Sometimes what looks like excess is where resilience lives.
Sometimes it's where learning happens.
Sometimes it's the only place an unexpected problem—or opportunity—has somewhere to go.
And sometimes the apparent redundancy isn't redundant at all. It's a person quietly holding together several things the organization hasn't learned how to hold without them.
Organizations are taught to be suspicious of redundancy.
Two systems doing similar things? Consolidate them.
Two people who understand the same process? Clarify ownership.
Extra capacity? Improve utilization.
A manual path beside an automated one? Eliminate it.
There are good reasons for this. Duplication can be expensive, confusing, and genuinely wasteful. I've spent plenty of my career removing it.
But redundancy and waste are not the same thing.
Optimization works partly by identifying what appears unnecessary under known conditions. The problem begins when we mistake not necessary right now for not valuable to the system.
A second pathway looks unnecessary while the primary pathway works. Extra capacity looks idle until demand changes. Overlapping expertise looks inefficient until the person with singular knowledge leaves.
Efficiency asks how little a system needs when things go as expected.
Resilience asks what it needs when they don't.
More than one possibility has to remain alive
There is another function of redundancy that gets less attention.
If every resource is committed to current execution, every role is fully utilized, every process has one approved path, and every technology has to justify itself through immediate efficiency, where exactly is the new thing supposed to come from?
Real experimentation contains redundancy almost by definition.
For some period of time, an old way and a new way may coexist. Two teams may approach the same question differently. Someone may investigate an idea that produces nothing useful. A prototype may duplicate functionality that already exists because the point isn't yet efficiency.
The point is learning.
Resilience and experimentation can look like different problems, but structurally they require something similar: the system has to contain more possibility than today's operating conditions strictly require.
Eventually some paths should disappear. Redundancy doesn't mean preserving everything forever.
It means allowing multiple possibilities to exist long enough to discover which future is worth building.
Sometimes execution is really escalation
I've seen another version of this in organizations that have optimized away too many alternate paths.
The normal process works until something falls outside it.
Then a manager resolves the exception. A director negotiates between teams. An executive makes a call because the system itself cannot.
From the outside, this can look like strong execution. Things keep moving. Leaders are responsive. Problems get solved.
Look more closely and the organization may be borrowing flexibility from hierarchy.
The manager becomes the alternate path. The director becomes the integration layer. The executive becomes the exception-handling system.
If ordinary work repeatedly requires extraordinary intervention, escalation isn't merely a leadership behavior.
It's information about the architecture.
Somewhere, the system needs flexibility it doesn't otherwise contain.
Capacity that looks unused may already be doing work
We tend to recognize capacity when it is visibly producing something.
But some capacity does its most important work by remaining available.
It absorbs an unexpected customer issue without derailing everything else. It gives someone enough time to notice a pattern rather than simply process the next task. It allows one team to help another without abandoning its own commitments. It gives the organization somewhere to put an opportunity it didn't predict.
That can look inefficient on a utilization report.
But 100 percent utilization leaves very little room for reality.
Adaptation rarely announces itself as a planned project. It arrives as interruption.
When every person, system, and process is optimized for maximum utilization, interruption has nowhere to go.
People can become the redundancy
Organizations often discover key-person dependency at the moment someone leaves.
The response is usually documentation: write down the process, record the walkthrough, move the files into the shared drive.
Documentation matters.
It also captures only part of what the person was holding.
Experienced people know which rule matters in which circumstance. They know when a dashboard is wrong, which customer exception is genuinely risky, who needs to be consulted before a change, and what happened the last time the organization tried something similar.
Much of that knowledge is relational and contextual. It can't be transferred by listing steps alone.
A person becoming indispensable can be flattering to the person and dangerous to the system.
Often it means several interfaces have collapsed into one human being.
They aren't only doing their job. They're translating, remembering, routing, reconciling, noticing, and absorbing ambiguity for everyone around them.
I once wrote a blunt version of this problem:
No single point of failure.
If you have two jobs that matter, you need two people who know enough about each other's work to cover them.
Instead, organizations often have one person doing two jobs.
That can look efficient for a surprisingly long time—right up until something changes.
The answer isn't to make every person interchangeable. Expertise is valuable precisely because it isn't generic.
Shared capacity means allowing knowledge to cross-pollinate before a crisis forces the transfer. Paired work, shared relationships, overlapping context, clear standards, and time for someone else to practice can make an organization less dependent on heroic memory without pretending everyone knows the same things.
Standardization can create capacity. Automation can create capacity. Clear ownership can create capacity.
None of them eliminates the need for slack.
In a young team, stable standards can be one of the best gifts we give people because they reduce unnecessary cognitive load. The point isn't to make every path identical. It's to make the stable parts stable enough that people have somewhere to stand when reality changes.
Ask what the redundancy is doing
None of this means more redundancy is always better.
Multiple systems can create conflicting sources of truth. Overlapping ownership can make accountability disappear. Too many paths can create cognitive load instead of resilience. Capacity can sit unused because nobody made the difficult decision to stop funding it.
Some redundancy really is waste.
But before removing it, I want to know what function it is performing.
Does it create a fallback?
Does it distribute knowledge?
Does it absorb variation?
Does it preserve a choice?
Does it create room to experiment?
Or is it simply duplication whose purpose disappeared years ago?
Those questions lead to a different kind of optimization.
The goal isn't to make everything redundant. It's to decide deliberately where the system should be lean and where it needs room.
Sometimes what looks like excess is where resilience lives.
Sometimes it's where learning happens.
Sometimes it's the only place an unexpected problem—or opportunity—has somewhere to go.
And sometimes the apparent redundancy isn't redundant at all. It's a person quietly holding together several things the organization hasn't learned how to hold without them.
If the organization stops working when one person leaves, the question isn't only what that person knew. It's what the system had quietly asked them to become.