Cases. Patterns. Structural failures.
Each pattern demonstrates the framework applied to a specific organisational failure mode.
These are not standalone observations — they are diagnostic applications showing how decision authority and incentives create rational failure.
When pricing authority is disconnected from economic accountability
A firm absorbed losses when pricing and payment authority were granted without accountability for cost, cash flow, or bad debt.
A senior associate performs well. He delivers consistently.
He brings in new clients.
He is promoted to partner. His compensation changes.
A fixed salary.
Plus a share of fees from clients he originates.
Delivery does not.
Work is still performed by the partner and firm-employed associates. Associate compensation remains fixed.
Pricing authority is granted.
Fees.
Discounts.
Deposits.
Payment schedules.
Discounts increase.
Deposits are deferred.
Payments are delayed.
Work begins before cash is received.
Lower fees reduce the partner’s variable pay. Associate costs remain unchanged.
Outstanding bills accumulate.
Some payments stall.
Some never arrive.
Bad debts form.
Partner salary remains paid.
Associate salaries remain paid.
Losses are absorbed by the firm.
The partner closes engagements.
The firm finances delivery.
This is not misjudgment. The incentives are explicit.
The partner is rewarded for revenue booked.
Not for cash collected.
Not for delivery cost.
Not for bad debt.
Authority over price and payment sits locally.
Economic accountability does not.
The outcome follows.
Deals are prioritised.
Commercial discipline erodes.
Margins collapse quietly.
After two years, the managing partner intervenes.
An external advisor is engaged. The mechanics surface.
The partner is asked to leave. The partner payment structure is redesigned.
The behaviour stops.
Not because people changed. Because incentives did.
This was not human failure. It was structural.
When authority is granted without downside, loss is rational. Redesign only occurs once loss reaches power.
This failure mode is one surface expression of a deeper structural loop.
The full model is developed in When Failure Becomes Rational.
When market insight never reaches authority
A product lost market leadership when a critical insight failed to trigger action due to missing authority and accountability.
The company was the market leader for a product.
That position rested on dominant distributor partnerships.
The model had worked for years.
A new analyst joined the FP&A team.
His remit was reporting.
Not commercial strategy.
While preparing a routine monthly report, a pattern stood out.
No one asked him to pursue it.
He did anyway.
He consolidated internal sales data.
He pulled external market data.
He analysed distributor share trends.
On his own initiative.
The signal was clear.
The distributors underpinning the product’s leadership were already losing share.
The decline was recent.
The acceleration was visible.
If the trend continued, distributor dominance would erode within two years.
He included the analysis in the report. He added recommendations.
He flagged it to his FP&A manager. Nothing happened.
He escalated to his N+2.
Both understood the insight.
Neither owned commercial outcomes.
Neither was accountable for the product’s results.
Ignoring the insight carried no personal cost.
Raising it would create discomfort upstream.
The choice was rational.
The insight was acknowledged.
Labelled “interesting.” Filed.
Not escalated.
It stopped there.
Acting early would have challenged the distribution model.
It would have disrupted entrenched partnerships.
It would have forced uncomfortable decisions.
Waiting was easier. So the system waited.
Within a year, distributor sales collapsed. The product’s market share followed.
Leadership was lost. It never returned.
This was not a failure of intelligence.
The insight was correct.
It was not a failure of effort.
The work was done.
It was a failure of design.
The insight existed.
Authority did not.
Those who saw the risk bore no consequence for inaction.
When insight creates discomfort but not obligation, it does not travel upward. And the organisation pays for what it chose not to confront.
When productivity improvement is not institutionally protected
Improving the work isolated people instead of changing the system.
A new graduate joined a team responsible for monthly reporting and lead generation.
In the first month, he automated his reporting work.
Quality improved.
Turnaround time shortened.
By the second month, the work was finished early.
Overtime stopped.
With time freed, he began producing analysis on top of reporting.
Insights replaced repetition.
Around him, others doing the same work were still working long hours.
One colleague asked for help.
The work was automated.
Overtime dropped.
Encouraged, he shared the idea more broadly. The response changed.
If this is automated, what do I do?
He suggested reallocating effort to analysis and higher-value work. The concern remained.
He raised the issue with his manager. The response was neutral.
You can share with the team.
You can work with the team.
There was no endorsement.
No role redesign.
No progression path.
No signal that improvement would be protected.
Improvement existed, but had no place to land.
Automation stopped where it threatened existing roles.
The new joiner disengaged. He had increased productivity and improved output.
The organisation had no structure to absorb it.
He requested a transfer to another department.
This was not resistance to change.
It was not a lack of initiative.
Productivity gains were permitted only where roles remained intact.
When improvement reduces work without redefining responsibility, it creates risk for those inside the system.
The organisation preserved roles. And removed the opportunity to improve.
This failure mode is one surface expression of a deeper structural loop.
The full model is developed in When Failure Becomes Rational.
When “data-driven” is blocked by design
Intent was declared. Execution never followed
The organisation announced a shift toward data-driven decision-making. A formal data function was established.
Two years later, a basic daily sales dashboard still did not exist.
The data function had no access to sales target data.
Sales targets sat outside the data warehouse.
The function had no authority to access source systems.
Authority to add the data sat with a senior leader who did not report to the data function.
The data function raised the dependency upward. It was rejected by middle management.
No escalation followed.
To keep delivery moving, the data function proposed a workaround.
Users would extract sales targets manually.
Reformat them.
Upload them weekly.
Check them repeatedly so the dashboard could run.
A user attempted to escalate the issue independently. Management did not respond.
Silence replaced decision.
The transformation team became involved.
The dependency was visible.
The constraint was understood.
Escalation to the authority that could redesign access did not occur. Instead, the same workaround was reinforced.
Manual extraction was added on top of the user’s existing responsibilities.
The process was documented.
Standardised.
Maintained.
Manual work became infrastructure.
Data responsibility was assigned.
Data authority was not.
The data function was accountable for insights.
It had no control over access.
No ability to compel integration.
No forcing mechanism when dependencies blocked delivery.
When escalation terminates below authority, redesign does not occur.
Workarounds do.
The organisation wanted data-backed decisions. The design made manual extraction permanent.
This failure mode is one surface expression of a deeper structural loop.
The full model is developed in When Failure Becomes Rational.
When incentives reward visibility over impact
Manual work and data issues emerged after automation was declared complete.
Company HQ rolled out a tool intended to automate an existing manual process.
On paper, the process was common across markets.
In reality, distribution structures, complexity, and required levels of detail varied.
Adopting the tool required more than training.
It required changes to ways of working, system adjustments, and coordination across multiple functions.
Two transformation leads took different approaches. The first prioritised speed and visibility.
Demonstrations were conducted.
Adoption was mandated.
Markets were instructed to use the tool as delivered.
To comply, markets force-fit their existing processes into the system.
Manual steps increased.
Workarounds multiplied.
Additional reconciliation was required to correct mismatches created by the forced fit.
Productivity declined.
Data quality issues surfaced.
Despite this, adoption metrics were met — quickly.
The second lead moved more slowly.
He engaged markets to understand how work actually flowed.
He coordinated alignment across functions.
He pushed through changes to ways of working and supporting systems.
That coordination depended on influence, enabled by direct access to local market CFOs and General Managers.
Both approaches produced visible adoption. Only one reduced manual work.
By the time the consequences of the first approach became visible, the lead responsible had already been promoted.
The costs — increased workload, degraded data, and remediation effort — were borne by local markets and the remaining transformation teams.
There were no repercussions for the decision path that created the damage.
This was not a failure of effort.
And it was not a failure of intent.
It was incentive misalignment.
When speed and visibility are rewarded without accountability for downstream consequences, systems learn to optimise for optics rather than deliver real work.
This failure mode is one surface expression of a deeper structural loop.
The full model is developed in When Failure Becomes Rational.
When strategy becomes inexecutable by design
Partial owners set to compete where collaboration was required.
A Vice President identified an under-targeted customer segment as a growth priority.
She asked three functions to grow it.
Sales.
Product.
Customer loyalty.
Each was accountable.
Each operated from its own domain.
Each knew performance would be compared.
They were competing.
No single owner was appointed to integrate strategy.
No authority was given to resolve trade-offs.
No forum existed where choices had to converge.
Product pushed the offering it believed best suited the segment.
Sales independently pushed a different product it believed would convert better.
Customer loyalty focused on recurring revenue through engagement.
Its messaging aligned with yet another offering.
There was no disagreement.
There was no discussion.
Each function acted within its mandate.
Same customer.
Three messages.
Three products.
Three value propositions.
No reinforcement.
Only interference.
All three strategies depended on the same research and analytics group.
Five people.
Already fully loaded.
Capacity stayed fixed.
Demand tripled.
Each function requested analysis to support its approach.
Each request was urgent.
Each assumed priority.
The research team complied. In parallel.
With no authority to collapse the work into one strategy.
Insights conflicted.
Trade-offs went unresolved.
Resolution required choosing one product, one message, one path.
No one was authorised to decide.
The customer experienced incoherence.
Attention split.
Messaging diluted.
Offers competed.
Conversion failed.
None of the strategies succeeded.
This was not miscommunication.
It was not poor execution.
It was design.
The design rewarded competition
where collaboration was required for success.
Comparison was incentivised.
Integration was not.
When collaboration is required but competition is rewarded,
strategy does not fragment at execution.
It is never executable.
This failure mode is one surface expression of a deeper structural loop.
The full model is developed in When Failure Becomes Rational.
When execution is blocked by the wrong decision rights
Authority was assigned. Accountability did not follow.
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.