South Africa’s public sector has a costly problem with ICT projects. Auditor-General reports year after year flag irregular expenditure, incomplete systems, and technology investments that deliver little value for public money spent.
This is not unique to South Africa. Governments around the world struggle to deliver ICT projects on time and within budget. But the consequences here are particularly serious. Overspending on technology means less money for health, education, and essential services. Failed systems mean citizens who cannot access the help they need.
The good news is that most of these failures are preventable. They share the same root causes — and those causes have well-known solutions.
Why Public Sector ICT Projects Fail
1. Poor Scope Definition at the Start
Many projects begin before anyone has clearly defined what the project must deliver. The scope is vague, the requirements are incomplete, and different stakeholders have different ideas about what success looks like.
When scope is unclear at the start, it grows during delivery. Every new requirement, every change request, every “while we’re at it” addition costs time and money. This is known as scope creep — and it is one of the leading causes of cost overruns in government ICT.
A project that starts without a clear, agreed, and documented scope will almost certainly cost more than planned.
2. Weak or Absent Project Governance
In many government departments, ICT projects are approved and then left to run without adequate oversight. There is no steering committee meeting regularly. There are no milestone reviews. No one is holding the project team — or the vendor — accountable for delivery.
Without governance, problems go undetected until they are expensive to fix. Budgets are spent without clear progress being made. Vendors deliver what is convenient rather than what was contracted. And by the time leadership becomes aware of how bad things are, the project is already in serious trouble.
3. Inadequate Procurement Planning
Government procurement rules exist for good reasons — transparency, fairness, and accountability. But when procurement is handled poorly, it creates problems that follow the project all the way through delivery.
Common procurement failures include writing specifications that are too vague, evaluating bids on price alone, not checking vendor track records, and awarding contracts to suppliers who lack the capacity to deliver. A bad vendor selection decision made at the start of a project is very difficult and expensive to undo later.
4. Underestimating Complexity
ICT projects in government are rarely simple. They involve multiple departments, legacy systems that must be integrated or replaced, data migrations, staff training, and change management — all while keeping existing services running.
When project teams underestimate this complexity, they also underestimate the budget needed to manage it. Optimistic cost estimates feel good at approval stage. They cause pain during delivery.
5. Skills Gaps in the Project Team
Many government departments do not have sufficient project management capacity in-house. ICT projects are run by officials who have strong domain knowledge but limited experience managing large, complex technology programmes.
Without trained project and programme managers, even well-planned projects run into trouble. Risks are not identified early. Issues are not escalated in time. Vendors are not managed effectively. And decisions that should take days take weeks.
6. No Change Management Plan
Technology on its own does not improve service delivery. People have to use it. When a new system is introduced without a proper change management plan — training, communication, user adoption support — staff resist it, work around it, or use it incorrectly.
The result is a system that was delivered on paper but never truly implemented. The full cost was paid. The full benefit was not received.
How to Fix It
Define Scope Before You Do Anything Else
Before a project is approved or a budget is allocated, the scope must be defined in writing. This means documenting what the project will deliver, what it will not deliver, who the stakeholders are, and what success looks like.
Scope definition is not glamorous work. But it is the single most effective thing a government department can do to protect its ICT budget.
Once scope is agreed and signed off, any change to it must go through a formal change control process. Every change must be assessed for its impact on cost, timeline, and risk — and approved by the right authority before it is implemented.
Appoint a Qualified Project Manager
Every ICT project above a certain value threshold should be led by a qualified, experienced project manager. Not someone with the title — someone with the skills, the certification, and the track record.
In the South African public sector, PRINCE2 and PMBOK are the most widely recognised project management frameworks. A project manager certified in either of these brings a structured approach to planning, risk management, issue resolution, and stakeholder communication.
If your department does not have this capacity internally, bring it in. The cost of a qualified project manager is a fraction of the cost of a project that goes wrong.
Set Up a Proper Steering Committee
Every significant ICT project needs a steering committee with real authority. This is not a box-ticking exercise. It is the decision-making body that keeps the project on track.
The steering committee should meet regularly — at least monthly for active projects. It should review progress against the plan, assess risks, approve changes, and escalate issues that cannot be resolved at project level.
Crucially, the steering committee must include senior leadership. If the Accounting Officer or a senior executive is not at the table, the committee lacks the authority to make the decisions that matter.
Do Your Procurement Properly
Procurement is where many government ICT projects are won or lost — before a single line of code is written or a single server is installed.
Take the time to write clear, detailed specifications. Evaluate bids on the full picture — technical capability, team experience, and track record — not on price alone. Check references. Ask vendors to demonstrate their solution. And make sure the contract is detailed enough to hold them accountable for delivery.
Poor procurement cannot be fixed during delivery. It can only be managed, at increasing cost.
Manage Your Vendors Actively
Signing a contract does not end your responsibility. It begins it. Vendors must be managed actively throughout the life of the project.
This means holding regular performance reviews, tracking delivery against agreed milestones, escalating issues early, and enforcing contract terms when they are not met. A vendor who knows they are being watched and held accountable performs better than one who is not.
Government departments that treat vendor management as an afterthought routinely find themselves locked into expensive contracts with underperforming suppliers and limited recourse.
Plan for Change Management From Day One
Your change management plan should be part of your project plan — not something you think about after the system has been built.
Identify who will be affected by the new system. Plan your training programme. Communicate early and often with staff about what is changing and why. Appoint change champions within the affected teams. And build time into your project schedule for user acceptance testing, feedback, and adjustment.
A system that staff actually use is worth far more than a system that was technically delivered but practically ignored.
Report Honestly and Act Early
Problems on ICT projects rarely appear without warning. There are almost always early signs — missed milestones, budget variances, unresolved issues, a vendor who stops responding promptly.
The key is to report these signs honestly and act on them early. A project that is two weeks behind schedule in month two can be recovered. The same project that is two months behind schedule in month eight is a crisis.
Build a reporting culture where project managers are expected to flag problems early — and where doing so is treated as good management, not failure.
The Role of External Support
Not every government department has the internal capacity to manage large ICT projects well. There is no shame in that. ICT programme management is a specialised discipline that takes years to develop.
Bringing in an experienced external partner — one that understands government procurement rules, has delivered ICT projects in the public sector, and is certified in the relevant frameworks — can make the difference between a project that delivers and one that doesn’t.
The right partner does not replace your team. They work alongside it, bringing structure, experience, and accountability that build your department’s own capacity over time.
Final Thought
Public sector ICT projects do not go over budget because technology is hard. They go over budget because the basics of good project management are not applied consistently.
Clear scope. Qualified project managers. Active governance. Proper procurement. Vendor management. Change management. Honest reporting.
None of these are new ideas. They are proven practices that work — when departments have the discipline and the support to apply them.
ZongeTech has spent over 35 years delivering ICT projects in South Africa’s most demanding public sector environments. We know what good looks like — and we know what the warning signs look like too.
If your department has an ICT project coming up — or one that is already in trouble — we can help.
