Insights, personas, and user journeys

Objectives

By the end of the lesson, you can look for patterns in raw research notes and turn a quote and an observation into a design insight. You can create a persona and a user journey that are usable for decisions, rather than an invented biography.

Why are notes not enough?

After an interview or observation you will have a lot of material: quotes, details, impressions. It is easy to remember the strongest or the most recent sentence and to draw conclusions from it. The purpose of analysis is to organize signals from several sources, and to treat as a result only what recurs or what has serious consequences. We learn three tools: the affinity map (organizing), the insight (interpretation), and the persona and journey map (condensing the research).

Notes are not yet a result

Affinity mapping

An affinity map is the grouping of raw notes. The steps:

1. One sticky, one observation or quote. Mark which participant it comes from (for example P1, P2).
2. Group the similar ones without using predetermined categories. Let the groups form from the stickies.
3. Name the groups with a statement each, not a topic label: not "Price", but "The price is missing before the decision".
4. Count how many mentioned the theme of the group, and see whether there are counterexamples.

It is worth labeling goals, obstacles, decision criteria, quotes, and exceptions separately. If three people say "I didn't know whom to write to", this does not yet mean a chat window is needed. First ask: what information was missing? Whom could they have turned to? Why was this not visible or trust-inspiring?

What makes an insight an insight?

An insight is a realization built on evidence that explains a behavioral pattern and leads to a design consequence. Distinguish three things:

	Example	Why is it not an insight?
Observation	"Two of them opened several tabs."	A fact, but does not explain
Wish	"They would like a simpler interface."	Does not say what and why
Insight	"Participants feel that options are comparable only if price, time, and restrictions are visible at the same time; therefore data hidden behind details causes decision uncertainty."	Explains, and gives design direction

A useful template: observation → interpretation → design consequence. This way the insight does not turn into opinion, and the team can trace what data it started from. If you saw something with only one participant, write that down too, but mark it as an exception or a signal awaiting further investigation.

Priority and counterexample

Not every insight is equally important. When prioritizing, examine the user impact, the frequency, the consequence of the error, and the uncertainty of the solution. A counterexample is also valuable: if someone completes the task without trouble, find out what prior knowledge, tool, or situation helped them. It may be that the interface did not work well, but they already knew the system.

Persona as a decision tool

A persona is a description of a target user derived from research patterns that helps decisions. A persona is not "Nóra, 21 years old, likes coffee". Demographics alone rarely tell us how to design. A useful persona describes from the point of view of the task:

• the situation: when and where they use it;
• the goal: what they want to achieve;
• the knowledge and device: what they know, what device they use;
• the constraint: what makes it harder (time, attention, language);
• the risk: what they fear, what the consequence of the error is.

For example: "A student handling an administrative matter for the first time, who has little time, does not know the official names of the process, and is afraid of missing a deadline." This immediately raises labeling, timing, and feedback questions.

In a project, one primary target user is usually enough. If you name several roles, write down who is primary in which task, and what happens in case of conflict. Do not make a persona from every quote; the persona condenses the important patterns. If you give it a name and a face (and this helps the team), do not let it become the focus: the essence is the situation and the decision, not the character.

An important limit: a persona without research is only an assumed character. Where an element of the persona does not come from research, mark it clearly as an assumption.

User journey map

A user journey shows the steps of a specific task from the user's point of view, from beginning to end, together with feelings and pain points. A journey map is its visual representation.

A typical grid (rows are the labels, columns are the stages):

	Orientation	Comparison	Decision	Registration	Before the event
Steps	Searches on several pages	Opens tab after tab	Picks one	Fills in a form	Checks the details
Thoughts	"What's worth it?"	"Which is cheapest?"	"Do I really need to register?"	"Is it final yet?"	"What time does it start?"
Feeling	Curious	Uncertain	Tense	Doubtful	Relieved
Pain point	Scattered sources	Missing data	Hidden conditions	No confirmation	–
Opportunity	One place, several sources	Unified card	Conditions up front	Clear confirmation	Reminder

The journey should follow a single, well-delimited task. If it shows several tasks at once, it will not be visible where the biggest trouble is. Derive the emotional line (curve) from the research: from the quotes and observations that showed uncertainty, relief, or frustration; do not invent it.

The journey is the predecessor of the user flow (chapter 5): the journey describes the user's experience, while the flow designs the steps of the system and the user.

Worked example: the insight and journey of Mai program

Based on four interviews, the Mai program team finds three groups on the affinity map: "Price and language are missing from the card", "The registration requirement only becomes clear at the end", and "Friends' opinions decide". The second group is mentioned by three out of four participants, and in two cases the outing fell through because of it.

Insight (observation → interpretation → consequence):

• Observation: participants often learned about the registration obligation when they had already decided, or on site.
• Interpretation: among the decision criteria, the conditions become visible late, so the decision is not firm.
• Design consequence: the registration requirement and the price should be on the result card, before the decision.

The persona in one sentence: "A student looking for a spontaneous program, who wants to decide within an hour or two, does not want to browse through several pages, and is afraid of arriving without a ticket." The journey follows a single task according to the grid above: "choosing a program for tonight and registering".

Common misconceptions

Claim	Clarification
"A persona replaces research."	A persona is a summary after the research; without research it is only an assumed character.
"Every request becomes a feature."	The goal and obstacle behind the request are more important than the solution the participant proposes.
"The most mentioned thing is always the most important."	A rarer but serious-consequence error, such as a wrong payment decision, can be prioritized.
"A journey map is a pretty infographic."	A journey map supports decisions: it shows where the biggest pain point and opportunity are.

In brief

• Organize the notes first (affinity map), and only then interpret them.
• An insight derives a design consequence from observation and interpretation.
• A persona describes the situation, goal, knowledge, constraint, and risk from the point of view of the task, not demographics.
• A journey map shows the experience of a specific task with steps, feelings, and pain points.

Review questions

1. What is the difference between an observation and an insight?
2. What evidence supports your strongest insight?
3. What design decision does your target user description help?
4. Which counterexample should you investigate further?