When execution is blocked by the wrong decision rights

A regulator mandated a change to industry classification affecting a monthly regulatory report.

The organisation executed.

Data capture processes were redesigned.
Source systems were updated.
The data warehouse was adjusted.
Downstream reports were rebuilt.
End-to-end testing was completed.

A large, cross-functional effort.

When the work was finished, only sign-off remained. The regulatory deadline was days away.

Decision authority sat with a mid-level manager.

He had not been involved in the work.
He did not understand the full scope of the changes.

If he approved and the change failed, the investigation would trace back to him.
If he delayed, nothing happened.
If he escalated, he signalled he could not handle the authority assigned to him.

The rational choice was clear.

He did nothing.

He did not review the work.
He did not decide.
He did not escalate.

The team waited.
The deadline closed in.

Execution resumed only after the formal decision path was bypassed.

Additional analysis was prepared.
A senior stakeholder assumed responsibility.

The change was approved.
The deadline was met.

Authority sat with someone detached from the work.

He held veto power without domain knowledge.
He carried full risk if the change was wrong.
He carried no risk if the deadline was missed.

Delay was not incompetence.
It was self-preservation.

The situation required urgency.
The design rewarded delay.

When authority carries consequence for action but not inaction, execution stops.

This failure mode is one surface expression of a deeper structural loop.
The full model is developed in When Failure Becomes Rational.

Read the Book ->

Read the Framework ->

The Author’s Position  ->

Back to Diagnostic Library ->

Previous
Previous

When strategy becomes inexecutable by design