Why housing & public-sector IT projects keep failing
It’s a story we’ve heard a hundred times, and one we’ll likely hear a hundred more. A local authority announces a bold new digital transformation programme with a housing management system at its core. There’s a press release, newsletters to the tenants and a general flurry of optimism.
After that? Months pass, deadlines slip and costs balloon. The system doesn’t do half of what was promised. Fingers are pointed…
And through it all, the same question lurks behind every closed-door review: why do these public-sector IT projects keep falling apart?
I’ve spent more years than I’d like to admit working in and around public-sector transformation projects, including in housing. I’ve seen the same patterns play out across councils, housing providers and government agencies. And while it’s easy to lay the blame at the feet of suppliers, software platforms or overwhelmed project teams, the real rot starts at the top.
More often than not, it’s not team incompetence or system complexity that sink these projects. It’s senior management’s self-preservation.
Let’s walk through what’s really going on behind those locked boardroom doors.
Deadlines set by politics, not possibility
Project milestones in the public sector are often set not because they’re achievable but because someone senior needs to be able to say, “We’re going live in Q4.”
The problem isn’t ambition; it’s that these dates aren’t tied to any realistic assessment of scope, resource or risk. They’re set because someone in a leadership role wants to stand up at a council meeting and make a bold claim.
Deadlines in the public sector aren’t project milestones, they’re political statements. And when reality inevitably bites, such as when legacy data proves harder to migrate or integrations take longer than expected, the reaction isn’t calm analysis, it’s panic.
The typical response of senior management is:
- Pile the pressure on already overstretched teams;
- Make arbitrary demands of suppliers to imply they have failed in some way;
- Shift accountability down the ladder;
- Shoot the messenger.
This isn’t about solving problems; it’s about being able to say, “We did everything we could, they let us down and it’s not our fault.”
Governance that deflects, not directs
Governance should be a guiding hand to ensure direction, clarity and responsible use of public funds. But in too many housing departments, governance has become a convenient shield.
The playbook is familiar. Pick a ‘trusted’ supplier, sign a hefty, jargon-laden contract, create a RAG report template, tick all the right boxes and then stand back and hope it all just works.
Of course, when it doesn’t, there’s a frantic scramble to distance the leadership team from blame. Out come the excuses:
- “The supplier misunderstood our requirements.”
- “The contract didn’t explicitly include that.”
- “We assumed that part was a supplier’s responsibility.”
I’ve seen it time and again – governance reinterpreted not as a safety net but as a stage for ‘blame theatre’. The goal isn’t to learn or adapt, it’s to create a paper trail that points in every direction but up.
The sudden panic – Handover hysteria
You can almost mark your calendar by it – the moment when the ‘handover demands’ arrive.
Late in the project, often after months of silence, senior leadership suddenly wants every line of code, every project note, every version of history… by Friday.
This flurry of panic usually coincides with the dawning realisation that the project is ‘going south’ and someone is going to ask why.
But instead of stepping in to help and taking the necessary actions that the project has been demanding for months, the senior leadership reaches for the nearest available lever to prove, on paper, that someone else dropped the ball.
It’s not about salvaging the project; it’s about covering their own backs
As a consequence, contracts get reinterpreted on the fly, conditions are invented and payments are withheld. And the delivery partner, whether in-house or external, is buried under a mountain of invented obligations, all in the name of plausible deniability.
The vanishing act – Silence from the top
Here’s how it typically goes.
Everyone’s present at the kick-off meeting, the executive sponsor delivers a rousing opening speech, the senior stakeholder chairs the first two steering meetings, there are handshakes, smiles, maybe even pastries. Then… nothing.
Weeks go by and steering group attendance drops, emails go unanswered, decisions stall and project teams are left to make it up as they go.
Until something goes wrong. Suddenly, the senior leadership reappear, all stern-faced and armed with excuses. The same suppliers they praised in Month Two are now branded ‘non-performers’ in Month Ten. Reports are rewritten, committees are convened and heads are demanded.
By then, it’s too late. The project is wounded, morale is in the bin and the budget’s long gone.
When ego costs millions
All of this might be grimly entertaining if it wasn’t so expensive.
Projects that should have delivered lasting transformation get stuck in endless recovery loops. Good suppliers walk away or get burnt. New suppliers charge a premium because they know they’re entering a political minefield.
And the real losers? Frontline staff and tenants. The people who need housing systems that actually work and for whom ‘digital transformation’ is supposed to deliver better, fairer and faster services.
Instead, they get clunky work-arounds, paper forms and a system that takes ten clicks to do what should take two.
All because the people at the top couldn’t bear to say, “We got it wrong.”
What it really takes to fix this
Let me be blunt – this isn’t a process problem, it’s a people problem.
You can have the best framework in the world, the slickest project plan and the most competent delivery team but if the leadership culture is one of fear, ego and self-preservation, failure is all but guaranteed.
What’s the fix? Here’s where we start:
- Senior leadership must own the delivery, not just the vision. You can’t delegate accountability; you have to be present, supportive and engaged throughout.
- Start dealing with problems early, not when the walls are on fire. If something’s drifting, fix it. Don’t wait for the quarterly review to make it someone else’s fault.
- Act with integrity. Celebrate the wins, sure, but own the losses too; that’s what real leadership looks like.
Because yes, public-sector IT projects can work, but only when leaders are brave enough to stay in the room when things go wrong, not just when the cameras are rolling.
Time to end the cover-up culture
We don’t need another transformation strategy. We don’t need another supplier review or governance rebrand. We need leaders who stop pretending that failure is always someone else’s fault.
It doesn’t have to be launch, ghost, fail, blame.
But that cycle won’t break itself. And the cycle definitely won’t break while the people in charge keep rewriting the ending to protect their image.
Until the cover-up culture goes, no framework in the world will save us.
Tony Simms is a director of Quality Led Projects.
