Foldwren

Mapping user journeys before you design a screen

How to write out the steps a customer takes from their point of view, spot the dead ends, and use a worked example to plan screens that fit.

Before anyone draws a button, write down what the customer is trying to do, one step at a time, in their words. Designers call this a user journey or a user flow. It takes an hour, costs nothing, and prevents the most common kind of rework: discovering halfway through the build that a step is missing.

What is a user journey map?

It is a plain list of steps a person goes through to get something done, written from their side of the counter. Not "system sends confirmation email" but "I get an email telling me it is booked".

A flow is the more detailed version, showing the choices and branches along the way.

Sticky notes on a wall or a numbered list in a document is plenty.

How do you write one?

Start with a single person and a single goal. Not "customers use the app" but "a first time customer books a dog wash for Saturday".

Then follow four rules.

  1. Begin before your product. The first step is whatever prompted the person. Their dog rolled in something. They searched on their phone.
  2. Write each step as "I" statements. "I pick a service." "I am not sure which size my dog counts as." Doubts and questions are steps too.
  3. Keep going past the finish line. The task does not end at "booking confirmed". It ends when the dog is clean and the customer is home. Reminders, directions, payment and the follow up are all part of it.
  4. Mark every decision point. Anywhere the person could go two ways, note both.

A worked example

Say you run a dog grooming salon and want to add online booking. Here is a first pass at the map for a new customer.

  1. My dog needs a groom before a family visit next weekend.
  2. I search for groomers near me and tap one that looks decent.
  3. I want to know if they do my breed and roughly what it costs.
  4. I look for a way to book.
  5. I choose a service. I am unsure whether I need a "full groom" or a "tidy up".
  6. I am asked my dog's size. I do not know what counts as medium.
  7. I pick a day and see the times available.
  8. Saturday is full. I check Friday.
  9. I enter my details and my dog's details.
  10. I am asked to pay a deposit.
  11. I get a confirmation.
  12. The day before, I wonder what time it was and where to park.
  13. I drop the dog off.
  14. I wait to hear when to pick her up.
  15. I pay the balance and go home.

Fifteen steps, and the business owner probably had four in mind: choose service, choose time, enter details, confirm.

Spotting the dead ends

Now read back through the list and ask at each step: what does the person need here, and what happens if it goes wrong?

  • Step 3: If prices and breeds are not easy to find, they leave before booking exists for them. That is a content problem, not a booking problem.
  • Step 5: The service names assume knowledge. Each needs a one line description of what is included.
  • Step 6: "Medium" means nothing. Give weight ranges or example breeds.
  • Step 8: A full Saturday is a dead end unless the screen offers the next available times, or a waitlist.
  • Step 10: A deposit request with no explanation feels abrupt. Say why, and say what happens if they cancel.
  • Step 12: They need a reminder with the time, address and parking note. That is a message to design, not a screen.

None of this required a single mockup. Yet the list of things to design has grown well past four screens: service descriptions, a size guide, a "no times available" state, deposit wording and a reminder message.

What about the other paths?

The first map is the "happy path", where everything goes to plan. Once you have it, sketch the main variations.

  • A returning customer who wants the same service as last time. Can they skip most of the form?
  • Someone who needs to reschedule. How do they find their booking? Is there a cut off?
  • Someone with two dogs. Does the flow cope, or do they have to book twice?

You do not need to design every one of these for launch. You do need to decide, on purpose, which ones you will handle and what the others will see in the meantime. "Call us to book for more than one dog" is a perfectly good answer for a first version. An error message is not.

Turn the map into a screen list

With the steps mapped, the screens almost write themselves. Go through the steps and group them.

  • Steps that happen together become one screen.
  • Each question the person has becomes a piece of content on that screen.
  • Each dead end becomes a state you need to design: empty, full, error, offline.
  • Each step that happens away from the app becomes a message: email, text or notification.

Take that list to your designer, or use it yourself if you are sketching the first version. The conversation shifts from "what should it look like?" to "does this cover everything the customer goes through?", and that is the better question to settle first.

Your order