The Accountability Spectrum: Why 'holding people accountable' is a confession of failure

In a previous briefing, we looked at the Data/Intelligence Spectrum. Now we look at the mechanism that dictates what people do with that intelligence: The Accountability Spectrum.

A key indicator of a failed architecture

When a CEO or an Executive says, "We need to hold people accountable," it sounds like strong leadership. It is not. It is usually a performative confession of failure.

It tells us that the organisation relies on retroactive punishment rather than proactive alignment. You do not need to "hold people accountable" in a resonant organisation because accountability is architected directly into the social structure. It is assumed, visible, and structurally unavoidable.

When accountability has to be demanded, the architecture has already failed.

Authority versus responsibility

The foundational error of the Industrial Operating System (IOS) is the belief that you can delegate responsibility without delegating authority.

In a Dissonant organisation, responsibility is pushed down the hierarchy, while authority is hoarded at the top. The people doing the work are held responsible for the outcome, but they lack the authority to change the process, allocate the budget, or alter the timeline.

This creates a structural double-bind. When the project inevitably fails, the people at the bottom are blamed (they had the "responsibility"), while the people at the top are insulated (they only had the "authority").

The danger of plausible deniability

Dissonant organisations do not build structures for accountability; they build structures for Plausible Deniability.

Look at the modern corporate matrix. We rely on cross-functional steering committees, massive RACI matrices, and consensus-driven decision-making - ensuring that, if everyone decides, then no one decides. If a project fails, the failure is diffused across a committee. No single individual's fingerprints are on the murder weapon.

While this may be couched as collaboration, it is very much about liability management.

Why boards should care: the cost of zombie projects

Displaced accountability is not just an HR issue; it is a massive financial liability.

When authority and responsibility are severed, no one feels empowered to kill a failing initiative. Projects limp along for years, consuming capital and resources, because the person who knows it is failing does not have the authority to stop it, and the person with the authority refuses to take responsibility for the sunk cost.

This inability to kill failure can cost a large organisation tens of millions annually in sunk costs.

Learned helplessness and the refusal of ownership

Neuro-economics reveals that when an animal is punished for outcomes it cannot control, it eventually stops trying to affect the outcome at all. It freezes.

In a Dissonant system, we punish people for outcomes they did not have the authority to prevent. The brain adapts by wiring for risk aversion. We condition our people to seek "plausible deniability" rather than results. We teach them that survival depends on process compliance, not value creation.

The Boeing conundrum

The intersection between Displaced Accountability and Systemic Signal Suppression contributed to recent high-profile corporate failures including NASA, the 2008 crash, and Boeing.

Following its 1997 merger with McDonnell Douglas, Boeing’s engineering-first culture was systematically dismantled by a management philosophy focused on financial metrics, cost control, and shareholder returns. When Airbus launched a competitor in 2010, Boeing chose finances over engineering, updating the existing 737 rather than designing a new aircraft. Engineers identified critical safety concerns with the resulting MCAS software, but their warnings were overridden by program managers focused on certification timelines and cost targets.

Boeing and the FAA

The relationship between Boeing and the Federal Aviation Administration (FAA) has been heavily scrutinised following the 737 MAX crashes in 2018 and 2019.

The FAA delegated significant safety oversight and certification tasks to Boeing’s own engineers, essentially allowing the company to "regulate itself". A U.S. House of Representatives report concluded the FAA was "captured" by Boeing’s commercial interests, leading it to ignore its own technical experts.

This Regulatory Capture, also see in such industries as Banking, Pharmaceutical, Energy, and Transportation are examples of where the regulatory agency prioritises the commercial interests of the firms it oversees over the public interest, essentially functioning as an advocate for the industry rather than an independent watchdog.

Specific to Boeing, the approach of prioritising speed to market and cost savings over fundamental safety set in motion a chain of decisions that killed 346 people in two preventable crashes, exposing an environment where safety advocacy had become career suicide.

The result is a system where no one owns the risk, and no one is allowed to report it.

1. Displaced: Regulatory capture creates a blurred line between the regulator and the manufacturer. Who owns the safety certification? The lines are blurred.

2. Suppressed: Engineers who see risks are ignored or sidelined because "the schedule" is the priority.

Next steps

We have structure, intelligence, measurement, and accountability. But do our words match our actions?

In the next briefing, we explore the source of all corporate cynicism: The Coherence Spectrum. We will look at why the "say-do gap" is the most expensive liability on your balance sheet.