Guide to Running UX Sessions: Personas, Design Empathy & Journey Mapping

Introduction

User experience (UX) design is most effective when grounded in a deep understanding of users. This guide walks you through three key 60-minute UX workshop sessions – User Persona Identification, User Empathy Mapping, and Customer Journey Mapping – which you can run with your team to build user-centered web or mobile applications. Each session is designed for beginners to intermediate practitioners and focuses on a specific activity that helps your team empathize with users and translate insights into better design decisions. The sessions can be run individually or in sequence for an accelerated design sprint.

Each of these workshops brings together cross-functional team members (e.g. designers, developers, product managers, marketers) to collaboratively capture who your users are, what they need and feel, and how they experience your product. By actively involving stakeholders, you “democratize knowledge” about users – everyone gains a shared understanding of the target audience and their pain points.

Below, we outline how to prepare and run each 60-minute session, including step-by-step agendas, tips, and expected outcomes. If you’re a Figma or FigJam user, checkout these free FigJam templates to drive your discussions around personas, empathy maps, and journey maps, so your team can fill them in during the workshops. Let’s get started!

User Persona Identification Session (60 Minutes)

Loading diagram...

A persona identification session (persona workshop) is a collaborative exercise where your team defines one or more user personas – fictional characters representing your key user segments. The goal is to synthesize research about real users into an engaging profile that highlights the user’s goals, motivations, behaviors, and frustrations. A well-crafted persona puts a face and name to your target user, helping everyone design with a specific user in mind rather than a generic "user".

Personas are useful only if they’re accurate and used by the team, so avoid the common pitfall of basing personas on guesses or stereotypes – use actual user data and insights. Also, treat personas as living documents: they may evolve as you do more research, rather than remaining a one-off artifact that “gathers dust” unused. The persona workshop helps ensure the persona is actionable and agreed-upon, not just a pretty poster on the wall.

Preparing for the Persona Session

• Gather Research Ahead of Time: Before the workshop, compile any existing user research – interview notes, survey results, analytics, support tickets, etc. – that sheds light on your users’ characteristics and needs. Analyze this data for patterns (e.g. common goals or pain points) and identify distinct user segments you might need personas for. If you have very diverse users, you might end up creating multiple personas (in multiple sessions) rather than trying to force everyone into one persona. For a 60-minute session, plan to focus on one persona at a time for depth and clarity.
• Invite a Diverse Group of Stakeholders: Include team members from different roles (design, engineering, product, marketing, etc.) who interact with or impact the user experience. A diverse group ensures varied perspectives when crafting the persona. Make sure attendees understand the purpose of the workshop and come prepared to actively participate (not multitask) – their engagement is key to success.
• Prepare a Persona Template: Have a Figma (or other) persona template set up with sections for all the information you'll capture (details on what to include below). This template serves as a canvas for the group to fill in. Keep it simple and clear – the focus should be on content, not flashy design. (If working in-person, you could use a whiteboard or large paper with sections drawn out instead.)

Persona Session Agenda & Steps

1. Introduction (5 minutes): As the facilitator, start by explaining the goal of the session and what a persona is. Emphasize that the persona should be rooted in real user observations and data, not personal conjecture. If participants have done pre-reading of research, briefly recap the key insights about users discovered so far. Also, introduce the format: the team will collaboratively draft a persona profile for a target user segment within an hour. This introduction sets the stage and gets everyone on the same page regarding why this is important – e.g. personas help "provide a clear picture of user goals, behaviors, and pain points" for the team.

2. Define the User Segment (5 minutes): Clearly identify which user you are persona-izing. Based on your research, describe the user segment or scenario you’re focusing on (for example, "first-time app users who are tech-savvy college students" or "busy working parents using our service on mobile"). This ensures everyone knows whose perspective to take. Give this proto-persona a tentative name or category (even something like “The Busy Parent” persona) to anchor discussions.

3. Brainstorm User Attributes (15 minutes): Now invite the team to brainstorm attributes of this user. A good method is to have each participant silently write down facts or insights about the user on sticky notes (physical or virtual) for a few minutes, then share with the group. Prompt them with questions: What are this user’s goals when using our product? What challenges or pain points do they experience? What motivates them? What is their background (job, age, tech experience)? Encourage basing these answers on real evidence from user research or customer feedback (“Our customer interviews showed this user often says_”, etc.). As participants share, cluster similar ideas together on the board. Discuss any conflicting assumptions and use data to resolve them where possible.

