Day 207 of the Daily · Product Management

The Opportunity Score

5 min read · 4 principles · apply it by lunch

Good morning. You know what your customers say they need. You’ve never asked how badly any of it is being handled today.

The question

Pull up the list of needs your team believes it’s building against and go down it line by line: for each one, can you say how much the people who actually do that work care about it, how well they’re served today by whatever they use instead, and which of those two numbers you’ve ever gone and measured?

The idea

Anthony Ulwick spent the 1980s at IBM, founded the consultancy that became Strategyn in 1991, and set the method out in ‘Turn Customer Input into Innovation’ in the Harvard Business Review of January 2002. His complaint isn’t that customers lie to you; it’s that they’re poor at naming solutions and unusually good at naming outcomes — what they want the work itself to do, said in a form somebody could measure. Cardiologists asked Cordis Corporation for a smoother angioplasty balloon; the outcome underneath was minimise the risk of dissecting a vessel, and that’s a sentence engineers can be turned loose on. So you collect the outcomes for a job — Day 4’s job — go back to the people who actually do it, and ask two questions about every single one. How important is this to you. How satisfied are you with the way it’s done today. Both come back as numbers out of ten, and Ulwick’s arithmetic is importance plus the shortfall: importance + (importance - satisfaction), the shortfall floored at zero. Cordis broke the procedure into four steps and put those questions to cardiologists of differing experience, age and location, to nurses, to hospital administrators. The winner scored 9.5 for importance and 3.2 for satisfaction — 15.8, the highest on the list — and it was about the blockage returning afterwards. Cordis built out its catheter range off the rest of that list, and over 1994 and 1995 its share of the American market grew from under 1 to nearly 10 per cent.

In the Daily · 4 principles and a template

The Opportunity Score is Day 207 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 217 · Product Management

The Kano Model

The last five things your team shipped: which kind was each one — the sort nobody thanks you for but people leave over, the sort where more is straightforwardly better, or the sort nobody asked for and everybody mentioned afterwards — and could you say which was which without checking?

See the framework →
Day 227 · Product Management

Versioning

Look at the cheapest thing you sell and the dearest one, then say what actually differs between them — not the price, the product itself: is that difference a dimension your best customers would genuinely pay to escape, or a handful of things somebody switched off on a Thursday so the tiers wouldn’t look identical?

See the framework →
Day 236 · Product Management

The Opportunity Solution Tree

Pick any item on the roadmap you’re working to right now and say out loud which outcome it’s meant to move and which customer need it addresses — then work down the list item by item, and how far do you get before the honest answer becomes ‘because it was already on the roadmap’?

See the framework →
Day 245 · Product Management

The House of Quality

Your customers keep asking for the same vague thing — that it feel faster, or simpler, or more solid — and delivering it means moving one measurable characteristic inside the product: can you say which one, and in what unit? Most teams can’t. So the unit gets chosen by whoever writes the code, at the moment they write it.

See the framework →