Blog / Design · 7 min read ·
User journey mapping for capstone systems
Build personas, map each stage of a user's journey, and turn real pain points into features your panel can trace back to evidence.
Most capstone systems are designed from the developer's chair: a list of modules, a database, and a login screen. A user journey map forces you to design from the user's chair instead, one step at a time, so that every feature you build answers a problem someone has.
This guide walks through personas, journey stages, the journey table itself, and the step most teams skip: turning pain points into features you can defend in front of a panel.
What a user journey map is
A user journey map is a structured description of how one type of user moves through a task from start to finish, including what they do, what they think, where they get stuck, and where your system could help. It is not a flowchart of your software. It describes the current experience first, often before any software exists.
For a capstone, the journey map sits between your data gathering (interviews, observation, surveys) and your requirements. It is the bridge that lets you say: "We built the SMS reminder because residents told us they miss their queue number while waiting outside." That sentence is far stronger in a defense than "We added SMS because it is a common feature."
Start with personas grounded in your data
A persona is a short profile representing a group of real users with similar goals and constraints. Build personas from what you learned in interviews and observation, not from imagination. If you have not interviewed anyone yet, do that first; a persona without data is a guess with a name attached.
Keep each persona to what affects design decisions:
- Role and goal: who they are in the process and what they are trying to finish.
- Context: where and when they do the task, on what device, with what connectivity.
- Skill level: comfort with phones, computers, and forms.
- Frustrations: the recurring problems they mentioned, in their own words where possible.
- Constraints: time, cost, language, accessibility needs, office hours.
For a barangay records system, you might end up with three personas: a resident requesting a barangay clearance, the barangay secretary who encodes and prints documents, and the punong barangay who signs and reviews reports. Each has a different journey through the same process.
Define the journey stages
Stages are the major phases of the task from the user's point of view. Name them with plain verbs the user would recognise. Four to six stages is usually enough; more than that and the map becomes a process manual.
For a resident getting a barangay clearance, the stages might be: Find out requirements, Go to the barangay hall, Wait and submit, Pay, and Receive the document. For a student enrolling in a private school: Check schedule, Submit documents, Get assessed, Pay fees, Get class schedule. Notice that none of these mention your system. You are mapping the current reality.
Build the journey table
For each stage, fill in four rows: what the user does (actions), what they are thinking or feeling (thoughts), what goes wrong (pain points), and how a system could help (opportunities). A table is easier to review with your adviser than a decorated poster, and it drops straight into your documentation.
| Stage | Actions | Thoughts | Pain points | Opportunities |
|---|---|---|---|---|
| Arrive | Travels to the clinic early, writes name on a logbook at the door | "If I am not early, I will not be seen today." | Arrives hours before opening; no idea how many are ahead | Show the daily slot count and current queue length before travel |
| Wait | Sits or stands outside, listens for name being called | "I cannot leave or I will lose my turn." | Cannot step away; names are misheard or skipped | Issue a queue number and send an SMS when three patients are ahead |
| Consult | Gives history again to the nurse and then the doctor | "I already said this last month." | Repeats history every visit; paper records are hard to find | Retrieve previous visit notes by patient ID for staff |
| Get medicine | Lines up at the pharmacy window | "I hope they still have stock." | Medicine is out of stock after waiting | Let staff record stock levels so the doctor sees availability |
| Follow up | Told verbally to return in two weeks | "Was it two weeks or three?" | Forgets the follow-up date | Print or send the follow-up date with the clinic schedule |
Write the thoughts column in the user's voice. Quotes from interviews, paraphrased to remove identifying details, are ideal. The pain points column should describe the problem, not the solution; "no SMS" is not a pain point, but "misses their turn while waiting outside" is.
Map more than one persona
Do a separate table for each key persona. The clinic nurse's journey through the same morning looks different: calling names, searching for paper records, tallying patients for the daily report. Often the staff-side journey reveals the features that make the system sustainable, such as reports that replace manual tallying.
Turn pain points into features
This is where the map earns its place in your manuscript. Every feature in your scope should trace back to at least one pain point, and every serious pain point should either map to a feature or be listed as out of scope with a reason.
- 01
List every pain point
Pull them from all persona tables into one list. Give each an ID such as PP-01, PP-02.
- 02
Rate severity and frequency
For each pain point, note how often it happens and how much it costs the user (time, money, missed service). Use what respondents told you, not your own guess.
- 03
Write an opportunity statement
Phrase it as "How might we…", for example: "How might we let patients leave the waiting area without losing their turn?"
- 04
Propose the smallest feature that solves it
An SMS alert when three patients are ahead solves PP-02. A full mobile app with live tracking might also solve it, but costs far more to build and maintain.
- 05
Check feasibility
Confirm you can build it with your team's skills, budget, and timeline, and that the client can operate it. SMS gateways cost money per message; record who pays.
- 06
Record the trace
Add the feature to a traceability table linking pain point, feature, and objective.
| Pain point | Feature | Related objective |
|---|---|---|
| PP-01: Consumers do not know their bill until the paper notice arrives | Consumer portal showing current reading and amount due | Objective 1: Provide timely billing information |
| PP-02: Meter readers re-encode readings from paper sheets | Mobile reading entry with offline storage and later sync | Objective 2: Reduce manual encoding |
| PP-03: Disputes over readings take days to resolve | Photo of the meter attached to each reading | Objective 3: Support faster dispute resolution |
| PP-04: Long lines at the cashier on due dates | Out of scope: online payment requires a payment partner agreement | Listed under limitations |
From journey map to screens and test cases
Once features are traced, draw the future journey: the same stages, but with your system in place. This becomes the basis for your use case diagram, your wireframes, and your test scenarios. Each stage of the future journey usually maps to one or two screens, and each pain point gives you an acceptance test: "A patient with queue number 15 receives an SMS when number 12 is called."
During usability testing, walk participants through the future journey and watch for new pain points. Update the map; it is a working document, not a one-time deliverable.
Common mistakes
- Mapping the system's screens instead of the user's real task.
- Inventing personas and pain points without interviews or observation.
- Writing solutions in the pain points column.
- Only mapping the end user and ignoring staff who will operate the system daily.
- Building features that no pain point justifies, then struggling to explain them in the defense.
- Treating the map as decoration rather than linking it to objectives, requirements, and tests.
Presenting the map in your manuscript and defense
Place personas and journey tables in the chapter where you present your data gathering results or system requirements, following your school's template. In the defense, one slide with the most important journey and one slide with the traceability table are usually enough. Panels respond well to a clear line from "this is what users told us" to "this is what we built".
Next step
Build the journey table for your main user this week, using what you learned from your interviews. Then turn each pain point into a feature and a screen, using the wireframing guide.