The Power of Prototype Testing Live Training

Understanding your customers is central to any organization which wants to deliver an outstanding experience. But how do you understand your customers better? Tailoring their experience with your products and your organization to suit them should include a customer journey map.

‍

It doesn’t mean your organization needs a brightly colored, fully designed infographic that outlines each and every action your user takes within your product. It does mean an effective customer journey map that promotes empathy and provides a clear vision for improving customer interactions. There are no rules around what that visualization looks like and it is up to your team to create one that makes the most of your customer’s journey.

‍

What is customer journey mapping? 🤔

‍

Customer journey mapping (sometimes referred to as a user experience map) is a technique that allows you to visualize your customer’s key touchpoints, sentiments, pain points, and actions. Plotted in sequential order. It’s a map of a customer’s experience with your brand or product, from awareness to purchase and beyond. 

‍

Customer journey mapping helps you look beyond key touchpoints and encourages empathy with your customers. To understand who they are, even a persona to give them a life and demographic. Helping designers and key stakeholders understand where they are coming from. And where you can address their needs, avoid their pain points and encourage them to engage with your product. And even identify opportunities for innovation and improvement across the board.

‍

Why you need a customer journey map 💥

‍

What’s better than a customer that feels seen and understood once? A customer that feels the organization or product really understands their needs (and responds to their frustrations). Like all successful, long-term relationships, keeping customers returning is built on empathy and a solid grasp of their needs and frustrations. 

‍

When you want to get to know your customer, like really get to know them, it’s essential to map their customer journey. Creating a shared understanding of what your customers think, feel, and struggle with as they interact with your organization. Spending the time to establish a customer journey map can help align around identifying known problems, identifying new user pain points, and removing roadblocks for your customers, ensuring their success.

‍

Spending the time to get inside the mind and journeys of your customers through mapping helps your team to:

‍

• Create a visual guide of the end-to-end customer experience
• Get an understanding of multiple customer pathways and unravel complex user experiences
• Create target personas and allow insights to solve problems more effectively
• Increase your organization’s empathy for your current and future customers
• Identify potential pain points and roadblocks for your customers
• Breakdown silos within your organization and improve alignment across teams
• With a clearer understanding of your customers, better insights to achieve stakeholder buy-in

‍

How to create a customer journey map 🛤️

‍

Here are 8 key steps to get the most out of your customer journey map process:

‍

1. Bring key stakeholders together for an initial brainstorming session
2. Identify potential user personas - demographics, pain points, interests, etc
3. Create an empathy map - get a real feel for your customer, who they are, and what they want
4. Flesh out your ideas with user research. Get under your user persona skin with focus groups, interviews, and surveys
5. Identify possible customer touchpoints
6. Choose the information you want to highlight - not everything will be relevant
7. Decide on the best customer journey map tool to answer your questions
8. Start building your map

‍

Customer journey mapping examples 🗺️

‍

Each and every customer’s journey is different. This, of course, means that there is no single best customer journey map example or template. Instead, the best customer journey map for any given situation will depend not only on your customers but also on your product, your team, and the goals you’re hoping to achieve by creating the map in the first place.

‍

We’ve found a few examples of customer journey maps to help inspire your thinking:

‍

Current state customer journey maps help you to visualize a user’s experience as it is right now. These are fact-based journey maps - to create an accurate, current state journey map. A good dose of user research data around your actual customers and interactions will help shape this.

‍

‍

Future state customer journey maps focus on what the customer journey can and should look like in the future. Although UX data is certainly an important aspect of understanding customers, future state journey maps involve a fair amount of creative speculation and interpretation. These customer journey maps focus on customer hopes and wants (future feelings), in addition to experiences and reactions. They can be a little objective and should be developed in balance with both positive and negative interactions.

‍

Day in the life customer journey maps help you visualize your customer’s entire daily routine. Interactions with family, their commute, work meetings, afternoon coffee, etc. Regardless of whether or not the activities are related to your company. This type of journey map should be organized chronologically to give key insights into how and where customers are. What are the distractions, and where could they interact with your brand or product? How can key pain points be eased?

