User story mapping is a collaborative process within a working group aimed at creating a dynamic representation of interactions between the user and the product, evaluating the features that could bring the greatest benefits to the user and the priority actions needed to meet the most urgent needs.
At SparkFabrik we organize dedicated workshops to help companies plan and conduct a user story mapping process aimed at designing a web product (website, software, application, and so on). Drawing on our experience and applying this technique, we guide the client through a process of discovery, rationalization, and visualization of product requirements, identifying which ones deliver the most value and creating a shared roadmap across the entire organization for their development and adoption. We can consider user story mapping one of the first steps in the Digital Transformation process.
Let’s take a step back and better understand what user story mapping is and how workshops are structured, reviewing the methods and tools used at each stage.
A brief introduction to user story mapping
The main advantage of user story mapping is that it allows organizations using agile methods to interactively build a product backlog without getting lost in deep technical specification analysis. User story mapping focuses on defining needs from the end user’s perspective, crafting a “story” to narrate the user experience and understand the actions needed to meet users’ wishes. The map, which summarizes the user story, is created graphically with a set of clearly visible post-it notes on a wall.
In summary, the user story mapping technique encourages the development team to put themselves in the user’s shoes, shifting the focus away from technical requirements and removing rigidities that constrain the creative process.
As the method’s creator Jeff Patton states:
“The best solution comes from collaboration between those who have a problem and those who can solve it.”
How to select participants
The fundamental prerequisite for successful user story mapping lies in the selection of participants and the creation of an interdisciplinary team, which enables a holistic view of the product and allows each feature to be designed to generate value for the user.
That is why the working group must absolutely include representatives from IT, Development and Operations, Marketing and Sales, Customer Care. It may also be necessary to include members from the Legal and Finance departments, in case the product and user experience significantly impact specific topics (for example, privacy and compliance when handling sensitive data).
Companies with greater openness and courage invite key clients (or particularly collaborative ones) to attend the conversations: thanks to their direct experience, they bring an invaluable contribution.
The phases of user story mapping
Defining objectives
In the initial phase of the user story mapping workshop, the discussion focuses on discovering user needs: what results do people want to achieve when using the web product?
Taking a travel booking website as an example, the objectives might be: “Find a hotel in a seaside city”, “Choose the best hotel near the beach”, “Book a room for a week”.
From the analysis, you need to derive a series of objectives that will then be ordered according to user priorities.
Mapping paths and behaviors
Next, the paths that allow the user to achieve their goal are reviewed: what clicks do they need to make? What navigation flow do they follow? All necessary steps are then noted.
For example, one of the paths to find a seaside hotel might be: Visit the homepage ➝ Open the search ➝ Apply filters ➝ Sort the results.
Envisioning the solution for the user
This leads to designing the solution, using semantics that differ completely from a list of functional specifications. You still need to put yourself in the user’s shoes and think according to their needs.
Within a user story mapping project, a description of solutions might be formulated as follows: “As a budget-conscious traveler, I want to browse a page of deals and discounts to find a vacation hotel”; “As a business user, I need a hotel for next week and I search based on check-in date”.
Why do we use such high-level requirement examples? What value do they have?
The real value lies in the conversation that arises among the stakeholders involved about issues, constraints, dependencies, corner cases, hidden needs and blockers, but also about ideas and improvements, about what the company already provides and needs to be integrated, etc.
The result of these “stories” is not the story itself, but the living memory of an extremely high-bandwidth conversation that conveys a shared understanding of the project from every angle.
Prioritizing actions
If the previous phases have gone well, the team has several user stories at its disposal and is ready to identify a priority order: what are the most common user behaviors and the desirable actions to meet their requests?
The most urgent objectives with their corresponding solutions should be placed at the top of the list. For example, if the user base has no budget constraints, the first filter to refine a hotel search won’t be price, but rather the date.
Creating a release plan
Through the user story mapping methodology, we will guide you in defining the minimum features that the product must have to go live and meet user needs.
The focus should be directed essentially at the must-haves, meaning the set of most requested features that must simultaneously be quick, easy, and cost-effective to implement.
Once the essential requirements are covered and the Minimum Viable Product capable of satisfying the most common use case is launched, you can proceed incrementally with the addition of new features, perhaps more sophisticated and expensive. Each release, small and frequent, will be subject to results monitoring, so as to identify potential areas for improvement or incorrect assumptions and be ready to change course quickly.
What you get from our workshops
We offer one or multi-day workshops that allow the company to gain effective value on multiple levels: first, a working methodology is transferred, based on extensive experience and proven best practices; additionally, a functional solution aligned with end-user needs is developed, maximizing product adoption and driving business returns.
Concretely, our clients receive a report detailing the identified user archetypes and their needs, along with a roadmap that defines priorities and next steps.
Last but not least, a key deliverable of these sessions is the shared experience: having taken part in the conversation and put themselves in the user’s shoes, all team members will take away a visceral and experiential understanding of the end users. A crucial, complete, and irreversible shift in perspective.
