Most government ICT projects struggle. They run over budget, miss deadlines, or deliver systems that staff refuse to use. The problem is rarely the technology. It is usually the strategy — or the lack of one.
A solid ICT strategy gives your department a clear direction. It aligns technology with your mandate, keeps spending in check, and makes sure your systems serve the people who depend on them.
This guide walks you through how to build one that actually delivers.
1. Start With Your Mandate, Not the Technology
Too many ICT strategies begin with technology. They start with what is available or what vendors are selling. That is the wrong place to start.
Begin with your department’s mandate. What are you required to deliver? Who do you serve? What does success look like for your citizens or stakeholders?
Your ICT strategy must answer one question above all others: how does technology help us deliver on our mandate better, faster, and at lower cost?
If you cannot connect a technology decision back to your mandate, it should not be in your strategy.
2. Assess Where You Are Now
You cannot plan a route without knowing your starting point. Before writing a single goal, you need an honest picture of your current ICT state.
Your baseline assessment should cover three areas.
Systems and Infrastructure
- List every active system, platform, and application your department uses.
- Note the age, support status, and cost of each one.
- Identify which systems are integrated and which operate in isolation.
People and Skills
- Assess the ICT skills available in your team.
- Identify gaps between what your team knows and what your strategy will require.
- Note where you rely on contractors or external vendors for core functions.
Governance and Compliance
- Review your current ICT governance policies.
- Check for compliance with applicable legislation and regulations.
- Identify any audit findings or risk areas that need to be addressed.
This assessment does not need to be perfect. It needs to be honest. You are looking for a clear view of your strengths, your gaps, and your risks.
3. Define Your ICT Goals
With your mandate clear and your baseline established, you can set goals. Good ICT goals for government share three features.
They are specific. “Improve service delivery” is not a goal. “Reduce the time to process permit applications from 15 days to 5 days by automating the intake workflow” is a goal.
They are measurable. If you cannot measure progress, you cannot manage it. Every goal should have a metric attached.
They are tied to your mandate. Technology goals that do not connect to service delivery, compliance, or operational performance have no place in a government ICT strategy.
Aim for no more than five to seven goals. Trying to do everything at once is a reliable path to doing nothing well.
4. Choose a Framework — and Stick to It
Government ICT strategies do not need to be invented from scratch. Proven frameworks provide structure, rigour, and accountability. Using one also makes your strategy easier to audit and defend.
The most widely used frameworks in South African and African public sector ICT include the following.
ITIL (Information Technology Infrastructure Library) ITIL provides practices for ICT service management. It helps departments manage IT services in a consistent, efficient way that is aligned to business needs. It is especially useful for managing service desks, change control, and incident response.
TOGAF (The Open Group Architecture Framework) TOGAF is used to design and manage enterprise architecture. It gives you a structured way to plan how your systems, data, and technology should be built and connected. If your department is going through a large system overhaul or migration, TOGAF provides the architectural discipline to do it correctly.
COBIT (Control Objectives for Information and Related Technologies) COBIT focuses on governance and management of enterprise IT. It is widely used in South African government and aligns well with the requirements of the Public Finance Management Act (PFMA) and National Treasury guidelines on ICT governance.
You do not need to implement all three. Choose the framework that best fits your current stage and your most pressing challenges. What matters is that you apply it consistently — across the whole organisation.
5. Build Your Roadmap
A strategy without a roadmap is just a wish list. Your roadmap turns goals into a sequence of actions with owners, timelines, and budgets.
Structure your roadmap in three time horizons.
Short Term (0–12 Months) Focus on quick wins and critical fixes. Address the most urgent risks. Lay the groundwork for longer-term work. These are the actions that show progress and build confidence across the organisation.
Medium Term (1–3 Years) This is where your core transformation work sits. New systems, architecture changes, major integrations, and skills development programmes belong here. These initiatives take time and need careful planning and strong programme management.
Long Term (3–5 Years) This horizon describes the future state you are building towards — the systems you want running, the services you want to offer, and the internal capability you want to have built.
Review your roadmap at least once a year. Budgets shift. Priorities change. Your roadmap must be a live document, not a shelf item.
6. Govern It Properly
The best ICT strategy will fail without proper governance. Governance means having clear structures to make decisions, manage risk, track progress, and stay accountable.
At a minimum, your ICT governance structure should include the following.
- An ICT Steering Committee with executive representation and a clear mandate.
- A defined process for approving and prioritising ICT projects and spending.
- Regular reporting against your strategy goals and roadmap milestones.
- A risk register that is actively maintained and reviewed.
- A process for managing vendors and contracts, including performance reviews.
In South Africa, government departments are also required to comply with the DPSA ICT Governance Framework and National Treasury guidelines. Your governance structure must meet these requirements — not as a box-ticking exercise, but as a genuine management discipline.
7. Get the Right People Involved
ICT strategy is not just a technology exercise. It touches every part of your organisation. The people who build it must reflect that.
Your strategy process should involve senior leadership, not just the ICT team. If the Director-General or Accounting Officer does not own the strategy, it will not get the budget, the priority, or the organisational backing it needs.
It should also involve end users — the staff who work with the systems every day. They know where the pain points are. Ignoring them is one of the most common reasons ICT projects fail.
If your internal capacity is limited, bring in an experienced external partner — not to own the strategy for you, but to provide the methodology, the frameworks, and the challenge your team may not be able to provide itself.
8. Measure and Report
A strategy that is not measured is not managed. Set up a clear reporting rhythm from the start.
Report monthly on operational performance. Report quarterly on strategic progress. Report annually on the overall state of your ICT and whether your strategy needs updating.
Keep your reporting simple and honest. The purpose is not to look good. It is to know where you stand — so you can make good decisions about what to do next.
Final Thought
A good ICT strategy for government is not a technical document. It is a management tool. It tells your organisation where it is going, how it will get there, and who is responsible for making it happen.
Done well, it protects public funds, improves service delivery, and gives your department the technology foundation it needs to serve citizens effectively.
If your department is ready to build or refresh its ICT strategy, ZongeTech can help. We bring over 35 years of ICT leadership across South Africa’s public and private sectors — and we know what it takes to deliver results in government environments.
