Pain Points & Winning

Anyone can list what’s annoying. Product sense is knowing which annoyance is a wound and which is a papercut, and knowing where the product could be the best in the world. This doc is the two halves of that: finding the pains that matter, and forming an opinion on how we win.

It’s also where the group turns from “understand” to “have a point of view.” Personas and jobs are diagnosis. Winning is the bet.

Find the Real Pain, Not the Surface Complaint#

What’s expected: For your prioritized persona, you can name their real needs along the journey, separated from the surface complaints they happen to voice.

A complaint is what a person says. A pain is what’s actually costing them. They’re often not the same, and the surface complaint is frequently a symptom of a deeper one. “The search bar is too narrow” is a complaint. The pain underneath might be “I can’t find the product I came for, so I leave.” Widen the bar and you’ve soothed the complaint. Understand the pain and you might rebuild search and recover shoppers who were bouncing before they ever reached a cart.

How to get there: Walk the customer journey step by step and, at each step, ask what the persona needs to accomplish and what’s in the way. Structure it as user stories, three to five, no more. Then push past the literal:

• Ask what they were really trying to do. The complaint is about the tool. The pain is about the goal. Map every complaint back to the job from Personas & Jobs.
• Weight aspirational needs over pain relief, once the basics hold. “Stop making me re-type my address” is a pain to remove. “Let me buy in one tap” is an aspiration to grant. Removing pain prevents churn (shoppers leaving and not coming back); granting aspiration creates advocates. But sequence matters: a broken basic still gets fixed first, because trust breaks faster than it builds.
• Watch for the pain nobody voiced. The shopper who abandons at checkout rarely files a complaint; they just close the tab. Silence in the data is often where the biggest pains hide, because the people they hurt leave instead of telling you. But silence is a lead, not a verdict: it tells you where to look, not what’s wrong. Treat it as a hypothesis to go measure (see Earning the Opinion), not a confirmed problem.

Rank by Impact on the Goal#

What’s expected: Your pains are stack-ranked, and the ranking is driven by impact on the goal, not by how loud or recent the complaint was.

This is the step the symptom-collector never does, and it’s the whole game. Ten pains with no order is a to-do list. Ten pains ranked by what moves the goal is a strategy. The same rule from every other doc applies: rank by impact on the goal.

Judge each pain on a few axes and let the goal decide:

• Frequency: how often does this bite, and how many people?
• Severity: when it bites, does it lose the outcome (an abandoned order) or just annoy (a small image)?
• Goal attribution: the Storefront’s goal is completed orders per week, flat at ~1,900 for two halves. Which pain, removed, produces the most orders? That one wins.

Run the Storefront’s real feedback through this and the flat list sorts itself. Two of the biggest pains were never even on it, and they came straight from looking at where the funnel actually leaks:

Same store. Completely different instructions to the team. The two unreported leaks jump to the top because they’re where the orders are actually lost, and we can put a number on each. The images and footer links drop, not because they aren’t real, but because fixing them moves nothing. And the single biggest opportunity, the shoppers abandoning at checkout, was never on the list at all, because nobody walked the store as a shopper trying to pay.

How We Win#

What’s expected: You can name the one seam where this product could be the best in the world, and defend why that’s the place to bet.

Ranking pains tells you what to fix. It doesn’t tell you how to win. Winning is a separate, harder question: if this product could be the best in its category at exactly one thing, what would that thing be? Parity everywhere and excellence nowhere is how products die politely. You win by being clearly, memorably better at the thing the prioritized persona cares about most.

A reliable place to find that one thing is a seam: a boundary the user has to cross that no tool actually owns well. Seams are where every competitor is weak, because each one built up to the edge of its box and stopped. Own the whole crossing and you’re instantly better than all of them at the part users hate most. A delivery app’s seam is order-placed to courier-assigned to at-your-door, the anxious gap where nobody tells you what’s happening. An expense tool’s seam is receipt to reimbursement.

The Storefront’s seam is the crossing from full cart to paid: the checkout. It’s where one in five shoppers quit rather than re-type an address, and it’s the exact step the north star is made of. So the winning bet points itself: one-tap checkout, saved address and payment, express pay, guest-friendly, so a decided buyer pays and leaves in seconds. Best-in-class one-tap runs 90%+ completion; the Storefront sits at 80. That’s a thing you could be the best in the world at, and it’s worth more than the entire cosmetic list combined, if it’s real. Which is the catch: a winning bet is still a hypothesis, and it’s the most expensive one you’ll make, so it gets earned before it gets built (see Earning the Opinion).

How to get there: Find the seam by looking for where the persona’s journey crosses a boundary the tools don’t: between two stages, two teams, or two systems. That crossing is where everyone is weak and where a single product that owns the whole span wins. Then ask the reversal question: what would this look like if the boundary didn’t exist, if paying took no typing at all? The answer is usually your bet.

Quality Attributes: What “Best” Is Measured On#

What’s expected: You can name the handful of qualities this product is judged on, and say which ones we’re choosing to be excellent at.

“Best” is not a vibe. Every product category has a small set of quality attributes, the dimensions the product is actually judged on, and winning means being deliberately excellent on the ones that matter and deliberately adequate on the rest. Naming them turns “make it better” into a set of targets.

Every category has its own short list. A messaging app is judged on speed, reliability that messages arrive, an accurate unread count, and search that works. A hiring tool is judged on time-to-fill and a clean handoff to onboarding. Name the four or five for your product. For the Storefront:

The image-size complaint doesn’t map cleanly to any of these, which is exactly why it ranked low. The checkout-abandonment pain maps straight to “checkout completion,” a headline attribute, which is why it ranked high. Quality attributes are the bridge between a pile of feedback and a coherent sense of what good means.

What We Over-Invest In, and What We Neglect#

What’s expected: You can say where the team’s attention is disproportionate to impact, in both directions.

Part of product sense is seeing the shape of the team’s attention and correcting it. Two failure modes, and both were visible in the Storefront feedback:

• Over-invested: cosmetic polish on the pages you happen to look at first. Image sizes, menu icons, footer links, filter niceties. Visible, easy to spec, satisfying to fix, and low impact. Attention pools here because it’s where the person giving feedback happened to be looking, the landing and listing pages, not the checkout. Notice when the list is all “nicer version of what exists.”
• Neglected: the step where money is actually made, and the shopper who doesn’t complain. The checkout where one in five quit. The slow pages that shed shoppers silently. These are the highest-impact areas in the product and they generate almost no feedback, because the people they hurt don’t file tickets, they just leave. The absence of complaints is not the absence of pain, and it’s why orders can sit flat at 1,900 for two halves while everyone stays busy.

The correction is a habit: for every initiative, ask “whose pain are we not addressing, and what are we polishing that doesn’t move the goal?” If the answer to the first is a persona at the checkout and the answer to the second is a pile of cosmetics, reallocate.

Next: Earning the Opinion