Importance vs. Satisfaction (Opportunity) Framework

Dan Olsen's prioritization tool for customer needs: plot each need on a 2x2 of importance (to the target segment) against satisfaction (with customers' current solution). The upper-left quadrant — high importance, low satisfaction — is the largest opportunity, since customers care a lot and are poorly served.

Opportunity size can be scored as importance × (1 - satisfaction) and rendered as a heat map across many needs, or approximated more cheaply with a coarse grid or a team sticky-note exercise (see Physical Prioritization via Post-it Wall Ranking) when survey data isn't available.

This is explicitly a first-pass prioritization, done before engineering scopes anything — its output (the "Return") feeds into a later, separate ROI calculation against effort (see Explicit Trade-off Prioritization).

Case studies: Segway targeted "walking," a need already high on both importance and satisfaction, and tried to compete via disruptive "to-11" innovation rather than an underserved need — it succeeded only in niche segments (mall cops, tour guides). Uber instead identified ground transportation as high-importance/low-satisfaction (taxis) and won by filling that gap. Google Search exemplifies a need already high-importance/high-satisfaction — competing there requires being "10x better," not just marginally better.

Rating Scales

Olsen uses differently-shaped scales for the two axes because importance and satisfaction behave differently:

Importance — a 5-point, one-sided scale from "not important" to "extremely important." Importance only runs from zero upward, so a simple ordinal scale suffices.
Satisfaction — a 7-point, bipolar (two-sided) scale with a neutral midpoint, because satisfaction can go negative: customers can be actively dissatisfied with a current solution, not merely neutrally unsatisfied.

Asking customers to point to a position on these scales, even across a handful of interviews, converts vague verbal answers into comparable pseudo-numeric data for the grid.

Tie-Breaking Techniques

When survey results cluster everything at "extremely important" — a common failure of the 5-point importance scale — Olsen recommends forcing differentiation with one of:

Expanding to a finer-grained scale.
Forced rank-ordering of all needs against each other.
A constant-sum allocation exercise, e.g. "distribute $100 across these needs," which makes trade-offs explicit because the total is fixed.

Opportunity Score & Heat Map

Opportunity = Importance × (1 − Satisfaction). This formula converts a need's importance and satisfaction ratings into a single number, so needs can be ranked numerically instead of just eyeballed on the quadrant. Olsen later built an opportunity heat map that colors every importance/satisfaction combination from 0 to 1 by this score — hotter colors mark higher opportunity — so the overlay can be read at a glance instead of computed by hand for each need.

Qualitative Shortcuts

For teams that want to prioritize without running a formal customer survey:

Qualitative Grid Hack — divide the plot into a coarse grid (e.g. 3x3 low/medium/high, up to about 5x5) and place needs by team judgment instead of numeric scores.
Sticky-Note Prioritization Exercise — each person writes a candidate benefit on a sticky note, the group debates its relative importance and satisfaction, and the notes get placed on the 2x2 grid together, building shared, debated alignment on priorities.
Line-from-Corner Shortcut — during that exercise, draw an imaginary line from the ideal corner (high importance, low satisfaction) to each plotted need; the shorter the line, the bigger the opportunity, without calculating a formal score. Olsen calls the region near that corner "the quadrant where you need to be 10x better" to win — see The '11 out of 10' Question.

Из тем: Strategy, Vision, and the Decision Stack