The next awesome opportunity to use labels is to visualize personas and journeys. In a user-centered world, you can’t miss the buyer persona out of the backlog. StoriesOnBoard offers a smart feature to create personas, add details and assign them to activities.
We got user reviews about the feature and some of them say, it’s cool. But, we would assign personas directly to steps. Someone would differentiate sub-personas on the story map.
Tag to visualize personas and journeys on a story map
Let’s get back to our example story map. If you found an effective structure for activities and user steps, the persona feature is enough to describe the persona’s activities. That’s why I put the three main personas above the blue cards.
On the other hand, there are user types who won’t finish the whole journey or even an activity.
I used the “👓” icon to visualize a blog reader who won’t book a room.
This method can substitute the persona feature when:
- hard to organize user steps into main activities
- the user journey is fragmented, not match the narrative flow
- top-level cards don’t describe the user activity
when top-level cards are not user activities
Mac: Hit CTRL + COMMAND + SPACE to open the emoji panel
Win 1. Add Touch Keyboard to the toolbar by clicking on it with the right mouse button and selecting “Show Touch Keyboard”. 2. Open Touch Keyboard by clicking on the keyboard icon.
Visualize sub-personas on the backlog
Although the persona feature works well in every product management tool, most of them offer only one level or one dimension. But it’s scarcely enough for more sophisticated persona mapping. Do you need a second or maybe also a third dimension to personas? I got something for you! Tag story cards and filter out user-related tasks using the search&filter panel.
What can be the second dimension? For example, a habit is characteristic of more personas and can result in different steps. I made up the “cheap buyer” attribute. Two of my personas can behave as cheap buyers. I used the “💵” for cheap buyers.
Sometimes, you don’t need to use sub-persona tags all over the story map. If the second dimension differentiates personas only in one (or a few) activities, then use these tags only on the selected part of the story map.
Compress the story map for a better view
The next hint is similar to a previously described one. Imagine the following case: Your personas do the same steps on the product but the tasks under a step belong to only one persona. Your team works in sprints (or releases), and you need to visualize the persona-related cards. If the journey contains a few steps you can solve the problem by duplicating the steps.
I organize marketing tasks also on a story map 🙂 and the issue is originating from that map. All of my personas take the same journey in the marketing funnel, but tasks were very different according to the personas. I don’t want to annoy you with one more marketing story map, so I made up the following one. It’s a small part of a car’s story map. This is, how I handled the problem for the first time:
If I used only one narrative flow the features would have would be mixed. If I put both personas above the blue card, that would be pointless. No chance to visualize persona-related cards in the same narrative flow? But, there is!
Just tag user stories, and you’ll see how effective is it. Now you can use the same narrative flow and everything keep organized.
“One more thing…” can be visualized with emoji icons, the user journeys. It’s another awesome opportunity, so don’t miss it!
Easy to understand why is a great opportunity to visualize user journeys on a story map. UX designers struggle to get more priority on user experience. User experience mapping is often just an afterthought but user journeys help a lot to design better products.
- It helps to discover gaps and functionality,
- ensures that the users get, what they need,
- breakdown silos in the product