Back to all posts

How to Run Empathy & User Journey Mapping Workshops

Introduction

This article will teach you two popular design workshop techniques: empathy mapping and user journey mapping. Empathy mapping is a way to characterise your target users in order to make effective design decisions. User journey mapping is a way to deconstruct a user’s experience with a product or service as a series of steps and themes. Put simply, these methods encourage your stakeholders to think about user needs effectively, identifying pain points and opportunities in a systematic and straightforward way.

To make things interesting, I’m going to explain the methods in the context of a fictional case study. Let’s imagine it’s 2004 and we’re a hardware company called Pure Digital looking to get into the digital video camera market. We’re just starting to work on a new type of camera that will later be named “The Flip” (If you’re old enough you’ll remember it was a really big deal in the days before the iPhone). At the time, other manufacturers were making bulky camcorders while The Flip ended up being small, plasticky and about ¼ of the price, managing to dominate the market through a superior user experience. In a way, it set the tone for many of the video sharing features you have on your smartphone today.

Empathy Mapping

A blank empathy map template. Download it here.

An empathy map isa very quick, very rough persona template ( Gray et al, 2010 ). It’s not much different to any other ad-hoc persona template — it’s really just a tool to articulate what you know about a particular type of user— their needs, goals, expectations, behaviours, pain points, and so on.

Once you’ve created an empathy map, you then use it as a tool for design decision making . In other words, you role-play as the persona and say to yourselves “What would this persona think when they see this?” or “What unanswered questions would prevent them from proceeding to the next step?” and so on.

Ideally all personas should be based on solid research findings, but this isn’t always possible. At the beginning of a project (during the discovery phase or exploration phase ) you’ll have no research to draw upon, but you will have a room full of project stakeholders. They probably already have some fairly clear hypotheses about their customer segments and the key defining characteristics of each type. Empathy maps will help your stakeholders externalise their knowledge in a form that assists with design decision-making. You can then treat your empathy maps as hypotheses for any formal user research that comes later in the project.

Anyway, let’s get back to our Pure Digital case study. The idea is that we’d get a group of stakeholders in a room, and get them to identify their main user types (there’s usually a few user types for any product or service, but for the sake of this article we’ll talk about just one). You then give them the template, some Sharpies and Post-its, then have them fill it in. You’ll notice that a post-it could go into one quadrant or another depending on the way you word it. Don’t worry about this — it’s not science, it’s just a way to get stuff out of their heads and onto paper as quickly as possible. Here’s what they create, below:

Our hypothetical empathy map showing Charlie, our target user.

As you can see in the diagram above, our target user is experiencing a lot of annoyances with the way products enable him to record and share video. She doesn’t care about codecs or spare battery packs. She doesn’t want to spend weeks choosing the perfect camera. She wants something that “just works”. Remember, we’re imagining this design exercise is being done 2004: pre-iPhone and pre-YouTube.

User Journey Mapping

Now we’ll take our insights about Charlie and apply them to an experience that the’ve had. There are two types of user journey map: retrospective maps : where you map out how users currently do stuff (typically based on research findings); and prospective maps : where you map how you expect users to behave with a new product idea. In this article we’ll be doing a retrospective map.

A user journey map is really just a big table with steps through time on the horizontal axis, and themes for analysis on the vertical axis. Either find a clean wall or get big foamcore board, and use masking tape to create a big grid. The steps on the horizontal axis will vary according to the problem you’re working on, but the vertical axis usually stays the same.

A simple user journey map framework

As a group, you now work together to fill in the grid. it’s best to start left-to-right top-to-bottom, regularly referencing the empathy map as a source of inspiration. Don’t worry if there are some blank cells, this is normal.

Actions : the thing the user needs to do to move to the next step
Questions : things the user needs answering before they’ll be willing to move to the next step
Happy moments : positive, enjoyable things that improve the experience
Pain points : frustrations and annoyances that spoil the experience
Opportunities : design enhancements that you could implement in a new product, that address any of the problems identified.

This is what our finished user journey map looks like:

A user journey map showing Charlie’s experience creating and sharing digital video in the mid 2000s.

It’s important to leave the “Opportunities” row until last. It’s basically a summary of the problems you’ve identified (i.e. unanswered questions and pain points), re-conceived as design opportunities.

Opportunities derived from the User Journey Mapping exercise

What comes next

Having done the workshop, you’ve gained the following things:

  • Participants have learned about user centred decision-making
  • They’ve started to think in terms of users and journeys , not specs and features
  • You’ve identified some potential opportunities for the product roadmap

That said, it’s important not to get carried away. A User Journey Map workshop doesn’t magically allow you to skip through the design process. It gives you a good starting point. It’s normal to spend a few weeks in the discovery and exploration phases, understanding your target users through research, exploring design concepts, iterating and throwing a lot of bad ideas away before a line of code gets written.

One final piece of advice: if you do an image search for User Journey Maps you’ll see lots of very elaborate posters. These are often made by design agencies to justify their fees — don’t bother doing this unless you’re certain it’ll bring value to your team. Your time may better be spent designing a prototype rather than a poster. Also, if you’ve done your maps based on assumptions, an elaborate poster creates a false sense of validity which is very dangerous. Instead, you should use your assumptive map as a straw man, and initiate some proper user research to find out whether the hypotheses stand up to reality (e.g. qualitative interviews, usability tests, field studies, surveys, and so on).

