Identifying Customer Journey Pain Points and Drop-Offs

Find customer journey pain points and drop-off moments in each stage by pairing funnel data with interviews, tickets and session evidence.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

Customer journey pain points are the moments where customers struggle, and drop-off moments are where they leave. The two are related but found differently. Drop-offs show up in numbers: fewer people reach the next step than started the last one. Pain points show up in words and behavior: complaints, confused questions, repeated attempts, workarounds. This skill combines both so each finding has a location and a cause.

Quantitative data alone tells you where customers leave but rarely why. Qualitative evidence alone tells you what frustrates people but not how many are affected. Nielsen Norman Group's guidance on journey mapping makes the same point: qualitative research should drive the narrative, with quantitative data supporting the findings. A pain point backed by both is one a team will fund.

Drop-off can be very large at specific steps, and the reasons are often mundane. Baymard Institute's aggregation of 50 studies puts the average documented online cart abandonment rate at 70.22%, and its shopper survey put extra costs such as shipping, taxes and fees at the top of the list of reasons. That is an ecommerce purchase-stage example, but the lesson carries: the fix for a large drop is often a specific, fixable obstacle rather than a broad change of strategy.

This skill applies the same diagnosis to every stage of the five-stage customer journey framework, including retention and advocacy, where drop-off looks like cancellation, disengagement or silence rather than an abandoned form.

How It Works

The diagnosis runs in two passes. The first pass is quantitative: measure the conversion between each pair of adjacent stages and between the main steps inside each stage, and find the largest relative drops. The second pass is qualitative: for each large drop, gather evidence about what customers were trying to do and what stopped them.

Each stage has its own form of drop-off. In awareness it is people who see you once and never return. In consideration it is people who start evaluating and stop, such as trials that are never activated or demos that are never followed up. In purchase it is abandoned carts, stalled proposals and unsigned contracts. In retention it is falling usage, downgrades and cancellations. In advocacy it is satisfied customers who never refer, review or recommend.

The qualitative evidence comes from several places. Support tickets and chat logs show where customers ask for help. Session recordings and product analytics show where they hesitate or repeat actions. Interviews with customers who left, or who nearly did, explain the reasons in their words. Reviews and community posts show what customers tell each other. Each source has blind spots, so a pain point confirmed by two sources is more reliable.

Effort is a useful lens for interpreting the evidence. Harvard Business Review research argued that loyalty depends more on how much effort customers spend than on moments of delight. Looking for places where customers have to repeat themselves, switch channels or work around the product often finds the pain points that cause drop-off later.

The output is a ranked list. Each item names the stage and step, the size of the drop, the evidence for the cause, and the stage metric it affects. Ranking by impact and confidence keeps the team working on the problems that matter most and have the clearest evidence.

Step-by-Step Guide

Step 1: Measure conversion between and within stages

Using your stage definitions, calculate the share of customers who move from each stage to the next and between the main steps within each stage. Use cohorts so seasonal changes do not distort the picture. Lay the numbers out in journey order so everyone reads them the same way. Mark the steps where the relative drop is largest.

Step 2: Segment the drops

Split each large drop by segment, channel, device or plan. A drop that appears in only one segment points to a specific cause, such as a mobile form that breaks or a channel that brings poorly matched visitors. A drop that appears everywhere points to something more fundamental. Record which segments are most affected.

Step 3: Collect qualitative evidence for each drop

For each large drop, gather tickets, chat logs, session recordings, reviews and interview notes that relate to that step. Look for repeated phrases, repeated actions and workarounds. Interview a few customers who stopped at that point, asking what they were trying to do and what happened. Keep quotes attached to the step they describe.

Step 4: Look for effort and repetition

Scan the evidence for places where customers had to try more than once, contact support to finish a task, switch channels or re-enter information. These high-effort moments are pain points even when they do not yet cause visible drop-off. Note them alongside the drops, because they often predict churn later in the journey.

Step 5: Write each finding as location, cause and effect

For each pain point, write where it happens, what causes it according to the evidence, and which stage metric it affects. Keep the cause specific, such as "shipping cost appears only at the last checkout step", rather than "checkout is confusing". Note your confidence based on how many sources agree. Findings without a specific cause need more evidence before anyone builds a fix.

Step 6: Rank by impact and confidence

Estimate how many customers each pain point affects and how much it moves the stage metric. Combine that with your confidence in the cause. Put high-impact, well-evidenced findings at the top. Keep low-confidence findings on a list for further research instead of discarding them.

Step 7: Hand findings to owners and re-measure

Assign each top finding to the owner of the affected touchpoint, with the evidence attached. After a fix ships, measure the same conversion in the same way to see whether the drop narrowed. Update the journey map with the result. Repeat the full diagnosis periodically, because fixing one drop often reveals the next.

Best Practices

• Pair every number with a reason. A drop without evidence of cause leads to guesswork fixes. Collect at least two kinds of qualitative evidence for each major drop.
• Look after the sale. Retention and advocacy drop-offs are quieter than abandoned carts but often cost more. Include cancellations, disengagement and silence in the diagnosis.
• Talk to customers who left. People who stopped at a step can explain why far better than people who got through it. Recruit them deliberately.
• Compare segments before concluding. Averages hide concentrated problems. Segment each drop before deciding the cause.
• Record effort, not only failure. Customers who succeed with difficulty are future churn risks. Count repeat contacts and workarounds.
• Re-measure after every fix. Use the same definitions before and after, so the team learns what worked.

Common Mistakes

• Relying on analytics alone: Funnel charts show where customers leave but not why. Add interviews, tickets and recordings before designing a fix.
• Relying on anecdotes alone: One loud complaint can send a team after a rare problem. Check how many customers the issue affects.
• Stopping the diagnosis at purchase: Most funnel tools end at conversion. Extend the analysis into retention and advocacy using usage and cancellation data.
• Writing vague findings: "Onboarding is confusing" cannot be assigned or fixed. Name the specific step and cause.
• Fixing without re-measuring: A change that is never measured teaches nothing. Measure the same conversion after the fix.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: The Five-Stage Customer Journey Framework

Related Skills

• Measuring Customer Journey Metrics and KPIs by Stage
• How to Create a Customer Journey Map That Drives Action
• Designing Customer Retention Strategies for Loyalty

Sources

• Nielsen Norman Group: When and How to Create Customer Journey Maps
• Baymard Institute: Cart Abandonment Rate Statistics
• HBR: Stop Trying to Delight Your Customers

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.