4. Fill Out the Persona Template (30 minutes): Together, start populating the persona template with the information you've gathered. Focus on the key sections one by one, ensuring group consensus on each:

   • Name & Basic Details: Give the persona a name (and maybe a fun alliterative descriptor like “Mobile Max” or “Analytical Anna” that hints at a key trait). Fill in basic demographics and career info: age, gender, job title, industry, etc.. (These details should align with your target user segment; use averages or typical values from research.)
   • Bio or Background: Write a short narrative about the persona’s life and context. This can include a personal quote summarizing their attitude or a key pain point in their own words. For example, “I need to manage my tasks on the go between classes” might be a quote for a student persona. Also, include a brief bio: what is a day in their life like? How did they come to need a product like yours? This story makes the persona more relatable.
   • Goals and Motivations: List the persona’s primary goals related to your product or domain. What are they trying to accomplish? What does success look like for them? Also note motivations – why do those goals matter? For instance, a goal might be “Keep track of my to-do list across devices” and the motivation “so I don’t miss important deadlines while away from my desk.” These help your team understand what value the user is seeking.
   • Frustrations and Pain Points: List the challenges, obstacles, or pain points the persona encounters. These could be general pain points in their life or specific frustrations with current solutions (or your product). For example, “Feels overwhelmed juggling work and family – often forgets tasks” could be a pain point. Pain points highlight opportunities for your product to solve problems.
   • Behaviors and Context: Note any relevant behaviors or context of use. How and when does this persona interact with products like yours? Are they tech-savvy or reluctant users? Which devices do they prefer? Any environmental factors (noisy workplace, on the move, etc.)? These details ensure the persona is grounded in reality (e.g. “Uses mobile app during commute”).
   • Influences and Information Sources: Capture what influences the persona’s decisions. Do they trust online reviews, advice from colleagues, social media? Also, note where they get information related to your product’s domain. For instance, “Researches solutions via YouTube tutorials” or “Follows industry blogs”. This can guide marketing and support strategies for this user type.

   Throughout this process, encourage the team to refer back to actual research findings. If there's uncertainty (e.g. “We think they value X, but not sure”), mark it as an assumption to validate later rather than guessing. The facilitator should write the information into the template in Figma (or stickies on a board) as the group agrees on each point. By the end, you should have a draft persona profile that feels tangible and based on real user insight.

5. Review and Refinement (5 minutes): Use the last few minutes to review the completed persona. Read through each section aloud and check for consistency – does it all make sense as one person? This is a good time to spot any gaps or overly vague statements. If something is unclear or too generic (e.g. “user is frustrated by bad UX” – too broad), ask why and refine it (e.g. “gets frustrated when apps require too many steps, due to limited time”). Ensure the persona passes the reality check: ask the team if they can visualize a real person when reading this profile, and whether this would be a user who meaningfully interacts with your product. If certain details are still based on assumptions, note them as research to-dos. Finally, agree on next steps – typically, the facilitator or a researcher will polish the persona document after the session (clean up the writing, maybe add a stock photo for the persona, etc.) and then share it with the team. Remember, a persona is never truly “finished” – it should be updated as you gather more user insights. Encourage the team to actually use this persona in future design discussions, and iterate on it over time rather than treating it as an immutable artifact.

By the end of the persona session, you will have one or more persona profiles that the whole team contributed to and agrees upon. These personas will be the foundation for the next sessions (Empathy Mapping and Journey Mapping) and for design decisions moving forward.

User Empathy Mapping Session (60 Minutes)

Once you have a persona defined, a user empathy mapping session helps the team deeply understand the persona’s perspective – their sensory and emotional experience. An empathy map is a visual exercise where you literally map out what the user says, thinks, does, and feels in a particular situation (often when interacting with your product or trying to achieve a goal). The empathy map adds richness to your persona by focusing on their mindset: what’s going through the user’s mind? what influences them? what problems or fears do they have? By the end, your team should empathize with the user’s situation and uncover insights that might not surface through data alone.

