80% of products and features are rarely or never used, according to Pendo's 2019 Feature Adoption Report, which analysed feature usage across 615 subscriptions. Most of that waste comes from teams building for problems customers don't care enough about.
I spent over a year on 100+ customer discovery interviews only to follow the wrong user need. I've also spent 5+ years as a Techstars Community Leader and Global Facilitator, helping hundreds of early-stage entrepreneurs validate their ideas and build first-concept products. Validation is hard.
At the end of March 2021, I came across a Twitter thread by Stripe product manager Shreyas Doshi describing a validation method called Customer Problem Stack Ranking, which he had first named in May 2020.
At the time, we were struggling to get website visitors to convert and people just didn't understand why they would use our product. We decided right away to give CPSR a try on our startup. The value proposition that we spent 7 months of discovery research crafting came dead last with both of our top two target customer segments.
Dead. Fucking. Last.
We learned more in 2 hours using this stack ranking approach than we did in 100+ customer discovery interviews.
So I took that experience and built a CPSR tool to help you validate your ideas and find product-market fit.
To explain how the method works, I'm going to take a startup idea I've heard at countless hackathons: an app that makes it easier for a group of people to split the payments for their upcoming holiday. Call it Splitzies. This guide covers what CPSR is, how to write the question, how to turn your idea into a problem statement, how to find peripheral problems and participants, and how to read the results.
Step 1: Write your question
CPSR is a type of survey, so it needs a question. CPSR questions usually go along the lines of "What is frustrating about ____ ?"
Your question should be broad enough that participants can explore every problem attached to the activity, not just the specific one your idea will solve.
For our imaginary app Splitzies, our 'activity of focus' is booking a group holiday, so our question is: What is frustrating about booking a group holiday?
Step 2: Turn your idea into a problem statement
Asking target customers to tell you if they like your idea is a bad approach. As Rob Fitzpatrick's book The Mom Test explains, if you ask people about your idea they will just tell you it's great so that they don't hurt your feelings.
Instead, turn your idea into a problem statement so that you can compare it to the other problems customers face during the activity of focus.
For Splitzies, our problem statement could be: "Dividing the cost of a hotel booking is frustrating and complicated when planning a group holiday."
You can create multiple problem statements to explore the different pain points your idea might solve and the different words your target customers might use to talk about the activity of focus.
Step 3: Create peripheral problem statements
Brainstorm other problem statements that fall under the same activity of focus but aren't related to your idea. These can be informed by asking open-ended questions during a handful of interviews, or by reading pain-point blog posts and forums. Problem libraries like 99 startup problems and B2B customer problems are another place to draw from.
Don't worry if you feel like you've missed some peripheral problems. Running your stack ranking on OpinionX means participants can submit new problem statements to cover areas you missed at the start.
Some peripheral problem statements for Splitzies:
It's difficult to plan activities when I haven't organised a transport method like car rental or public transport.
It's hard to find out how expensive a destination is for general things like food and transport.
Agreeing on dates that suit everyone is a pain.
Some destinations are very different depending on the time of year, but good information on seasonality is hard to come across.
Keeping a list of potential Airbnbs and hotels turns into a giant messy spreadsheet.
Step 4: Send your stack rank to target customers
Send your survey link to target customers. Pick one specific segment instead of a generic demographic, to avoid noisy data. If I send my Splitzies stack rank to both young parents planning a family holiday and student backpackers, they're going to have very different priority problems and the data gets messed up. Segmenting the results afterwards works better than mixing the audiences at collection.
If you haven't got a pre-release waitlist, hit people's DMs on online communities, forums, and social media. When we used CPSR on ourselves, we joined a few Slack communities for product managers and got a +25% response rate on a couple hundred messages. That outreach took a couple of hours one evening. Here are more free tactics for finding participants.
Step 5: Iterate
The most important part of running a CPSR is growing your problems list as you discover pain points you missed at the start. Based on OpinionX product data, 81% of stack rankings run on the platform finish with new opinions added by participants sitting in the top 3.
That's why we recommend against using a normal survey for this. Tools like SurveyMonkey, Typeform and Google Forms lock you in with whatever blind spots you had when you wrote the multiple-choice list, because participants can only pick from what you thought of first. Traditional surveys fail at idea validation for exactly this reason.
Step 6: Read the results
Once you've got enough participants, sort all the problems by highest importance to stack rank your statements. In one click, you'll see how your value proposition and your idea rank against the other problems your target customers face.