It’s 2021, and that old code is way over due. How to plan your Legacy rewrite.

Re-write your legacy application using User Story Mapping

Does your current application need its legacy code rewritten to benefit from security, new features, modern integrations and to get with the new working world of remote WFH lifestyle?

Stop putting it off.

We’ll go over how to tackle the mammoth task and break it down to an approcable and task worth completing.

People often mistake User Story Mapping as a tool to start projects, but it is entirely suitable for building up an old project or design or plugging into an active project to help redefine the backlog, MVP and process. Afterall.. you need to start with your MVP or risk feature creep and stagnation.

FeatureMap can be used to help you plan out a current project or in this case, current piece of software. First approach the product/project/app and hash out the main features of the finished and current code.

A few options may be available to you, depending on the code:

Are you able to update the tool in sections?
Are you able to approach the update in sprints/versions?
Do you need to rebuild the entire program from scratch?

Take a moment, start you map and make a column and throw in ideas, thoughts, approaches, decisions. This is more for reference that you can draw from as you plan out the current software.

You can utilise basic User Story Mapping and decide where to place these cards, with which layers, columns and sections on your map.

Below and in these examples, we will refer ot our “Moviebuddy” app, a fictional app to help sorts your DVD collection.

The Moviebuddy Current Version

We then worked through identifying which sections were redundant and not required after the code update. We identified these and added them to a new column to the side. Essentially removing them from view. Some of these features were workarounds that the new framework would natively support so we can remove those, yet we still need to rewrite some of the related code. Be sure to add discriptions for your team to reference that may help them realise your decisions.

In this case, our team assembled and had an online meeting to identified which parts of the code would be updated and what we should be prioritised as a framework. We labelled this as version 1 and aimed to get the core functions updated. The MVP of re-writes.

Identifying what we should upgrade first in Version 1

We were able to identify one function which we were able to upgrade. We also added new cards which reminded us to update our code standards and highlighted them green to ensure they were completed.

We then moved along to the next version which allowed us to introduce our new payment gateway to the application. A function that had alluded us due to the old codebase.

Adding a new Codebase column and moving to version 1.5

This allowed us to deploy more frequently and provide value sooner as we updated sections of the site. We still had a lot of ‘old legacy code’ but as we added new features we moved the legacy code functions inline with our updates.

Re-writing your legacy code is so very typically neuenced and specific to your use case, but I hope with these examples above you can see how to:

  • Add your current app to a map.
  • Collaborate with your team to share the same understanding.
  • Highlight what is redudant.
  • Task and outline new expanded features.
  • Work through the MVP and assign with the team members.
  • Estimate time, costings and aggregate them for team leaders to quickly understand.
  • Rewrite your legacy code
  • Have a celebration

As you can see using User Story Mapping can be brand new projects, or old existing projects.

It’s 2021 already, stop putting that task off, realise how easy and approachable it is with a User Story Map. Break down the mountain to bite size tasks and update that out of date framework!

If you need direct advice, coaching, a guide or want to book some time to explore FeatureMap, do feel free to reach out to us, but first…

Moviebuddy is all fictional for the purpose of training.

Shared Understanding – Benefits of Story Mapping

Shared Understanding - A buzzword to describe group knowledge

“Shared Understanding” is a well known buzz word, or common expression, in the User Story Mapping and project management scene. It really easily breaks down to a common group concenus of a projects. Getting to the point of a common shared concensus can be met with pitfalls and misunderstandings without even realising the issue is there!

Paul, Alex and Simon can all believe they agree and understanding one anothers design idea…. but do they?

User Story Mapping is not strictly a method of building software as it can be applied and utilised in a multiple of ways, but for this.. it is perfect.

The main drive is to result in a shared understanding, to expose the absolute “given” in philsosophy.

Shared Understanding in 2021
Shared by Jeff Patton, author of User Story Mapping – The Shared Understanding Problem.

When working with a large organisation it is not uncommon for everyone to picture the product in different ways.

