Organizational Memory
User journey card, MethodKit for Memory & Reminiscence
Card 63 of 66 · MethodKit for Memory & Reminiscence
  • ThemeProduct & Offering
  • CardCard 63 of 66
  • Questions5 to explore
Product & Offering

User journey

How users find & experience what you offer

How users find you, try you, and decide to stay (or leave) is some of the most important knowledge in the organization, and most of it goes undocumented.

The user journey is not the marketing funnel and it is not the product spec. It is the actual path a real person takes from not knowing you exist to becoming a regular user or customer, including all the moments of confusion, delay, and delight along the way.

Most organizations have a version of this written down somewhere: an onboarding flow diagram, a customer lifecycle model, a set of personas. What is usually missing is the qualitative layer: the friction points users hit that the team does not expect, the workarounds people invent, the moments where people almost left but did not.

Capturing the user journey well means combining what the data shows with what users actually say, and keeping both up to date as the product or service changes. It is a living document, not a one-time research output.

What to capture

For this part of the company brain, what is worth writing down and keeping current. The goal is not a complete archive but a living record that new people can read and returning people can trust.

Journey map or flow

Document the stages a user goes through: how they discover the offering, how they try it, how they become regular users or customers, and what a churned user's path typically looks like.

Key friction points

Capture where users most often get stuck, confused, or drop off, and what is currently known about why. Include both quantitative signals (drop-off rates) and qualitative ones (what users say).

Insights & research findings

Keep a running record of what you have learned from user research, usability tests, and support conversations. Note when each insight was gathered and whether it is still believed to be current.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

  1. Where does a new team member go to understand how a user actually experiences the product or service from first touch to regular use?

  2. What are the moments in the current journey where users most often fail to complete what they are trying to do?

  3. How does your team currently capture and share what they learn from talking to users?

  4. When the product or service changes significantly, is the journey map or flow updated to reflect that?

  5. What do you know about why users leave, and how was that knowledge gathered?

Things to notice

  • A journey map built once and never updated quickly becomes a historical artifact. If the product has changed significantly since the map was made, the map describes a journey that no longer exists.
  • Quantitative data (conversion rates, time to complete) and qualitative data (user interviews, support logs) each tell half the story. Organizations that rely only on one tend to misread what is actually happening.
  • User journey knowledge is often siloed: product knows one part, marketing knows another, support knows a third. Without a shared map, no one has a complete picture.