Opportunity Scoring And Why It Matters In Business

Opportunity scoring is a product feature prioritization framework. It asks customers to identify features they deem important but that are otherwise underdeveloped or disappointing. Opportunity scoring is derived from the outcome-driven innovation (ODI) strategy developed by Tony Ulwick in the 1990s. It is a user-centric process that gives product teams direct access to customers and their associated needs and wants. 

Understanding opportunity scoring

Opportunity scoring is closely related to the Jobs To Be Done (JTBD) methodology, also one of Ulwick’s creations. With respect to JTBD, the key to maximum product value is determining the goals and desired outcomes of the user. In other words, what job does the product empower a user to complete?

Given the similarity of both approaches, it’s useful to think of opportunity scoring as an additional layer of JTBD. Customers are asked to identify important product features they feel are underdeveloped or indeed absent entirely. This removes the guesswork out of product design, shifting the focus from theory-based to practical-based product development.

Opportunity scoring differs from other product prioritization approaches such as the Value vs. Complexity analysis. Instead, think of opportunity scoring as an importance-versus-satisfaction analysis that seeks to make product innovation more predictable.

Conducting opportunity scoring

To conduct an opportunity scoring analysis, businesses must follow these steps:

1 – Create lists

Begin by creating a list of product features and the associated results (outcomes) of each feature.

2 – Survey customers with a scoring system

Then, survey a group of customers by asking them two questions:

  • How important is this feature or outcome to you?
  • How satisfied are you with how the product delivers this feature or outcome?

Both questions are rated on a scale of 1-5, where 1 denotes low importance/satisfaction and 5 denotes high importance/satisfaction.

3 – Analyse the results

Any features receiving a high importance rating coupled with a low satisfaction level should be investigated further. These will likely yield a significant ROI for the business but in any case, product teams must also consider the associated costs of seizing such an opportunity.

Features deemed low importance and low satisfaction can be ignored or removed altogether. This frees up resources to enhance other product features.

4 – Further detailed analysis (optional)

When scoring product features, opportunity scoring gives importance and satisfaction equal weight. However, some product teams may choose to borrow concepts from Ulwick’s ODI methodology. In this case, the value of user importance is doubled in relation to satisfaction

With an emphasis on gauging the outcomes customers value most, a thorough understanding of their goals and motivations is crucial. Again, the features or outcomes most suited to innovation are those that have high importance values coupled with low satisfaction values. 

Key takeaways:

  • Opportunity scoring is a product prioritization framework. It asks customers to score features based on their relative importance and how satisfied they are with each.
  • Opportunity scoring is closely related to the Jobs To Be Done (JTBD) methodology, which has a focus on understanding the goals and desired outcomes of the end user.
  • Opportunity scoring is an importance-versus-satisfaction analysis that seeks to make innovation more predictable. Product teams can deepen the analysis by giving importance values double weight.

Related Business Concepts

Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.
The MVC framework is a predictable software design pattern separated into three main components and suitable for many programming languages. The goal of the MVC framework is to help structure the code-base and separate application concerns into three components: View, Model, and Controller.
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.
DevSecOps is a set of disciplines combining development, security, and operations. It is a philosophy that helps software development businesses deliver innovative products quickly without sacrificing security. This allows potential security issues to be identified during the development process – and not after the product has been released in line with the emergence of continuous software development practices.

Read Also: Jobs-To-Be-Done.

Read Next: Business AnalysisCompetitor Analysis, Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Main Free Guides:

Scroll to Top