The Corporate Impotence Cycle

There is a strange phenomenon inside many large organisations that nobody puts on the strategy deck. The people with the most authority often have the least understanding of what is actually happening—not because they are unintelligent, and not because they do not care, but because the further someone climbs from the work, the more their view of reality becomes filtered through dashboards, status reports, steering committees, and carefully curated narratives.

Eventually they stop experiencing the business. They start consuming summaries of the business. That difference is not semantic. It is structural. And it explains a lot of decisions that look rational in the boardroom and absurd on the ground.

What executives actually know

Most senior leaders genuinely believe they understand their organisation. They know the revenue numbers, the quarterly targets, the utilisation rates, the margin pressures, the transformation priorities, and the cost reduction initiatives—often in impressive detail. What they often do not know is how work actually gets done:

The daily friction their employees navigate to hit a deadline.
The shortcuts people take to survive broken processes.
Which systems are creating drag—and which single manager is quietly carrying an entire department.
Where morale actually sits, not where the engagement survey says it sits.

The signals either never reach them, or they only arrive once they have become a crisis: a talented employee resigns, a major client leaves, a delivery failure makes the news internally, a platform collapses under its own complexity. By then the damage is done. The organisation is not surprised by a sudden change in reality. It is surprised by a reality that was obvious to the people doing the work for years.

The cycle

I think of this as the Corporate Impotence Cycle—not impotence in the cheap insult sense, but in the older sense of without power to act effectively. Leadership becomes increasingly detached from operational truth. Detachment produces poor decisions. Poor decisions produce more bureaucracy, more controls, and more reporting. More reporting increases the distance between leadership and the work. The cycle repeats.

The response is almost always predictable: cost cutting, reorganisation, another transformation programme, another operating model, another leadership initiative with a new name and the same missing ingredient. Rarely does anyone stop and ask the uncomfortable question: "When was the last time we genuinely listened to the people doing the work?"

I have sat in enough transformation reviews to recognize the pattern. The deck shows green. The hallway conversation tells a different story. The hallway is not consulted because the hallway does not fit the template—and because consulting it would slow the programme down. That is how you get monolithic product orgs that gate every workflow, agile ceremonies that survive long after the bottleneck moved, and AI pilots that never leave demo because nobody mapped the exceptions the business actually runs on.

Measuring outcomes, ignoring causes

Many organisations have become incredibly sophisticated at measuring outcomes while becoming remarkably poor at understanding causes. They monitor symptoms. They ignore weak signals. They reward narrative coherence over ground truth. Over time they become surprised by problems that were obvious to employees for quarters—or years.

This is not a capacity problem. It is a proximity problem. The answers already exist inside the organisation:

The people closest to customers know where the product breaks.
The engineers know where the bottlenecks are—and which reports nobody reads.
The project managers know which processes waste everyone's time.
The frontline staff know exactly where customers become frustrated.

Leadership has lost the mechanisms required to hear it. Not because those mechanisms never existed, but because layer after layer of abstraction made direct signal feel like noise. When every insight must be translated into a KPI before it counts, most of the useful information dies in translation.

What breaks the cycle

Breaking the cycle is not a culture initiative. It is an operating design problem—and it gets harder, not easier, in the agentic era. When implementation speed compresses, the gap between "what leadership thinks is happening" and "what is actually happening" can widen in weeks instead of quarters. The teams that win will not be the ones with the best model. They will be the ones with the shortest path from signal to decision—something I have written about in the context of the agentic enterprise and micro-teams at the edge.

Practical moves I have seen work—none of them glamorous:

Leaders back in the work, regularly. Not town halls. Not skip-levels scripted by HR. Actual time inside the workflow: listening to a client call, watching a release fail, reading the ticket queue without a filter.
Separate non-negotiables from preferences in governance. Automate the former. Stop convening forums for the latter. Friction is not seriousness; it is a tax on compounding.
Reward early bad news. If the only safe signal is a crisis, you have trained the org to hide problems until they explode.
Build infrastructure that surfaces ground truth. Observability for systems, yes—but also for operations: where work stalls, where handoffs break, where the same exception gets manually resolved fifty times a week.

Businesses rarely fail because reality changes overnight. They fail because they stop listening to reality while it is changing. The Corporate Impotence Cycle is already well underway in many organisations. The uncomfortable fix is not another transformation programme. It is proximity—restoring the mechanisms that let the people doing the work be heard before the crisis makes them impossible to ignore.