Preparing for the Empathy Mapping Session

• Define the Scope: Decide which persona (or personas) and scenario you will map. It’s best to do one empathy map per persona per scenario. For example, you might choose to map how “Persona A feels when using Feature X of our app for the first time.” Having a clear focus ensures the exercise is grounded. If you have multiple distinct scenarios, you can run separate 60-minute mapping sessions for each.

• Use Research to Inform the Map: Gather qualitative inputs about the persona’s experience ahead of time. Ideally, this comes from user interviews or observations. Atlassian’s playbook emphasizes: “don’t guess, and don’t make assumptions” – base the empathy map on real customer quotes and behaviors whenever possible. If you’ve interviewed users like this persona, have notes or recordings available. If not, consider doing quick user research before this session, or at least use support tickets, app reviews, etc., to draw insights about what users say and feel.

• Prepare the Template: In Figma (or on a whiteboard), set up an empathy map diagram. Typically, this is a four-quadrant layout with sections labeled "Says", "Thinks", "Does", "Feels" (sometimes “Sees” and “Hears” are included, making six sections, or combined into the four main quadrants as in the image above). Many empathy map templates also include areas for Pain (pains/frustrations) and Gain (goals/needs or what success looks like). Make sure each section is clearly titled. If using Figma, you might pre-fill the persona’s name and scenario at the top, and perhaps even drop in any relevant user quotes you have as starting points.

• Invite the Right People: Similar to the persona workshop, include team members who will benefit from stepping into the user’s shoes – designers, developers, product managers, customer support reps, etc. A smaller group of 3–6 people is ideal for a mapping exercise, so everyone can contribute actively. Share the chosen persona profile and scenario with them beforehand, so they come in with context.

Empathy Mapping Session Agenda & Steps

Loading diagram...

1. Set the Stage (5 minutes): Begin by restating the persona and scenario you’re focusing on. For example: “We’re going to immerse ourselves in Alex (Persona A)’s experience of trying to accomplish {Goal} using our product.” Clarify that the task for the next hour is to think like the user – this isn’t a brainstorming about features, but an exercise in empathy. Encourage participants to really put themselves in the user’s context (imagine their day, their pressures, their environment). Remind everyone of the ground rule: use any real user data we have (quotes, observations) to inform the map and avoid just guessing. This mindset setting is important so the session isn’t a superficial checklist activity – it should feel like role-playing the user.

2. (Optional) Warm-up Example (5 minutes): If your group is new to empathy mapping, it can help to do a quick fun example unrelated to your product. For instance, pick a random persona (e.g. “a 10-year-old at their first day of school”) and as a group spend a couple minutes walking through what that person might see, say, think, and feel in that situation. This warm-up loosens creativity and illustrates the goal: imagining a perspective very different from our own. Keep it brief and lighthearted (Atlassian suggests a quirky example like mapping a “42-year-old cereal enthusiast’s” morning routine). After a few laughs and ideas, move on to the real persona. (If time is tight, you can skip this step, but it’s helpful for first-timers.)