When you have multiple smaller teams come together to create a product, each team can have different requirements. This can clog up development and in some instances waste time, building the same features in multiple different ways.

Check out FeatureMap and start your trial now.

A few years ago I was assisting in the development of a now-popular mobile app. The team of designers all had different ideas on the end goal and it wasn’t until we mapped the entire user story that this was realised.

Confused Team Mapping Out Individual Requirements

The managers wanted to see a CRM in the backend that would allow them to see the flow of products and users and to manage the support workers and content creators.

The content creators wanted to have a CRM in the backend that allowed them to edit, create and update articles and products.

The sales team wanted to have a map system that would allow users to find a product based on location.

Seeing our goals visually on a map was a big help in shared understanding

Project Manager in this case.

Before using FeatureMap to plan out their goals, the team used multiple shared documents, lists and tasks. It was possible to achieve what they sought, but it was certainly wrought with overlapping issues.

Shared Understanding with a Shared Vision

When we put all three together we could see an overlap of two different CRM systems and a product completely overlooked by the other teams.

Mapping your story helps you find holes in your thinking.

When we set out and built an entire wall, it was clear that each team had a different idea. Once they were able to list each card across the map, teams merged ideas, worked on the initial idea and framed the entire product.

Once the ideas had been merged, expanded and realised, the team was able to expand their understanding to a shared understanding.

Shared MVP Achieved With Understanding

The team were then able to split up their design into a minimum viable product that successfully achieved the desired outcome.

Sadly, it was realised that months had been wasted on planning features of a project with no compatiblity with the rest of the team.

Which teams should be involved?

Really, the answer is as many as you can.

  • UX/UI Team
  • Agile Coaches
  • Software Engineers
  • Product Owners
  • Product Managers
  • Customers
  • Marketing Teams
  • Executives

User Story Mapping is better when a group advises, rather than an individual.

How to get Started?

Getting started is easy, assembled your team, open up a map and start talking!

The Future of Remote Work in 2021

The world saw a huge shift in the 2020 working environment due to the Covid-19 Pandemic. While still here in many countries, and fears of third waves on the horizon, many are holding hope for the Vaccines that seem to be still shaping out the future landscape of the working world.

While some companies used to offer a work from home perk, it has fast become the go-to standard. Now in 2021 companies are transforming workplaces to places of collaboration, rather than a dedicated heads-down workplace.

Many companies are making the permanent move to dedicate a number or all of their team to a remote working solution. Dell want to move 50% of its workfoce to remote. Amazon have picked up over 3000 remote workers, and other companies such as Saleforce and SAP have been well reported as remote working companies.

With the economy, the after effects of the worldwilde pandemic, the stagnant wages and growing government state incentives. It is clear to see why it is predicted that by 2025, nearly 70% of the workforce will work remotely, at least part-time.

By 2025, 70% of the workforce will work remotely part-time.

Kate Lister, president of Global Workplace Analytics

A few years before the Pandemic; FeatureMap itself moved from its dedicated office space to remote employees across three countries. In making these changes, we identified more effective practices, saved on overheads and costs, and introduced a new culture and productivity.

As the pandemic forced other companies also turn to the remote online workspace, we thought it would be a good time to share some of our experiences and tips for getting the best out of your distributed team. We shared our initial thoughts and experiences in our last blog related to working from home. But how baout 2021?

We are here to help, so if your small–medium business is impacted by COVID-19, reach out to us at team@featuremap.co and see how we can find a solution for you during this time.

Working from Home

Things you need for your team to be successful while working from home remotely:

  • Team chat
  • Video conferencing capability with screen share options
  • Digital backlog management
  • Shared documents
  • Time management
  • Ways to stay connected with each other
A laptop of a remote worker starting with distributed team about to utilise user story mapping with featuremap.co
Make your office space at home comfortable for remote working.

Team chat

