“Baking an Experience Map”
Experience Maps are a well known and useful UX tool, but the truth is that when it’s time to get one’s hands dirty aren’t easy to solve. The options are too many and the models so varied that making the right decisions can be really complicated, if you aren’t experienced enough in the end the best case scenario will result in an irrelevant Experience Map, and in the worst case with nothing…
But fear not! Today I will share with you my personal recipe to bake an Experience Map or User Journey
As with cakes, there are many different recipes for baking an Experience Map. Today I am going to tell you one basic technique which include a few steps that will allow you to create an Experience Map from scratch. And guarantee that in the end you will have a steaming, tasty Experience Map in your hands.
Lets starts with the basics, we will need some essential ingredients for our preparation:
1 System to be modelling (Obviously)
1 Persona. You need one persona belonging to your product target. It is advisable to have at least two personas, sometimes one persona trip can be more interesting and useful for stakeholders than others as they expose more relevant issues and opportunities.
1 Goal. One goal that will direct user behaviour during experience flow. Basically: what is the persona’s purpose for this specific interaction in this particular scenario? What is she trying to accomplish?.
1 Mental Status. You will need to define an initial Mental State as a starting point for your persona. This mental status will suffer variations during the experience and you should reflect these changes in the key phases of interaction.
1 Task model (optional) It is preferable to have a previously created task model -it will make the job easier-.
2 to 3 Scenarios. It is better to have several possible scenarios. When sketching you may discover some are useful or richer than others. It is important keep in mind that your Experience Map should make a contribution to the knowledge you (and stakeholder) already have about the product. To make a beautiful graphic representation of an irrelevant (or obvious) interaction issues has no point at all. The scenario presents a situation and the goal behind the entire experience. The scenario must respond to: What is the user Goal: what problem or need is it trying to address? Does he hurry? Is he relaxed? Is he alone or with others?
1 Context. Some people use context and scenarios as synonymous but I prefer to keep them separate as it seems you can have same context for very different scenarios. For me a context is defined by the set of facts that surround a scenario such as physical environment, device and platform constraints, physical space and device or platform in which the experience is taking place: persona is at home, work, street?. Is it using a desktop computer or a mobile phone? What are the device/platform constraints?
Some tips before starting…
1-Quality ingredients are key: Remember all ingredientes should come from strong research and analysis.
2- Keep in mind that the ultimate goal is to end up with a graphical representation which should at least reflect process and interactions, customers needs and customer perceptions through the experience flow. This means that those who work with it should be able to easily understand the overall interaction, positive and negative issues, and make product/business decisions from it.
3- The second thing you must have in mind is: “you are the persona you are working on”. Try to keep that in mind in every moment. ¿How will this persona react to this? What would she do? How would she feel?
Define an initial Mental State: Take your persona, and use context and scenario to define an initial Mental State.
You may have an impatient persona, or a very demanding one -personality characteristics- or 2 personas with different backgrounds and experiences -expertise level- both of them will act quite different even if seeking the same goal. A context can be also very determinant for user behavior and affect the attention directly, attitude or mood (mental status variables).
Mental status is defined as a combination of user personality, background and previous experiences, scenario and context and change during the flow experience. In your Experience Map you could reflect Mental status in a detailed way using likert scale for different variables -like Attention, Motivation, etc- or use a simplified representation indicating only mood status -using emoticons, or color scale- complexity depends on the focus you want to do in this factor.
Using task model to identify touchpoints: Use task model to outline touchpoints between system and persona behaviour. If you don’t have a task model for your tested interaction just jump to next step where you can identify touch points simultaneously to the path draft.
2. MIXING… Drawing a path draft
This is for sure the most important step, if not done properly the result will be poor or defective. In this phase I recomend you to work directly on paper or whiteboard which allow you to take quick notes.
Note: the goal is to find all possible touch points, define impact and emotional persona reactions -using think aloud technique could be very useful-.
Starting with the scenarios first scene run a persona simulation of the experience, keeping in mind the persona characteristic, the goal, the scenario and the context. At this point you have to be as much as an actor, a focus on the persona you are representing now -it helps to have the persona character print in front of you-. Do it in only one flow and draw a graphic scheme of the path indicating the key interaction points.
When finished, go back and forward at all times you need to correct the initial path if you think is not being natural to that persona and scenario. You probably have to re-make that path several times, but it is better if you try to do it in one go the first time -the result will be more natural-.
Follow the path as many time as you need. Each time you go back down the path, you will add different dimensions and elements to your map.
Here you have a tentative go-over flow (Each point represents a new repetition of the path):
a- Initial draft: Finding touchpoints. Indicate whether they are positive or negative for that user in that scenario, based on their emotions or thoughts -again follow the think aloud technique which will help-. At this point you’ll end up with “delights points” and “pain points”. Also, if you didn’t count with a Task Flow, you should identify different interaction phases in this step, this will allow you to group content in a clearer way in further steps.
b- Go deeper into the emotions and thought of your simulate user, trying to identify the needs behind them. Here you could end up with a very descriptive user “comment” or thoughts.
c- Identify Interaction flow phases. Split the experience into logical units.
d- Identify all interaction connection types between touchpoints
In the next go, strive to identify opportunities or service barriers behind touch points:
e- Use point 2-4 to describing content opportunities or improvements. Could content information or hierarchy be improved for this path? (E.g. Is user needing content that is not available now? Should we think of reorganizing the content differently according to the relevance they have for the user in this flow?)
f- Use points 2-5 to find Interaction opportunities or improvements. Could interaction flow be improved based on user experience in this path? (E.g. Would it be better to move from a direct interaction to a Controlled evaluation? )
It’s a good time to find high-level opportunities that perhaps involve a change in the all flow task.
Tips: Use think aloud technique and take note of the steps, trying to build a clear and realistic dialogue, alternatively record your voice for each run. This will help you focus on the fidelity with the persona you’re using, the environment and the chosen scenario. Separate dialogues lets you distribute the cognitive process more easily in clear steps and stages.
Do not force the path in order to show or demonstrate what you think should be important. Follow the path naturally you may be surprised at the result. Remember, experience map is not just a graphical representation of what you already know about the product, it is a tool for understanding and discovering.
The most natural expression is a time-line but you will see in further steps that this visual representation (layout) could change depending on the needs.
Let THE MIXTURE STAND AND TASTE…
3. ANALYZE, DISCUSS AND TEST
Now stop mixing, let the mixture stand and observe: How natural is the resulting flow? It is the result information relevant for all product actors?. If you are part of a UX team this is a good moment to share your sketch with them. Give them the goal, initial mental status and persona details and let them recreate the flow with the system. After, show your draft and discuss with them main differences. Make all necessary adjustments.
Whenever possible, test same goal and scenario with a matching-persona real user before designing final version. Make necessary adjustments.
SELECT THE CONTAINER
4. CHOOSING THE RIGHT LAYOUT FOR THE EXPERIENCE MAP
Finally choose the best recipient for your Experience Map. This is a key step on final result, the success and clarity of your Experience Map will depend largely on choosing the right layout and graphic elements.
You can find more details about the different layouts and how to choose one in my other post: Experience maps user journey and more.
For this recipe I’m using the classic time-line layout. This layout can be displayed horizontally or vertically.
5. PUT ALL ELEMENTS IN PLACE
a- Experience path, touchpoints and connection type.
b- System interaction and actions.
c- Include outside system stages.
d- I use balloon messages to illustrate persona think-aloud about the experience through interaction (feelings and thoughs).
e- I illustrate the different mental status and moods using a scale (depending on the focus I want to make on this, may use emoticons).
f-At the bottom include references to all the touchpoints, adding ideas and notes on opportunities or pain points.
g- On top include a brief reference to the used persona.
Below you have a guide to how I locate all the above elements in a time line layout:
For more details on the differents elements check my other post: Experience maps user journey and more.
6. SERVE AND TEST
It is time to savor :). When distribute your Experience Map don’t forget include link to persona details and System basic information (version number, testing on OS, or Browser, etc).
Finally remember to keep your Experience Map up to date!.
NEW: Just a plus, when I try to make this post shorter I removed it but I think it can be be helpful:
How to illustrate the different Interaction Connection Types of the system:
Use this signs for connecting touch points or interaction flow steps: