I sent you this chapter. Reply on LinkedIn or by email.
Data shows where customers stop. It rarely shows why. For that you need their words, a small number of them, and an honest label on what you’re guessing.
The cohort table can tell you that 1,900 customers a month never show a first-use signal. It can’t tell you whether the product was confusing, was a gift, or was used without triggering your signal. Those are different fixes, and the only way to tell them apart is to ask.
| Source | What it shows | Blind spot |
|---|---|---|
| Support tickets | Problems in the customer’s own words, tagged by stage | Only customers who bothered to write; most who leave don’t |
| Return reasons | What didn’t work, by product | Vague codes; nothing from customers who kept an item they didn’t like |
| Session recordings | Where people hesitate, scroll back or quit on the site | Only on-site stages; no view of the cupboard, the bathroom or the dog |
| Interviews | The circumstance, the goal and what got in the way | Small numbers; people explain their past behavior tidily |
Use the first three to form a view, and interviews to test it. For reading tickets and return reasons as a defect log, see The Return Trip. For session recordings and on-site research, see The Honest Test.
Fewer than most teams think. Abbie Griffin and John Hauser, studying how firms identify customer needs, found that “interviewing 20 customers identifies over 90% of the needs provided by 30 customers”, and hypothesized that 20 to 30 interviews find 90% to 95% of needs. Two one-on-one interviews were about as productive as one focus group Published. For website problems, Jakob Nielsen’s rule of thumb is that five users surface about 85% of usability issues, with more needed for distinct groups Reported.
For a journey stage, that suggests eight to ten interviews with customers who stalled and five or so with customers who passed, per round. The comparison is what makes it useful: the difference between the two groups is the fix.
The script is in Appendix B. Offer a small thank-you, and be clear it doesn’t depend on what they say.
Mark each stage, and each claim about why customers stall there, as measured (from data), heard (from customers in their words) or inferred (believed, not yet checked). The Nielsen Norman Group’s advice on hypothesis maps is to validate them with research before using them for decisions Reported. The label keeps that visible. An inferred claim can still guide a test; it shouldn’t drive a budget.
Want to answer the note that sent you here? Reply on LinkedIn or by email.
If this is your store
The free Klaviyo audit reads your own account and scores it. Start with your store’s address. A read-only key gets the full report.
Written by Andrew Lauchner, a growth and retention operator for consumer brands. The paid work is one ninety-day Sprint.
This is one chapter of The Journey Map, which is free and readable in full on a single page with no form in front of it.