When More Control Makes Performance Worse

The signals are easy to miss. Quarterly results are on track. Meetings run smoothly, and decisions appear resolved. But some decisions are revisited weeks later. Fewer hard questions are asked. Strong operators who once challenged assumptions stop doing so. Nothing looks broken. The numbers are acceptable. But sustaining them requires more effort.

This pattern shows up under accelerating change. Markets move faster than planning cycles. Competitive pressure compresses timelines. Investors expect results. Boards expect progress. Conditions are less predictable, yet accountability remains near-term and visible. Slowing down is rarely an option. So the system adapts.

What Accelerating Change Does to Performance Systems

Under accelerating change, organizations move to reduce unpredictability. When conditions are unstable but outcomes must remain predictable, layers of control accumulate. Additional metrics are introduced. Approval checkpoints are added. Status updates become more frequent. Initiatives stack on top of existing priorities.

None of this is irrational. It is a disciplined effort to maintain control over outcomes in unpredictable conditions. If performance cannot slip, more control feels responsible. The assumption is simple: tighter control produces better performance. Over time, attention shifts from improving performance to managing the appearance of control.

The Observable Consequences

When control layers accumulate, nothing fails immediately. Delivery can still look acceptable on paper. Deadlines are met. Dashboards remain green. The cost is not yet visible in the numbers.

As oversight increases, people stop saying what they really think. Hard questions are voiced less often. Assumptions receive less scrutiny. Discussion becomes shorter and more streamlined. The team appears aligned, but the hard conversations have moved elsewhere.

When dissent and friction are filtered out of the room, they do not disappear; they relocate. Decisions that felt resolved resurface when concerns are raised downstream. The system maintains pace, but teams keep reworking the same issues.

The change is also visible in strong operators. They continue to execute, but they stop stretching the work. They deliver what is expected but no longer extend beyond it. The cost is lost discretionary performance.

None of this presents as crisis. It can resemble efficiency. It can even feel like progress. The cost shows up in execution: more rework, later surprises, and more friction during delivery.

This is often the point at which leaders are told to slow down or simplify. When pace cannot slow, simplification becomes the obvious answer. The problem is that simplification requires subtraction.

Why Simplifying Is Hard

Simplifying requires removing something that is already visible: a metric, a meeting, a checkpoint, or an initiative that has already been committed to. In most executive contexts, visible activity signals control. Removing work carries risk. The short-term risk of subtraction is easier to see than the long-term cost of carrying too much.

As a result, systems tend to add oversight rather than remove work. Simplification is correct, but it is harder to execute than it sounds.

What leaders need is not a mandate to simplify, but a way to remove controls without creating unnecessary risk.

Controlled Subtraction

Controlled subtraction is the deliberate removal of a single control layer, under defined conditions, to test whether it is still producing the outcome it was intended to protect.

Instead of attempting to simplify the entire system, leaders remove a single control layer tied to a specific outcome. A reporting step, a checkpoint, a metric, or a meeting is paused for a defined period while the outcome it was intended to protect continues to be monitored.

The objective is information. The test determines whether the risk of removing a control is real or assumed. If performance deteriorates, the control can be restored. If performance holds, the organization has identified a control that is no longer necessary.

Over time, these small removals reveal which layers are protecting performance and which are simply maintaining the appearance of control.

Recalibration as a Leadership Discipline

Accelerating change will not slow down. Control layers will accumulate again. The discipline is knowing when to remove them.

Controls should not be assumed to be permanent. A control earns its place if the outcome it was designed to protect cannot be sustained without it. The method is straightforward: pause the control, monitor the outcome for four to six weeks, and let the data answer the question.

The natural cadence is the reporting cycle. Leaders are already asking whether the organization is performing. The additional question is whether the controls in place are still necessary to sustain that performance. For most organizations, that means at least quarterly, though the principle scales to whatever rhythm the organization already runs on.



In volatile environments, the real discipline is not adding more control. It is knowing what no longer deserves to stay.