A user journey maps the steps someone takes to accomplish a goal. Not the ideal path the designer imagined, but the actual sequence of actions, thoughts, and emotions along the way. From first awareness to final outcome.

Journeys are usually visualized as a timeline or flowchart. Each step gets a row. Below the steps, researchers plot what the user is doing, thinking, and feeling. The emotional curve matters as much as the functional one. A checkout flow might be technically smooth but emotionally frustrating if the user cannot tell whether their payment went through.

What a journey map captures

• Touchpoints where the user interacts with the product
• Pain points where friction or confusion occurs
• Moments of delight or relief
• Channels: web, mobile, phone, in-person
• Time gaps between steps

Journey maps work best when based on real research, not assumptions. Interview users. Watch them use the product. Ask what they were thinking at each step. The map that results often surprises the team that built the product. People use things in ways designers never intended. That gap between intention and reality is exactly what a user journey exposes.