What is a User Journey?

From a website point of view, when a user comes to your website, they are usually there to do something – find information, make a purchase, make a comment. A user journey is what this person undertakes from the moment they arrive at your site to when they leave. Every individual step they take in their entire journey through your website is noted and forms what we call a user journey. The diagram below shows how a user journey can be represented.

So how do I know the steps my user is taking?
Quite often, you don’t! You can track overall user actions and behaviours on your website through the use of analytics software such as google analytics, but it is nigh impossible to pin point an actual individual user journey with this software. In order to create a user journey, you’ll need some scenarios and personae.

What is personae?
Personae is plural of persona. You will need several personas (upto 7) in order to ensure that each type of user visiting your website is covered. Essentially you need to create a persona that represents your archetype (typical) user. As there are likely to be quite a few of these, each will require a persona. For each persona you create, establish a scenario which will then decide on the user journey.

An example
Assuming I have a website that sells business stationary and leather goods for the office. My persona is:-

Joe, a 45 year old businessman. Joe falls in the “middle income” group, has a wife and two kids and is a travelling salesman. He uses the internet often, both at home and on his mobile device and netbook/iPad. He’s a regular user of my website and spends on average £30 per visit.

My scenario is:-
Joe is travelling by air to his next appointment, which is the following day. As he has been travelling for some time now, he has luggage which he needs to check-in. This he does, but unfortunately, when he gets to his destination the luggage has been lost in transit. He gets to his hotel after the stores have closed and is in urgent need of some clothes and a briefcase for his mid-morning sales presentation on the following day. As soon as he checks in to the hotel, he gets on the internet and goes to www.mywebsite.com to find a briefcase that can be delivered in the morning.

My user journey would therefore be something like this, albeit not in a diagram format:-

Home Page -> Products ->Office Leather Goods -> Briefcases -> Product detail page -> Shopping bag -> Account Log in -> Checkout -> Delivery address change -> Checkout -> Payment -> Confirmation

Of course, Joe may well get diverted and do other things on the website, but here the user journey encapsulates all that Joe needed to achieve. This is why you need a scenario for your user journeys as well, as this is where you establish the goal/motivation for that user.

Where User Experience and Information Architecture combine

In the digital world, and in a number of digital agencies today, the term
Information Architecture is being replaced with that of User Experience
consultant or expert. Despite the change in title, the work required to be done is
primarily the same but with one key difference – that being that the site/intranet
/application etc. being developed is designed from the users point of view i.e.
how we expect the user to interact with the product. In traditional IT software
development, the term Information Architect is still commonly used whereas in
digital agencies, and those focusing on the web, User Experience is now much
more common.

However, even a piece of software should be developed with the user in mind.
In fact, I believe this should be the case with any “product” – even a poorly
designed parking meter can have a big impact on a user and their impression of
the company/brand.

In the early days of the internet, it seemed that every company that existed
wanted to have an online presence irrelevant of what their customers/users
wanted. As such, many organisations put up “brochureware” sites that did
nothing more than act as a marketing tool. As the internet has evolved, and
usage increased, customers are demanding that more be made available online –
and companies are responding.

This is where the user experience and architecture of your offering comes into
play. No longer are we pushing static content out to our customers – we are
inviting them to come and interact with us, in an online environment. Come and
do your shopping, come and play games, come and do your banking. By inviting
customers to come to our sites, we’re asking them not only to engage with our
brand but also to experience the brand, and therefore as a business, we need to
ensure this experience meets their expectations and needs – and indeed, that it
meets the expectations of internal stakeholders as a result.

Defining and understanding your customers/users needs, is key in information
architecture. You have to know what information your user needs and when.
This helps in defining the structure (architecture) of the information that you’re
providing to the user. You also need to know the “how” though i.e. how are you
going to provide the information in the best way possible, and this is where you
have to be more focused on the “user experience”.

I suspect that the need to have an informational structure and also present this
to the user in an engaging and usable way, is what has resulted in the terms
Information Architecture and User Experience being used interchangeably,
although they are actually slightly separate functions. Whether you are an IA
or UX by title though, I think its fair to say that you actually need to do both
functions to be sure the product or solution meets the end users needs… but I’d
be interested to hear what others have to say…