HERM's lifecycles trace which systems a constituent touches. Journey mapping adds what they experience at each step — the thoughts, emotions, and pain points a systems diagram can't hold.
A user (or customer) journey map is a visualization of the end-to-end experience one person has while trying to accomplish a goal — stage by stage, from their point of view rather than the institution's. It records not just what happens, but what the person is doing, thinking, and feeling, and where the experience helps or fails them.
There is no single owning standard the way HERM governs capabilities or the TBM Council governs cost. It is an established UX and service-design practice, with widely used reference forms — the Nielsen Norman Group journey-map template and service blueprinting (which extends the map to the back-stage systems and staff behind each step). Treat those as reference forms to adapt, not a specification to conform to.
However they look, journey maps share five elements (Nielsen Norman Group). One point of view per map — to capture a student and a faculty member, build two.
The persona whose journey this is — one point of view per map, rooted in real data.
The situation the map addresses and what the actor expects — best for a sequence of events over time.
The high-level stages that organize everything else — they vary by scenario.
What the actor does, thinks, and feels in each phase — the emotion plotted as a line across the journey.
The takeaways — what to improve, who owns it, and how the change is measured.
Components from the NN/g Journey Mapping 101 framework.
Several map types are easily confused. Which you reach for depends on how specific and how internal the view needs to be.
The broad parent — a generic person in a general activity, agnostic of any one product. Good for understanding behavior before you design.
A specific actor in a specific scenario with your service — the form this page describes.
The journey extended to the back-stage — the systems, staff, and processes behind each step, from the institution's side. The tightest fit with the estate model.
For planning and implementation, not discovery — steps broken into features for delivery. The Agile cousin.
Most maps stack the same layers against a row of stages. Read across a stage to understand one moment; read down a layer to follow one thread the whole way through.
The phases the person moves through, front to back — the horizontal spine of the map.
What they are actually trying to do at each stage, in their words.
How the experience feels stage by stage — where confidence dips and friction bites.
The systems and channels they meet at each stage — the tie back to the catalog.
Where it breaks, and the make-or-break moments that define the whole journey.
What to fix, and who is accountable for the fix — the output that drives action.
A full student journey across the college experience, modeled on the Advising Success Network's Student Journey Map. It stacks the classic layers — emotion, ideal experience, interactions, technology, the student's own words, and the institution's responsibilities — against the stages a student moves through. The technology and institutional-responsibility rows are the tie back to the estate model.
Structure and content adapted from the Advising Success Network Student Journey Map. The full map continues into branching paths — graduation, transfer, certification, and career. The ideal use of technology and institutional responsibilities rows are where this map meets the estate: each names systems and owners the catalog records.
The University of Edinburgh's Prospective Student Web Team published a set of research-grounded journey maps for prospective students — one for undergraduates, one for taught postgraduates, and two for PhD applicants — built from three years of interviews and workshops. Their write-up is a clear, real-world model for the practice this page describes: maps grounded in user research, treated as a living resource, and used to break down the silo effect across recruitment and marketing services.
The evidence base is also maturing. A 2025 systematic review in Review of Education screened over 15,000 studies and synthesised 21, covering the three main frameworks — Customer Journey Mapping, Service Blueprinting, and the Brand Touchpoints Wheel. It reports real benefits (service improvement, innovation, sharper awareness of student and staff needs) alongside the recurring challenge of turning maps into sustained change — the same gap this page closes by tying each mapped pain point to a system and owner in the estate model.
HERM and journey mapping meet at the lifecycle. HERM's constituent journeys already name the stages and the systems each touches; journey mapping layers the human experience onto those same stages. The map gives the feeling and the friction; the model tells you exactly which system and capability sits behind each painful step — so a fix has an owner, not just a sentiment.
A pain point stops being a complaint and becomes a specific system-and-step to change.
The hand-offs the model surfaces are usually the exact moments the journey map shows frustration spiking.
Emotion shows what to fix first; the model shows what it will take and who owns it.
Extending the model toward journey mapping means adding an experience layer to each lifecycle stage. A pragmatic starting set:
Whose journey this is — first-year student, transfer, PI, new hire — since experience differs by who.
What the person is trying to do at each stage, in their language.
A sentiment rating per stage, so the highs and lows read at a glance.
Where the experience breaks, linked to the system and step behind it.
The make-or-break stages that shape the whole impression.
The improvement and the person accountable — the map's actionable output.
Take a lifecycle the model already holds, pick one persona, and walk it stage by stage with the people who live it. Add an emotion rating and a pain point to each stage, then link each pain point to the system behind it. You now have the experience and the fix in one view — the map shows the where-it-hurts, the model shows the what-to-change.
Journey mapping is a UX and service-design practice with no single owning standard; the Nielsen Norman Group template and service blueprinting are common reference forms. The layers and example here are local extensions an institution would populate with its own research.