Failing banking programmes rarely collapse without warning. They show clear signs of stress long before failure becomes visible, but those signals are often ignored, softened, or misinterpreted. By the time leadership recognises the programme is off-track, delivery confidence has already declined, timelines are compromised, and recovery is materially harder. The difference between programmes that recover and those that fail is not effort. It is how quickly the underlying issues are identified and whether the intervention addresses the real causes rather than the symptoms.
When programmes go off-track, the default response is to:
This does not fix the problem.
Failing programmes are not short on effort. They are structurally misaligned.
The underlying issues are consistent:
Unless these are addressed directly, recovery will fail regardless of how much pressure is applied.
Before recovery starts, one question matters:
Is the programme still structurally recoverable?
A proper diagnostic is fast, focused, and direct. It assesses:
Is there one person who truly owns the outcome, or is ownership distributed across functions?
If accountability is unclear, recovery has not started.
Are decisions made quickly and owned, or repeatedly escalated without resolution?
Slow decisions are one of the strongest indicators of programme failure.
Are plans actively managed and enforced? Are dependencies understood and tracked in real time?
If delivery is not controlled, timelines are already unreliable.
Are experienced operators embedded in execution, or is delivery reliant on leveraged, junior-heavy teams?
Recovery requires experience at the point of execution, not layers of oversight.
Are business, technology, and control functions aligned on outcomes, or operating with competing priorities?
Misalignment will surface as rework, delay, and conflict.
Is there a credible narrative with regulators, or are gaps emerging in governance, controls, or delivery transparency?
Loss of regulatory confidence accelerates programme risk quickly.
If multiple areas show weakness, the programme is already under pressure whether formally recognised or not.
Recovery is not about redesigning the programme.
It is about regaining control first.
Objective: Stop further deterioration.
Actions:
At this stage, speed matters more than perfection.
Objective: Fix the structure that caused failure.
Actions:
This is where most internal recovery attempts fail because structural issues are avoided.
Objective: Restore delivery confidence.
Actions:
Momentum is created through consistent execution, not planning.
Objective: Sustain delivery under pressure.
Actions:
Recovery is complete when delivery becomes predictable again.
Even when recovery is attempted, failure is common.
The reasons are predictable:
Recovery is not a softer version of delivery. It is a different discipline.
The earlier a programme is stabilised:
Delay reduces optionality.
At a certain point, programmes move from recoverable to critical, and then to unrecoverable.
Most organisations do not recognise when that line is crossed.
Brickendon is brought in when programmes are off-track, losing control, or too critical to fail.
We do not advise from the sidelines.
We take full accountability for recovery and delivery, embedding senior operators directly into execution. We reset governance, ownership, and delivery control, and stabilise programmes quickly before driving them through to completion.
No leveraged teams.
No separation between oversight and execution.
Just control, clarity, and delivery under pressure.
Failing programmes are predictable.
So is recovery, if intervention happens early and focuses on the right issues.
If accountability is unclear, decisions are slow, and delivery confidence is declining, the programme is already under pressure.
And if it cannot fail, waiting is not a strategy.
Confidential. No obligation. Senior conversation from day one