From Gaps to Gains: How Opportunity Scores Can Drive Product Success

In the world of product development, especially for early-stage startups, it’s easy to become enamored with the idea of building innovative features or leveraging the latest technologies. However, at the core of any successful product is a fundamental truth: customers don’t buy products for the sake of the product itself. Instead, they hire products to achieve specific outcomes that their current solutions fail to deliver. Understanding this principle is essential to creating products that truly resonate with customers and solve their most pressing problems.

The Allure and the Reality

For many startups, the excitement of building something new can often overshadow the more critical task of solving urgent customer problems. Features may seem exciting, and new technologies may appear revolutionary, but if they don’t address an unmet need or help customers achieve an important outcome, their value is limited. The reality is that customers are looking for results—they’re trying to solve problems, save time, reduce costs, or improve their workflows. They aren’t interested in features for features’ sake; they want a product that will get the job done better than anything else available.

The Concept of the Gap

This is where the concept of the "gap" comes into play. The gap represents the difference between what customers need to achieve and what their current solutions allow them to do. It’s the space where unmet needs exist, where customers are dissatisfied with their current options, and where your opportunity to provide value lies. Without a clear understanding of this gap, product development efforts can easily miss the mark. Identifying and quantifying this gap is crucial for ensuring that your product aligns with what customers are truly trying to achieve—and this is where the Opportunity Score becomes an invaluable tool.

Understanding Why Customers Hire Your Product

The Jobs to Be Done (JTBD) Framework

To truly grasp why customers would choose your product over others, it’s essential to move beyond thinking of your product as a set of features or technologies. Instead, consider what your customers are actually hiring your product to do. This is where the Jobs to Be Done (JTBD) framework becomes crucial. The JTBD framework centers on the idea that customers hire products to fulfill specific jobs or achieve particular outcomes. These jobs represent the progress a customer is trying to make in their life or work, and your product is simply a tool they use to get there.

By understanding the jobs that customers need to get done, you can design your product to be the best possible solution for those needs. This approach shifts the focus from building features to solving real problems that customers face every day. It also helps avoid the common pitfall of creating products based on what you think customers want, rather than what they actually need.

Connecting JTBD to the Opportunity Score

The Opportunity Score is a powerful tool that helps you quantify how well your product can fulfill the job your customers are hiring it to do. By measuring both the importance of the outcome they’re trying to achieve and their satisfaction with current solutions, the Opportunity Score directly links the JTBD framework to actionable product development insights.

Here’s how the connection works: When you identify the job your customer is trying to get done, you also need to understand how crucial that job is to them and how well their current tools or methods are performing. The greater the gap between the importance of the job and the satisfaction with current solutions, the larger the opportunity for your product to step in and become the tool of choice.

For example, if a customer is trying to achieve faster invoicing to improve cash flow, and their current solution is slow and error-prone, the gap between the importance of this job and their satisfaction with the existing solution reveals a significant opportunity for your product to make a real impact.

By applying the JTBD framework alongside the Opportunity Score, you gain a deeper understanding of not just what your customers need, but why they would choose your product over others. This approach ensures that your product development efforts are always aligned with the most pressing needs of your market, increasing the likelihood of creating a product that customers will actively choose to hire.

Defining the Opportunity Score

The Formula

The Opportunity Score is a straightforward yet powerful formula designed to help you prioritize product development efforts based on the real needs of your customers. It measures two critical factors: the importance of the outcome your customer is trying to achieve and their satisfaction with the current solution. Here’s the formula:

Opportunity Score = Importance + (Importance - Satisfaction)

This formula may appear simple, but its implications are profound. It quantifies the gap between what customers want to achieve and how well their current solutions are helping them get there. The bigger the gap, the greater the opportunity for your product to fill it.

Importance of Outcomes

The first element of the Opportunity Score is understanding how critical the desired outcome is to your customer. This is the "Importance" factor in the formula. To accurately assess this, you need to ask your customers to rate the importance of the outcome on a scale of 1 to 10.

For example, if you’re developing an invoicing solution, you would ask, “How important is it for you to have accurate and timely invoicing to maintain healthy cash flow?” A high score indicates that this outcome is crucial to your customer’s operations or personal goals, making it a key area where your product can add significant value.

By focusing on outcomes rather than features, you align your product development efforts with what truly matters to your customers. This approach ensures that you’re not just building features but solving problems that are vital to your customers’ success.

Satisfaction with Current Solutions

The second element of the Opportunity Score is assessing how satisfied customers are with their current solutions for achieving the desired outcome. This is the "Satisfaction" factor in the formula. Like the importance factor, satisfaction is rated on a scale of 1 to 10.

When a customer rates their satisfaction with current solutions, you gain insight into the effectiveness of those solutions in helping them achieve their goals. If the satisfaction score is low, it signals dissatisfaction with the current offerings, indicating a significant gap that your product can potentially fill.

