Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Digital Marketing › Customer Journey

Walking the Customer Journey Yourself

How to experience your own customer journey as a customer would: search, compare, enquire, buy, receive and complain, then record every moment of friction.
Tutorialbeginner10 min readUpdated

Why marketers should walk the journey

A business looks different from the inside. Its marketers know the brand name, so they never search the category; they know which page has the price, so they never hunt for it; they have the direct line, so they never wait in a queue. Every shortcut hides friction a customer meets. Walking the journey removes the shortcuts on purpose and records what happens.

The walk is good at finding practical failures that reports average away: a form that does not submit on one phone, a confirmation email with no address, an ad that promises one thing and a page that says another, a callback that never comes, a cancellation route that cannot be found. Each of these touches only some customers, so it rarely shows up clearly in analytics, and customers who hit it often leave without saying why.

What the walk cannot do is tell you how common a problem is or how customers feel about it. One marketer is not a segment, and someone who knows the business cannot fully forget what they know. The Nielsen Norman Group's introduction to journey mapping, cited in the sources, describes a journey map as a visualisation of the process a person goes through to accomplish a goal, and the journey mapping tutorial builds that map from interviews, analytics and other evidence about real customers. The walk-through is one more source for that map, alongside the methods in the conversion research methods guide, not a substitute for them. Where the question is whether a newcomer can complete the website part of the journey, the tutorial on running a usability test on a conversion journey watches people who do not know the business attempt it. To hear how real customers experience a journey that stretches over days or weeks, the tutorial on running a diary study has them record each moment as it happens.

MethodWhat it showsWhat it cannot show
Walking the journeyFriction one person meets across every channel, end to end, with timingsHow many customers meet it, and how they feel
Customer interviewsWhy customers act, in their words, including what happens off the websiteThe exact step where a form or email failed
Analytics and funnelsWhere many people drop, on the website and appPhone calls, emails, stores and anything untracked
Support and complaint recordsWhat goes wrong after purchase, at volumeProblems people abandon rather than report

Before you start

  • Choose one segment and one scenario. "A new customer" is too vague. "A parent booking a first eye test for a child, on a phone, on a weekday evening" is a scenario that can be walked. Use the segments from the segmentation guide and the stages from the stages guide.
  • Set aside the time. A complete walk, including waiting for responses and deliveries, takes days of elapsed time and several hours of attention. Block the hours and keep the log open throughout.
  • Prepare an outsider's kit. A device you do not use for work, a browser with no saved logins, a fresh email address and, where it matters, a phone number the business does not recognise.
  • Tell the people who need to know, and no one else. A manager should know the walk is happening, so that a real complaint from you is not escalated as a crisis, but front-line staff should not be warned, or the walk records the experience they give when they know they are watched.
  • Prepare the log. A simple table with a row per step: the time, the channel, what you did, what happened, how long it took, what confused you and what the page or person promised.

The steps

  1. Pick a segment and a realistic scenario

    Write the scenario in a sentence or two: who the customer is, what has prompted them, what they are trying to achieve, what device and time of day, and what would count as success. Base it on what you know about real customers, not on the journey the business would prefer. Choose a scenario that ends somewhere real, such as a booking, an order or an enquiry answered, so that the walk has a finish line.

  2. Set up as a new customer with no insider shortcuts

    Use the outsider's kit. Log out of everything, clear the browser or use a private window, and use the fresh email address. Do not type the company's web address or use its internal phone numbers. If you already have an account, create a new one as a customer would. The aim is to meet every screen, form and message a stranger meets, including the cookie banner, the account sign-up and the first welcome email.

  3. Start where real customers start

    Begin with the search a customer would type, the social post they would see, or the recommendation they would be given, not with the homepage. Search the category and the problem, not the brand name, and note where the business appears and where rivals or comparison sites appear instead. Click through as a customer would, and record which Landing Page you reach and whether it answers the question the search asked. The touchpoints guide explains how to map these first encounters by stage.

  4. Walk two rivals' journeys alongside

    Repeat the same scenario with two competitors that customers actually compare you with, at the same time of day and on the same device. As general practice, behave as an ordinary prospect would: read their pages, make a normal enquiry or booking, and cancel promptly anything you will not keep, without misrepresenting yourself or tying up their staff beyond a normal enquiry. The comparison turns your own experience into a judgement, because a wait that felt acceptable may look slow beside a rival that answered at once. The competitor analysis guide covers the wider study of rivals from the outside.

  5. Enquire or buy through each channel

    Use every channel the scenario allows: the web form, the phone, live chat, messaging, email and, where it applies, the store. Time each response from the moment you make contact to the first reply from a person, and record whether the reply answers what you asked. Lead Response Time often differs sharply between channels in the same business. If the scenario involves an online purchase, go through checkout fully; if you are tempted to give up part-way, note exactly where and why, because that is where the business's Cart Abandonment Rate is being made. The lead response time test shows how to find out whether faster follow-up would change results.

  6. Receive, open and use what arrives

    Record everything that follows the purchase or enquiry: confirmation pages, confirmation emails and texts, reminders, delivery updates, the product or service itself and the first follow-up. Check each message on the device you used for the walk. Note whether each one tells you what you need at that point, such as the address, the time, what to bring, how to change the booking and who to contact, and whether the tone matches what came before.

  7. Try to change, cancel and complain

    Most walks stop at the purchase, and that is where much of the friction lives. Try to move the booking, change the order, cancel, return something and make a complaint through the routes a customer would find. Record how long each takes to find and to complete, and whether a person or a help page answered. The support channels and self-service guide explains how support channels should match the questions customers ask, which is the standard to judge them by.

  8. Record time, effort and confusion at every step

    Fill the log as you go, not from memory afterwards. For each step note the time taken, the effort, anything that confused you, and every gap between what was promised and what appeared: the ad offering one price and the page another, the email promising a callback that never came. That gap is a failure of Message Match, and the message match guide shows how to check promise against page systematically. Record slow or broken pages on a phone too; the speed and mobile guide explains why they lose visitors before the page has made its case.

  9. Sort the friction by cause and owner

    When the walk is complete, list every problem and ask why it happened until you reach a cause someone can change. The five whys framework is built for this: a confirmation email with no address is a template nobody owns, a slow callback is a rota with no cover after hours. Group the problems by cause, because one cause often produces several problems, and give each cause an owner, which will often sit outside marketing, in operations, sales, service or the website team. Problems that make the customer repeat details, switch channels or chase an update are effort the business has moved onto them, and the guide to reducing customer effort sets out how to find and remove each kind.

  10. Hand the findings to the map and the test backlog

    Add the findings to the journey map as evidence, marked as coming from a walk-through rather than from customers, and check them against analytics and support records: if many real customers drop at the step where you struggled, the problem is likely common. Straight fixes, such as a broken form or a missing address, go to their owners with a date. Changes whose effect is uncertain, such as a new booking flow, go into the test backlog, where the prioritising tests guide helps order them against everything else. Walk the journey again once the fixes are live. For the website steps on their own, an expert review of the conversion journey checks each page against criteria from the conversion guides and rates every issue for severity and confidence before research confirms it.

