A practical guide for senior leaders responsible for regulatory delivery
Regulatory programmes rarely fail overnight. They start to drift.
A milestone moves. A remediation action remains open. Decisions take longer. Dependencies multiply. Governance becomes increasingly focused on reporting rather than resolving problems. Delivery teams become stretched while senior stakeholders receive increasingly complex updates without a clear view of what is actually happening.
For Chief Risk Officers, Heads of Risk, Heads of Change, Heads of Regulatory Change, Compliance leaders, COOs and senior Programme Directors, this is where intervention matters.
The question is not whether the programme has problems. The question is whether you still have enough control to recover it.
Brickendon works with financial institutions to stabilise complex regulatory and transformation programmes, identify the issues preventing progress and put delivery back on a controlled path.
1. Know when the programme is genuinely off track
A programme can appear broadly healthy while critical problems are developing underneath.
Traditional status reporting can mask the reality of delivery. A programme may remain Amber while key remediation actions continue to slip, critical dependencies remain unresolved or teams lack the capacity required to meet regulatory commitments.
Warning signs include:
• Repeatedly missed milestones
• Remediation actions moving between reporting periods
• Increasing numbers of risks and issues without clear resolution
• Decisions waiting for escalation or executive approval
• Dependencies between Risk, Compliance, Technology, Finance and Operations remaining unresolved
• Delivery teams relying on manual workarounds
• Governance meetings becoming focused on explaining delays rather than removing them
• Senior management receiving inconsistent information from different workstreams
• Regulatory commitments depending on activities that are not yet sufficiently controlled
The critical point is that individual problems rarely exist in isolation.
A delayed technology dependency can prevent remediation. A resource constraint can delay testing. Poor ownership can prevent decisions. Weak governance can allow all three to continue unnoticed.
Experienced programme operators look beyond individual workstreams to understand the system causing the programme to drift.
2. Establish what is actually preventing delivery
The first step in recovery is not adding more meetings. It is establishing the facts.
When a regulatory programme is under pressure, senior leadership needs a clear view of the current delivery position, the reasons behind it and the actions required to change it.
A focused recovery assessment should establish:
• What has actually been delivered
• What remains outstanding
• Which milestones are genuinely at risk
• Which dependencies are blocking progress
• Where ownership is unclear
• Which risks require immediate intervention
• Whether available resources match the delivery requirement
• Whether governance is enabling decisions or creating additional delay
• Whether the existing plan remains achievable
• What regulatory commitments could be affected
This creates the evidence required to distinguish between a programme that needs additional support and one that requires fundamental intervention.
The objective is not to produce another assessment document. It is to create a fact based recovery plan that leadership can act on.
3. Regain control before accelerating delivery
Acceleration without control creates more risk.
When programmes fall behind, organisations can respond by adding resources, increasing meeting frequency or pushing teams to work faster.
That rarely addresses the underlying problem. Recovery requires control first.
Brickendon’s approach focuses on establishing clear ownership, decision making, priorities, dependencies and measurable delivery outcomes.
This can include:
• Rebuilding the integrated programme plan
• Reassessing critical path activities
• Establishing clear accountability across workstreams
• Strengthening governance and escalation routes
• Creating transparent dependency management
• Prioritising remediation based on regulatory and business impact
• Aligning resources to the activities that genuinely determine delivery
• Introducing focused executive reporting
• Establishing measurable recovery milestones
The result is a programme where leadership can see what matters, understand what is blocking delivery and intervene before problems become larger.
4. Move from reporting problems to resolving them
A regulatory programme does not recover because its status report becomes more accurate. It recovers because problems are resolved.
This requires governance that drives decisions rather than simply records them.
Senior leaders need to know:
What is blocked?
Who owns it?
What decision is required?
When must it be resolved?
What happens if it is not?
These questions create accountability.
They also expose whether governance is genuinely controlling the programme or simply documenting its deterioration.
Effective recovery governance creates a direct connection between issues, decisions, actions and outcomes.
That is particularly important where regulatory commitments involve multiple functions, jurisdictions or technology platforms.
5. Protect the regulatory outcome
The ultimate measure of recovery is not whether a programme has fewer Red statuses.
It is whether the organisation can deliver the required regulatory outcome with confidence.
For programmes connected to PRA, FCA or ECB expectations, this means maintaining a clear line of sight between regulatory commitments and delivery activity.
Every major action should connect to an outcome.
Every material risk should have an owner.
Every critical dependency should be visible.
Every significant delay should have an agreed response.
This is where experienced delivery leadership becomes essential.
Regulatory transformation sits across business, risk, compliance, data, technology and operations. Recovery therefore requires someone capable of connecting those areas rather than managing them as isolated workstreams.
What experienced operators do differently
When a programme starts to slip, experienced operators do not immediately add more process.
They simplify.
They establish the facts.
They identify the critical path.
They expose the dependencies.
They clarify ownership.
They make decisions.
They focus resources on the activities that determine the outcome.
Most importantly, they act before the programme becomes significantly harder to recover.
This is the difference between programme management and programme recovery.
Recovery is intervention with a clear objective: restore control, remove the blockers and get delivery moving again.
When regulatory delivery is under pressure, act early
A regulatory programme under pressure rarely improves through passive monitoring.
The longer issues remain unresolved, the more dependencies accumulate. The more dependencies accumulate, the harder recovery becomes. Eventually, the cost of intervention increases while the available options narrow.
Brickendon supports financial institutions when critical programmes need experienced intervention.
We combine programme delivery, regulatory change, governance, risk, technology and transformation expertise to identify what is preventing progress and put the right structure around recovery.
We do not simply tell you that your programme is off track. We help get it back on track.
Is your regulatory programme under pressure?
Do not wait for the next missed milestone or regulatory escalation.