From Spreadsheets to Strategy: Data Maturity in the New Zealand Public Sector
· 3 min read · Nic Keating
Most government agencies have more data than they can use and less insight than they need. Building genuine data maturity requires more than dashboards — it requires a fundamental shift in how organisations value, govern, and operationalise their information assets.
Every New Zealand government agency produces vast quantities of data. Service delivery metrics, financial reports, HR records, citizen interactions, sensor readings, geospatial data — the volume grows annually. Yet when ministers ask for evidence-based advice, the response too often involves analysts manually extracting data from multiple systems, reconciling inconsistencies in spreadsheets, and producing static reports that are outdated before they reach the decision-maker's desk.
This is not a technology problem. It is a maturity problem.
The Five Levels of Data Maturity
Level 1: Ad Hoc. Data exists in silos. Analysis is reactive and manual. There is no data governance. Most small agencies operate here, and many large ones do too.
Level 2: Repeatable. Key reports are standardised. Some data quality processes exist. A few analysts know where to find things. This is where most New Zealand government agencies sit today.
Level 3: Defined. A data governance framework exists and is actively maintained. Data definitions are consistent across the organisation. A data catalogue makes assets discoverable. Self-service reporting reduces analyst bottleneck.
Level 4: Managed. Data quality is measured and actively improved. Predictive analytics inform operational decisions. Real-time dashboards replace monthly reports. Data literacy programmes reach beyond the analytics team.
Level 5: Optimising. Machine learning models are embedded in operational processes. Data products are maintained like software products. The organisation treats data as a strategic asset with measurable ROI.
Why Dashboards Are Not the Answer
The most common response to "we need better data" is "let's build dashboards." Dashboards are useful, but they are a presentation layer. If the underlying data is inconsistent, ungoverned, or poorly understood, dashboards simply make bad data more visible.
Worse, dashboards create a false sense of maturity. Leadership sees colourful charts and assumes the data problem is solved. Meanwhile, analysts spend 80% of their time cleaning and reconciling data and 20% actually analysing it.
The Foundation: Data Governance
Genuine data maturity starts with governance — not the bureaucratic kind that creates committees and policies that no one reads, but operational governance that answers three questions:
1. Who owns this data? Not "who stores it" but "who is accountable for its quality, currency, and appropriate use?"
2. What does this data mean? Consistent definitions across the organisation. When Finance says "FTE" and HR says "FTE," do they mean the same thing? (They usually do not.)
3. How should this data be used? Classification, access controls, retention policies, and privacy impact assessments that are integrated into business processes, not bolted on afterwards.
The New Zealand Opportunity
New Zealand's relatively small public sector is an advantage here. The number of critical data domains is manageable. Cross-agency relationships are close enough to enable federated governance models. And the government's commitment to open data and digital public infrastructure creates a policy environment that supports maturity progression.
The agencies that invest in data governance now — not dashboards, not AI, not data lakes, but governance — will be the ones that can actually use AI effectively when the technology matures. You cannot build intelligence on a foundation of chaos.