Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Student Success edition of September 13, 2026

Academic researchEmergingNew this fortnight

UK survey exposes differing AI expectations without measuring learning

Peter Kahn and colleagues; University of Manchester and University of the Basque Country · Higher education teaching and student learning · United Kingdom; one social-science school at a research-intensive university

Publisher
Still emerging: understanding Generative AI use in Higher Education
Original publication
September 10, 2026; survey conducted April–June 2024
Source retrieved
2026-09-14
Read original source

What happened

Staff and students differed in their expectations and perceptions of AI use; the study does not measure learning gains.

Why it matters

Useful for U.S. colleges planning teaching support, with substantial limits from a single UK setting and older observations.

Evidence and measured results

Two questionnaires, with 45 complete academic responses and 86 complete student responses; partial responses increase item denominators. Table 1 measures expected performance, not tested achievement. There is no experimental baseline.

Limitations and uncertainty

Self-selection, low response, one school and 2024 data constrain current generalization. The underlying dataset is not openly released. Scale consistency cannot establish educational efficacy.

Put this evidence to work

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

Sales

Role takeaway

A teaching leader may lack a shared understanding of acceptable AI help across courses. Include faculty, students, learning support and institutional research in discovery. Ask where expectations differ, what independent skill the course assesses, and whether students can obtain help without paid subscriptions. A bounded engagement could examine one course's instructions and test revised examples with both groups. The value hypothesis is clearer expectations and fewer avoidable support problems. The survey provides a reason to investigate this locally, not a forecast of learning gains. Do not promise better grades, retention, reduced misconduct or staff savings. Applicability depends on the local student mix and teaching context.

Pre-sales engineering

Role takeaway

Start with a sandbox exercise that makes permitted assistance observable, such as comparing a generated answer with a student explanation. Prerequisites include faculty-approved tasks, accessible examples and a fixed model configuration. Connect only approved course materials; keep grades and student records outside the experiment. Test whether learners can identify errors and complete an unaided follow-up task. Record model changes so differences are not attributed entirely to training. Validate privacy and course-access boundaries independently of educational quality. This would be a new proof of value, because the survey measures perceptions rather than system behavior. Avoid treating usage logs or satisfaction scores as substitutes for mastery.

Delivery

Role takeaway

A course director should own the educational decision, with learning designers facilitating joint staff–student sessions and institutional research defining evaluation. Prepare examples, recruit beyond enthusiastic users, and budget staff time for discussion and revision. Dependencies include accessible participation, consent and clear assessment rules.

Proposed acceptance criteria
every tested task has an agreed assistance boundary, participants can explain it in a scenario exercise, and independent follow-up results are reported alongside participation gaps. These are proposed local gates. Review at pilot exit before expanding training or licenses. Risks include selecting only confident users, discouraging candid disclosure and measuring policy recall while overlooking whether learning support works.

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?

Use an approved practice environment with explicit task instructions and separate assessment access. No comparative evidence selects cloud, on-premises or hybrid hosting; developer tools and autonomous agents were not evaluated.

Governance

Who approves, reviews and stays accountable for outcomes?

Ask learners how they actually use assistance before setting assessment rules; do not equate a staff impression with misconduct evidence.

Security and privacy

What data, permissions and controls need testing?

Collect minimal, voluntary workflow examples and anonymize consultation records; avoid surveillance of personal AI accounts.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Include disabled learners, multilingual students and non-users in task testing; reserve staff time for learning rather than assuming an efficiency dividend.

Procurement

What should contracts, pricing and exit terms secure?

Require a short evaluation period, accessible access and configuration records; adoption interest alone does not justify long-term licenses.

Operating model

Which teams own the service once it runs?

Faculty own educational boundaries, learning technology staff own the environment, and evaluators separate perceptions from independent performance.

What changed

Absent from all 274 archive records inspected across offsets 0, 100 and 200 and targeted DOI search. Recent publication newly added to the archive; no post-last-run event is asserted. It adds direct staff–student comparison to earlier student-only adoption coverage.

Publication history

  1. 2026-09-13Student Success · Issue 082 resources
Read preserved resource versions (JSON)

Stable resource ID: kahn-staff-student-ai-perceptions-2026