· product-managers Editorial · Career · 6 min read
Pm Customer Journey Mapping Interview Exercise
How to run a customer journey mapping exercise in a PM interview, including the framework, a stage-by-stage template, and grading criteria.
PM Customer Journey Mapping Interview Exercise
Customer journey mapping exercises have become a standard component of product sense interviews in 2026, particularly at companies with complex, multi-touchpoint products such as fintech, healthcare tech, and B2B SaaS platforms. Unlike a pure product design question, a journey mapping exercise tests whether you can think end-to-end about a user’s experience across time, not just about a single feature or screen. This guide covers the exact framework interviewers expect, a worked example, and the specific things that separate a strong answer from a mediocre one.
Why This Exercise Exists
Companies use journey mapping exercises because a huge share of product failures in production come from ignoring what happens before and after the “happy path” screen the PM was focused on. A checkout flow can be beautifully designed and still fail because the user was frustrated three steps earlier, or because the post-purchase confirmation email never arrived. Interviewers use this exercise to see whether a candidate defaults to thinking in isolated features or in full user arcs.
The Standard Framework: Five Stages
Most journey mapping exercises, whether for a consumer app or a B2B tool, map cleanly onto five stages. Memorize this structure so you can apply it to any prompt without needing to invent a framework live under time pressure.
- Awareness: How does the user first learn the product/feature exists?
- Consideration/Onboarding: What happens between first exposure and first meaningful use?
- Core Usage: What is the repeated, core-value-delivering loop?
- Friction/Support: Where does the user get stuck, need help, or hit an edge case?
- Retention/Advocacy: What brings the user back, and what makes them recommend it to others?
For each stage, a strong answer identifies: the user’s goal, the user’s emotional state, the touchpoints involved (app screen, email, support channel, physical interaction), and at least one pain point with a proposed fix.
Worked Example: Mapping the Journey for a Telehealth App’s First-Time Patient
Prompt: “Map the journey for a first-time patient booking a telehealth appointment.”
| Stage | User Goal | Emotional State | Key Touchpoints | Pain Point | Fix |
|---|---|---|---|---|---|
| Awareness | Find a way to see a doctor without an in-person visit | Anxious, time-pressured | Search ad, employer benefits page, referral | Unclear if their symptom qualifies for telehealth | Add a symptom-checker gate before booking |
| Onboarding | Create account, verify insurance, pick a time | Impatient, wary of forms | Signup flow, insurance upload, calendar picker | Insurance verification takes 24+ hours, blocking same-day booking | Real-time insurance eligibility API check |
| Core Usage | Have the actual video visit and get a diagnosis/prescription | Vulnerable, hoping to be taken seriously | Video call, chat, e-prescription | Video call drops or has audio issues | Auto-fallback to phone call on connection failure |
| Friction/Support | Get a prescription filled or ask a follow-up question | Frustrated if something goes wrong post-visit | Pharmacy integration, support chat | No clear channel to ask a quick follow-up without booking a new paid visit | Add a free 48-hour post-visit message thread with the same doctor |
| Retention/Advocacy | Come back for future needs, recommend to family | Relieved, trusting (if it went well) | Push notification, review prompt, referral link | No reason to think of the app for non-urgent future needs | Proactive reminder for annual checkups tied to insurance renewal |
Notice that half the value in this exercise comes from stages 2 and 4, the two stages most candidates rush past to get to the “cool feature idea” stage. Interviewers specifically watch for whether you slow down on onboarding and support/friction rather than jumping straight to a flashy core-usage feature pitch.
Comparison: Journey Mapping vs. Related Product Exercises
| Exercise Type | What It Tests | Typical Output Format | Time Given |
|---|---|---|---|
| Customer journey mapping | End-to-end thinking, empathy, prioritization across a full lifecycle | Table or stage-by-stage narrative | 15-20 min |
| Product design (“design an X”) | Single-feature ideation and prioritization | Sketch + feature list | 20-30 min |
| Root cause analysis | Diagnostic reasoning on a metric drop | Hypothesis tree | 15-20 min |
| Market sizing | Quantitative estimation and structure | Equation + number | 8-10 min |
| Strategy/prioritization | Trade-off reasoning across competing initiatives | Prioritized list + rationale | 20-25 min |
How Interviewers Grade This Exercise
- Completeness across stages (25%): Did you cover all five stages, or did you spend 80% of the time on core usage alone?
- Specificity of pain points (30%): Generic pain points (“onboarding could be smoother”) score low. Specific, plausible pain points tied to a named touchpoint score high.
- Prioritization (25%): When asked “if you could only fix one thing, what would it be,” can you defend a choice using impact and frequency reasoning rather than picking your favorite idea?
- User empathy (20%): Do you narrate the user’s emotional state accurately at each stage, or does your answer read as purely mechanical?
Common Mistakes Candidates Make
- Starting at core usage instead of awareness: Skipping straight to “here’s the cool feature I’d build” without establishing how the user got there or what happens after.
- Treating every stage as equally weighted: Not every stage deserves equal time; the strongest candidates spend more time where the interviewer’s prompt hints the pain actually lives.
- Proposing fixes with no prioritization: Listing five pain points and five fixes with no ranking signals you haven’t internalized that PMs must choose, not just generate ideas.
- Ignoring non-digital touchpoints: For journeys involving physical products, in-person visits, or phone support, forgetting these touchpoints exist is a common and easily avoidable miss.
How to Practice This Exercise
Pick five different product categories (a bank app, a food delivery app, a B2B expense tool, a fitness wearable, a telehealth app) and run the five-stage framework against each one, timed at 15 minutes, talking out loud. Then force yourself to name exactly one fix you’d prioritize first and defend why, using an impact-times-frequency estimate rather than intuition alone.
For a structured walkthrough of journey mapping alongside other core product sense exercises, with graded example answers and interviewer commentary, The 100x Product Manager Interview Playbook (available on Amazon) includes multiple full journey-mapping case studies across consumer and B2B products.
FAQ
Q: Is this the same as a “day in the life” exercise? A: They’re closely related. A “day in the life” prompt usually asks you to narrate a single persona’s day, while a journey mapping exercise asks you to map a specific product interaction across its full lifecycle stages. The five-stage framework works for both.
Q: Should I draw the journey map, or is a verbal/written table enough? A: In a live interview, a simple table (on a whiteboard, shared doc, or even narrated verbally) is sufficient. Interviewers are grading your reasoning and prioritization, not your diagramming skill.
Q: What if the interviewer’s prompt is vague about which user segment to map? A: Ask a clarifying question before starting: which persona (new vs. returning user), and which specific goal within the product. Mapping the wrong user’s journey in detail wastes most of your allotted time.