3. Fill the Empathy Map (30–40 minutes): Now dive into the persona’s world. Work through each section of the empathy map, either one at a time or in parallel, depending on your group’s style:

   • What does the user Think and Feel? – Discuss the persona’s inner thoughts, worries, hopes, and emotional state during the scenario. What are their core needs or anxieties? For example, “Alex feels anxious about finishing his task on time” or “She values feeling in control of her schedule.” If you have an actual quote from a user expressing a feeling, include it.
   • What do they See? – Consider what this user encounters in their environment. Is it a busy mobile interface? Competing product ads? Input from colleagues? For instance, “Alex sees a confusing dashboard with too many options” or “Pop-up tips that are distracting.” This section captures the context or visual stimuli affecting them.
   • What do they Say and Do? – Identify outward expressions or actions the user takes. What might they be saying out loud (or in writing) and what actions are they doing in this scenario? E.g. “Alex says ‘This is taking too long!’ and tries clicking the help icon”. These could be things observed or reported by users. If you have user quotes from feedback or usability tests, they fit well here (what did the user say while using it?).
   • What do they Hear? – Consider influences from others: things friends, coworkers, or media are telling the user. For instance, “Alex’s colleague tells him about a shortcut, but he hears it’s hard to learn” or “She hears her kids asking for her attention in the background”. These could be external voices that impact the experience (social influences, word-of-mouth, etc.).
   • Pain Points (Pains): List the persona’s pains, fears, or frustrations in this context. What pain are they experiencing? It might overlap with some “Think/Feel” items, but here you distill specific pain points. E.g. “Overwhelmed by too many features”, “Afraid of losing her data if she presses the wrong button”. If it helps, phrase them as problems or negatives the user wants to avoid.
   • Gains (Goals/Needs): Identify what the persona wants to gain or achieve – their needs, desires, or measures of success. Essentially, what outcome would make this experience a success for the user? For example, “Successfully schedules all tasks for the week in 5 minutes” or “Feels confident and relieved after using the app.” Gains often connect to the goals you listed in the persona profile, but here you frame them in context of this scenario (what positive outcome or benefit the user is looking for).

   As you progress, have participants either shout out ideas to the facilitator or, for a remote session, let them add digital sticky notes to the map simultaneously. Encourage them to draw from real data: What did users say in interviews? What emotions did we observe? – these go into the map. If the team starts making assumptions, gently ask, "Do we know this from research or is it a hypothesis?" It's fine to include hypotheses if labeled, but the richest parts of the empathy map come from genuine user insight.

   It can be effective to tackle the Think/Feel quadrant first (since understanding the user’s mindset sets the tone), then Say/Do (observables), and See/Hear, and finally Pains and Gains. But you can choose any order. The key is to cover all sections. Keep the discussion flowing but focused – if one area is sparse, prompt the group with questions (e.g. "What might Alex be hearing from others?"). If one area is overly full, that’s okay – it might indicate where the richest insights are.

4. Discuss and Synthesize (10–15 minutes): Once the map is filled with notes, step back and review it as a group. Have someone (often the facilitator) read out the highlights of each section: “So our user is thinking/feeling, seeing, saying/doing, and hearing. Their main pains are, and they really need/want.”* This recap helps the team absorb the overall emotional picture. Ask the team: What stands out? Look for any contradictions (e.g. the user says everything is fine but feels frustrated – that could be an insight about unspoken pain). Identify the most prominent pain points and needs that emerged – these are gold for design. You might mark the top 2–3 pains and gains with a star or a different color. Also discuss any surprises: “We didn’t realize Alex was so anxious about time – that’s a big insight.” This debrief turns the raw map into shared understanding.

5. Wrap Up (5 minutes): Thank everyone for stepping into the user’s shoes. Emphasize how these insights will be used – for example, "We’ve identified that Alex’s biggest frustration is the complexity of our interface, and he needs quick guidance. We’ll keep this in mind as we design the onboarding experience." Make sure someone is responsible for cleaning up or digitizing the empathy map if it was done on paper (often the facilitator will tidy the Figma board if needed). Finally, remind the team that this empathy map is a living artifact – it should inform design decisions and can be updated as you learn more. It’s also useful to share it with any colleagues who didn’t attend, to spread the empathy. The goal is that everyone on the team can refer to this map and say, “What would Alex be thinking and feeling if we implement this feature?” – keeping user empathy at the heart of your project.

An empathy mapping session yields a clearer, shared picture of the user’s experience – it humanizes the data. It often brings out emotional and environmental factors (e.g. stress, distractions) that might not surface in a persona alone. These insights will be extremely useful when you move on to designing solutions or mapping the user’s journey in detail.

Customer Journey Mapping Session (60 Minutes)

Loading diagram...

A journey mapping session goes one step further by charting the end-to-end journey of your user persona as they interact with your product or service (or attempt to accomplish a goal that your product is a part of). Where the empathy map explored the user’s mindset in a moment, the journey map lays out the sequence of steps the user takes – and how they feel at each step – to achieve their goal. This could be the journey of a first-time user signing up and using key features, or a returning user trying to resolve an issue, etc. Journey mapping is great for identifying pain points across the entire experience and finding opportunities to improve the product or create new features.

Preparing for the Journey Mapping Session

• Narrow the Scenario and Persona: To make the most of a 60-minute session, focus on a specific persona and a specific user goal/scenario for the journey map. For example, “Journey of Persona A from discovering our app to completing their first task,” or “Persona B’s journey of using our service over a one-week period.” Clearly define the start point and end point of the journey. Journey maps that are too broad (or try to cover all types of users at once) can become generic and less insightful. It’s better to do separate maps for separate personas or goals than a giant one-size-fits-all map. Ensure the persona you choose is well-defined (ideally, you have the persona profile from the earlier session). If you haven’t created personas yet, do that first – Atlassian advises that you may need to pause journey mapping until personas are defined from research.
• Gather Touchpoint Data: Pull together any data or research about how users move through the current experience. This could include funnel analytics (where do users drop off?), user interview transcripts detailing step-by-step experiences, support logs, etc. Real customer journeys rarely follow a happy path exclusively; try to include what actually happens (e.g. “user had to contact support at step 4” or “user work-around using Excel”). If you have customer journey analytics or maps from prior research, bring those insights in. Also, bring the empathy map from the previous session – it will inform the emotional aspect of the journey.
• Prepare Materials: For a remote session, set up a Figma board (or Miro/Mural, etc.) with a blank journey map template. A common format is a timeline with stages or steps along the top, and rows underneath for things like User Actions, Thoughts/Feelings, Pain Points, and Opportunities. You might prepare stage headers in advance (e.g. “Stage 1: Awareness, Stage 2: Signup, Stage 3: First use, ...” depending on your scenario) or determine them during the workshop. Also have markers or sticky notes ready (virtual ones if online) – journey mapping is often done by writing each step or thought on a separate note so they can be rearranged. If in-person, you’ll need a large whiteboard or roll of paper, sticky notes, and markers. Don’t forget a timer to keep track of the segments.
• Participants: Invite team members who have insight into various parts of the user journey. This might include marketing or sales (for early stages like awareness), product designers and engineers (for usage stages), and customer support or success (for post-purchase or problem-resolution stages). Having a mix ensures you cover the journey comprehensively. Ensure everyone is familiar with the persona and scenario ahead of time – consider sending out a brief with the persona profile and a description of the journey scope a few days before. If possible, have them review any user feedback or data related to this journey so they come informed.

Journey Mapping Session Agenda & Steps

1. Set the Stage (5 minutes): Re-introduce the persona and clarify the specific journey you'll be mapping. For example: “Today we’re mapping the journey of Dana (Persona B) as she goes from first hearing about our app to successfully booking a service through it.” State the intended start and end points of the journey. Make sure everyone is on the same page with the scope: ask if anyone has questions about what’s included or not. Emphasize that the goal is to view the experience through Dana’s eyes, step by step. Encourage the team to recall any direct user stories or data related to this journey. If you had pre-work (like reading user interviews), quickly recap key findings. Also, outline the process: "We will outline each step Dana takes, how she feels at each step, and any pain points or delights encountered. Then we’ll look for opportunities to improve."

2. Map the High-Level Stages (5 minutes): As a group, break the journey into a few major stages or phases. This provides a framework to populate. For example, stages might be Awareness -> Consideration -> Onboarding -> Active Use -> Outcome. Or if it’s a narrower task, it could be Step 1: Login -> Step 2: Do Task -> Step 3: Logout. Decide on the stage names that make sense for the scenario. Limit it to a manageable number (perhaps 5–7 stages). Write these as column headers on the board or template. (If you already defined stages beforehand, validate them with the group now.) This stage definition helps compartmentalize the journey and give the team a mental model to follow.

3. Build the User’s Backstory (5 minutes): Before diving into steps, quickly establish why the persona is on this journey in the first place. Atlassian suggests brainstorming the persona’s back-story: their triggers, pain points, and goals leading into the journey. Take a moment to list the persona’s motivations for engaging with your product and the problems they hope to solve. For example, “Dana is frustrated with how long it takes to book a service by phone (pain point), and she needs a more convenient solution (motivation). She heard about our app from a colleague”. This context sets the narrative: it reminds everyone of the user’s mindset at the journey’s start. Jot down one or two key pain points or goals as a prelude to Stage 1. (If you did an empathy map, much of this is already known – you can summarize the main pain/gain from that map here.)

