Universities need a whole-journey view of student voice, not isolated survey snapshots
Updated Jun 04, 2026
Most universities collect student feedback in fragments. Module evaluations sit in one system, service surveys in another, and open comments often remain unread until a review meeting forces them back into view. Hyunjoo Kim and Min Jae Park's Higher Education Research & Development paper, "Rethinking the student journey with voice of student: unstructured data-driven approach", matters because it asks what happens when universities treat student voice as a connected stream of evidence rather than a series of disconnected survey events. For UK teams trying to turn comments into usable institutional evidence, that is a more practical question than another standalone satisfaction score.
Context and research question
Universities already generate large amounts of narrative student data: module evaluation comments, NSS-style free text, induction surveys, service feedback, complaints, and other records of what students say as they move through university. The problem is that these sources are often analysed in isolation, with one-off coding exercises or shallow dashboards that do not add up to a coherent view. That makes it harder to see whether an issue starts at transition, grows during teaching, or resurfaces later in the student lifecycle, which is one reason a repeatable NSS open-text analysis methodology matters.
Kim and Park address that problem by proposing a "Student Journey" perspective for unstructured data. The paper asks how universities can analyse student-generated text from admission to graduation in ways that reveal learner needs and support better management decisions. The authors test that idea through a university case study in South Korea, using text mining and network analysis to turn dispersed narrative data into a more strategic picture of the student experience.
Key findings
The paper's central move is to treat unstructured student data as journey evidence, not just feedback residue. Rather than focusing on a single survey or a single point in the year, the authors argue for analysing student-generated text across the full university experience. For UK institutions, the benefit is clear: recurring issues become easier to spot when they are tracked across stages instead of being rediscovered in separate surveys every term.
The "student journey" is presented as a practical analytic frame, not a metaphor. The abstract makes the ambition explicit:
"The perspective of 'Student Journey' aims to analyze various unstructured student data generated throughout the university experience"
That matters because it shifts the task from summarising isolated feedback exercises to building a connected view of need, friction, and change over time.
Text mining and network analysis are positioned as institutional tools, not just research techniques. The paper does not use unstructured comments simply to describe what students feel. It uses those data to identify key factors that can inform policy and service design. That is useful for UK higher education because free-text comments often contain the earliest signals about transition, support access, workload, clarity, or belonging, long before those issues show up cleanly in a headline score.
The case study also suggests that value comes from breadth plus comparison. According to the abstract, the approach combines comprehensive analysis of unstructured student data with comparative insight that can support student-centred management policy. In practical terms, universities learn more when they compare patterns across departments, subject areas, and stages of the journey than when they read each dataset as a standalone story.
A quieter methodological point runs through the paper: collecting more comments is not enough. Without a framework for organising narrative data, institutions remain stuck with anecdotes. For UK teams, the message is that method, taxonomy, and reporting discipline determine whether student voice becomes actionable evidence or background noise.
Practical implications
First, UK universities should stop limiting student voice analysis to single survey windows. A stronger approach links induction feedback, module evaluations, major surveys, and service comments through a shared set of themes and clear ownership. When teams can see where a theme first appears and where it persists, they can intervene earlier and assign responsibility more clearly. The benefit is earlier action with better accountability.
Second, institutions should treat unstructured student data as governed evidence. Before combining sources, decide which comments can be used, who can access them, how categories will stay stable over time, and how sensitive material will be handled. Our student comment analysis governance checklist is relevant here because lifecycle listening only helps if the method is consistent and defensible. The benefit is that insights become safer to use in quality enhancement and institutional reporting.
Third, universities should compare narrative patterns across departments and cohorts rather than defaulting to one institution-wide summary. The logic of this paper is strongest when it reveals variation: one school may struggle at transition, another at feedback clarity, another at support access. That is where Student Voice Analytics fits naturally. It helps universities categorise free-text comments consistently across surveys and stages, so teams can benchmark patterns without recoding from scratch every cycle. The benefit is more precise local action without losing institutional comparability.
Finally, institutions should keep scores and comments together. Quantitative indicators remain useful, but they rarely explain why student experience shifts. A joined-up workflow that pairs survey results with narrative themes, and that uses specialist text analysis software for education when scale demands it, gives UK teams a stronger basis for decisions. The benefit is better diagnosis, not just better monitoring.
FAQ
Q: How could a UK university start using a student-journey approach without launching a major transformation project?
A: Start with two or three high-value touchpoints, such as induction comments, module evaluations, and NSS or PTES open text. Use a stable theme set, document the purpose of each dataset, and review the combined results after each cycle. The goal is not to ingest every piece of text immediately. It is to build a repeatable view of where the same issues reappear, so action becomes more targeted.
Q: What are the methodological limits of this paper?
A: It is a single-university case study from South Korea, and the publisher abstract explains the approach more fully than the implementation detail. UK teams should therefore read it as a strong design proposition rather than a ready-made template. The important test is whether the same approach surfaces useful, governable patterns in local comment data and decision cycles.
Q: What does this change about student voice practice more broadly?
A: It shifts student voice from an end-point measurement activity to a continuous evidence function. Instead of asking only what students said in one survey, universities can ask what students keep telling them across the whole journey, and where action should start first. That makes student voice more useful to Student Experience teams, PVCs, and Market Insights staff because it connects listening directly to institutional decision-making.
References
[Paper Source]: Hyunjoo Kim and Min Jae Park "Rethinking the student journey with voice of student: unstructured data-driven approach" DOI: 10.1080/07294360.2025.2543410
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.
UK-hosted · No public LLM APIs · Same-day turnaround