When you're looking for a gift idea think about the Rubik's Cube. The online Rubik's Cube solver will guide you through the solution.

This article was originally posted at:
https://medium.com/@harrybr/how-to-run-an-empathy-user-journey-mapping-workshop-813f3737067

Can we take you from stuck to unstuck?

We'd love to hear from you

Call to action (CTA)

A call to action is a marketing term that refers to a prompt that invokes a response leading to a sale. When referring to a call to action (CTA) in the digital design world we usually mean the interactive element that leads to the next step in the experience - something that needs to be clicked or tapped.

User testing

User testing refers to a technique used in the design process to evaluate a product, feature or prototype with real users. There are several reasons why you might want to undergo usability testing, the most common is that it allows the design team to identify friction in a user experience they are designing, so that it can be addressed before being built or deployed.

WYSIWYG

WYSIWYG (pronounced WIZ-ee-wig) is an acronym for "What You See Is What You Get". It helps identify an an interface that allows user input resulting in an output that is rendered in a similar way. For example; a word processor application interface might resemble a piece of paper,so when printed the user can see how the output will appear.

Content Management System

A content management system (CMS) is an tool that allows a website editor/administrator to manage the content that is displayed. Websites are made of HTML and CSS to create pages. Pages can be hard-coded but would require technical development skills to make changes. A CMS usually allows a person without coding knowledge to amend existing and add new content to a website using a WYSIWYG interface.

Responsive Web Design

Responsive web design refers to a web page that dynamically adapts its layout to fit the size and orientation of the device on which it is viewed. A responsive design allows for a more optimised user experience across desktop and laptop computers as well as smartphones and tablets of varying sizes.

User Stories

User stories allow the functionality of a product or service to be expressed as written descriptions of an experience as seen from the users perspective. The writing of user stories creates a list of design and development tasks to complete in order to create any required functionality.

User Interface

A user interface (UI) is a conduit between human and computer interaction - the space where a user will interact with a computer or machine to complete tasks. The purpose of a UI is to enable a user to effectively control a computer or machine they are interacting with, and for feedback to be received in order to communicate effective completion of tasks.

Personas

A persona in UX Design is the characterisation of a user who represents a segment of your target audience. On a project you might create any number of personas to be representative of a range of user needs and desires. The solutions you design must answer these needs in order to deliver value to your target audience.

Card sorting

A great, reliable, inexpensive method for discovering patterns in how users would expect to find content or functionality. Card sorting is used to test the taxonomy of data with a group of subjects, usually to help inform the creation of the information architecture, user flow, or menu structure on a project.

Brainstorming

A technique used to generate ideas around a specific topic. Often done in groups, but can be done individuals. The process usually involves writing down all ideas around a topic onto paper, a whiteboard or stickies often implying some kind of association.

Minimum Viable Product

An MVP is a product that has the minimum set of features to prove the most essential hypothesis for a product. Businesses building a new product can create a Minimum Viable Product to prove that an idea is viable and warrants further investment. A further benefit being that the next stage of development can be informed by feedback obtained from testing that MVP.

Sitemap

A sitemap is a diagrammatic representation of a hierarchical system. It usually depicts the parent-sibling relationship between pages in a website, showing how sub pages might be arranged underneath their parent groupings. This arrangement forms a map of the site.

User journey

A user journey represents a sequence of events or experiences a user might encounter while using a product or service. A user journey can be mapped or designed to show the steps and choices presented as interactions, and the resulting actions.

Prototype

A prototype is draft representation built to test ideas for layout, behaviour and flow in a system. Prototypes are an indispensable tool for resolving a large number of potential issues in a concept or business before too many resources are deployed to put a design into production.

Wireframes

A Wireframe is a visual schematic that conveys a basic level of communication, structure and behaviour during the design of a system. Wireframes are low-fidelity designs that bypass including a detailed user interface or visual design, conveying just enough to get across the core idea.

Usability

To say something is usable is a qualitative statement about how easy that thing is to use. Usability is an assessment of how learnable a system is and how easy a user finds it to use. The usability of a system or product is a key factor in determining whether the user experience is a good one.

Information Architecture

Information architecture is the design and organisation of content, pages and data into a structure that aids users understanding of a system. A more organised system enables users to more easily find the information they require and complete the intended tasks.

UI Design

User Interface Design is the discipline of designing software interfaces for devices, ideally with a focus on maximising efficiency, responsiveness and aesthetics to foster a good user experience.

UX Design

The practice of User Experience (UX) Design is the coming together of many specific design related disciplines to improve the usability, responsiveness, uptake and aesthetics of a product or service.

User Experience

A general term that covers all aspects of a user's participation while engaging with something that has been designed. Usually when talking about User Experience in the digital design field it refers to the interactions, reactions, emotions and perceptions while using an app, service, website or product.

Got a problem to solve with your service? 

We'd love to hear about it. We can add value to any business that has a digital product/offering.

Book a FREE 30 min consultation

You can also call +44(0)20 3653 1310 or email us

Book a FREE 30min consultation