For example, if customers are currently using a manual process for invoicing that they rate a 3 out of 10 in satisfaction, it indicates a substantial opportunity for a more efficient, automated solution. The low satisfaction score combined with a high importance score creates a wide gap—exactly where your product can step in to make a meaningful difference.

By quantifying both the importance of outcomes and the satisfaction with current solutions, the Opportunity Score provides a clear, data-driven way to prioritize which problems to solve. This method helps ensure that your product development is focused on the areas with the highest potential for impact, where customers are most likely to hire your product to achieve the outcomes they need.

Quantifying to Reduce Bias

Importance of Data-Driven Decisions

In product development, it’s easy to fall into the trap of relying on anecdotal evidence, gut feelings, or the loudest voices in the room when making decisions about what to build next. However, these approaches can introduce significant bias into your process, leading to products that don’t resonate with the broader market. This is where quantifying customer needs through the Opportunity Score becomes invaluable. By assigning numerical values to the importance of outcomes and the satisfaction with current solutions, you can make data-driven decisions that are grounded in reality rather than assumptions.

Quantification helps ensure that your focus is on the areas with the highest potential for impact. Instead of building features based on what you think customers want, you can prioritize based on what the data tells you they actually need. This shift from subjective to objective decision-making is crucial for minimizing bias and maximizing the chances of your product’s success in the market.

Moving Beyond Anecdotal Evidence

A common pitfall in product development is relying too heavily on the feedback of a few vocal customers or early adopters who may not represent the broader target market. While these insights can be valuable, they can also skew your understanding of the true needs and pain points of your entire customer base. The Opportunity Score provides a way to move beyond this anecdotal evidence by focusing on quantifiable data.

For example, a few customers might tell you that they love a specific feature of your product, but when you quantify their overall satisfaction with the current solution compared to the importance of the outcome, you might discover that the feature is not addressing a critical gap. Conversely, customers might express satisfaction with their current solution, but when asked to rate their satisfaction numerically, they may reveal underlying dissatisfaction that they hadn’t articulated.

By using the Opportunity Score, you force yourself to validate assumptions with hard data. This approach reduces the risk of building features based on wishful thinking or overestimating the importance of outlier opinions. Instead, you focus on the gaps that represent the most significant opportunities for your product to provide real value.

Quantifying customer needs in this way ensures that your product development efforts are guided by objective insights rather than subjective biases. It also helps you avoid the trap of building something based on what a few people say they want, rather than what the majority of your market truly needs. By relying on the Opportunity Score, you can prioritize your development efforts on the areas that will have the most significant impact, increasing the likelihood that your product will be hired by a wide range of customers to achieve their desired outcomes.

A Call to Action for Early Stage Founders

Focus on the Outcome

As you embark on your product development journey, keep the customer’s desired outcomes at the forefront of every decision you make. Remember that customers don’t buy features—they hire your product to achieve specific results. Ensure that every aspect of your product is designed to help them achieve those outcomes more effectively than their current solutions. This focus will guide you in building a product that truly resonates with your target market and stands out as the best tool for the job.

Fill the Gap

The key to creating a product that customers will hire is to identify and fill the gaps in the market. Use the Opportunity Score to quantify these gaps and prioritize the areas where your product can deliver the most value. Don’t be tempted to chase after every potential feature or idea. Instead, concentrate your efforts on addressing the most significant gaps—the areas where customer satisfaction with current solutions is low, and the importance of the outcome is high. By filling these gaps, you ensure that your product is solving the problems that matter most to your customers.

Ensure Your Product is the One They Hire

Ultimately, your goal is to make your product the obvious choice for customers to hire when they need to achieve a particular outcome. This means not only delivering the features they need but also demonstrating that your product is the best tool for the job. Communicate clearly how your product fills the gap in their current solutions and how it will help them achieve their desired results. By doing so, you position your product as indispensable—something customers can’t achieve their goals without.

To achieve this, consistently test your assumptions, gather customer feedback, and iterate on your product based on the data you collect. The Opportunity Score should be a living part of your product development process, helping you stay aligned with customer needs and market opportunities.

Acknowledgements

This article draws heavily on the foundational work of several thought leaders in the field of product development and innovation.

• Dan Olsen: The Opportunity Score, as outlined in his Lean Product Playbook, provides a practical framework for quantifying gaps in customer satisfaction and directing product development efforts toward high-impact areas. His work has been instrumental in helping product teams prioritize based on real customer needs rather than assumptions.
• Tony Ulwick: His pioneering work on Outcome-Driven Innovation has fundamentally shifted how we approach product development, emphasizing the importance of understanding the outcomes that customers are trying to achieve. Ulwick's model encourages product teams to focus on delivering value by addressing the specific outcomes that matter most to customers.
• Clayton Christensen: Building on Ulwick's model, Christensen's introduction of the Jobs to Be Done (JTBD) framework has provided a deeper understanding of why customers hire products. His work underscores the importance of viewing products as tools that customers use to make progress in their lives or work, which is central to the approach discussed in this article.

‍