New Zealand's government digital services have improved measurably over the past three years. RealMe works. IRD's myIR portal handles tax returns without crashing. COVID-19 contact tracing was built and deployed in weeks. None of this is world-class yet, but it's functional, accessible, and getting better. For enterprise teams, the public sector's approach to digital services offers lessons that are surprisingly relevant - and some cautionary tales worth noting.
What You Need to Know
- NZ government digital services have improved significantly, driven by the Digital Government Partnership and Service Innovation Lab
- The COVID-19 response accelerated digital delivery capabilities across government agencies
- Accessibility and inclusivity standards in public sector work often exceed private sector norms
- Enterprise teams can learn from the government's approach to service design, even if the delivery speed doesn't match
What's Working
Service Design Thinking
The Department of Internal Affairs and associated agencies have adopted service design as a core practice, not a buzzword. The NZ Government Web Standards and the Digital Service Design Standard provide clear, practical guidance for building digital services that work for New Zealanders.
What stands out is the emphasis on user needs over organisational structure. The traditional government approach was to build a digital service for each department. The service design approach asks: what does the citizen need to accomplish, and how do we make that journey coherent across agencies?
76%
of New Zealanders who used government digital services in 2020 rated them as easy to use
Source: Department of Internal Affairs, Digital Government Survey 2020
NZ Government Digital Service Delivery Performance, 2020
Source: Department of Internal Affairs, Digital Government Survey 2020
The MSD (Ministry of Social Development) online services for COVID-19 support payments were a good example. The service was designed from the applicant's perspective: what do they need, what information do they have, how quickly can we get them an answer. The technical implementation was straightforward. The service design work that made it usable was not.
Accessibility as Default
Government digital services in NZ are required to meet WCAG 2.1 AA standards. This isn't optional. It's policy. And while compliance varies across agencies, the expectation creates a baseline that the private sector often lacks.
Rainui and I reviewed three government digital services this year as part of an accessibility benchmarking exercise. All three met basic WCAG requirements. Two exceeded them in specific areas - keyboard navigation and screen reader support were better than any private sector enterprise application we've audited this year.
Government agencies don't have the luxury of choosing their users. Enterprise teams should adopt the same mindset: design for everyone from the start.
Rainui Teihotua
Chief Creative Officer
Open Standards
The NZ government's commitment to open standards - open data formats, open APIs, platform-agnostic design - is ahead of most private sector enterprise practice. Data.govt.nz provides machine-readable datasets. APIs follow consistent patterns. The vendor lock-in that plagues enterprise IT is actively resisted.
What's Not Working
Delivery Speed
Government procurement and delivery timelines remain slow. A digital service that the private sector could build in three months takes government twelve to eighteen months. Some of this is necessary caution - public money, public accountability. Some of it is unnecessary bureaucracy.
The COVID-19 response showed that government can deliver quickly when the urgency is clear. The wage subsidy system was built in days. Contact tracing infrastructure was operational within weeks. The question is whether that urgency-driven speed can become normal practice without the crisis.
Legacy Integration
Most government agencies run on legacy systems that are decades old. The digital services that citizens see are often thin interfaces over infrastructure that's fragile, poorly documented, and expensive to maintain. Until the underlying systems are modernised, the digital services will remain constrained by what the backend can support.
This is directly relevant to enterprise teams. The pattern is identical: a modern frontend connected to a legacy backend through middleware that nobody fully understands. The government's approach to managing this - incremental modernisation, API layers, strangler patterns - is instructive even when the execution is slow.
Cross-Agency Coordination
Each government agency has its own technology team, its own systems, its own data. Making them work together is the central challenge. RealMe was supposed to be the unified identity layer. It works, but adoption across agencies is uneven. The "tell us once" principle - where a citizen provides information to one agency and it's shared across government - remains aspirational.
Lessons for Enterprise
Design from the user's journey, not the org chart. Government services work best when they're designed around citizen needs, not departmental boundaries. Enterprise software works best when it's designed around user workflows, not team structures.
Mandate accessibility early. The government's WCAG requirement is blunt but effective. Enterprise teams that treat accessibility as a requirement from sprint one, not a pre-launch checklist item, build better products.
Invest in open standards. Government's commitment to open data and open APIs reduces vendor dependency. Enterprise teams that invest in standard data formats and well-documented APIs gain the same flexibility.
Accept that legacy is the norm. Government's legacy challenge is every enterprise's legacy challenge. The incremental modernisation approach - API layers over legacy, strangler pattern migration, gradual replacement - works better than big-bang rewrites in both contexts.
NZ's public sector digital capability is further along than most enterprise teams realise. It's not perfect. It's slow. But the design principles and accessibility standards are worth studying.