Does the IT curriculum match what students need and expect?

Updated Mar 13, 2026

type and breadth of course contentinformation technology

An IT curriculum only feels valuable when students can see where it leads: current tools, practical projects, and assessment that reflects the work they want to do after graduation. NSS open‑text feedback shows that breadth matters, but students lose confidence quickly when resources fall behind or marking feels opaque. Across National Student Survey (NSS) open‑text comments tagged type and breadth of course content from 2018–2025, students are broadly positive (70.6% Positive across 25,847 comments), indicating that scope and variety usually land well across the sector. In Information Technology, sentiment is more mixed (53.0% Positive), with student voice prioritising dependable learning resources (10.5% of comments) and signalling that opaque marking criteria depress experience (sentiment −43.3). In a fast‑moving applied subject, breadth only feels meaningful when content stays current, resources work reliably, and assessment expectations are clear.

Students do not just want a wide syllabus. They want evidence that modules, examples, and tools still match the field they are entering. When programmes refresh content regularly and show how theory maps to application, students are more likely to see breadth as substantive rather than superficial.

How should course content and structure evolve?

Students value breadth when it is visible, navigable and current. Publish a one‑page content map showing core and optional topics across years, and schedule options to avoid clashes so cohorts retain real choice. Make quarterly refreshes to readings, datasets, case studies and toolchains routine in fast‑moving areas, a pattern echoed in computer science students' concerns about outdated course content. For work‑based routes, co‑design with employers so on‑the‑job tasks map to module outcomes and are reviewed on a set cadence. This gives students a clearer route from fundamentals to specialism, without duplication or gaps.

What shapes the IT learning experience?

Practical application shapes whether breadth feels worthwhile. Students expect labs, studios and projects that mirror the workplace and use contemporary stacks. Reliability of platforms, licences and IT facilities underpins learning; when these work, students focus on content rather than friction. Provide equivalent asynchronous materials and clear signposting so part‑time learners can access the same breadth without guessing what they missed. In IT, the strongest learning experience blends seminars with case work, labs and projects that show why the curriculum matters in practice.

How should we judge course quality and assessment?

Student feedback highlights assessment design as the lever that most affects perceived quality. In adjacent computing subjects, computer science students' trust in marking criteria is especially weak, and assessment methods attract the strongest negative tone in IT, so programmes should make expectations unmistakable: share annotated exemplars, checklist‑style rubrics and plain‑English assessment briefs that tie tasks directly to criteria. Set and meet feedback service levels with short "what to do next" summaries so students can act quickly. These moves protect academic standards, reduce avoidable anxiety, and improve perceived fairness and utility.

Do course expectations and goals match reality?

Many IT students choose the subject for employment‑focused study in areas like cloud, UI/UX and cybersecurity. When modules lag current practice or repeat content, trust drops quickly. Run an annual content audit, track quick wins to closure, and invite students in week‑4 and week‑9 pulse checks to flag missing or duplicated topics. Programmes that evidence timely change sustain confidence that breadth maps to real‑world roles.

What delivery and support models work best?

Operational dependability lifts student experience in IT. Keep a single source of truth for timetabling and programme updates, with short weekly notices and named owners for changes. Remote and hybrid elements work when virtual labs, simulations and discussion spaces are designed into modules rather than bolted on. Maintain straightforward routes to support, including personal tutors, office hours and service status pages, reflecting what IT students say about teaching staff and support, so students know where to go and what will happen next.

Where do students experience difficulties and challenges?

Fast‑moving content risks becoming dated and dense. Prioritise a progressive build‑up of knowledge with practical examples that reduce cognitive load, and retire obsolete material promptly. Facilities and software friction impede learning, so publish status pages and clear fix ownership to reduce downtime. Collaboration also needs scaffolding: design group tasks with staged deliverables and transparent contribution tracking to improve both experience and perceived fairness.

How should staff act on course feedback for improvement?

Use short, regular pulses to separate quick fixes from longer‑term redesign, and communicate the outcomes visibly. Share "you said, we did" updates that close the loop. Protect optionality in timetabling to keep breadth genuine, and provide equivalent asynchronous routes for flexible learners. These actions move sentiment from mixed to positive by showing that feedback translates into timely, substantive change.

What works in distance learning for IT?

Active online components, including virtual labs, containerised environments and real‑time walkthroughs, best replicate hands‑on learning. Combine recorded explainers with live problem‑solving sessions, and ensure assessment rubrics are visible within the virtual learning environment. Clear routes to technical help and pre‑flight checks for tool access reduce attrition and help distance learners stay engaged with core practice.

How Student Voice Analytics helps you

If you want to know whether students are asking for fresher content, clearer marking, or more reliable resources, Student Voice Analytics makes those patterns visible early.

• Track movement in student sentiment on breadth, content currency and resource reliability by cohort, mode and demographic, with exportable summaries for programme and module teams.
• Drill from institution to school/department and subject group to compare like‑for‑like peers in Information Technology.
• Generate concise, anonymised action briefs that show what changed, for whom and where to act next, ready for Boards of Study, Annual Programme Reviews and student‑staff committees.
• Evidence improvement by linking topic shifts, such as assessment clarity, resources and timetabling, to specific interventions over time.

Explore Student Voice Analytics to see which IT cohorts are asking for fresher content, clearer marking, and more reliable resources.

Request a walkthrough

Book a free Student Voice Analytics demo

See all-comment coverage, sector benchmarks, and reporting designed for OfS quality and NSS requirements.

• All-comment coverage with HE-tuned taxonomy and sentiment.
• Versioned outputs with TEF-ready reporting.
• Benchmarks and BI-ready exports for boards and Senate.

Book a free demo Prefer email? info@studentvoice.ai

UK-hosted · No public LLM APIs · Same-day turnaround

Related Entries

• What do IT students say about their teaching staff?
• What are UK computer science students saying about course content?
• Do current assessment methods meet computer science students’ needs?
• Do computer science students trust marking criteria?