There are many chat tools available online. We recommend Slack, Teams and Skype, but Slack in particular. It allows you to continue conversations throughout the course of work, either directly through private messages or in channels that act as meeting rooms. Everyone will be able to see discussions in these channels, so wise management using features like thread conversations will be key to an effective collaborative environment. You may already have a Microsoft solution and Teams have developed well in the last year.

Video conferencing

This includes daily discussions, team voice chats, and one-to-one meetings. We recommend video conferencing to encourage a continued level of professionalism, but being able to chat with somebody face-to-face can create more effective communication.

Good video conferencing software offers voice chat, video, and screen share. The ability to easily and quickly share your screen to your remote team during a meeting is time-saving gold dust. Zoom, TeamViewer, and Slack all offer this functionality.

However, be aware that both chat and voice calls can be disruptive if used unnecessarily: imagine getting called to meeting after meeting in the office!

We found a careful balance of start of the week meetings and end of the week meetings with ad hoc, required, progress meetings when required.

Common Problems

Remote work, does have its problems. Some people dislike working in the same place where they live, relax and can be hard to create a personal seperation. Other people require face to face, contact and interaction with people and the seperation can cause a disconnect. Some talk about the challenge of how to collaborate and state it is difficult to get on the same page with projects.

Luckily while we cannot help with the face to face contact. We can advise creating an area or state to help with the switch from work to personal.

Establishing discipline, dressing for work, and setting your desk or workspace in a particular manner. One trick I use is different coffee cups! Bizzare, I know, but it works!

Finally we can help with collaboration. Projects, teams, and remote working on completing a project, blacklog or product is the name of the game here at FeatureMap.

Digital backlog management

When you first start working remotely, it’s important to update the management of your tasks and responsibilities to your new environment. All those sticky notes on your monitor and scribbles left on your desk won’t work anymore. You have to go digital.

If you have a project manager, ask them to recreate your collaborative spaces in a digital space as soon as possible. Your remote team being able to access a single platform for project planning will not only help foster self-discipline but will also improve productivity. Ensure you use a tool that protects you, is easy to set up, and is clear, precise, and agnostic.

If you have any questions about FeatureMap.co, privacy, security of our online cloud or our on-premise options, drop an email over to team@featuremap.co

When we first created FeatureMap, we designed the fundamental principles based on Jeff Patton’s User Story Mapping model. Since then, however, we have evolved and developed to create a tool that can be used in multiple environments with a wide range of practices, including user story mapping, development, product management, team task management, agile workflows, kanban, and task lists.

When you recreate your collaborative space online, remember that utilising labels, custom fields, colour tags and assignments can really help you take control of your workflow.

A remote worker taking his user story mapping post it notes to a digital tool
Take your post-it notes and put them online for your team.

Moving to the digital space for project management

If you are moving from a physical workspace to the digital one, and are starting afresh, you will need to first identify and define the project’s backbone.

Designate a group of people to explore your project and identify the user experience and journey. Focus on the breadth of tasks first, then build in the depth.

If its easier we now support SAML integration to allow an easier onboarding process for On-Premise accounts

Using a shared workspace to collaborate live, whilst using video chat, can really help bring your session together as well as improve the quality of the end result.

Build a map and, if you need to, outline all the projects, cases, tasks and work within it. If you want to dig deeper into user story mapping while your team is distributed, check out our guide on how to get started.

If you are still uncertain and want a demo of FeatureMap.co, do reach out at sales@featuremap.co and we’ll be happy to schedule a live demo for a small team.

A FeatureMap marketing story map demonstrating some of the features of User Story Mapping and Agile.
Covid-19 – Taking your physical to the digital with FeatureMap.co

Distributed team culture

Building a culture, keeping the team connection healthy, and improving communication with remote teammates is crucial. For this, team chat and communication is important. Adding a space where people can chat, share their daily lives, or simply talk before work or a meeting fosters healthy growth, keeps people engaged, and helps your teammates learn about each other. You can even build on this by creating virtual lunches together, having healthy competition about the “best lunch”, and more.

Try FeatureMap Today, and if you need more users, have feedback or suggestions we have new solutions for 2021 to help get you onboarded.

