I’ve spent twenty years in the trenches of large-scale delivery. I’ve seen the same movie play out in London, Washington, and Canberra.
A government department announces a "landmark" digital transformation. The press release is full of buzzwords: cloud-first, citizen-centric, agile.
Three years and $100 million later, the project is a "watermelon", bright green on the outside (reports look great), but blood-red on the inside. Eventually, the audit comes out, the minister resigns, and the taxpayer picks up the tab for a system that barely works.
The most frustrating part? It’s almost never about the technology.
I’ve worked with some of the smartest engineers in the world on public sector projects. The failure isn't in the code. It’s in the operating model. If you try to build 21st-century software using 19th-century procurement and mid-20th-century governance, you are going to fail. Period.
Here are the three structural reasons why public sector IT keeps hitting the wall, and what we actually need to do to fix it.
1. The Procurement Time Warp
12-Month Cycles for 3-Month Technology Windows
The way we buy technology in the public sector is fundamentally broken.
Most government procurement processes take anywhere from 9 to 18 months from the initial "Statement of Requirements" to the actual contract award.
Think about that. In the world of technology, 18 months is an eternity. By the time the ink is dry on the contract, the original business case is obsolete, the chosen tech stack is outdated, and the market has moved on.
We are essentially asking vendors to bid on a snapshot of a problem from two years ago. We force them into fixed-price, fixed-scope contracts that leave zero room for the iterative learning that is the hallmark of modern product engineering & technical enablement.
The result? You don't get the solution you need; you get the solution you thought you needed 18 months ago.
The Fix: We need to move toward "Continuous Procurement." Instead of massive, monolithic tenders, we should be procuring for outcomes and capacity through pre-vetted frameworks that allow us to start delivery in weeks, not years.
2. Governance as a Brake, Not a Steering Wheel
Prioritising Compliance Over Delivery
In most government agencies, the "Governance Committee" is where delivery goes to die.
These committees are often staffed by well-meaning senior leaders who have plenty of policy experience but zero experience actually delivering software. Because they don't understand the technical risks, they default to the only thing they know: compliance.
They demand 200-page status reports, detailed "RAG" dashboards, and exhaustive risk registers. They want to see every "i" dotted and every "t" crossed on the project plan.
But here’s the reality: You can have perfect compliance and still deliver a useless product.
Governance should be about removing blockers and making fast decisions to keep the momentum. Instead, it’s become a bureaucratic hurdle that forces teams to spend 40% of their time reporting on work rather than doing it. This is why so many programmes need delivery governance consulting to untangle the mess.
The Fix: Governance needs to shift from oversight to enablement. We need delivery-literate boards that focus on "Net Velocity" and "Unblocked Days" rather than just checking off milestones in a Gantt chart. If your board doesn't understand the difference between a technical debt and a bug, they shouldn't be on the board.
3. The Vendor Death Grip
The Illusion of Safety in Big Outsourcing
There is a famous saying in government: "No one ever got fired for buying IBM."
This mindset has led to a massive over-reliance on a handful of "System Integrators" (SIs). These large-scale outsourcing deals are often sold as a way to "transfer risk" to the vendor.
But as any public sector programme rescue veteran will tell you: You can transfer the work, but you can never transfer the risk.
If the system fails, the vendor pays a penalty, sure. But the government still has the failed system, the citizens still don't have the service, and the political fallout still lands on the minister's desk.
Long-term, multi-year outsourcing deals create "Vendor Lock-in." The vendor has no incentive to innovate because they’ve already secured the revenue. Meanwhile, the government loses its "intelligent customer" capability, the internal knowledge required to actually manage the technology.
The Fix: Break the "Death Grip." We need to shift toward multi-vendor ecosystems where the government retains control of the core architecture. This is a central pillar of enterprise transformation & modernization. Smaller, modular contracts with SMEs (Subject Matter Experts) allow for more agility and better value for money.
The Global Graveyard: Lessons from the UK, Australia, and the US
This isn't a local problem; it's a global epidemic of systemic failure.
- United Kingdom: The National Programme for IT in the NHS (NPfIT) remains one of the most expensive IT failures in history. It failed not because of bad code, but because it was a top-down, monolithic design that ignored the actual needs of the doctors and nurses on the ground.
- Australia: The Victorian justice system and various "myGov" iterations have suffered from the "Design-Reality Gap", where systems are built to meet abstract policy requirements rather than the operational reality of service delivery.
- United States: Beyond the famous HealthCare.gov launch, the US federal government spends nearly 80% of its IT budget just keeping COBOL-based legacy systems alive. The sheer weight of technical debt makes any government IT modernisation consultant jump for joy and scream in frustration at the same time.
What It Will Take to Fix It: A New Operating Model
If we want to stop the cycle of failure, we need a fundamental shift in how the public sector approaches digital delivery. We call this an Execution-First Mindset.
- Bring the Talent In-house: You cannot outsource your strategy. Government departments must rebuild their internal technical leadership. You need an "Intelligent Customer" function that actually understands what the vendors are doing.
- Start Small, Scale Fast: Stop the $100M "Big Bang" projects. Start with a Delivery Diagnostic to find the smallest possible piece of value, build it in 12 weeks, and then iterate.
- Modernize the Governance: Move away from "Watermelon Status" reporting. Implement real-time delivery telemetry. If a project is failing, we should know in week 4, not month 24.
- Embrace Platform Modernization: Don't just "lift and shift" legacy mess to the cloud. Use cloud, data & platform modernization to rebuild services around modern data architectures.
The technology exists to make government services seamless, efficient, and user-friendly. The only thing standing in the way is the way we manage the work.
Is your programme showing early signs of "Watermelon Status"?
Don't wait for the audit. Let’s have a blunt, practitioner-to-practitioner conversation about how to get your delivery back on track.
Book a Strategy Session with Kunal Patel
FAQ
Q: Why does public sector IT fail more often than private sector IT?
A: It doesn't necessarily fail more often, but the failures are more visible and the constraints (procurement laws, political cycles, and legacy debt) are much more rigid. In the private sector, a failing project is often quietly killed; in the public sector, it becomes a headline.
Q: Can "Agile" really work in a government environment?
A: Yes, but only if the governance is also agile. You cannot have an agile dev team reporting to a waterfall steering committee. You need to align the entire stack, from the contract to the code.
Q: What is a "Delivery Diagnostic"?
A: It’s our low-risk engagement model at Dark Consultancy. Before we commit to a massive roadmap, we spend 2-4 weeks looking under the hood of your programme to identify the real bottlenecks, risks, and "false green" status indicators.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia ; ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn