Is Another UK Government Tech Disaster on the Horizon? Let’s Talk Welfare and IT
So, the UK Government is at it again. This time, they’ve announced a massive overhaul of the benefits system. According to UK PM Keir Starmer, the current benefits system is “unfair and indefensible” (BBC News). But instead of getting caught up in the political debate around welfare, let’s take a step back and focus on the real ticking time bomb: the technology behind it all.
From applying for benefits online to processing payments through the BACS system, tech is at the heart of these changes. But with the UK Government’s track record on large-scale IT projects, we can’t help but wonder: Is another tech disaster on the horizon?
Let’s break it down and dive into why the government’s history with tech isn’t exactly something to be proud of. And more importantly, what needs to change to make sure we don’t fall into the same traps again.
The UK Government’s Troubling Tech Track Record
Let’s face it: big government IT projects and success rarely go hand in hand. When it comes to large-scale projects, the government has struggled time and time again to meet deadlines, stay within budget, and deliver effective systems that work.
Take Universal Credit, for instance. Introduced back in 2012 to overhaul the welfare system, this project was initially expected to cost £2 billion and be fully rolled out by 2017. Fast-forward more than a decade later, and it’s still not finished! The cost has ballooned to £12 billion, and we’re not expecting the system to be fully operational until 2027. Talk about a never-ending project.
And then we have the NHS National Programme for IT (NPfIT) – a bit more info here. This was supposed to be a game-changer for the NHS, helping modernize and digitize the country’s healthcare system. Launched in 2005 and abandoned in 2013 after billions of pounds were poured into it, the project was ultimately deemed a failure. The result? A huge waste of taxpayer money, missed deadlines, and a massive headache for healthcare professionals who had to navigate the broken system.
It’s not just bad luck either – there are serious issues that keep recurring across these failed projects.
Why Do These Projects Keep Failing?
So, why do these projects keep falling apart? We can pinpoint several factors, but three key issues tend to keep popping up:
Political Accountability: When the Headlines Matter More Than the Outcome
One of the biggest reasons for tech disasters in the public sector is the focus on politics over the actual project. Politicians are often more concerned with how their decisions will look in the media rather than ensuring the technology is designed, tested, and implemented properly. As a result, decisions are often rushed, corners are cut, and the most budget-friendly (rather than needs-appropriate) options are selected.
Imagine this scenario: You’re in charge of selecting a car for the government’s welfare system. You’re told to choose the “best value” for taxpayers, so you pick the cheapest car on the lot. Sounds smart, right? But then, you realize it’s a Smart Car, and it can only fit two people. You were hoping for a Range Rover—something robust, functional, and able to handle the job properly. This is exactly what happens in government IT projects: the cheapest option gets picked, and it simply doesn’t meet the complex needs of the system.
The project suffers because the focus was on cost savings and optics, not on delivering something fit for purpose. This short-sightedness leads to missed expectations and serious failures.
Lack of Stakeholder Engagement: Why Listening to Users Is Key
Next, we have stakeholder engagement. It’s simple: if a system is going to affect millions of people, you must listen to those people. But the UK government seems to often overlook the importance of user involvement during the development and design of their systems.
Take Universal Credit as an example. It was largely a top-down initiative, with decisions about the technology being made without real input from the people who would actually use the system – the claimants. When you design a system that impacts people’s lives, they need to be part of the conversation.
Proper stakeholder engagement goes beyond just collecting feedback from users; it means involving them in the process from the start. The more people feel their voices have been heard, the more likely they are to champion the project instead of fighting it. When users feel engaged, they’ll become advocates and help iron out issues along the way. However, when they’re ignored, frustration builds and leads to active opposition.
As we’ve seen time and time again, the absence of user input can be a fatal flaw in these projects.
A Closed Shop: How Limited Competition Fuels Failure
Let’s talk about the closed shop mentality in government procurement. While this might sound like a term from labor unions, it applies here to a situation where the same companies get selected over and over for government contracts. These companies become so ingrained in the system that there’s no incentive to innovate or deliver real value – after all, they know they’ll keep getting the contract, regardless of how well they perform.
This often leads to complacency, and in some cases, a wall of silence when things inevitably go wrong. A prime example of this is the Post Office Horizon system. It was handed out to ICL (now part of Fujitsu), and despite its glaring issues, the company chose to ignore the problems instead of owning up to them. This even led to wrongful imprisonments of sub-postmasters, who were blamed for errors in the system that weren’t their fault. This “closed shop” approach not only discourages transparency but also reinforces failure. When companies don’t fear the consequences of underperforming, there’s little motivation to improve.
Will the New Welfare System Fall Into the Same Trap?
Given the UK Government’s track record with big tech projects, the question on everyone’s mind is: Is the new welfare system doomed to fail as well?
Sadly, it seems likely that we’re heading down the same road. The government seems to continue focusing on political optics and budget cuts rather than investing in solid planning, user engagement, and effective technology. History has a nasty way of repeating itself, and unless there’s a major shift in how these projects are managed, we could be looking at another drawn-out, expensive, and ultimately ineffective overhaul.
The Importance of Proper Planning
What we’ve learned from Universal Credit, NPfIT, and other government IT failures is that proper planning is absolutely crucial. Instead of rushing into projects, the government needs to spend time designing a clear, realistic roadmap that takes into account the complexity of the task at hand.
Planning must also include a thorough risk assessment, a transparent process for handling potential issues, and a clear timeline for rollouts. This isn’t something that can be decided overnight – it requires meticulous effort and a commitment to getting it right.
Can the UK Government Get It Right This Time?
The burning question is: Can the UK government actually get a tech project right for once?
The answer is yes, but only if they make a fundamental shift in how they approach these projects.
Stop Focusing on the Cheapest Option – in Welfare and everything else!
First and foremost, the government must stop prioritizing cheap solutions that only look good on paper. While cost-saving is important, the focus must be on long-term value and quality. This might mean choosing a solution that costs a bit more upfront, but will work effectively and be scalable in the future.
In other words, the government needs to stop thinking about “value for money” purely in terms of price and instead focus on solutions that will stand the test of time.
Proper Stakeholder Engagement is Key – particularly in Welfare
Second, engagement with stakeholders is critical. The government needs to involve the users – the people who rely on these systems – at every step of the way. For welfare, that means millions that need to be listened to. Listening to their feedback and adapting the system to better meet their needs will make all the difference. Users are the best experts when it comes to designing a system that works, so their input cannot be overlooked.
Break the Closed Shop Mentality
Finally, the government must break the closed shop mentality in contracting. Companies should be selected based on their ability to deliver, not because they’ve been on the roster for years. Open competition, combined with greater accountability and transparency, would encourage companies to actually perform well rather than simply meeting the bare minimum. Our consultancy services are so far from this – it’s almost unrecognisable from what happens in the UK Public Sector.
Final Thoughts: Investing in the Right Projects
The truth is, we need the UK Government to invest in large-scale IT projects that make a real difference. If done correctly, these projects have the potential to radically improve the lives of millions of people. But, as a taxpayer, it’s hard not to feel a sense of dread when we see past failures. For the government to get it right, it will need to overhaul its approach, focusing on proper planning, stakeholder engagement, and accountable contracts. If they can do that, maybe – just maybe – we’ll see a benefits system that actually works and delivers on its promises. Let’s hope they finally get it right this time. We’ve been waiting long enough. And if you’re looking to do a project, but not on this scale, get in contact with us today.