Do reach out and we can find a solution to help cover you while Covid-19 impacts your business.

FeatureMap – User Story Mapping Tool 2021

Categories

Archives

Story Mapping in 2021: A Reliable Agile Methodology

Managing a project can be approached in a multitude of ways, and in 2021, with remote working and offices on the rise. User Story Mapping has rapidly stood out amongst the many agile methods. In one sentence, it can be easily explained as ordering a project (or product) into tasks and organising by priority and sophistication.

Let’s start with a brand new project, or we can take an existing project backlog. When it comes to backlogs it can be overwhelming, at times difficult to grasp, or what you should prioritise. At times projects are entirely sidetracked by mismanagement of priorities but user story mapping can resolve this.

Story Mapping can be utilised to reduce the backlog, refocus the project and remind the entire team of the end goal.

When designing a Story Map you must look at the bigger picture. It is often sensible to set aside a period of time (hours or days) to effectively cover exploring your vision.

You will need to set out the goals of the entire product, the ideals, the dreams, think big. To best utilise Story Mapping is the big picture, not just a sprint. Do not fall into the trap of a niche narrow sprint at this stage.

First write out the user stories by setting out functions.

Step 1 — Functions and user stories set out in a grid.

Horizontally, set out the title and set the user story under each function.
Vertically, set out the main stories or issues related to each other.

At this stage you can then prioritise importance from left to right, and from up to down. This creates a format of the top left card, being the most important.

Slicing the list.

Once the stories are organised into groups and themes. You can start with slicing the list into sprints of what is the Minimum Viable Spec, or as Jeff Patton puts it — “The minimum viable product in the smallest product releases that successfully achieves its desired outcomes”.

Step 2 — You can see the sprints have seperated, clearly, what functions are required in each layer.

You can set sprints into what you need to achieve. The trick of utilising story mapping is by setting out the entire dream product, then breaking your product/project into sections of achievable, working, and required sprints.

Next Steps.

Do remember, the story map is not a static beast, it can be adjusted, amended with feedback, changed and adapted to suit the needs of each sprint.

With multiple team members working on it, as a team, you can start to see the end goal. The ideal product starts to form and when working as a group you will be able to clearly define what each task, and part of the project needs.

  • Set status of a card
  • You can set time estimations
  • Set importance of cards
  • Use colours to set a custom identifier, such as challenge or complexity.
  • Use extra columns and set sections

The use of a story map will grow with each iteration, and with each demand.

Step 3 — Expanded map with colours, rags, and time estimations.

One thing is to ensure you are always planning the entire project, clearing backlog and not focusing on individual sprints.

If you want to see the tool we used for the images, check out FeatureMap.co

If you want to dig deeper into User Story Mapping, check out the how-tos Tutorials.

Online User Story Mapping for Remote Teams

If you are new to User Story Mapping or have already done user story mapping, it is highly likely that you’ll be doing Remote User Story Mapping online in 2020.

Since the pandemic we have seen over 31% of the US Workforce migrate from offices in March 2020 to working from home in April 2020.

Already we see businesses changing the way they work, creating permanent changes to include remote working, hot desking, partial office attendance and in some cases, removal of the office entirely. It is clear that if we seek out a positive from all this, the education of a better work-life is certainly one.

One downside of the removal of a physical office space is the ability to carry out planning, and if we look at User Story Mapping – the ease to create a board. This is where FeatureMap comes in as an online digital space.

Lets go over the 5 things for a successful remote User Story Mapping session.

  1. Foundations

First make sure your entire team understands the principle of User Story Mapping. Who, What, Why? Of user story mapping, the multi-uses, some examples of why to use it for project management and basic intros. As long as your team understands – you will be golden.

  1. Plan your introduction

It may take a few days, may take a week, or may take a quick catch up over the day. Whatever the use case of your group is, and the required time, be sure to keep in mind the differences between working in the office and working from home.

Figure out an agenda, plan the day over introductions, activities, presentations, and when to carefully place the breaks.