‍

Service blueprints are a useful counterpart to a classic customer journey map. Whereas a customer journey map focuses on the thoughts, needs, and actions of the customer, a service blueprint reflects the perspective of the organization and its employees. What needs to happen behind the scenes to ensure the customer’s experience is the very best it can be.

‍

Circular customer journey maps may be useful to visualize the customer journey as a circle or loop. Recognizing that some customers are recurring and non-transactional. Particularly through subscription-based relationships.

‍

An empathy map is used to create a shared understanding of customers around their wants, needs, thoughts, and actions. This can be a great starting point to getting under your customer’s skin.

‍

‍

Wrap Up 🌯

‍

There is no one size fits all customer journey map. Each customer is unique, each organization is different. Through creating customer journeys, personas and visualizing their key touchpoints, pain points, and understanding who they are, empathy throughout the organization can be generated. With this as a tool to bring key stakeholders on board and to pinpoint where products (and services) can be improved to keep customers or even bring new ones on board, the user experience can be better and more effective.

We’re excited to announce our first six project templates are now available in Optimal Workshop! We understand that not everyone knows where to start with customer research, so these ready-made templates have been created with UX industry experts to give you the confidence to quickly launch studies and get the results you need to make data-driven decisions.  

‍

Templates aren’t only a great solution for people who need guidance with which study type to use and when; our detailed templates also give you the tools to develop your IA thinking, compare the performance of studies over time, and get detailed project plans to guide you through your information architecture. 

‍

‍

How do templates work?

‍

On the dashboard, you’ll see a new button called Browse Templates. From the templates menu, you can select a template that matches your use case, e.g. ‘I need to organise content into categories’. The templates are a helpful starting point, for you to adapt to suit your research goals. 

‍

Let’s take a look at some of our favourite project templates. 

‍

‍

Organize content into categories

‍

‍

This template helps you design the best categories to organize your information based on how your  users think. It's useful for designing your product, website, or knowledge base experience, as well as re-evaluating any part of it. In this template, we will first conduct an open card sort, and then use that information to design a navigation structure that will be tested on end users.

‍

‍

1. First up run a card sort with OptimalSort

‍

During this study, users will organise all information presented to them into categories they create themselves using an open card sort. This method is great for generating category ideas based on how users process this information allowing you to better design an experience in a more user-focused way. To find out more on how to set up your card sort, refer to our card sorting 101 guide.

‍

‍

2. Test your navigation structure with a Treejack

‍

Based on the groupings that were produced from the card sort, you can now generate a hierarchy for your users to test using Treejack. Users search for the information you’ve categorised and represented as a hierarchy, which is valuable because it helps to confirm whether information placed within your hierarchy is findable and understandable.  
‍

To learn more about tree testing, refer to our tree testing 101 guide.

‍

Evaluate an existing navigation experience 

‍

‍

Regularly evaluating an existing navigation experience is a good way to monitor the health and performance of your website and product. This template is useful for both redesigning your experience and for re-evaluating part of it by helping you design ideal categories to organize your information based on how your target users think and improve findability and task completion. 

‍

‍

1. Start by identifying your top tasks using Reframer

‍

Using Reframer, conduct interviews with various stakeholders in your business to evaluate and theme which tasks your organization believes are the most important within your existing environment. This is a solid first step towards building a list of top tasks for testing. Reframer allows you to easily visualize and group your observations by proximity using the affinity map.  

‍

‍

2. Survey users to understand their top tasks

‍

Next, survey users to confirm their top tasks and identify any existing issues with our survey tool Questions. This will provide insight into what users believe are their top tasks and whether anything is getting in their way to achieve them. This step helps to ensure all design work is informed by up-to-date user tasks.

‍

‍

3. Design and test your current experience in Treejack  

‍

