Day 272 of the Daily · Innovation

Assumption Mapping

5 min read · 4 principles · apply it by lunch

Good morning. The idea isn’t the risky part. The beliefs holding it up are.

The question

Take the plan you’re most committed to this quarter and write down the one belief that, if it turned out to be false, would make everything else in the plan worthless — then look honestly at what you hold as evidence for it. If the answer is a conversation, a competitor’s homepage and a strong feeling, you’re funding that belief at full price.

The idea

David Bland had been running a workshop exercise called assumptions mapping with team after team before he and Alexander Osterwalder — who created the Business Model Canvas with Yves Pigneur, and co-founded Strategyzer — set the method down in Testing Business Ideas (2019). Their starting position is that a new idea isn’t a plan at all; it’s a stack of beliefs, most of which have never been said out loud. So you say them out loud. Every belief the idea needs in order to work gets written on its own card, sorted into three families — desirability, feasibility, viability — and plotted on two axes: how much of the idea collapses if the belief is wrong, and how much evidence you already hold. Well-evidenced beliefs need no more work. Unimportant unknowns can stay unknown. What is critical and unevidenced sits in the top-right corner, and that corner names the next test without anybody having to win an argument about it. The trap is testing whatever’s convenient: feasibility questions sit inside your own building and are answered by people who report to you, while the questions about whether anyone wants this live outside with strangers who might say no. That’s how firms end up building beautifully working versions of things nobody asked for.

In the Daily · 4 principles and a template

Assumption Mapping is Day 272 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 Innovation

The next four in the course.

All 24 Innovation frameworks
Day 281 · Innovation

Pretotyping

For the thing you’re planning to build this quarter, what’s the smallest and most embarrassing version you could put in front of a stranger this week — a sign, a page, a form, you doing the work by hand — and what would you need to watch them do before you’d believe the demand is real? If you can’t picture that version, it is usually because you’d rather not find out yet.

See the framework →
Day 290 · Innovation

Co-Innovation Risk

Take the thing you plan to launch next year and count everyone outside your business who has to do something new before a customer gets any value from it at all — the supplier who has to make a part that doesn’t exist yet, the installer who has to learn a procedure, the regulator who has to write a rule, the retailer who has to stock something nobody has asked for — and then ask what each of them would privately put their own odds at. You’ve costed your own risk carefully. The rest of the chain sits in the plan as one word: partners.

See the framework →
Day 299 · Innovation

Discovery-Driven Planning

For the venture you’re most excited about, do you know the profit it has to earn before it’s worth doing at all — and, separately, the price, the volume and the unit cost the world would have to hand you for that profit to exist? Most people can produce the first on request. The second is the one that settles it, and almost nobody has written it down.

See the framework →
Day 304 · Innovation

The Innovation Tournament

Count the genuinely separate attempts you have running at the problem you most need solved — separate in approach, not merely in name, so that one of them failing would tell you nothing about the others — and if the honest count comes to one, what exactly is meant to happen on the day that one turns out to be wrong? Most plans have no answer, because the plan was that it wouldn’t be.

See the framework →