For some, working from home can be distracting, while for others it can provide a freedom and comfort to allow them to work efficiently. Cater to everyone.

Is everyone on the same timezone?

Will everyone be available for the full time?

Social time?

Can you create a course?

  1. Get your Tech in order.

If you’ve been in any meetings with people new to remote working it can derail the meeting to tech support and cause all sorts of issues.

Ensure everyone is ready with their hardware, software and prepared to participate and collaborate.

This will be basic things such as:

  • Your main communications, be it Teams, Zoom, Skype or Slack – ensure everyone is signed in, ready and working.
  • VOIP, Headphones, Microphones, audio tests – Ensure everyone is good ahead of time. There is nothing worse than having one person spend 45 minutes troubleshooting a microphone.
  • Webcams working – These are great to make the remote working feel like you are all in it together.
  • The PC and Internet! – Basic basic basic tests. Make sure it all works.
  • FeatureMap Accounts – signed up, invited an in the correct map ready (either in a trial if new, or setup with the group leader if business). We’ve made this bit easy 😉

You can send this out pre-meeting and ensure everyone can do a mock load, test and make sure they are ready to go 9am the day of the course.

  1. Set out clear rules

So this is more of a per group basis. I’ve sat in meetings where everyone is completely new to remote working, and I’ve sat in groups where it is a tried and tested done deal. The huge range of experiences were staggeringly immense – talking over one another, crunching of food, tech issues, volume, lag – oh my.

Set out some rules to ensure your remote user mapping session is productive:

  • One person talks at a time
  • Ensure everyone has had time to participate
  • Check chat frequently
  • Eat only in your break
  • Good audio and camera (put your webcam on!)
  • Mute your microphone between conversations and don’t hot mic!

In an ideal world, your remote colleague might be in a self contained home office, free from distractions and sound – but in a real world… sometimes the kids, dog, neighbours or even home office equipment may not behave. So give slack but also be aware of your team and work to these requirements.

  1. Meeting Execution

Now we have our tech sorted, our plan, our rules and accounts. It is worth considering that working online for long periods of time can be extremely tiring and regular breaks are recommended.

One simple rule for remote working is that when scheduling meetings plan them to finish 5 minutes before the end of the hour, or before the half hour, to build in time for much needed breaks.

Here are some basic tips for running effective online sessions:

  • Manage Talking Time – Communicating online can take longer, typing, thought process (the removal of visual feedback) but also allow clearer and direct communication. However it can take time so try timeboxes. Use a timer, visible to all, to ensure conversations do not drift.
  • Visualise Information – Share sources of information when referring to it in the meeting, use your dedicated channel to get a clear visualisation. This is an important goal and why the User Story Map and its visual collaboration is important to be real time.
  • Avoid repetition – Maintain engagement, and keeping attention is important as so you do not need to repeat coverage. There are many tips to do this, but random selection or asking the last person who spoke to choose who speaks next is a good way to keep everyone alert and listening to the course.
  • Records and Notes – If the call needs to be recorded, or notes do so in an online document. Webcams at flipcharts, photos of whiteboards can deliver a very poor and low impact experience. While you’ll have the story board covered with FeatureMap, it is important to ensure accompanying tech to deliver a strong course.

One thing 2020 has shown us – Remote Working is here to stay, so get ahead of the curve and ensure your team is productive and effective.

User story mapping games for learning

User Story Mapping can seem daunting when you first pull up a full FeatureMap. If those on your team are not familiar with the technique it can really slow down your sessions. Yet the technique is innately simple and can be taught very quickly.

Here I outline some of the quick and easy 30 minute games that you can add to your teaching workshop, or that you can go over yourself to help share or gain a n understanding on how to approach user story mapping.

 

Get to Work!

One of the easiest and well known games is the “Get to work” or “Wake up in the morning” tasks.

You write out on your map what you do each morning. This can be broken down to the most mundane steps.

