From the SLED-wide archive edition of September 2, 2026
Ten-country survey links effective public-sector AI use to approved access, clear rules, training, and workflow embedding
Public First and Center for Data Innovation · Government workforce · Ten countries: Brazil, France, Germany, India, Japan, Saudi Arabia, Singapore, South Africa, United Kingdom, and United States
- Publisher
- Public Sector AI Adoption Index 2026
- Original publication
- February 2026
- Source retrieved
- Not recorded in the historical archive
What happened
A survey of 3,335 public servants across ten countries reports that 74% use AI, yet only 18% think government uses it very effectively. The study separates enthusiasm, education, enablement, empowerment, and workflow embedding and finds large associations between those conditions and confidence, advanced use, and reported benefits.
Why it matters
The survey provides a cross-national operating-model lens for employee copilots and assistants. It suggests that access and governance are complements: withholding practical approved tools can push work into personal accounts, while clear permission, support, and embedded enterprise access can spread benefits beyond already-confident users.
Evidence and measured results
In low-enablement organizations, 64% of enthusiastic users reported personal-login use and 70% reported work use unknown to managers. Across countries, 50% cited data security or privacy as a barrier. In high-empowerment environments, 91% reported confidence compared with 45% in low-empowerment settings; in high-embedding environments, 58% of workers aged 55 or older reported saving more than an hour with AI versus 16% in low-embedding environments.
Limitations and uncertainty
The index is based on self-reported cross-sectional survey data and shows association, not causation. Public First produced it for the Center for Data Innovation with Google sponsorship. Country samples, job roles, public-sector definitions, and cultural response patterns may differ, and perceived benefit or time saved is not independently measured mission impact.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source as summarized in the preserved archive. Enriched 2026-09-05; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
Problem and stakeholders: CIOs, HR, security, managers, and frontline staff may face personal-account AI use because approved access and practical guidance lag demand.
- Discovery
- Which tasks drive unofficial use, what blocks enterprise tools, and how do users obtain permission or help?
- Value hypothesis
- Usable approved access with rules, training, and integration could improve adoption conditions and risk visibility.
- Potential engagement
- A workforce-use and workflow-readiness assessment followed by a bounded managed-access pilot.
- Evidence boundary
- The Google-sponsored cross-sectional survey reports associations and perceived benefits across ten countries. It does not show that a platform causes productivity gains, eliminates shadow use, or saves a locally applicable amount of time; mission outcomes need independent measurement.
Pre-sales engineering
Role takeaway
- Fit
- Consider identity-bound enterprise access for everyday drafting, summarization, and related workflows when usable and supported.
- Architecture
- Reuse approved models, connectors, classifications, logs, and escalation within existing work tools.
- Prerequisites
- Permitted tasks, enterprise contracts, data owners, support capacity, and a practice baseline.
- Constraints
- Cloud or hybrid fit depends on data and integrations; convenience matters if personal accounts remain easier.
- Security
- Validate privileges, data-loss controls, connector scope, retention, and manager visibility without indiscriminate surveillance.
- Proposed validation
- Have representative staff complete approved tasks, test sensitive-data boundaries, and compare usability, quality, and measured effort. Keep confidence and reported savings distinct from observed public-service performance and do not infer causal benefits from survey associations.
Delivery
Role takeaway
Work and dependencies: Pair access with low-risk guidance, role-specific training, support, and stronger review for sensitive or consequential tasks.
- Ownership
- Workflow leaders own service outcomes; IT operates integrations; security and privacy define boundaries; HR and learning teams support adoption.
- Skills and adoption
- Include less-confident users and managers and provide trusted reporting of unofficial use.
- Governance checkpoints
- Review connectors and high-risk workflows before access and reassess after changes.
- Proposed acceptance
- Staff complete agreed tasks in approved tools, boundary tests pass, support resolves observed problems, and quality and service measures remain separate from sentiment.
- Risks
- Surveillance-heavy monitoring may suppress honest feedback, usable access alone may not change behavior, and cross-country self-reports do not establish locally realized benefits.
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?
Provide an identity-bound enterprise AI layer integrated into ordinary workflows, with approved models, data classifications, support, logging, and clear escalation. Hybrid or cloud choices should be driven by data sensitivity and integration needs, but an official platform must be usable enough to compete with personal accounts.
Governance
Who approves, reviews and stays accountable for outcomes?
Pair safe-harbor rules for low-risk tasks with stronger review for sensitive data and consequential actions. Treat onboarding, role-specific training, support channels, manager visibility, and workflow redesign as parts of deployment. Track public-service outcomes separately from confidence, adoption, or reported time savings.
Security and privacy
What data, permissions and controls need testing?
Reduce shadow AI through managed identities, enterprise contracts, DLP, approved connectors, auditable use, and practical guidance on what data can be shared. Monitor for work performed through personal accounts without treating surveillance of employees as a substitute for usable approved tools and trust.
The preserved archive analysis covered architecture, governance and security. Not assessed for this record: accessibility and workforce, procurement, operating model.
Publication history
- 2026-09-02SLED-wide archive · Issue 065 resources
Stable resource ID: public-first-public-sector-ai-index