FeatureMap allows Markdown in the description of each card. Markdown is intended to be as easy-to-read and easy-to-write as is feasible.
Markdown is a simple markdown language you can use to easily add formatting to your cards. We do not support images or HR from Markdown at this time, you can see below the list of supported Markdown Text that can help you get your descriptions on cards:
Adding Markdown to text
This is how you **bold** text.
This is how you bold text
This is how you *italicize* text.
This is how you Italicize text
* Bullet one (don’t forget a space after the asterisk)
* Bullet two
Note: You must type a line break before and after the list.
Bullet one (don’t forget a space after the asterisk)
1. Step one
2. Step two
Note: Do not use a hashtag (#) when creating numbered lists in Markdown, as the symbol is used for other formatting.
User Story Mapping is often described as an easy process and maps are created by simply working through the user’s journey.
Sometimes it can sound simple, but at times you need to define the user’s journey.
Occasionally you’ve had a developer, or project manager who has already defined stories and just wants to regurgitate this journey onto a plan and have everyone agree. This sometimes works, but more often than not other team members are left wondering about more details and features, problems, and most importantly, better solutions are missed.
User Story Mapping is not just creating a map for the purpose of a great visual understanding, but it is also a great time to go over questions and really expose the plan.
Just as your first bunch of questions:
Critical thinking can be applied with great b0ons to any endevour and User Story Mapping is no different.
Those working on the map should have a clear defined understanding who the users are.
Who is the user that mapped this journey?
How is this user different to other users?
Do we need to expand our user scope at this stage?
Understanding who the users are will provide that focus for complex design and if the user is an actual real user, then knowing this person will help with focusing the team to provide something for someone real.
Defining what the user is doing with your project, app or endevour will be the main crux and defining question for all over User Story Mapping.
What are the users trying to achieve?
What do the users benefit over using your solution?
What other solutions are available?
What needs to defined?
Starting with an understanding of not only who the user is, but why this story needs to be mapped is crucial to have a worthwhile map.
Asking questions to help the entire mapping team directs.
Why does the story need to be created?
Why does it need to be defined?
Why would this information help decide scale and stability?
Once you have the ideal persona, and the ideal customer or user you can create an epic from the persona.
Label all your epics necessary to meet your users goals, but it is okay to keep them rough as you’ll be able to quick edit the table, adjust, delete and add more columns as needed.
Turn the users functions into rough epics
Turn the products functionality into rough epics
Capture the interaction and sequences
Then go deeper and refine each Epic into the cards.
It is normal to be challenged with your first iterations with a User Story Map and it’s okay to continually develop them.
Keep the users entire journey and story in mind, and don’t stop asking the questions, who, what , why?
User Story Mapping is normally a technique for Product Development, but you need not limit yourself for just one task or function.
Here we explore outside the box and look at applying User Story Mapping to product lessons, customer feedback, marketing strategies and even Christmas lists.
User Story Mapping is most commonly used for software development. You are able to outline and see the bigger picture of your product. You can prioritise the user stories, identify the journey of your users and involve all team members to have a shared understanding.
It is not just a tool that you use to outline the project, it is a technique applied to every step of the way. You can change, adapt, reprioritise, add further tasks, scrap old tasks, and so on. While ideal to sit on a wall in the office with post-it notes one large company has a large 75″ display in the office with their FeatureMap on display for all offices and departments.
Moving to the digital has its benefits and allows all departments and those remote to the office to collaborate. In addition, you can allow your shareholders and in some cases, even your customers to get involved.
Occasionally after a campaign, season, or annual review you look back at your product and hold a session of “product lessons learnt”:
Promote the recurrence of desirable outcomes
Preclude the recurrence of undesirable outcomes
Using User Story Mapping here can help you outline the user journey. Define each step which worked, and highlight what should be removed or revised.
Using layers you are able to prioritise your learnings by the impact on the user using analytics data, internal comments and observations, incident reports, and any further data or knowledge that can build a picture about your product and its presence.
Your goal is not to create a product but to highlight the users experience to learn.
Developing your map can involve the customer, allowing a public-facing map and open process you can get feedback direct from the customer.
Taking suggestions, feedback and ideas from customers is the golden goose.
We’ve all had the occasional user when you open up your ticket support system or email and in the inbox sits 10 emails all from the same person hammering feedback after feedback. These users are my favourite, and while initially a shock to the system, they offer the best value.
Taking all feedback to build your User Story Map and highlight the pain points reported.
Set columns for feedback, suggestions, bug reports and crashes.
Again, do not set this as a product development map but a feedback map and this can help you prioritise your next steps for development and also feed directly into Product Lessons.
Marketing and email strategy
When defining the user flow from a cold lead to a warm lead, add in tracking, and stages you’ll soon hit a complicated process. User Story Mapping, the super-hero of project management is here again.
Setting our a User Flow from cold lead, to warm lead, to sign-up, to conversion can all be done with a FeatureMap.
While mailing systems, like mail-chimp, can work exceptionally defining a campaign, following a user along a sales process (especially when plugged into marketing) is broader than MailChimp.
Happy Holidays to you all, and time for a bit of fun, but an entirely function one.
This year I was planning out what to buy my friends, family and fellow office workers and wanted a way to track what I had purchased. In some cases, I have commissioned artwork and needed picture frames and had presents that became a multi-stage process. I turned to User Story Mapping and whipped up a FeatureMap to help manage who was getting what!
When building your story map, you should include all the relevant people, regardless of position, in the team. Due to their different foundations and interests, they will all offer unique and valuable points of view. A User Story Map is used to map out what you, as developers or managers think about when it comes to the user’s experience.
One advanced tactic is to involve the customer with a customer facing Story Map.
Customers have probably seen roadmaps but to truly involve a customer a back-log will always show more detail, yet a Story Map can show your progress with a beautiful planned out snapshot.
Why use a customer facing Story Map?
Story Maps are for shared understanding and can share a clear overview of the whole product or project.
While you may not be able to share your post-it note maps very well, here at FeatureMap you can create a copy of your internal map and create a map for public facing, set it to public and share the link, such as this demo map:
A tool such as FeatureMap, used to share your product design lends more value to the customer, as it is always online, available to view and offer feedback.
When should I use a customer facing story map?
When sharing story maps with customers, it is important to iterate that a story map is not a roadmap, it is a living, breathing, evolving workflow. One day you may have features and functions set for the next release and the very next day it could be bumped up, down or adjusted.
The value of such a map is measured not only in the transparency of your dev team and work, but the process of your dev team.
In one such instance, we saw a knowledgeable member of the public witness a planned feature who then recommended an alternative method and offered code, for free. Through sharing your Story Map the project was assisted by a passionate user.
Story Mapping evolves and changes. If your customers struggle with the methodology it is probably wise to have two maps, one for devs, and one for the customers. You can set one to private, for your team and shareholders who can work through it and have a public shared customer facing map which encourages feedback, and interaction. We advise experimenting with the entirely public facing single map first.
As such we advise involving a customer as soon as possible.
How to make the map public?
When on your FeatureMap, click the top right blue spanner icon:
Then below you’ll have your options pop up.
Here you can click “Make map public”.
Do note you can click this button again “Make map private” to remove your public access link.
Once public you’ll be able to share the URL and add this to your emails, webpage or direct as links.
Creating your user story maps you will notice a few fields with due dates, importance, color, and custom fields which are default set to Estimation and Elapsed time.
The custom fields have the option to be aggregator fields and the numerical value will add up with other cards in the column, task, activity.
Here you can see that two cards have point values and cost values which are aggregated at the title card at the top:
All these features and functions can help with building trust with your customers as you demonstrate transparency with your activities.
Take customer feedback and deliver extra value by integrating their suggestions, ideas and changes into cards, sprints and allow those customers to see their feedback, in real-time, get integrated into a product promoting customer loyalty.
FeatureMap offers JIRA integration.
You can sync your map with JIRA or import a snapshot of JIRA and edit it from that point.
With your User Story Map integrated with JIRA, you can sync your tasks and display a beautiful map of your backlog suited for your customer facing interaction.
User Story Mapping has been described as a niche tool to achieve much. Tools for product development, feature definition, version improvement and project management just to name a few.
In this case we are looking at the steps to success, utilising User Story Mapping methodology to help define your path. The first two steps instantly reward.
Firstly, planning the map rewards you a pathway to the point so that you can start writing user stories (a user story is a short description of something your customer will do when using your product).
Secondly, the end result is a visual chart showing the structure of your stories which gives you the steps to development.
Here is another way to approach User Story Mapping in three steps and this is a relatively quick way of getting to a point to start development work.
Hosting your Story Mapping Session
Because User Story Mapping can come across as complex it is important that management of the session is approached with a framework. Needless to say that User Story Mapping can be a new tool for most people so outlining what it is all about and describing the process is important.
Start with tasks where the team thinks about the product, users, development and personas.
We start by brainstorming every task that users will want to address when using the product.
Silent Brainstorming. Task each participant to write down steps in your cards, every step will need to cover from the users first engagement to the conclusion of the users interaction. Encourage the team to think of these as actions not features.
Top Tip: Writing them so they start with a verb is a good technique.
Encourage people to be creative and try to cover tasks and steps wide, but not deep. This part of User Story Mapping is about breadth not depth.
Start posting all cards and tasks in one large map. Thats fine, you’ll have duplicates, and these should sit beside each other on the line (not above or below). As you expand and learn you can easily drag and drop and delete if needed. The beauty of using digital software for large collaberation tasks such as this allows you and you and your team to easily edit, expand and develop your map.
This first line is the user tasks and they form the backbone of your story map.
Then we organise these tasks into wider goals, and arrange them in order of completion.
These groups are known as “epics” or “activities”.
As facilitator you can walk along the line of tasks and ask where the team think the splits are between each group of tasks, and what each group should be called.
For example, if you were building an app for an app to arrange your movies you might group user tasks into epics like this:
Browse DVDs in collection – epic
View flat list of all DVDs – user task
View DVD cover thumbnails in results – user task
DVD Spec Call – user task
We can then move into the Prioritisation exercise, further developing the user story map.
This is the stage where you start writing in the details, building up the tasks and redifining tasks. This may include adding tasks, merging tasks or seperating tasks.
It is important to detail the tasks enough to remember in the future.
After writing all the tasks, you should have a comprehensive map by this stage.
Task your team to go over each line (now defined as Epics/actitives) and ensure you have everything charted. This is where the User Story Map will become easier as you will now have a visual chart of a defined product. Here you can move to the next steps.
Now you are ready to start prioritising the user stories on your map. You can start adapting and moving your tasks to sprints, also known as versions for your product.
User Story Mapping can be regarded as a simple, or unsophisticated approach to software development planning, but normally this is because it is being utilised in a basic manner. All methodologies can be used as a sub-par process resulting in a simple outcome. Instead look at in depth.
In essence, a simple story idea is; write something on a card, talk about it, converse and agree on what to build. Complete the build and move to the next.
It sounds simple, but in a working environment, it is normally vastly more complex. Stories end up going through multiple processes, cycles and conversations. Stories end being created with 3 main needs. A card for the business, a card for the user and a card for the developers. Luckily User Story Mapping is something that can absolutely lend itself to this process.
The Right Size for the Right Story
When writing a User Story Map with a team, you loosely fall into three categories:
The user’s right size is a story or card that fulfills a need.
The businesses right size is a story which bundles features, outlines updates, themes or new products. First it is set-up as a Minimum Viable Product and following releases are the right size which helps a business achieve a business outcome.
The developer’s right size is the most efficient for designing, building and testing.
Big Stories Break Down to Smaller Stories
Big stories (or epics) can be broken down to smaller stories, and then again even smaller. Each sprint/epic/story/card can be defined for each group but no matter the size, they are still a story.
To break down larger stories, use conversation.
Discuss and Discover
When you discuss, break down each story until it fits the “right size”.
Each size will vary from business to business, and project to project, so don’t define too much. Use conversations to allow you to naturally identify the “right size”.
When you discuss, dig deep into:
Who the user will use your solution.
How the user meet their needs without your solution.
How it would change with your solution.
How your solution would look and function.
How long will your solution take to build.
Even after your discussed discovery session, don’t stop talking, dont stop collaborating.
With each step, each conversation will have different teams and different conversations, in particular, the main three, so do note each evaluation will vary.
Yet with each conversation, each meeting, each get-together, this can lead to slow down, so be aware of how you plan your meetings.
With FeatureMap you are able to construct your maps and have constant, flowing conversation on each card, story or epic. Have your entire team chime in, discuss and do so remotely. Allow this process to be part of the working stage eliminating unnecessary meetings for all and saving time and money.
With each card, story and sprint you design and build, every single card will have consequences, re-explore these, discuss them, confirm them.
5 Reasons to use User Story Mapping for Project management.
It can be a nightmare when planning out a project or joining a team to plan the project and you are met with Word documents. It is even worse when the customer and your team are expected to settle on the design outline of a word document with no future changes.
Requirements always change as customers and teams discover more about their project as it progresses. Expectations change, development requirements are adjusted, improved upon and developed and tracking all these changes in a Word document leads to madness.
User Story Mapping is a clear-cut methodology that let teams plan software releases that create visual maps of customer requirements. User stories are typically written on sticky notes or developed on a virtual map with absolute collaboration. (FeatureMap).
Here are five reasons why you should utilise User Story Mapping for your next project.
1. Prioritize the most important requirements.
Story maps let teams identify the really important reuqirements, and then allows the team to real-time amend and edit the map with development and feedback. While doable with sticky notes, the interactive collaboration of FeatureMap allows on the fly editing and at a glance live progress. With a story map, teams can prioritize the most important features first and deliver code based on the prioritized features.
Features can be identify and built in sprints in multiple MVP states with ease, rather than developing one function in its entirety. It allows you to build your function, then at a later stage refines the features across with each iteration. You can easily identify what is most important and what is a core feature. Splits large requirements into small slices
2. Enforces task separation to encourage smaller sprints.
Cards and Post-it notes have literal maximum space. A good habit is born and can be utilised for your User Story Map creation. You have to be brief in the requirement description. If the requirement description is too complex to be stated on a single card, simply break it up into two cards. Create to functions, two tasks which can be split (if required) into multiple sprints.
This again allows the project to be refined and delivered on time with clarity and simplicity.
No more twenty page documents!
3. Communication with the stakeholder.
User Story maps aid with communication with the customer/stakeholder. Each customer requirement is then aligned with a task or card, the customer can understand at a glance what functionality will be delivered with each sprint and release.
With FeatureMap you can create a map for your development team, and share it publically to those with the URL link, the customer will see, real-time of your development map. Alternatively, you can create a map from a map (like cloning) and then share that map as a “snapshot” of the progress. And of course, you can export the map in a multitude of ways.
If the customer wants a feature delivered earlier, the customer can see which stage the feature or card is in and if involved in the process can adjust the map.
4. Communication with the team to help define and manage trade-offs and objectives.
Potentially the most important benefit. Using a User Story Mapping map will boost communication and discussion. Visual thinking is common in approximately 60%–65% of the general population, leaning on statistically your team will benefit too.
Having this visual aid and 2D map will reveal questions of all participants in the early phases of the project, which will lead to more quality and faster product backlog creation.
This will allow you as a Project Manager to keep on top of trade-offs and manage features and the project objective.
5. Visualisation of the entire Roadmap
A story map can focus the stakeholder and team to see a snippet. It can reduce that 200-page word document of completed tasks, or charts of completed tasks to a visual map of completed sprints and planned development.
The focus is smaller and the stakeholder can visually understand the requirements being delivered in the first release, second release and subsequent releases. The stakeholder can pay more attention to the relevant requirements (and requirements always change).
The customer here can see the current release and the solving of an issue, but can also tell at a simple glance that the “even better mega solution” is in the next release.
User Story Mapping can be utilised in a multitude of ways. Project Managers can step in and compliment their planning with a digital version of User Story Mapping and work with the team, developers, customers, and even users for feedback.
If you want to learn more about building a project we recommend “easily testable” to “useable” then to “loveable” rather than building a broken bike in all stages. Read more in our Idea to MVP.
A story user map can be used as a method for visually outlining your roadmap for your product.
We started this intro to story mapping with a basic run down and a simple exercise taking you through the morning tasks and making a map. Now we will look at how to outline your roadmap. Also don’t forget to check out some good practises in going from Idea to MVP.
In our case study we are going to look at “Movie Buddy”. The Initial MVP was to generate an app which could be used to manage your DVD collection.
The first step is to identifiy your main goal, in this case it was “Manage my DVD Collection”
The next layer introducing tasks and we identified 4 main features.
Add a DVD to my collection
Browser DVDs in collection
Find a DVD in collection
View/Edit DVD info
From here we were able to fill in further details for each card in our first sprint.
The horizontal sprint delimits the first iteration we implemented from stories, from ideas and how we chose to postpone features for a further iteration. We chose to implement the backbone for the main features and come back later to add details and fine-tunings.
From here we moved to the next step and that was expanding our features. You can see we have expanded a colum to the right (in green.)
We wanted to introduce a social element, a movie recommendation feature.
Now to add cards to this next sprint we needed a new horizontal layer, so adding sprint 2 (in purple) this allowed us to identify what improvements we wanted to add to our core back-bone features.
You can see how with each new column of improvements and with each deployment of your application (or version) you can develop and expand your application using a simple user story map.
At a glance you can see which features are implemented, or which features are set to be implemented down the road.
In this example it was decided that the “Get Movies Recommendations” section was a good hit and so the idea was expanded. In addition our users wanted to expand our core backbone and introduce scanning of barcodes of DVD’s to identify it in our database.
We realised we could scan DVD’s by barcode, but taking photos of the cover would need extra work so we seperated the sprints, in addition we also wanted to improve our management of favourite directors/actors by allowing recommendations on directors but that would take time. This was also added to the later sprint.
This left us with our final idea and roadmap for the coming development cycles.
When designing a roadmap from your MVP it is okay to place down expanded ideas and the best features you can imagine. A user Story Map is designed to allow you to see the overall roadmap, the big picture, the ideal application.
Taking that application can then allow you and your team to arrange the features, arrange the sprints, split the application up to version and settle, together, with an ideal roadmap.
We started this intro to story mapping with a basic run down and a simple exercise taking you through the morning tasks and making a map. Now we will look at how to define features in a product.
When you first start off it is best to have an idea of the ideal product, but have not yet started on your product roadmap. Instead start with the user’s normal workflow (minus the app or software) and figure out how to translate that flow into a product experience.
Below I have outlined an example case study of arranging a conference with the persona of the organiser and board member.
The team sat down and exchanged tasks, goals and ideas. We then started to construct a story map based on the conference organiser’s first set of responsbilities and workflow.
After the initial workflow you will notice the goal at the top linked to the persona.
The main activities are in the first row, divided into further tasks in each column which details each activity.
On a card we have further detail such as:
After we established the conference organiser’s tasks we then expanded the story map to include the expanded responsibilities and workflow of the entire Team.
With this map now completed we can see the user workflow and what features we need defined.
When building your story map, you should include all the relevent people, regardless of position, in the team. Due to their different foundations and interests, they all get valuable points of view. Everybody has an unmistakable and common comprehension of what they are about to build together.
Product owner, testers, technical lead, customer support, architect, UX/UI designer, sales and marketing, etc. All have their own techniques and requirements which will help you create your map.
How to build a story map
If you are brand new to user story mapping, we have a short and sweet exercise. Let’s take a simple real-life example of “getting ready for work”.
Start with the goal.
What is the story map about?
What are you trying to accomplish?
The main overall purpose.
Second list your main stories, your main tasks or activities. From left to right, insert the main steps of the story map that need to happen.
Move on and detail each main list – column by column, left to right.
In the case of product features, the layers can be then developed and you can plan out MVP‘s, or product iterations with each following layer.
When exploring product features, build story maps for multiple options that solve the underlying problem. Allow your entire team to contribute and come to and understanding of the final decision.
Story User Maps are ideal for allowing a team to design out a product feature and reduce the need to go back half way through development because XYZ requirement was missed out.