Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the State Government edition of September 8, 2026

Government evaluationEmergingUndated source

New Zealand survey shows operational expansion while effectiveness remains self-reported

New Zealand Government Digital Delivery Agency · Government shared services and workforce · New Zealand; transferable governance lessons for U.S. states

Publisher
2026 cross-agency survey of use cases for artificial intelligence
Original publication
Last updated August 19, 2026
Source retrieved
2026-09-09
Read original source

What happened

Agency reporting indicates more operational AI use, but adoption counts do not establish causal service benefits.

Why it matters

A comparator for state shared-service portfolios, not a U.S. state census or a transferable legal framework.

Evidence and measured results

59 organisations reported 545 use cases, including 167 operational cases. The prior survey had 70 organisations and 272 cases. Benefits are agency-reported; changing respondents complicate trend interpretation.

Limitations and uncertainty

No controlled baseline, measured time savings, response-rate denominator or common outcome rubric supplied. August update is not a September measurement. Jurisdiction and survey composition limit transfer.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-09; this does not change the original publication date. Labels below come from the analysis itself.

Sales

Role takeaway

Discuss portfolio visibility with the state CIO, agency leaders, workforce representatives and budget owners. Ask how many listed uses actually operate, who benefits and what evidence justifies continuation. A bounded inventory validation and measurement engagement could help distinguish scaling candidates from unsupported experiments. The value hypothesis is better allocation of support and implementation effort. Do not translate overseas adoption growth into a customer's likely savings or maturity ranking. Identify which agencies can supply comparable records and whether a shared service would meet their differing responsibilities, access needs and funding arrangements.

Pre-sales engineering

Role takeaway

Fit is portfolio instrumentation across copilots, developer tools and bounded agents, rather than a particular model deployment. Link each use case to its environment, data class, connectors, human authority, version and telemetry. Prerequisites include agreed lifecycle definitions and access to actual deployment records. Validate a sample against system configuration, test tenant boundaries, and rehearse service fallback. A proposed proof of value should compare one workflow's quality, effort and operating cost with its existing baseline. National survey findings provide no capacity specification; local latency, sovereignty, security and legacy-integration requirements remain decisive.

Delivery

Role takeaway

Start by reconciling agency inventories with operational owners and selecting a small evaluation cohort. A central portfolio lead maintains common definitions; agency service owners remain accountable for outcomes. Dependencies include analyst capacity, staff participation and approved handling of evaluation records. Train contributors to distinguish usage, sentiment and observed benefit.

Proposed acceptance criteria
each sampled operational use has a named owner, verified lifecycle status, baseline and scheduled continuation decision; unresolved sovereignty or accessibility failures have an approved disposition. Risks include respondent selection, inconsistent definitions and continued funding based on activity rather than public value.

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Record lifecycle stage, dependencies and model permissions in a common portfolio record; do not infer an architecture from adoption counts.

Governance

Who approves, reviews and stays accountable for outcomes?

Validate portfolio entries against actual workflows and give every claimed benefit an evidence owner.

Security and privacy

What data, permissions and controls need testing?

The report identifies reliability and data sovereignty as remaining challenges. Interpretation: verify boundaries locally rather than treating reduced concern as reduced exposure.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Test usefulness by role and accessibility needs, including staff who do not adopt the tool.

Procurement

What should contracts, pricing and exit terms secure?

Buy reusable capabilities only after checking program fit and lifecycle support obligations.

Operating model

Which teams own the service once it runs?

Portfolio staff should separate planned, trial and operational uses and schedule evidence reviews.

What changed

No matching survey URL in the complete archive or targeted cross-agency search. August material newly added for the changing survey denominator and operational-stage distinction; no fresh September outcome asserted.

Publication history

  1. 2026-09-08State Government · Issue 034 resources
Read preserved resource versions (JSON)

Stable resource ID: nz-cross-agency-ai-survey-2026