At the start of any new project here at Box UK it’s the job of our User Experience consultants and Business Analysts to help everybody involved in the project reach a shared understanding as quickly as possible. There are naturally numerous ways to capture and document the requirements for a new website or mobile application, but one technique we often use is ‘user journey mapping’.
Personally I like to use them in conjunction with user stories (a statement that captures the ‘who’, ‘what’ and ‘why’ of a particular feature), or to break-out a particular element of a sitemap when discussing requirements with clients.
For instance, on a recent project with a client who relies on membership for their revenue stream, one user story for their new site was:
“As a non-member, I want to apply online for membership so that I don’t have to complete a paper-based application”
Taken at face value this is doesn’t seem too complex a requirement, but thanks to the user research and business analysis I’d carried out with users, client stakeholders and other 3rd parties, I knew that this was just the tip of the requirement. I also needed to take into account:
Suffice to say, the user story is actually pretty epic and has many, many sub-stories to consider. Now, I could have broken this user story down into further stories, but for the sake of getting my own head around the requirements, and reaching a shared understanding with the client quicker, I decided to turn this user story into a user journey map:
As can be seen in the example above, the user journey map helps to identify a whole host of different things that we as designers and developers need to be aware of, as well as the client. This includes:
They are a very flexible tool to use, as they can also be augmented with likely timescales (if a journey is likely to take weeks or even months, or if the journey is time-critical) and with interactions within the physical world (ie. accessing content across multiple devices). When printed out and stuck up on the walls in a meeting, they can be scribbled on and plastered in post-it notes, and serve as a great discussion point for our clients and internal team.
Naturally, user journey mapping works best if it’s based on actual user research, but as with the example above, sometime the user interaction is only half the story. There are often a whole host of business rules, 3rd party systems and non-customer users that are vital to the completion of the end-user’s journey. As such, mapping these in an at-a-glance picture can be a vital exercise.
For all these reasons, I find user journey mapping a very powerful, easy to understand, and ultimately enjoyable way to capture and share ideas with clients.
To find out more about our UX process at Box UK, visit the User Experience & Design section of our site.