Until the New Capability Exists, the Old System Is Still in Charge

A leader can see the signal and still lose the organization.

That is the hard lesson inside Amanda Taub’s New York Times article, “Actually, Democracy Dies in H.R.” The article examines research on how authoritarian systems recruit lower- and mid-level workers to do the work of institutional decay. The disturbing insight is not that every participant is a zealot. Often, the system does not need zealots. It needs career pressure, weak standards, a second ladder for advancement, and people willing to trade judgment for opportunity.

For enterprise leaders, the lesson is not only political. It is organizational.

Variance is signal. But a signal does not become useful because it exists. It becomes useful only when the organization has the capability to receive it, interpret it honestly, act on it, and make the learning hold. Until that capability exists, the old system remains in charge.

That is why the first phase of building organizational capability is so fragile. The leader may want truth. The current system may want protection. The leader may want learning. The current system may want continuity. The leader may want Sustained Competitive Advantage. The current system may be organized around the perceived truths, incentives, and cultural habits that made the new capability necessary in the first place.

The Existing System Processes the First Signal

The New York Times article describes research from Adam Scharpf and Christian Glassel on Argentina’s Dirty War. Their work found that low-performing military officers could use service in the secret police as a career detour. The ordinary hierarchy had standards. The detour created another path. Officers who were unlikely to advance through the normal system could gain promotions, compensation, and status through work the institution should have rejected.

The pattern is severe in that context, but the organizational principle is broader: systems teach people how to survive and advance.

Every organization has formal values. It also has working truths. The working truths are the assumptions people learn through consequences. They answer practical questions:

• Which problems are safe to name?
• Which leaders can be challenged?
• Which metrics matter more than the stated mission?
• Which failures are punished, hidden, or reframed?
• Which behaviors actually get people promoted?

When those working truths are misaligned with the capability a leader is trying to build, variance becomes politically dangerous. Not necessarily political in the partisan sense. Political in the organizational sense. It threatens status, budget, identity, authority, or the story a leadership team has been telling itself.

A signal that threatens the perceived truth of the organization will not travel neutrally. It will be filtered by the system that receives it.

Variance Often Contradicts the Story

Leaders often talk about wanting transparency. The harder question is whether the organization can tolerate what transparency reveals.

Variance rarely arrives as an abstract data point. It usually arrives as a contradiction.

• The strategy says the company is customer-centric, but renewal conversations show trust is weakening.
• The culture says people speak up, but employees know which topics shorten careers.
• The talent system says excellence is rewarded, but promotion patterns reward loyalty, speed, or silence.
• The operating model says the business can scale, but handoffs fail whenever volume increases.
• The leadership team says it is aligned, but decisions reveal competing priorities.

Each of these is variance. Each is signal. Each is also inconvenient.

This is where many capability-building efforts break down. Leaders assume that because the signal is visible, the organization will act. That assumption is false. Organizations do not act on signals simply because they are rational. They act on signals when the system makes it safe, useful, and expected to do so.

Without that capability, the old system does what old systems do. It protects itself.

It may suppress the signal. It may reinterpret the signal as an attitude problem. It may punish the person who raised it. It may turn the signal into a task force, a slide deck, or a language exercise that allows everyone to feel responsive without changing the operating reality.

That is the first risk in building organizational capability: the current organization is the first interpreter of the signal.

Related video: Watch the full breakdown here

Capability Cannot Be Delegated Too Early

This is why leadership involvement matters most at the beginning. A leader cannot announce a new capability agenda, assign it to a function, and expect the organization to transform its own response to variance. The legacy system will process the new agenda through legacy incentives.

If the culture has learned that bad news creates risk, people will sanitize the signal before it reaches the room. If promotion has favored internal loyalty over external truth, people will frame variance in ways that protect sponsors and power centers. If past initiatives created fatigue, people will treat the new language as another cycle to endure. If the organization has cultural scars from earlier efforts that launched but never held, people will wait for this effort to fade too.

The leader’s first job is therefore not simply to ask for variance. It is to protect variance long enough for the organization to learn what to do with it.

In EdgeFinder terms, this is the early discipline of building the capability for Sustained Competitive Advantage: the ability to convert emerging variance into durable gain, repeatedly. That conversion is not automatic. It depends on organizational muscle.