Using the prioritised top tasks create a tree test using Treejack to test your navigation experience with your users. For example “How would you open a home loan” or “How would you upgrade your broadband plan” This will enable you to see how your users navigate your website in order to achieve the most business critical tasks in your organization. This is a valuable step that helps to identify information and design problems to solve early in the design process. 

‍

‍

More templates from our community

‍

This is just the beginning of templates in Optimal Workshop and while we continue to add value and build up our collection, we’d love your input! If there are templates that you regularly use and think the community could benefit from, let us know at hello@optimalworkshop.com.

“If storymapping could unearth patterns and bring together a cohesive story that engages audiences in the world of entertainment and film, why couldn’t we use a similar approach to engage our audiences?’Donna Lichaw and Lis Hubert

‍

User Experience work makes the most sense to me in the context of storytelling. So when I saw Donna Lichaw and Lis Hubert’s presentation on storymapping at edUi recently, it resonated. A user’s path through a website can be likened to the traditional storytelling structure of crisis or conflict, exposition — and even a climax or two.

‍

The narrative arc and the user experience

‍

So just how can the same structure that suits fairytales help us to design a compelling experience for our customers? Well, storyboarding is an obvious example of how UX design and storytelling mesh. A traditional storyboard for a movie or TV episode lays out sequential images to help visualize what the final production will show. Similarly, we map out users' needs and journeys via wireframes, sketches, and journey maps, all the while picturing how people will actually interact with the product.

‍

But the connection between storytelling and the user experience design process goes even deeper than that. Every time a user interacts with our website or product, we get to tell them a story. And a traditional literary storytelling structure maps fairly well to just how users interact with the digital stories we’re telling.Hence Donna and Lis’ conception of storymapping as ‘a diagram that maps out a story using a traditional narrative structure called a narrative arc.’ They concede that while ‘using stories in UX design...is nothing new’, a ‘narrative-arc diagram could also help us to rapidly assess content strengths, weaknesses, and opportunities.’

‍

Storytelling was a common theme at edUI

‍

The edUi conference in Richmond, Virginia brought together an assembly of people who produce websites or web content for large institutions. I met people from libraries, universities, museums, various levels of government, and many other places. The theme of storytelling was present throughout, both explicitly and implicitly.Keynote speaker Matt Novak from Paleofuture talked about how futurists of the past tried to predict the future, and what we can learn from the stories they told. Matthew Edgar discussed what stories our failed content tell — what story does a 404 page tell? Or a page telling users they have zero search results? Two great presentations that got me thinking about storytelling in a different way.

‍

Ultimately, it all clicked for me when I attended Donna and Lis’ presentation ‘Storymapping: A Macguyver Approach to Content Strategy’ (and yes, it was as compelling as the title suggests). They presented a case study of how they applied a traditional narrative structure to a website redesign process. The basic story structure we all learned in school usually includes a pretty standard list of elements. Donna and Lis had tweaked the definitions a bit, and applied them to the process of how users interact with web content.

‍

Points on the Narrative Arc (from their presentation)

‍

‍

Exposition — provides crucial background information and often ends with ‘inciting incident’ kicking off the rest of the story

‍

Donna and Lis pointed out that in the context of doing content strategy work, the inciting incident could be the problem that kicks off a development process. I think it can also be the need that brings users to a website to begin with.

‍

Rising Action — Building toward the climax, users explore a website using different approaches

‍

Here I think the analogy is a little looser. While a story can sometimes be well-served by a long and winding rising action, it’s best to keep this part of the process a bit more straightforward in web work. If there’s too much opportunity for wandering, users may get lost or never come back.

‍

Crisis / Climax — The turning point in a story, and then when the conflict comes to a peak

‍

The crisis is what leads users to your site in the first place — a problem to solve, an answer to find, a purchase to make. And to me the climax sounds like the aha! moment that we all aspire to provide, when the user answers their question, makes a purchase, or otherwise feels satisfied from using the site. If a user never gets to this point, their story just peters out unresolved. They’re forced to either begin the entire process again on your site (now feeling frustrated, no doubt), or turn to a competitor.

