{"resourceId":"braun-khafizov-admin-ai-use-denominators-2026","versions":[{"version":"external-ada9c6791ee3b1392a2b725e278bf21920618c3b2ada28c708c13f976851589c","resource":{"id":"braun-khafizov-admin-ai-use-denominators-2026","title":"University survey separates staff AI experimentation from weekly use","organization":"Yuriy S. Braun and Salavat M. Khafizov","sector":"Higher education administrative workforce","geography":"Single anonymized teacher-education university; location not established in inspected methods","publishedAt":"August 25, 2026","publicationDate":"2026-08-25","eventDate":null,"sourceName":"arXiv:2608.25063v1","sourceLabel":"Academic preprint; cross-sectional survey","sourceUrl":"https://arxiv.org/html/2608.25063v1","evidenceClass":"academic-research","outcomeClass":"mixed","topics":["knowledge-work","governance-procurement","accessibility-workforce","operating-model"],"finding":"Reported experience with AI and regular use are different adoption measures in the administrative subsample.","sledRelevance":"Interpretation: directly useful to campus administrative evaluation; teaching, student-success and research outcomes are outside this item's scope.","evidence":"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.","architectureImplications":"Interpretation: connect evaluation to the actual institutional workflow; no tested deployment architecture is supplied.","governanceImplications":"Interpretation: record the decision owner, evidence threshold and re-review trigger for the selected workflow.","securityPrivacyImplications":"Interpretation: minimize institutional records in tests and verify access boundaries; these sources establish no security effectiveness.","caveats":"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.","streamIds":["campus-operations"],"roles":{"sales":"Interpretation: 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.","engineering":"Interpretation: 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":"Interpretation: 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."},"retrievedAt":"2026-09-13T03:00:50Z","enrichedAt":"2026-09-13T03:02:50Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: test accessible task completion with affected staff and count training and review effort; no accessibility outcome is established.","procurementImplications":"Interpretation: make pilot continuation depend on evidence, recurring support costs and feasible exit; no supplier performance guarantee follows.","operatingModelImplications":"Interpretation: assign business correctness, technical operation and staff support to named owners before expanding the pilot.","updateExplanation":"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.","sourceVerification":{"openedUrl":"https://arxiv.org/html/2608.25063v1","referenceExcerpt":"The administrative sample comprised 62 respondents","promptVersion":"sled-research-v3.1","model":null,"basis":"agent-reported inspection"}}}]}