Skip to content

Walk The User's Journey ​

Every screen is designed and checked as the user's journey through it: who the user is at that point, what the user is experiencing, what the immediate goals are, and then each question and each click, step by step. What the screen shows supports the user's decisions: it answers the next question, guiding the user's thoughts without steering them.

Why ​

Every screen answers the questions the user has.

How To Apply ​

  • Write the journey before the screen: who, experiencing what, wanting what, then the user's thoughts in order.
  • Walk it for both ways of thinking: the explorer asking what can I do here, and the follower asking what does the product want me to do. A screen serves both: it shows what is possible, and it sets a goal, an empty cart beside the products, say.
  • At each step ask what the user wonders and whether the screen answers it. A word or number that answers nothing the user asks goes.
  • A number needs a reference: for a value with steps, such as a plan or a level, show where the user stands, where it goes and the difference, and what it comes to.
  • No spoilers: copy never names an event, a reward or a step the user has not reached yet, though the docs and tickets already hold it.
  • What lies ahead can still show, locked or disabled, such as a step locked until the one before it is done, and it is told in words the user already knows.
  • Foreshadowing is the exception: a hint placed on purpose, vague enough to pass now and plain on a second visit. It is designed in the product's narrative, never leaked from a ticket.
  • Walk the journey in the running app before calling the change done.

Examples ​

  • A price of 0 means nothing on its own. "Free" says this is a purchase, that things here normally cost something and that this one costs nothing, and naming what it includes says where to look next.
  • A screen can be fully consistent with the code and still answer nothing the user asks.