Imagine sitting down to write a novel without first breaking down the plot or having the end in mind. Though it may go well enough at first, once youâre surrounded by words and paragraphs, itâs difficult to know how to develop the story or where you should be driving the narrative. The best authors donât just sit down and whip out a book: it takes a considerable amount of planning.
The same goes for the best products. These products seem to intuit what their users need. Theyâre easy to learn and easier to use, and they deliver real value to the userâs life. Getting to that point requires empathizing with the user. Thatâs where user story mapping comes in.Â
User stories are critical for understanding the behaviors driving your customers to your product as well as through your product.Â
Read on to learn how you can use Lucidspark to quickly and easily develop a story map with the help of your entire team.
How to create a user story map in LucidsparkÂ
The beauty of Lucidspark is that itâs a cloud-based collaborative tool that allows for better input from every member of the team. That makes it easy to work through the creation of a user story map with help from stakeholders. Hereâs a step-by-step guide to doing just that:
1. Collaborate cross-functionally
Start by scheduling a meeting that will bring your product, UX, and development teams together to start mapping out your user story. Each team has a specialty and perspective that adds valuable information to the user story map.Â
For instance, your UX designers may want a facial recognition login on your app, but your development team may remind the team that most of your users log in through their desktops. Your product team may want to include all the product information on a particular landing page, but the UX team may inform the group that, actually, flooding the landing page with too much information causes unnecessary cognitive load stress on the user.Â
Itâs important to have everyone weigh in on the behaviors your users exhibit as they interact with your product.
But what ifâand this is purely hypotheticalâyour team is separated by, say, some sort of persistent pandemic that requires each member to isolate for their own safety? Not a problem: Lucidspark allows both remote and in-person teams to engage with the creation of the user story map.Â
Lucidspark even lets each member of the team have their own color as they make contributions to the user story map, so if there needs to be clarification on a particular point in the map, itâs easy to ask the original contributor. This kind of flexible cross-functional collaboration enables a holistic look at the user map that is key to making it as beneficial and realistic as possible.
2. Prepare your board
Before your team gathers, set up your Lucidspark board. You wonât be jumping into the organization of the story map just yetâyouâll need to start with a brainstorm. But the key to useful brainstorming sessions is to give them guidelines.
First, add containers to organize your brainstorm. Potential containers could be labeled:Â
- User activitiesÂ
- User pain points
- Objectives and goalsÂ
Itâs useful to label your board, add collaborators, and even share a brief tutorial before the brainstorming happens.Â
3. Understand your customer
Imagine making a childrensâ movie without having any idea what children like. It wouldnât end well. Similarly, not understanding your customersâ needs will mean your product will offer them no real value. Thankfully, understanding your customer can be a guided process.Â
Use a persona template to better understand your customerâs motivations, frustrations, goals, and wants. You can even picture what a typical day looks like for your customers, from their preferred breakfast to their social media of choice.Â