Blog - Hornbill

Five public-sector headwinds and how to tackle them

Written by Nigel Martin | 28-May-2026 10:26:36

Public-sector service management is entering one of the most consequential periods of change I have seen in more than 20 years in the ITSM industry.



For many years, IT service management was viewed primarily through the lens of operational control: incidents, requests, changes, service levels, and supplier performance. Those disciplines still matter. In fact, they matter more than ever. But the context around them has changed dramatically. 

Public-sector organisations are now dealing with structural reform, persistent efficiency pressure, legacy modernisation, rising workforce expectations, and the rapid emergence of automation and agentic AI. Each of these forces is significant on its own. Together, they are reshaping what service management must become. 

The challenge is no longer simply to run IT services well. The challenge is to build service management capability that can absorb organisational change, reduce avoidable demand, support digital transformation, govern transition risk, and create better employee experiences at scale. 

Public-sector service management is being reshaped by five major headwinds. Each has a direct implication for transformation. 

1. Structural reorganisation

Public-sector organisations are facing structural change on multiple fronts: unitary reform, trust mergers, ICB boundary changes, shared-service models, and arm’s-length operating arrangements.

For ITSM, this means services must operate across multi-entity, multi-provider, hybrid estates. Organisational codes, policies, approval models, identity structures, and governance arrangements may all be changing at the same time. 

This pushes service management beyond traditional ticket operations. Operating-model design, tenancy strategy, identity management, policy harmonisation, service ownership, and continuity planning become core capabilities. 

How to tackle:  The public sector cannot afford service disruption every time the organisational map changes. ITSM must provide the operational fabric that allows structural reform to happen without breaking service delivery. 

2. Efficiency pressure through 2028–29 

Efficiency pressure is not going away. Public-sector organisations will continue to face demands to do more with less, improve productivity, and demonstrate value from digital investment. 

The service-management implication is clear: organisations must reduce demand, not simply handle demand more efficiently.

Better incident handling is useful, but it is not enough. The real productivity gains come from reducing avoidable contacts, redesigning fulfilment, improving knowledge, automating routine work, removing duplication, and simplifying service portfolios.

How to tackle: A shift in leadership mindset is required. Service desks cannot be treated as the place where inefficiency is absorbed. They must become a source of intelligence about where the organisation is creating friction, failure demand, and unnecessary cost.

3. Legacy estate consolidation and cloud migration

Many public-sector organisations are still carrying complex legacy estates. At the same time, they are under pressure to consolidate platforms, migrate services to the cloud, rationalise applications, and improve resilience. This changes the role of service management. 

How to tackle: ITSM can no longer sit at the end of the lifecycle, waiting to support services after go-live. It must become part of structured transition governance. Transition readiness, cutover control, dependency mapping, service acceptance, knowledge transfer, supplier coordination, and post-go-live stabilisation are now central disciplines. Mature service-management involvement is required to avoid organisations moving technical debt from one environment to another while increasing operational complexity. 

4. Rising workforce experience expectations 

Employee expectations have changed permanently. Public-sector workers now compare workplace services with the best digital experiences they receive as consumers: banking, retail, travel, entertainment, and personal productivity tools. They expect services to be intuitive, joined-up, transparent, and fast. 

They also increasingly use AI in their personal lives, which raises an obvious question: why is equivalent capability not available at work? This turns employee experience into an operational risk issue, not a soft measure. 

Poor service experience creates lost productivity, workarounds, shadow IT, lower trust, and increased support demand. In frontline public services, poor employee experience can also affect service outcomes for citizens. 

How to tackle: Service management must design for experience, not just process compliance. That means understanding journeys, reducing friction, improving self-service, making knowledge easier to consume, and ensuring automation genuinely helps rather than simply deflects demand. 

5. Automation and AI expansion 

Automation and AI are now central to the future of service management. But the opportunity comes with risk. 

Agentic AI can act across workflows, make decisions, invoke tools, and execute tasks based on available data, rules, and access rights. That is powerful. It is also unforgiving. 

If data quality is poor, if access controls are weak, if knowledge is outdated, if workflows are inconsistent, or if governance is unclear, agentic capability can create new risks faster than traditional controls can respond. 

How to tackle: Governance, auditability, access control, and data fitness are prerequisites for safe scale. The organisations that benefit most from AI will not simply be those that buy AI capability first. They will be the organisations that have prepared their service-management foundations: clean data, clear ownership, reliable knowledge, mature workflows, strong governance, and measurable outcomes. 

What does this means for ITSM leaders?

For public-sector ITSM leaders, the message is clear. Service management must move from operational support function to transformation enabler. That does not mean abandoning ITIL disciplines, service desks, incident management, request fulfilment, change control, or supplier governance. It means applying those disciplines in a broader context. 

The next phase of public-sector ITSM will be defined by the ability to: 

- Support structural change without service disruption
- Reduce avoidable demand rather than simply process it
- Govern transition across legacy, cloud, and hybrid estates
- Design better employee experiences
- Prepare the organisation for safe, scalable automation and AI

The data suggests that organisations with active transformation programmes are better positioned, but many still operate in waves that decay over time. Meanwhile, organisations without defined transformation workstreams risk slipping back into fragmented improvement activity, even after the lessons of the pandemic. 

The public sector cannot rely on episodic transformation anymore. The pace of change is too fast. Employee expectations are too high. Efficiency pressure is too sustained. The AI opportunity is too significant, and the risks of weak foundations are too great. 

What action should public-sector service management leaders take?

After two decades in this industry, one thing is clear to me: ITSM has always evolved when the operating environment demanded it. We saw it with the rise of ITIL. We saw it with outsourcing and managed services. We saw it with cloud. We saw it again during the pandemic, when service teams became essential to organisational continuity almost overnight. We are now at another inflection point. 

The future of public-sector service management will not be defined by who has the most tickets, the most workflows, or the most automation scripts. It will be defined by who can create a resilient, adaptive, data-driven service operating model that supports continuous transformation.

For public-sector organisations, that means service management must become more strategic, more integrated, and more persistent. Transformation can no longer be a three-year cycle. It must become a core organisational capability. 

If you would like to learn more about how Hornbill can help you with addressing the adapting needs of ITSM in the public-sector take a look at how we are helping organisations adopt AI with guardrails and governance.