How Stripe Validates New Product Ideas Using Customer Problem Stack Ranking
Understanding whether your product idea truly addresses customer needs is a universal challenge for entrepreneurs and product managers alike. Research indicates that about 80% of newly launched products and features are rarely or never used, often because they target problems that customers don’t find pressing enough to prioritize. To avoid this misstep, robust validation methods are essential.
Having spent over a year conducting more than 100 customer discovery interviewsΓÇöand with extensive experience as a Techstars Community Leader and Global Facilitator guiding early-stage startups worldwideΓÇöIΓÇÖve learned firsthand that validation is incredibly challenging. ItΓÇÖs easy to develop solutions based on assumptions rather than real customer pain points.
Recently, I came across an insightful validation technique called Customer Problem Stack Ranking (CPSR), as described by Shreyas Doshi, a seasoned product management expert and Twitter wizard. This approach, employed at Stripe, offers a powerful way to gauge the relative importance of customer problems and to test whether your proposed solution resonates with your target audience.
The Power of Customer Problem Stack Ranking
Customer Problem Stack Ranking shifts the focus from asking customers whether they like your idea to understanding how pressing their pain points are relative to other problems they face. In essence, it helps you determine if your product targets a burning pain point or merely a mild inconvenience.
Implementing CPSR: A Step-by-Step Guide
LetΓÇÖs walk through how this method works, using a hypothetical startup idea: an app called Splitzies, designed to simplify cost-splitting for group holiday bookingsΓÇöan idea commonly encountered at hackathons.
(Note: While I applied this to my own startupΓÇÖs tool, the technique is broadly applicable and not limited to survey tools.)
1. Craft a Broad Question
Begin with a broad question about the overarching activity:
ΓÇ£What is the most frustrating part of booking a group holiday?ΓÇ¥
This allows respondents to consider all related pain points without steering them toward your specific solution.
2. Translate Your Idea into a Problem Statement
Avoid directly asking if customers want your product. Instead, frame your idea as a problem statement, which can be rated relative to other issues.
For example:
“Dividing the cost of a hotel booking is frustrating and complicated when planning a group holiday.”
Creating multiple problem statements helps explore diverse pain points and discover the specific language your customers use.
3. Develop Peripheral
2 Comments
This post highlights a critical aspect of product development: moving beyond assumptions to genuinely understand customer pain points. The Customer Problem Stack Ranking (CPSR) approach exemplifies a strategic shift in validation ╬ô├ç├╢ from asking “Do you like this idea?” to assessing the severity and priority of underlying problems. This aligns well with the broader principles of Jobs-to-Be-Done (JTBD) theory, which emphasizes understanding the core jobs customers are trying to accomplish.
By focusing on relative importance rather than isolated feedback, CPSR enables teams to identify “burning” problems worth solving, increasing the likelihood of product adoption. Additionally, integrating this method early in the innovation process can help prevent the common pitfall of developing solutions based on surface-level needs or feature requests, which often fail to resonate in practice.
Overall, adopting structured validation techniques like CPSR fosters customer-centricity and data-informed decision-making, vital for building products that truly meet market needs. It’s a reminder that successful innovation hinges on deeply understanding and prioritizing customer problems, not just validating solutions.
Thank you for sharing this insightful overview of Stripe’s Customer Problem Stack Ranking (CPSR) technique. I appreciate how this approach shifts the focus from validation of ideas to validation of customer pain points, which is often a more reliable indicator for product-market fit.
One aspect I find particularly valuable is the emphasis on ranking problems relative to each other. This not only helps prioritize development efforts but also uncovers the true “burning” issues that customers are willing to invest time and resources to solve. It reminds me of the importance of empathy in product management—understanding not just what customers say they need, but what they *truly* feel is urgent.
Additionally, integrating problem statements instead of direct product questions is a strategic move that likely reduces bias and leads to more authentic insights. It might be interesting to explore how iterative CPSR sessions could help startups refine their solutions over time by continuously validating the evolving importance of their target problems.
Overall, leveraging techniques like CPSR can significantly improve the quality of early-stage validation and help startups avoid building solutions for problems that lack genuine urgency. Thanks again for highlighting this approach—definitely a practice worth adopting for product teams aiming to build impactful solutions.