‍

Falling Action — The story or user interaction starts to wind down and loose ends are tied up

‍

A confirmation of purchase is sent, or maybe the user signs up for a newsletter.

‍

Denouement / Resolution — The end of the story, the main conflict is resolved

‍

The user goes away with a hopefully positive experience, having been able to meet their information or product needs. If we’re lucky, they spread the word to others!Check out Part 2 of Donna and Lis' three-part article on storymapping.  I definitely recommend exploring their ideas in more depth, and having a go at mapping your own UX projects to the above structure.

‍

A word about crises. The idea of a ‘crisis’ is at the heart of the narrative arc. As we know from watching films and reading novels, the main character always has a problem to overcome. So crisis and conflict show up a few times through this process.While the word ‘crisis’ carries some negative connotations (and that clearly applies to visiting a terribly designed site!), I think it can be viewed more generally when we apply the term to user experience. Did your user have a crisis that brought them to your site? What are they trying to resolve by visiting it? Their central purpose can be the crisis that gives rise to all the other parts of their story.

‍

Why storymapping to a narrative arc is good for your design

‍

Mapping a user interaction along the narrative arc makes it easy to spot potential points of frustration, and also serves to keep the inciting incident or fundamental user need in the forefront of our thinking. Those points of frustration and interaction are natural fits for testing and further development.

‍

For example, if your site has a low conversion rate, that translates to users never hitting the climactic point of their story. It might be helpful to look at their interactions from the earlier phases of their story before they get to the climax. Maybe your site doesn’t clearly establish its reason for existing (exposition), or it might be too hard for users to search and explore your content (rising action).Guiding the user through each phase of the structure described above makes it more difficult to skip an important part of how our content is found and used.

‍

We can ask questions like:

• How does each user task fit into a narrative structure?
• Are we dumping them into the climax without any context?
• Does the site lack a resolution or falling action?
• How would it feel to be a user in those situations?

‍

These questions bring up great objectives for qualitative testing — sitting down with a user and asking them to show us their story.

‍

What to do before mapping to narrative arc

‍

Many sessions at edUi also touched on analytics or user testing. In crafting a new story, we can’t ignore what’s already in place — especially if some of it is appreciated by users. So before we can start storymapping the user journey, we need to analyze our site analytics, and run quantitative and qualitative user tests. This user research will give us insights into what story we’re already telling (whether it’s on purpose or not).

‍

What’s working about the narrative, and what isn’t? Even if a project is starting from scratch on a new site, your potential visitors will bring stories of their own. It might be useful to check stats to see if users leave early on in the process, during the exposition phase. A high bounce rate might mean a page doesn't supply that expositional content in a way that's clear and engaging to encourage further interaction.Looking at analytics and user testing data can be like a movie's trial advance screening — you can establish how the audience/users actually want to experience the site's content.

‍

How mapping to the narrative arc is playing out in my UX practice

‍

Since I returned from edUi, I've been thinking about the narrative structure constantly. I find it helps me frame user interactions in a new way, and I've already spotted gaps in storytelling that can be easily filled in. My attention instantly went to the many forms on our site. What’s the Rising Action like at that point? Streamlining our forms and using friendly language can help keep the user’s story focused and moving forward toward clicking that submit button as a climax.

‍

I’m also trying to remember that every user is the protagonist of their own story, and that what works for one narrative might not work for another. I’d like to experiment with ways to provide different kinds of exposition to different users. I think it’s possible to balance telling multiple stories on one site, but maybe it’s not the best idea to mix exposition for multiple stories on the same page.And I also wonder if we could provide cues to a user that direct them to exposition for their own inciting incident...a topic for another article perhaps.What stories are you telling your users? Do they follow a clear arc, or are there rough transitions? These are great questions to ask yourself as you design experiences and analyze existing ones. The edUi conference was a great opportunity to investigate these ideas, and I can’t wait to return next year.