4. Map the Journey Steps (30–40 minutes): Now the core of the workshop: go through the journey stage by stage, and for each, have the team enumerate what the user is doing, what they are thinking/feeling, and any pain points or delights at that step. A good approach is to use one color sticky note for User Actions, another color for Thoughts/Feelings, and another for Pain Points/Issues (and you can optionally use another for Opportunities or ideas, which we’ll get to). Start at Stage 1 and ask: “What does Dana do first in this stage?” Someone might say, “She searches for our app in the app store.” Write that as an action. Then ask, “What might she be thinking or feeling here?” Maybe “Hopes this app will save her time, but skeptical if it’ll work” – that goes under Thoughts/Feelings for that stage. Also ask, “Any friction or pain at this point?” Perhaps “Too many apps shown, she’s unsure which is the official one” – note that as a pain point. Proceed step by step. Each subsequent action might follow logically: “She downloads the app”, next “opens it and is asked to create an account”, and so on. For each action, capture what she thinks/feels (e.g. “Impatient with long signup”) and any issues (e.g. “Verification email took too long”).

   It’s often easiest to map Actions first across the whole journey – essentially writing out the user’s workflow in sequence. Encourage the group to be detailed and sequential: “After downloading, what’s the very next thing she does? Then what?” Keep going until you reach the end of the journey (the defined end point). Once actions are laid out, go back and fill in Thoughts/Feelings and Pain Points for each action or stage. However, teams often discuss these in one go for each step, which is fine. The key is not to skip the user’s mental or emotional state at each step – these are crucial for empathy.

   If the journey can branch in different ways (e.g. user takes an alternative path or hits a yes/no decision), you can note that as a branch. For simplicity in a short session, you might choose one primary path to map. If a branch is important (say, if the user might either succeed or fail a step), you can split the map or use swim lanes for each path. For example, “If password is correct, go to dashboard; if wrong, user gets an error and feels frustrated.” This can get complex, so manage it based on time – possibly stick to the main flow and just annotate what happens on errors or alternate paths.

   Throughout mapping, refer to your persona and empathy map: what likely emotions did we identify? Make sure they appear in the journey at the appropriate points. Also consider channels: note where the action happens – on the mobile app, website, email, a phone call, in person, etc. It can be helpful to mark the channel for each action (e.g. label a step “(Mobile app)” or “(Email)”）. This highlights context shifts (e.g. user goes from app to checking email for a code – a potential friction). If relevant, also distinguish frontstage vs. backstage actions: frontstage are user actions, backstage are internal processes (like "system sends confirmation email"). In a beginner-friendly session, you might keep focus on the user-facing steps and just make a note of any internal process that impacts the user (e.g. "confirmation email sent (could be delay)").

   Keep the pace brisk but not rushed. If debate arises (“Does the user do X or Y at this step?”), you might record both or mark it as something to research, then move on – avoid getting bogged down. The facilitator’s role is to keep the story moving forward. By the end of this step, you should have a horizontal flow of user actions from start to finish, each paired with insights about what the user is thinking/feeling and where they encounter highs or lows.

5. Identify Pain Points & Opportunities (10 minutes): Now have the group look at the completed journey and discuss which steps are particularly painful or problematic for the user. You likely tagged many pain points already; call them out. For each major pain point, ask “Why is this painful? How might we improve it?” and jot an Opportunity note (perhaps on a different color) near that step. For example, if “user is frustrated by a long sign-up form,” an opportunity might be “Simplify sign-up or allow social login.” Don’t go deep into solution design now, just capture ideas or improvement areas. Similarly, note any stages where the user is especially happy or things work well – these are things to preserve or even amplify. The aim here is to turn the journey map into a springboard for action: you’ve visualized where the experience falters and where it shines.

   If time allows, you can also discuss metrics or ownership: e.g. which team deals with each stage, and what metrics correspond (conversion rate at sign-up, etc.). In a quick session, this might be too much, so focus on user pain/pleasure points.

6. Wrap Up (5 minutes): Recap the journey in narrative form: “So from Dana’s perspective, it starts with_, then she_, feeling_, and at the end she_.” Emphasize the emotional journey – perhaps it started with optimism, dipped into frustration at certain points, and ended with relief (or maybe ended poorly, which is a huge insight). Thank the team for their input. Make sure someone will refine and document the journey map neatly after the session (often the facilitator will photograph a physical map or tidy up the digital board). This journey map should be shared as a living document. Conclude by highlighting the top pain points the team identified and expressing how valuable this is: "Now we know exactly where our user struggles most (e.g. Stage 3), and we have some ideas on how to fix it. Our next steps will be to prioritize those improvements."

   Reiterate that journey mapping is about building empathy and a shared vision. It’s normal if you didn’t have all the answers; the map can be updated as you gather more data. If there were unanswered questions or assumptions, note them for future research. End on a motivational note that designing with this journey in mind will lead to a better user experience, as you can now address the specific issues from the user’s viewpoint.

Journey Mapping Tips: In the discussion, keep bringing it back to the user’s perspective. It’s tempting for teams to jump into internal or technical details (e.g. “Engineering knows that step is slow because of X…”). Acknowledge those, but keep the map focused on what the user experiences, not the underlying cause (though you can footnote causes for context). Use visual cues on the map: for instance, draw a simple 🙂 or 😢 under steps to denote user sentiment, or use colored dots (green for positive, red for negative) to create an “emotional journey line” across the stages. This makes it easy to see highs and lows. Also, remember that not every journey is linear – but try to map it in a linear way for clarity, noting loops or back-and-forth as needed. Given the short session, prioritize the most common path the persona takes, and be okay with simplifying less common detours. Encourage openness – if someone on the team knows of a pain point but was hesitant to bring it up (maybe because it reflects poorly on the product), assure a blameless environment. The goal is to uncover truth, not to assign fault. By fostering a candid discussion, you get a more accurate map.

After a journey mapping session, the team should have a vivid, shared story of the user's experience. This artifact is incredibly useful: you might pin it up in the office or share it in Confluence/Jira so that when making product decisions, the team can refer to "Where in the journey does this feature fit? Does it alleviate any pain?". It’s a cornerstone for user-centric innovation, ensuring you address the right problems at the right stage of the user’s journey.

Combining Sessions & Next Steps

The three sessions outlined – Persona, Empathy Map, and Journey Map – complement each other and can be run in sequence as part of an accelerated UX workshop series. For example, in a single day or over two days, you might: first create the persona, then immediately do an empathy mapping for that persona, and then map their journey. Running them back-to-back can maintain momentum and deepen the team's empathy continually. In accelerated mode, you might tighten each session to 40-50 minutes or streamline some steps, but be cautious not to skip the reflection and discussion – those are where insights emerge. It’s also critical to carry over outputs between sessions: the persona you create will feed the empathy map (as the character you empathize with), and the empathy insights (pain points, feelings) will feed into the journey map.

If you plan a sequence of sessions in one day, consider scheduling short breaks in between – these workshops are mentally intensive, and teams benefit from a breather to process information. You could also rotate facilitators if needed (one person leads persona, another leads journey mapping, etc.) to keep energy high.

After completing all sessions, you’ll have a set of valuable UX artifacts: persona profiles, empathy maps, and journey maps (likely in Figma or exported for your documentation). Ensure these are accessible to the whole team and referenced in your design process. They should directly inform ideation and design decisions. For instance, if the persona’s biggest challenge is a certain pain point uncovered, your team can brainstorm features specifically to solve that. If the journey map shows a drop-off at a particular stage, that stage becomes a focus for improvement.

Finally, remember that these artifacts are living documents. As you continue user research and testing, update the personas, empathy maps, and journey maps. Maybe you’ll run a quick 30-minute follow-up session in a few weeks to refine the persona with new insights, or add a new journey map for a different scenario. UX work is iterative, and these sessions can be repeated whenever you need to realign the team around the user.

By following this guide, even beginner teams can run structured UX sessions that build empathy and understanding for users. With practice, you’ll get better at facilitating and might customize the templates or timing to your needs. The investment in these 60-minute sessions pays off by preventing design mistakes and ensuring your product truly resonates with its users. Good luck, and happy designing with your users in mind!