Principles of Product Management: Empathy Maps, User Journey Maps, Service Blueprints

Empathy Maps, User Journey Maps, Service Blueprints

Empathy Maps, User Journey Maps, Service Blueprints – Study Guide

What This Is

Empathy Maps, User Journey Maps, and Service Blueprints are user-centric tools that help PMs deeply understand user behaviors, pain points, and touchpoints to design better products. They matter because products fail when teams assume they know users’ needs—these tools force structured empathy and reveal hidden friction. Example: A fintech startup used a Service Blueprint to uncover that users abandoned loan applications not because of UI complexity, but because they were confused by third-party credit checks. Fixing this (via clearer messaging) increased completion rates by 30%.

Key Terms & Frameworks

• Empathy Map (4 Quadrants):
  Says (user quotes), Thinks (internal thoughts), Does (actions), Feels (emotions). Used to synthesize user research into a single, shareable artifact.

• User Journey Map (5 Components):

• Stages (e.g., Awareness → Consideration → Purchase → Retention)
• Actions (what the user does)
• Thoughts/Feelings (emotional highs/lows)
• Pain Points (friction or unmet needs)

• Opportunities (where to improve). Example: Airbnb’s journey map revealed hosts struggled with pricing—leading to their "Smart Pricing" feature.

• Service Blueprint (Layers):
  A journey map on steroids, adding:

• Frontstage (user-facing touchpoints, e.g., app UI)
• Backstage (internal processes, e.g., customer support)
• Support Processes (third-party dependencies, e.g., payment gateways)

• Physical Evidence (tangible artifacts, e.g., receipts, emails). Example: Uber’s blueprint showed riders cared less about car type and more about driver ETA visibility—leading to their real-time tracking feature.

• Jobs to Be Done (JTBD) + Journey Maps:
  Combine JTBD ("I need to hire a product to do X") with journey maps to focus on why users take actions, not just what they do. Example: Slack’s onboarding journey map revealed users didn’t care about "channels"—they just wanted to reduce email clutter.

• Touchpoint:
  Any interaction between user and product/service (e.g., push notification, checkout page, customer service call).

• Moment of Truth (MoT):
  Critical touchpoints where users form lasting impressions (e.g., first login, payment failure). Example: Amazon’s "1-Click Ordering" was designed to optimize the MoT of checkout.

• Emotional Curve:
  A line graph overlaying the journey map showing user sentiment (highs/lows) at each stage. Example: Duolingo’s emotional curve showed users felt frustrated during grammar lessons but proud after completing a streak—leading to more gamification.

• ICE Score (for Opportunities):
  Impact × Confidence × Ease – Prioritize opportunities from journey maps. Variables:

• Impact (1–10, how much it improves user experience)
• Confidence (1–10, evidence strength)

• Ease (1–10, implementation effort).

• Double Diamond (Design Process):

• Discover (empathy maps, research)
• Define (journey maps, pain points)
• Develop (ideate solutions)

• Deliver (service blueprints, prototypes). Used by Google Ventures for sprints.

• Kano Model + Journey Maps:
  Classify pain points/opportunities into:

• Basic Needs (must-haves, e.g., login security)
• Performance Needs (more = better, e.g., faster load times)
• Delighters (unexpected, e.g., Spotify’s "Discover Weekly").

Step-by-Step / Process Flow

1. Define Scope & User Segment
2. Pick one user persona (e.g., "Freelance Photographer" for a photo-editing app).
3. Define the specific journey (e.g., "Uploading and editing a photo for Instagram").

4. Why? Broad scopes (e.g., "all users") lead to generic maps.

5. Gather Data (Empathy Map Inputs)

6. Interviews: 5–7 users (ask: "Walk me through the last time you did X").
7. Analytics: Heatmaps, session recordings (e.g., Hotjar), or funnel drop-off data.
8. Support Tickets/Reviews: Mine for recurring complaints.

9. Pro Tip: Use open-ended questions (e.g., "What was going through your mind when you saw the error message?").

10. Create the Empathy Map

11. Fill the 4 quadrants with direct quotes (Says), inferred thoughts (Thinks), observed actions (Does), and emotions (Feels).

12. Example: For a food delivery app:

    
    
    • Says: "I wish I could track my driver in real time."
    • Thinks: "Is my food even coming? Maybe I should call."
    • Does: Refreshes app 5x, checks phone for texts.
    • Feels: Anxious → Frustrated.

13. Build the User Journey Map

14. Step 1: List stages (e.g., "Browse → Add to Cart → Checkout → Delivery").
15. Step 2: Add actions, thoughts/feelings, and pain points at each stage.
16. Step 3: Plot the emotional curve (e.g., excitement → frustration at checkout).
17. Step 4: Highlight Moments of Truth (e.g., payment failure).

18. Tool: Use Miro or FigJam for collaboration.

