Day 267 of the Daily · Innovation

The Double Diamond

5 min read · 4 principles · apply it by lunch

Good morning. Four movements — and most projects only ever run the last one.

The question

The last project your team ran — the one with a deadline and a budget attached — how much of it went on deciding what the problem actually was, before anyone started drawing the answer? For most teams that’s a single meeting, and it’s called the kick-off.

The idea

The Double Diamond came out of the UK Design Council in 2004, drawn from reviews of projects the Council had run and from kite-shaped models of design that went back to the 1960s. It draws the work as two diamonds side by side. The first belongs to the problem: Discover, where the enquiry is deliberately widened past the brief you were handed, then Define, where all of that closes into one written problem statement. The second repeats the shape on the answer: Develop, where you generate more options than is comfortable, then Deliver, where you test, cut and ship one of them. Tim Brown, then chief executive of IDEO, made a similar case to a management audience in Harvard Business Review in June 2008, describing the design process as a system of spaces that projects loop back through, rather than a straight line from brief to launch. Four movements, two of them widening and two narrowing, each pair wanting different behaviour from the same people in the same room. The trap is starting inside the fourth: somebody arrives with the answer already chosen, the work becomes delivery, and both halves of the problem get skipped by people who’d swear they ran a process.

In the Daily · 4 principles and a template

The Double Diamond is Day 267 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 272 · Innovation

Assumption Mapping

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.

See the framework →
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 →