Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Campus Operations edition of September 12, 2026

Academic researchMixedRecent

University survey separates staff AI experimentation from weekly use

Yuriy S. Braun and Salavat M. Khafizov · Higher education administrative workforce · Single anonymized teacher-education university; location not established in inspected methods

Publisher
arXiv:2608.25063v1
Original publication
August 25, 2026
Source retrieved
2026-09-13
Read original source

What happened

Reported experience with AI and regular use are different adoption measures in the administrative subsample.

Why it matters

Directly useful to campus administrative evaluation; teaching, student-success and research outcomes are outside this item's scope.

Evidence and measured results

Table 1 reports 53/62 administrative respondents used an AI service; weekly use was 9/57 valid responses. December 2025 survey data cover 2,121 people overall. No objective productivity baseline or causal operating effect was measured.

Limitations and uncertainty

Preprint, single anonymized institution, self-report and small administrative group. Recruitment and response rate are undocumented; missingness changes denominators. Role-adapted instruments lack confirmed measurement invariance. Data collection day is unknown. Generalization to U.S. public campuses is unestablished.

Put this evidence to work

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

Sales

Role takeaway

The customer problem is a rollout dashboard that treats initial experimentation as sustained service use. Ask HR, institutional research and the administrative sponsor how they define an active user, which staff are missing from feedback, and whether the targeted task occurs often enough to justify a license. A bounded engagement could redesign one pilot's measurement plan. The value hypothesis is a more credible renewal decision, not increased use for its own sake. The small administrative sample supports careful questions about denominators; it cannot forecast another campus's adoption rate, quantify addressable demand or justify savings and staffing claims.

Pre-sales engineering

Role takeaway

Instrument the selected administrative workflow with separate measures for access, attempted tasks, repeated use, completed tasks and reviewed correctness. Prerequisites include an agreed eligible population, privacy approval and a baseline observation period. Keep telemetry minimized and separate operational evaluation from individual employee surveillance. Proposed validation should reconcile dashboard counts to a manually checked sample and show how missing responses alter conclusions. Integrate only the logs needed for the decision, regardless of hosting model. The preprint offers survey evidence rather than behavioral traces; do not convert its percentages into expected production load or assume they validate an agent architecture.

Delivery

Role takeaway

Assign institutional research to measurement design and the administrative service owner to service outcomes, with HR reviewing staff participation and communications. Document the invitation population, response coverage and denominator for every reported rate. Train pilot participants and include a route for nonusers to report barriers without penalty. Review privacy and accessibility before collecting data and before publishing small-group results. Proposed acceptance requires a reconciled participant count, documented missingness and an agreed quality measure alongside frequency. Compare over a defined follow-up period; proposed monitoring is not an observed result. Risks include selection bias, surveillance concerns and pressuring staff to use unsuitable tools.

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?

Connect evaluation to the actual institutional workflow; no tested deployment architecture is supplied.

Governance

Who approves, reviews and stays accountable for outcomes?

Record the decision owner, evidence threshold and re-review trigger for the selected workflow.

Security and privacy

What data, permissions and controls need testing?

Minimize institutional records in tests and verify access boundaries; these sources establish no security effectiveness.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Test accessible task completion with affected staff and count training and review effort; no accessibility outcome is established.

Procurement

What should contracts, pricing and exit terms secure?

Make pilot continuation depend on evidence, recurring support costs and feasible exit; no supplier performance guarantee follows.

Operating model

Which teams own the service once it runs?

Assign business correctness, technical operation and staff support to named owners before expanding the pilot.

What changed

New source and arXiv identifier across all 247 archived resources. Adds a concrete adoption-denominator distinction for staff evaluation; predates the latest run and is not daily news.

Publication history

  1. 2026-09-12Campus Operations · Issue 073 resources
Read preserved resource versions (JSON)

Stable resource ID: braun-khafizov-admin-ai-use-denominators-2026