An optician walks its own journey (illustrative)

Illustrative example — not a real result

Clearbramble Opticians books an eye test as a stranger

Clearbramble Opticians is an invented independent optician. Its marketing manager walks the scenario "an adult who has never had an eye test, booking on a phone in the evening after searching for eye tests nearby". She uses her own phone in a private window and a new email address, and makes the same booking at two rival opticians, cancelling each the next morning.

StepClearbrambleRival ARival B
Found in local search resultsThird listing, no photosFirst listing, 40 photosSecond listing
Booking form on a phoneDate picker fails; form will not submitBooked in 3 minutesBooked in 5 minutes
Fallback routeContact form asking for a callbackNot neededNot needed
ConfirmationEmail after 2 hours, no address or parking informationText and email within a minute, with mapEmail within a minute, no map
First human responseCallback after 3 daysNot neededText reminder the day before
CancellingPhone only, during opening hoursLink in the textLink in the email

The five whys trace the failed form to a booking plugin last updated two years ago that nobody owns, the missing address to an email template copied from the head office of a former partner, and the three-day wait to callback requests landing in an inbox checked only on Fridays. The owner fixes the form within a week and the template the same day, and moves callback requests to the reception rota. Analytics then show that 38% of mobile visitors who opened the booking page in the previous quarter left without booking, against 19% on desktop, which suggests the failed form had been costing bookings for months. A test of a shorter booking form goes into the backlog, and she walks the journey again a month later.

Common mistakes

  • Walking with insider knowledge. Typing the brand name, using a work login or calling the direct line hides the friction customers meet.
  • Stopping at the purchase. Confirmations, changes, cancellations and complaints are where many journeys fail.
  • Walking only your own journey. Without rivals beside it, a slow response or a clumsy form can feel normal.
  • Writing the log from memory. Timings and confusion fade within hours; record each step as it happens.
  • Treating one walk as research. One person on one day finds problems; only evidence about real customers shows how common they are.
  • Blaming people instead of causes. The five whys stop at a process or rule someone can change, not at a member of staff.
  • Warning the team in advance. A walk that front-line staff know about records the service they give when they know they are watched.
  • Finding problems and fixing nothing. Every finding needs an owner and a date, or a place in the test backlog.

Frequently asked questions

How is walking the journey different from journey mapping?

A journey map is built from evidence about many customers: interviews, analytics, search data and support records. Walking the journey is one person's first-hand experience of the same path, done deliberately as a new customer. The walk finds practical friction quickly, such as a broken form or a confirmation with no address, but it reflects one person on one day. Use it to add evidence to the map and to check fixes, not to replace research with real customers.

Is it acceptable to walk a competitor's journey?

Looking at what any customer can see is ordinary competitor research. As general practice, keep it to what a normal prospective customer would do: read the site, make a normal enquiry, compare the follow-up. Do not book appointments you will not keep without cancelling promptly, do not tie up staff with long calls you have no intention of following through, and do not misrepresent yourself to obtain anything a customer would not be given.

How often should we walk our own journey?

Whenever something important changes, such as a new website, a new booking system, a new channel or a new offer, and on a regular cycle in between, because journeys drift as platforms, staff and suppliers change. Rotate who does it: a person who has never seen the back end of the business notices things the marketing team has stopped seeing.

Terms used on this page

Frameworks

Where this page is used

Sources

  1. Journey Mapping 101 — Nielsen Norman Group

Related