A string winding across the table past a box, a key, a cup and a parcel, caught in a tight knot near the end of the route.

11of 13

Customer journey mapping for early product teams

Customer research becomes more useful when you can see how experiences connect across the journey. Map what happens before, during and after use, then focus on the friction that matters most.

Build & Validate
Customer discoveryEvidence-led building

By the EWOR Team3 min read

Imagine you’re improving an equipment-rental portal. Your team focuses on making it easier to find and book equipment. But customers struggle just as much with collecting their rental, figuring out the return requirements or disputing the final invoice.

If you only study the booking experience, you could spend weeks improving the wrong part of the journey.

Before deciding which problem to solve, look at the experience as a whole. What happens before customers use your product, while they use it and after they leave? The answers may change what your team chooses to build.

Define the customer journey

Choose a specific customer and task, then trace the steps they take to get the job done. Start before the point where your product enters the picture and continue beyond the outcome your team considers the finish line.

Ask customers to walk you through what they actually did, rather than relying on how you imagine the process works. You may uncover forgotten steps, workarounds or frustrations that never appear in your product analytics.

Remember that not everyone follows the same path. A first-time rental may look very different from a repeat booking. Keep distinct experiences separate rather than creating one blended journey that reflects nobody’s reality.

Map the evidence to the steps

Lay out the journey stages and connect them to what customers reported or what your research observed. Short quotes and specific examples can help the team understand what happened at each step.

Keep observations separate from interpretations. A customer saying they felt anxious is evidence of their experience; concluding that a delay caused that anxiety is your interpretation. And if a stage has no supporting evidence, treat it as a gap in your research, not proof that everything works smoothly.

Be thoughtful about what you share. Use participant codes and restricted references rather than putting names, identifying photographs or sensitive records on a board everyone can access. The format matters less than having a clear view of the evidence that the team can review together.

Look for patterns without losing the details

Once the journey takes shape, look for moments where different customers describe similar difficulties. Ask who is affected, what the problem costs them and when it occurs.

But don't assume the most frequently mentioned issue is automatically the most important. Several notes might come from one long interview, and a small research sample cannot tell you how widespread a problem is. A rare issue with serious consequences may deserve more attention than a common but minor complaint.

Pay attention to differences, too. Customers who have different needs, workarounds or expectations may be revealing something important about the experience, not simply providing conflicting feedback.

Choose the next focal question

Use the journey to compare potential problems. Which has the greatest consequences for customers? What workarounds do they already use? How strong is the evidence, and what do you still need to learn?

The map won't tell you the answer on its own. It helps you challenge your assumptions, identify missing perspectives and decide where further research could make the biggest difference. Only then should you turn the evidence into a focused problem statement.

No comments yet.

Be the first to comment on this signal.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter

Continue learning

Related modules