3.2 Pain Point Sorting
At a Glance
Other names Pain Point Prioritization · Problem Card Sorting · Card Sorting - Pain Points
In Brief
Card Sorting for pain points is a simple prioritization exercise where you create approximately 10 cards, each representing a problem, pain, or unmet need, and ask participants to rank them by importance. While ranking, participants explain their reasoning, revealing not just what matters most but why. The exercise challenges founder assumptions about which problems are most pressing.
For the feature-focused variant of this method, see Card Sorting.
Common Use Case
You have already talked to potential customers and surfaced several distinct pain points your product could address. Before committing engineering effort to any of them, you need to know which problems matter most — not which ones you find most interesting. You want to force a prioritization and hear the reasoning behind their choices.
Helps Answer
- Which customer problems are most important to solve?
- How do different sets of customers prioritize the same set of problems?
- Are the problems I think are most important actually the ones customers care about most?
- Are there problems I have not considered that belong on the list?
- How much do customers care about this problem relative to other problems?
Description
Card sorting for pain points is a forced-choice prioritization technique. Most participants, when asked in an interview, will say that all of their problems are important. Card sorting makes them choose. By physically arranging cards from most to least important, participants must make trade-offs that surface priorities they would not name in open interviews.
This method should not be confused with the better-known information-architecture variant of card sorting, which asks participants to group and label cards to understand how they think.
The method creates both quantitative and qualitative data. The pain points sorted are a fixed set you provide. However, it’s common practice to give participants 2-3 blank cards so they can add new ideas. When multiple participants independently add the same problem, you have discovered a blind spot worth taking seriously.
The conversation during the sorting is where most of the qualitative learning happens. As participants move cards around, they think out loud about why one problem matters more than another. They describe situations, frequencies, consequences, and workarounds. That narration is qualitative data the ranking alone cannot give you.
How to
Prep
-
Create the pain point cards. Write approximately 10 cards, each describing one problem, pain, or unmet need in clear, jargon-free language. Use the participant’s language, not yours. Each card should describe the problem itself, not a solution. For example: “Spending too much time on manual data entry” instead of “Need an automation tool.” Include 2-3 blank cards so participants can add problems you missed.
-
Recruit 8-12 participants. Finding useful patterns typically requires 8-12 sessions; 5-6 at least. If you suspect multiple segments, recruit at least 3 from each. See Customer Discovery Interviews for sourcing and outreach guidance.
-
Plan session mechanics. Decide whether sessions are in-person or remote, how you will record (video, audio, or notes-only — get explicit consent before recording), and whether you will compensate participants. Compensation typically ranges from a $25-100 gift card for B2C consumers to a $100-300 honorarium for B2B specialists, varying by time commitment and seniority. Document consent and compensation terms in your recruiting outreach.
-
Prepare the session script. Prepare an introduction to the exercise, what follow-up questions you will ask, and how you will record the final ranking and key quotes. The script should explain that there are no right or wrong answers and that you want to understand their perspective.
-
Pilot the deck. Run one or two pilot sessions before committing to a full round. Pilots almost always surface a card that is too vague, a duplicate, or a problem you did not realize was too solution-focused.
-
Revise. If the pilot sessions surface problems, revise the deck and script. Consider using a Comprehension Test to revise the pain point descriptions.
Execution
-
Shuffle and present the cards. Lay all cards face-up on a table (or in a digital whiteboard). Present them in random order to avoid anchoring the participant’s thinking. Use the intro script to frame the exercise.
-
Rank by importance. Instruct the participant to arrange the cards from most important (top) to least important (bottom). Encourage them to think aloud as they sort if they go silent. Ask them to fill in any blank cards with problems that are missing from the set.
-
Probe the reasoning. As the participant sorts, ask follow-up questions: “Why did you put that one higher than this one?” “How often do you experience this problem?” “What happens when this problem occurs?” “How do you currently deal with this?” Do not challenge or correct their rankings.
-
Take notes. Note clusters and gaps. Pay attention to cards that participants group together (“these are all related”) and cards they set aside as irrelevant (“this is not really a problem for me”). Both patterns are informative. Also note any blank card additions.
-
Add an intensity check (optional). After the ranking, you can have the participant allocate a hypothetical sum across the cards to reveal how much they care about each problem, not just the order. For the full version of this technique, see Buy a Feature.
Analysis
-
Aggregate rankings. After each session, record the final ranking and key quotes. Once you have 8-12 sessions, record each person’s final sort as an ordered list, then count patterns across lists for how often each problem placed in the top 3, top 5, and bottom half. Problems that recur in the top 3 across most participants are strong candidates for the core value proposition.
-
Group the reasoning quotes. Pull every participant’s quote that explained a high-rank choice into a working doc, then group similar reasons together. The clusters reveal why certain problems rank high — frequency, severity, blocked workaround, money lost — and that why is more actionable than the rank itself.
-
Look for divergence as a segmentation signal. Problems with high variance in ranking (some participants rank them first, others last) may indicate distinct segments with different needs. Look at what those split groups have in common — role, company size, vertical, life stage — and form a segmentation hypothesis to test.
-
Catalog blank-card additions. Problems added on blank cards by multiple participants independently are blind spots worth exploring. Group similar additions before deciding whether to add them to the deck on the next round.
-
Watch for flat allocations. If you ran the intensity check and a participant spread the amount evenly across the cards, they may not have a strong pain point at all — which is itself an important finding. A flat allocation with a high-ranked top problem usually means the top problem is real but mild.
-
Note what participants set aside. Problems that participants set aside as irrelevant may have been based on your assumptions rather than reality. Add to the running list of cards to drop or rewrite.
-
Treat the data as directional. With 8-12 participants, individual outliers can skew the results. Look for consistent patterns rather than precise orderings, and treat the data as directional rather than statistically significant.
- Framing bias The way you describe each problem on the card influences how participants perceive its importance. Use neutral, descriptive language and avoid emotionally charged framing.
- Researcher blind-spot bias The cards you choose to include define the conversation. If you omit an important problem, blank cards will not reliably surface it — participants rarely volunteer a problem they have never been asked to name. Without prior exploratory interviews, the sort confirms your existing list rather than challenging it.
- Anchoring and order effects The first few cards a participant reads can anchor their thinking, and the wording of the highest-stakes card can shift relative rankings of everything else. Fully randomize card order per session (not just rotate between sessions), and shuffle again before each participant.
- Availability bias Participants will overweight problems they experienced this week and underweight problems they experience less often but with greater consequences. Probe for frequency separately from rank (“how often does this happen?”) so the rank is not driven entirely by recency.
- Social desirability and interviewer effects Participants may rank problems they think they “should” care about (security, privacy) or that they think you care about higher than problems they actually struggle with. The intensity check partially counteracts this; staying neutral when probing — no nodding, no “great” — counteracts the rest.
Learn more
Case Studies
Shreyas Doshi: Customer Problem Stack Ranking
Shreyas Doshi (then a product leader at Stripe) formalized the practice of giving customers a candidate problem alongside the other problems they face and asking them to rank, rather than asking whether they like a proposed solution.
OpinionX: Stack ranking revealed misaligned priorities
Tested 20 candidate problem statements against their most engaged users, collected nearly 800 votes, and learned the problem they had been prioritizing was not the one users most wanted solved.
Adobe Dreamweaver: $100 feature allocation
In the late 1990s the team gave customer advisory board members an imaginary $100 to spend across candidate features. The forced allocation defined the product’s MVP feature set.
Further reading
- Luke Hohmann — Innovation Games: Buy a Feature
- Greg Guest, Arwen Bunce, Laura Johnson — How Many Interviews Are Enough? An Experiment with Data Saturation and Variability (Field Methods, 2006)
- Donna Spencer — Card Sorting: Designing Usable Categories (Rosenfeld Media)
- Card Sorting: Uncover Users’ Mental Models — Nielsen Norman Group
- Three Levels of Pain Points in Customer Experience — Nielsen Norman Group
- Alex Osterwalder — How Card Sorting Can Help You Understand User Priorities (Strategyzer)
- Card Sorting — Interaction Design Foundation
Got something to add? Share with the community.