19. Expand to Service Blueprint (If Needed)

20. Add frontstage (e.g., app UI), backstage (e.g., order processing), and support processes (e.g., payment gateway).
21. Identify failure points (e.g., "Driver app crashes during high demand").

22. Example: A bank’s blueprint revealed that mortgage approval delays were caused by manual document checks—leading to an AI automation project.

23. Prioritize Opportunities

24. Use ICE Score or Kano Model to rank pain points.
25. Example: For a SaaS onboarding journey:
    • High ICE: "Users don’t understand the value prop in the first 30 seconds" (Impact: 9, Confidence: 8, Ease: 7).
    • Low ICE: "Users want dark mode" (Impact: 3, Confidence: 5, Ease: 8).

Common Mistakes

• Mistake: Assuming the journey is linear.

• Correction: Users loop, skip, or abandon stages. Example: E-commerce users often browse → abandon → return via email reminder. Map these loops!

• Mistake: Focusing only on digital touchpoints.

• Correction: Include offline/emotional touchpoints (e.g., "User feels embarrassed asking for help in-store"). Example: Starbucks’ journey map includes the barista’s greeting as a key touchpoint.

• Mistake: Creating maps in a silo (without stakeholders).

• Correction: Co-create with engineers, designers, and customer support. Why? They’ll spot backstage issues (e.g., "Our payment API fails 10% of the time").

• Mistake: Treating the map as a one-time artifact.

• Correction: Update maps quarterly (user behaviors change). Example: Post-COVID, DoorDash’s journey map added "contactless delivery" as a key stage.

• Mistake: Confusing "pain points" with "solutions."

• Correction: A pain point is "Users forget their password" (not "We need biometric login"). Why? The solution might be passwordless login or better recovery flows.

PM Interview / Practical Insights

1. Tricky Distinction: Empathy Map vs. Persona
2. Interviewer Trap: "Why not just use a persona?"

3. Answer: Personas describe who the user is; empathy maps describe how they think/feel. Personas = demographics + goals. Empathy maps = emotional context for a specific scenario.

4. Journey Map vs. Service Blueprint

5. Interviewer Trap: "When would you use a service blueprint instead of a journey map?"

6. Answer: Use a journey map to understand user experience; use a service blueprint to diagnose operational failures (e.g., "Why are support tickets taking 3 days to resolve?").

7. Prioritization Question

8. Interviewer Trap: "Your journey map shows 10 pain points. How do you prioritize?"

9. Answer: Use ICE Score + strategic alignment (e.g., "Does this align with our goal of reducing churn?"). Example: For a fitness app, "Users struggle to find workouts" (ICE: 8) might beat "Users want social features" (ICE: 5).

10. Stakeholder Pushback

11. Scenario: "Engineering says fixing the payment failure is too hard. How do you respond?"
12. Answer: Show the service blueprint to prove the failure cascades (e.g., "Payment failure → support tickets → refunds → churn"). Quantify the cost of inaction (e.g., "$50K/month in lost revenue").

Quick Check Questions

1. Question: Your team wants to add a "Refer a Friend" feature to increase virality, but your journey map shows users are already overwhelmed during onboarding. How do you decide?

2. Answer: Prioritize reducing onboarding friction first (e.g., simplify the first-time user experience). Why? Adding features to a broken flow worsens the problem (see: Hick’s Law).

3. Question: Your empathy map shows users say they want more customization, but do they always pick the default option. What’s the insight?

4. Answer: Users overestimate their desire for customization (see: Paradox of Choice). Focus on smart defaults instead. Example: Netflix’s "Top Picks for You" reduces decision fatigue.

5. Question: Your service blueprint reveals that a third-party vendor causes 80% of delivery delays. What’s your next step?

6. Answer: Negotiate SLAs with the vendor or build redundancy (e.g., multiple delivery partners). Why? Backstage failures often have outsized impact on user experience.

Last-Minute Cram Sheet

1. Empathy Map = 4 Quadrants: Says, Thinks, Does, Feels.
2. User Journey Map = 5 Components: Stages, Actions, Thoughts/Feelings, Pain Points, Opportunities.
3. Service Blueprint = Journey Map + Backstage Processes (frontstage, backstage, support, physical evidence).
4. ICE Score = Impact × Confidence × Ease (prioritize opportunities).
5. Kano Model: Basic Needs (must-haves), Performance Needs (more = better), Delighters (unexpected).
6. Moment of Truth (MoT): Critical touchpoints where users form lasting impressions.
7. Emotional Curve: Plot user sentiment across the journey to spot highs/lows.
8. ⚠️ Empathy Maps ≠ Personas: Personas = who; empathy maps = how they think/feel.
9. ⚠️ Journey Maps ≠ Service Blueprints: Journey maps = user experience; blueprints = operational diagnosis.
10. Always update maps quarterly—user behaviors change!