Pain-Point Process Mapping

Definition

A pain point is a specific area where a customer experiences frustration, boredom, or inefficiency while pursuing a job — and pain points are best found by mapping the customer's process step by step, for one narrowly defined occasion, rather than for an "average" scenario. This same mapping exercise also surfaces stakeholders beyond the buyer: the person who buys, the person who prepares, and the person who consumes are often different people with different, sometimes conflicting requirements.

In the Book

Chapter 3 opens with an alarm clock owner who glued a bump onto one of fifteen identical buttons because he couldn't find the single button that silenced the alarm while fumbling half-asleep in the dark — a workaround that reveals a pain point the manufacturer never saw. The book then walks through grocery research where the authors identified at least three distinct stakeholders in the "shelf-to-table" flow — the shopper, the meal preparer, and the diner — and shows that studying only one (say, the in-store shopper) would have wrongly concluded that price and shopping-pattern fit were the dominant jobs, missing ease-of-preparation and spiciness entirely. The chapter insists process maps be built per specific occasion (a Tuesday lunch, a Friday date-night dinner), not for "shopping for meals" in general, because functional and emotional jobs shift by occasion. It also covers the decision of whether to replace or complement existing behavior: Kellogg's Breakfast Mates (cereal, milk, and a spoon in one package) failed because it forced an unresolved choice — refrigerate and eat chilled cereal, or pour warm milk — while the book's account of girls'-education programs in post-Taliban Afghanistan shows the same lesson at civilizational scale: only when NGOs stopped working around community elders and started "swimming with the tide" of existing attitudes did enrollment programs succeed.

Why It Matters

Treating "the customer" as a single undifferentiated actor, and treating their journey as one generic average scenario, both erase the exact place where a solution needs to intervene. Mapping the real process for a real occasion — and naming every stakeholder who touches it — turns a vague intention to "reduce friction" into a specific, actionable target, and surfaces whether a new solution must fight entrenched behavior or can simply slot in alongside it.