Strategic Meta Skills provides that capability system. It helps the organization sense meaningful variance, determine whether the response requires optimization or transformation, shape the move, and align the Pack so the response can hold. But in the earliest phase, those skills are not yet installed. They are being built.

Until the new capability exists, the old system is still in charge.

That sentence should sit on every leader’s desk during the first phase of capability-building.

The Leadership Role Is to Protect the Signal

Leadership-protected sensing is the first phase. It is not micromanagement. It is not executive theater. It is the temporary leadership discipline required while the organization learns how to surface, classify, and act on variance without distorting it.

In this phase, leaders need to watch the system, not just the metric.

They need to ask what happens after a signal appears. Does it move? Does it get softened? Does it get trapped in a function? Does it get converted into blame? Does it become a political threat? Does the person who raised it gain credibility or lose standing?

The answer tells the leader whether capability is forming or whether the old system is absorbing the new language.

Several leadership disciplines matter here.

1. Inspect promotion logic. The system’s real values are visible in who advances. If the organization claims to value judgment but promotes people for loyalty, speed without discipline, or the ability to shield leaders from discomfort, it is building the wrong capability.

2. Protect inconvenient truth-telling. Early variance often comes from people close to the work. If those people learn that surfacing reality creates career risk, the sensing system will collapse before it matures.

3. Separate signal from blame. Variance should not become a hunt for offenders. The first question is what the system is revealing. Personal accountability still matters, but blame-first cultures destroy signal quality.

4. Tune attention quickly. Not every signal deserves the same response. Leaders must help the organization distinguish noise from the variance that matters most now. Tuning is the discipline of aligning effort around the variance that matters most now. Without it, sensing creates overload.

5. Fortify the learning. If the organization detects a signal and makes a move, the gain must hold. Fortify means embedding the change into routines, handoffs, incentives, and expectations so the system does not revert under pressure.

These disciplines are not permanent executive dependency. They are scaffolding. The goal is to create an organization that eventually does this without constant senior intervention.

The Pack Must Learn to Act Together

Capability is not built inside one heroic function. It forms across the Pack: the smallest complete set of interdependent capabilities and handoffs that must move together to keep a customer promise reliably.

That distinction matters. A team can see variance and still be unable to act if the rest of the Pack is not ready. Sales may hear the market changing. Product may see usage shifting. Operations may see failure patterns first. Customer success may hear trust weakening before the dashboard confirms it. Finance may see margin pressure before strategy names the cause.

Any one of these signals can be valuable. None of them becomes Sustained Competitive Advantage until the Pack can move together.

This is where political risk often appears. A signal from one part of the Pack may imply that another part must change. A customer signal may challenge the product roadmap. An operational signal may challenge the growth plan. A talent signal may challenge a favored leader. A financial signal may challenge the narrative behind a strategic bet.

If the Pack cannot absorb that tension, variance becomes internal politics. Functions defend themselves. Leaders protect prior commitments. Metrics are selected to support the preferred truth. The organization keeps moving, but it is no longer learning at the rate the environment requires.

Sustained Competitive Advantage requires a different response. The Pack must develop the shared capability to treat variance as intelligence, not accusation. That is how the organization converts signal into action and action into durable gain.

The Bottom Line

The New York Times article offers a stark reminder that institutions are shaped by the people systems beneath them. Career pressure, weak standards, second ladders, and distorted incentives can turn ordinary organizational behavior into institutional risk.

For business leaders, the lesson is direct.

Variance is signal, but capability determines what happens next.

If the organization lacks the capability to act on variance, the signal will not become advantage. It will be suppressed, reinterpreted, politicized, or punished. The system will protect its perceived truth instead of investigating reality.

That is why leaders cannot delegate the first phase of capability-building. They must remain directly involved until the right operating systems, incentives, cultural norms, and Pack-level routines are installed.

Only then can the organization do what Sustained Competitive Advantage requires: convert emerging variance into durable gain, repeatedly, under pressure and at pace.

Until then, the old system is still in charge.If your organization is seeing signals it cannot yet act on, or if the current system keeps protecting the old story, let’s talk. I help leadership teams build the capability to turn variance into durable advantage.