Tools of Expression — How to Share the Invisible with Your Team
Understanding the user shouldn't stay locked inside one person's head. We look at five tools — Persona, Empathy Map, Scenario, User Journey Map, and Storyboard — for sharing the invisible experience of the user with the rest of the team.
Observing, analyzing, and defining the user builds an understanding inside our own heads. But that understanding still lives only within one person. Design is never a solo act, so this understanding has to be shared with the rest of the team. The tools covered in this post are the ones we reach for when it’s time to share the user and their experience with teammates.
These tools all have something in common: they make the invisible visible. A user’s motivations, emotions, context, journey — none of these can be seen directly. These tools give shape to what is otherwise invisible, so that the whole team can look at the same thing and move in the same direction.
Persona
“Who exactly are we designing for?”
A persona is a fictional character built to represent a group of users. Basic facts — name, profile photo, occupation, age — are combined with personality, preferences, and goals to construct the identity of a single person. Not every one of these elements is mandatory. Start with the minimum information needed to picture the user, then keep filling it in while checking whether the persona is becoming a solid enough basis for design decisions.
The tagline deserves special attention. It condenses the persona’s core concern or need into a single sentence, and it becomes a compass whenever there isn’t time to study the full persona during the design process. A single question — “Would someone who carries this sentence close to their heart enjoy this experience?” — is often enough to bring the user back to mind. The more carefully the tagline is crafted, the more consistently the insights from user observation carry through the rest of the process.
Picture the Double Diamond: the persona sits exactly at the point where the two diamonds meet. It’s the condensed output of observation and definition, and at the same time the starting point for the experience design that expands outward from there.
A caution. A bad persona can throw an entire project into confusion. Never fabricate attributes irresponsibly just to fill every field of a template, use a name or celebrity photo that doesn’t fit the user group, or reverse-engineer a persona to match a scenario you already had in mind. When an attribute is uncertain, it’s better to leave it out and keep the persona lean.
Above all, a persona without observation behind it is a fiction. A persona must be the distilled product of user observation and definition. A persona that appears out of nowhere severs the early half of the project from the later half, and undermines the entire point of going through a UX design process in the first place.
Empathy Map
“What’s happening inside the user’s mind?”
An empathy map records the user’s experience across four quadrants.
- Says: Direct quotes and utterances captured during interviews or observation
- Thinks: Inner thoughts, expectations, and questions the user didn’t voice but that surface anyway
- Does: Concrete observed behaviors and behavioral patterns
- Feels: The user’s emotional state — anxiety, anticipation, frustration, satisfaction, and so on
If a persona sketches the user’s outer contour, an empathy map looks inward. Deep insight tends to emerge from the gap between Says and Thinks — the space between what the user says and what they’re actually thinking. If a user says “It’s fine, it’s usable” (Says) while pressing the same button a third time (Does), there’s something happening in between worth paying attention to.
A caution. An empathy map is a tool for organizing observed data, not imagined data. What goes into all four quadrants has to come from actual observation and interviews. Thinks and Feels, in particular, involve the observer’s interpretation, so it’s worth building the habit of recording the observed facts that back up each interpretation.
Scenario
“What kind of experience does the user go through, and in what context?”
A scenario is a narrative account of the sequence of events a persona goes through to reach a goal in a specific situation. The key word is “narrative.” A scenario isn’t a feature list — it takes the shape of a story. A feature list tells you only the “what”; a scenario captures the “when, where, why, and how it felt” as well.
“The user searches for a product and adds it to the cart” is a functional spec. “On the subway ride home, Jimin — trying to pick out a birthday gift for a friend’s party tomorrow — holds her phone in one hand and types ‘gift for man in his 30s’ into the search box. The results are overwhelming, and as she scrolls, the train jolts and she accidentally taps the wrong item…” is a scenario. The second version carries context, constraints, emotion, and the unexpected.
Scenarios split by purpose. An As-Is scenario describes the experience the user currently goes through, exposing exactly where the problems occur. A To-Be scenario describes the improved future experience that the design aims to deliver, laying out the direction of change. Placing the two side by side makes it clear what the design is actually trying to change.
A caution. A good scenario has to be rooted in a persona. The persona’s personality and tagline should be the basis for the behavior described in the scenario, and the flow of context and emotion needs to be faithfully reflected. A scenario disconnected from its persona is nothing more than the designer’s imagination.
User Journey Map
“Where does the overall flow of the experience break down?”
A journey map is a scenario rendered visually. Time runs along the horizontal axis and the user’s emotion or satisfaction runs along the vertical axis, showing the ups and downs of the experience at a glance.
The strength of a journey map is that it gives you a view of the whole rhythm. Things that are easy to miss when you’re absorbed in individual steps — a stretch of consecutive negative experiences, or a flat journey with no emotional high point — stand out clearly once they’re mapped.
Two core concepts make up this map. A touchpoint is any moment where the user comes into contact with the product or service — seeing an ad, downloading the app, calling customer support — and at each one, the user forms an emotional reaction. A pain point is a moment where the user experiences discomfort or frustration: a place where the emotion curve drops sharply, and where design intervention is most urgently needed.
The word “map” is worth dwelling on. In the earlier post on KJ Mapping, we noted that the word “map” carries the meaning of two-dimensional coordinates, distance, and relative position — and the same is true here. On the horizontal axis of time and the vertical axis of emotion, the coordinates of each point, and the distance and slope between points, all carry meaning.
A caution. A beautifully drawn journey map that fails to reflect the user’s actual experience is nothing more than decoration. The value of a journey map lies not in visual polish but in accuracy grounded in observation.
Storyboard
“Can the whole team grasp the flow of this experience at a glance?”
A storyboard expresses a scenario as a sequence of visual scenes, like panels in a comic strip. Each panel captures the user’s action, environment, and emotion through a simple drawing and a short caption.
If a scenario is a story told in words, a storyboard is a story told in pictures. Things that are hard to convey through text alone — spatial arrangement, physical movement, the passage of time, the relationship between the user and their environment — come through intuitively in a visual scene. Reading about “a scene of searching one-handed on a jostling subway train” and seeing that scene drawn out simply land differently.
A storyboard also reduces divergent interpretation in team communication. People reading the same scenario can each picture a different scene in their head, but a storyboard puts everyone in front of the same one.
A caution. What matters in a storyboard isn’t the polish of the drawings but the accuracy of scene selection. It should capture, as panels, the moments that matter most in the experience — where expectation forms, where a problem occurs, where an emotion shifts. Trying to draw every single step without exception only blurs the focus.
The tools covered in this post — Persona, Empathy Map, Scenario, User Journey Map, and Storyboard — all do the same job: giving shape to something that is inherently invisible, the user’s cognition and emotion. Once something has shape, it can be shared. Once it can be shared, the team can align. And once the team is aligned, design moves forward on shared understanding instead of relying on any one person’s gut feeling.
In the end, these tools exist for one reason. In a field that deals with something as invisible as user experience, they make the invisible visible and place it on a table where it can be discussed together.
The next post moves on to “tools of implementation” — the tools that turn an idea still living in someone’s head into something you can hold in your hands, like paper prototypes and wireframes.