Month: February 2026

Public sector integration doesn’t usually fail because it’s complex. It fails because its risks are predictable, poorly surfaced, and rarely owned.

Seven places reform derails

Decision Rights Ambiguity

Dual Accountability

Business as Usual Dominance

Capability Overestimation

Cultural Drift Disguised as Progress

Change Treated as Messaging

Assurance Focused on Reporting, Not Reality

In this article, our CEO John Dean explores the integration risks that derail public sector reform – not the ones on the risk register, but the ones that emerge in how decisions, accountability, and delivery actually work in practice.

Public sector integration is often described as complex. That description is unhelpful. 

What matters is not that integration is complex, but that its failure points are predictable. They recur across sectors, structures, and reform agendas, regardless of intent or political sponsorship. 

Most organisations recognise the risks. Fewer understand how they materialise. 

Decision Rights Ambiguity

The most common failure point, and the least explicitly owned. Integration collapses when people do not know: 

• who can decide
• when they can decide
• what happens when priorities conflict

On paper, governance looks clear. 
In practice, decisions stall at the boundaries between legacy organisations, national and local authority, policy and delivery. 

The system becomes cautious, then slow. Speed is lost not through resistance, but through uncertainty. 

Dual Accountability

People are asked to integrate, while still being held accountable for legacy outcomes. This creates a rational contradiction: 

• leaders are told to collaborate
• but performance frameworks still reward silo delivery 
• budgets remain segmented
• risk is still owned individually

Integration becomes optional behaviour layered on top of non-integrated incentives. 
The organisation says ‘one system’. The measures say otherwise. 

Business as Usual Dominance 

Integration is treated as a programme. Business-as-usual treats it as background noise. 

When delivery pressure increases, integration activity is the first thing dropped: 

• joint forums are postponed
• shared processes quietly bypassed
• temporary workarounds become permanent

This is not sabotage. It is survival.  Unless integration is designed to support delivery, delivery will always defeat integration. 

Capability Overestimation 

There is an assumption that integration is a leadership stretch goal, not a specialist discipline. In reality, integration demands: 

• systems thinking
• behavioural change under constraint
• operational transition planning
• and live decision arbitration

Most teams have deep domain expertise. 
Few have experience of running multi-organisation transitions while maintaining service continuity. 

The gap is rarely acknowledged until momentum is lost. 

Cultural Drift Disguised as Progress

Early signs of failure are subtle and often misread as ‘settling in’. 

Indicators include: 

• increased escalation without resolution
• polite agreement without follow through
• parallel processes re-emerging ‘temporarily’
• growing reliance on informal relationships to get work done

By the time these symptoms are visible at senior level, the integration has already hardened into a hybrid state that is difficult to unwind.

Change Treated as Messaging

Communication increases as clarity decreases. Roadshows, briefings, and updates multiply, but frontline questions remain unanswered: 

• What has stopped? 
• What has changed? 
• What happens if we disagree? 

When change is reduced to narrative rather than operational instruction, people improvise. 
Improvisation produces inconsistency. Inconsistency produces risk. 

Assurance Focused on Reporting, Not Reality

Integration assurance often measures activity, not effectiveness. Progress reports look positive: 

• milestones met
• forums established
• documents approved

Meanwhile: 

• decisions are slower
• interfaces are noisier
• accountability is blurred

By the time performance issues surface externally, the internal narrative is already out of sync with reality. 

The Pattern Behind the Pattern 

These risks do not arise because public bodies lack commitment or competence. 

They arise because integration changes how power, accountability, and decisions flow, and those changes are rarely made explicit enough, early enough, or operationally enough. 

This is not a culture problem. It is a design and transition problem. 

Why Some Organisations Avoid These Failure Points

Successful integrations do not eliminate risk. They surface it early and manage it deliberately.  

• make decision rights visible and test them in live scenarios
• align incentives before asking for behavioural change
• embed integration capability alongside delivery
• and treat readiness as seriously as governance

They recognise that integration is not an initiative. It is a change in how the system actually works. 

A final observation

Most public sector integrations fail quietly, not dramatically. They settle into something that is almost integrated but harder to manage than what came before. 

The difference between those outcomes and genuine integration is not ambition or policy. It is whether the organisation designs for these risks or discovers them too late. 

I’d love to hear from you. Share your experience in the comments, I find great learning often comes from real world stories.

Contact me, John Dean, or the wider team at Change Specialists. You can Follow Change Specialists to access insights and practical tools to support successful project management.