I once had a team member write out everything they did which included an impressive rising time of 4am and 3 hours of morning preperation. I have since added to the challenge that they only have 20 minutes to get up and to get out the door to get to work.

What you can do is expand the task to reduce the time available, and to extend the time available to experience with what they add and cut aka minimal viable product! 😉

We have a map here of an example of our “Get to work”

Getting Ready for Work example on FeatureMap
Getting Ready for Work example on FeatureMap

 

Planning a vaction

Another exercise is to add a time limit, deadline and propose they prepare for a vaction.

Setting my team of 1 month to there vaction they had to go through steps of checking passport, renewing, booking flights, checking luggage, buying missing items, packing, items, etc.

After the team had planned what they needed to do, you can again add time restraints such only 1 week to plan, and even only 1 day.

Doing this can education again the MVP and how to adjust and move the map around to suggest the best plan.

 

Describe an existing product

A good exercise to describe a common well known product, or even if a competitors product. This exercise can be used to take the focus from games and activies to a more development and industry focused task and will later help with your projects.

The last time our team covered this we had just seen a recent update to Spotify so we outlined and described the product, desktop, browser and mobile.

We explored the application and spent some time designing the task out, splitting it into sections and then created the foundation or backbone of the application.

 

When you have created the backbone product you can then start adding extra features in sprints, or even removing tasks and features to create an application lite, in this case it was “Spotfiy lite” or a media player.

We ended up designing Winamp!

 

We then ended up designing a fictional application about movies called “Movie Buddy” which we now use as a demonstration FeatureMap still today.

The Moviebuddy Current Version

 

 

User Story Mapping Exercises

Using games and exercises to teach any product or methodology will be met with variation. Be aware of your audience, what will work and tailor your tutorials to fit them.

Some important tips for running these games.

  • Keep the time taken per exercise to under 30 minutes
    • Split each task of a game into 5 minute periods.
  • User FeatureMap or good old fashioned sticky notes and markers.
    • Use walls, floors or tables.
    • You can always do a final lesson of converting sticky notes to digital
  • Discourage a “leader” who may make all choices, allow all particpants to take part.
  • Try to aim for 30 tasks.
  • If you are teaching, do the tasks beforehand so you are able to help with prior experience on the subject matter.

 

User Story Mapping is innately simple with a huge range of depth that can be demonstrated in deep and powerful maps. If you need more assistance or ideas, check out how to help your team understand.

 

Good Luck!

Who, What, Why? – User Story Mapping

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:

  1. Who for?
  2. Why?
  3. What?

Critical thinking can be applied with great b0ons to any endevour and User Story Mapping is no different.

Who for?

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.

What?

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?

Why?

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

The StoryMap of Alex’s Morning with the Goals, Then Epics, then Cards.

 

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?

Multi-uses of User Story Mapping

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.

Software Development

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.

Movie Buddy first MVP

 

Product Lessons

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.

 

Customer Feedback

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.

Below I have defined a map in FeatureMap to give you an example of a marketing process. Click the image to see the Map on FeatureMap.co:

A Marketing and Email example for a fictional product.

 

Christmas Lists

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!

Check out our Christmas Demo Map below:

Christmas Gifts Mapping – A fun way to use FeatureMap

Do you use User story mapping for any other purpose?

If you wish to try out FeatureMap.co it is free to use, and has a trial period upon signup of the premium features!

Customer Facing Story Mapping

A user story map is a method for visually covering a story, to help discussions, share understanding and can even be shared with customers.

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:

The Moviebuddy Current Version

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.

Make your map public

 

Once public you’ll be able to share the URL and add this to your emails, webpage or direct as links.

To see an example demo map check here: https://www.featuremap.co/mp/FviDEf/moviebuddy

Due Dates, Estimations, Custom Fields

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.

Card view with further details about priority, deadlines and custom fields

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:

 

Aggregation.

 

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.

JIRA Integration

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.

You can get started with FeatureMap, and if you need more help or ideas, check out our 5 reasons to use User Story Mapping or a specific idea such as Feature Definition.