From the State Government edition of September 7, 2026
NCDOT study finds staff expectations change after hands-on Copilot use
University of North Carolina at Charlotte and North Carolina Department of Transportation · State transportation workforce · North Carolina, United States
- Publisher
- Persona Migration and Expectation Recalibration in Generative AI Adoption: A Longitudinal Study at a State Department of Transportation
- Original publication
- July 15, 2026, arXiv v1; pilot conducted in 2025
- Source retrieved
- 2026-09-08
What happened
Perceived usefulness fell after the pilot; other aggregate acceptance constructs did not change significantly.
Why it matters
Direct state workforce evidence, relevant to shared productivity-suite rollout rather than traffic-system performance.
Evidence and measured results
Eight-week 2025 NCDOT pilot; 175 baseline respondents, 133 matched responses and 124 after screening. Table 3 reports usefulness 3.85 before versus 3.62 after, adjusted p<0.001. Paired survey analysis and exploratory clustering measure perceptions, not causal productivity effects.
Limitations and uncertainty
Single agency, short horizon, self-reports and no untreated comparison. Small persona transitions and keyword-based qualitative coding limit inference. Attrition checks cover measured baseline attitudes only. Preprint status; no verified net savings or accessibility effect.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-08; this does not change the original publication date. Labels below come from the analysis itself.
Sales
Role takeaway
Ask the CIO, transportation business-unit leaders, learning team and budget owner which office tasks justify the license and what would count as sustained value. Use the study's changing usefulness ratings to discuss expectation setting, not to label staff resistant. A bounded engagement could assess a small set of communication, analysis and document workflows and recommend targeted enablement. The value hypothesis is more informed allocation of training and licenses. Ask how managers will measure quality and correction effort alongside perceived usefulness. Do not claim this survey proves productivity loss, financial return or improved transportation outcomes, and do not generalize its user clusters to another workforce.
Pre-sales engineering
Role takeaway
Begin with the existing collaboration tenant and identify precisely which documents and applications each test role may access. Prerequisites include approved test material, clear information ownership and accessible interaction paths. Validate representative drafting, summarization and spreadsheet tasks separately; an acceptable summary does not establish reliable numerical analysis. Instrument errors, source checking and correction time under a documented configuration. Include adversarial content in retrieved documents and tests for unauthorized information access. Compare observed task performance with the current process while separately collecting feedback. The research does not compare hosting architectures, coding assistants or autonomous agents, so those require their own technical assessment.
Delivery
Role takeaway
The workforce enablement owner should coordinate business managers, platform IT, accessibility specialists and security. Deliver role-based examples, office hours and guidance on checking outputs, then repeat feedback collection after routine use. Dependencies include protected learning time, stable configuration and managers willing to hear disappointment.
- Proposed acceptance criteria
- each selected workflow has an observed quality assessment and cost record, staff can demonstrate correction and escalation, and the license decision records unresolved fit gaps. Track adoption without treating high usage as success by itself. Risks include surveillance-like employee scoring, using preliminary personas as permanent labels and continuing subscriptions where local workflow evidence remains weak.
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?
Copilot operated in approved NCDOT Microsoft 365 applications. Interpretation: validate content permissions and task-specific integrations before license expansion.
Governance
Who approves, reviews and stays accountable for outcomes?
Collect recurring feedback while evaluating quality separately; enthusiasm is not an approval control.
Security and privacy
What data, permissions and controls need testing?
Retain access restrictions even when staff report greater confidence; verify permission and disclosure behavior directly.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Provide accessible, role-specific learning and confidential ways to report skill concerns without labeling individual employees.
Procurement
What should contracts, pricing and exit terms secure?
Plan license reassessment by demonstrated workflow fit and include vendor-change notice in commercial review.
Operating model
Which teams own the service once it runs?
Workforce enablement and platform operations should jointly own recurring feedback and service improvement.
What changed
No matching source URL or arXiv identifier in the full archive or targeted search. Adds unarchived state-specific longitudinal evidence; July publication and 2025 pilot are explicitly historical.
Publication history
- 2026-09-07State Government · Issue 023 resources
Stable resource ID: ncdot-copilot-expectation-recalibration-2026