Triple Diamond Initiative Playbook

About the Initiative Playbook (Triple Diamond)

As an industry we've spent a decade making our delivery pipelines faster, slicker and more automated. The only problem? A faster pipeline mostly helps you deliver a bad idea to your customers more efficiently.

The bottleneck usually isn't the tooling. It's the invisible context gap: the missing bridge between the what and the why. It's invisible because everyone genuinely believes they've communicated perfectly. But communication without collaboration leaves plenty of room for assumptions to settle in quietly.

This template is a map of that space. It takes an initiative from a rough idea through to running software (a Product Development Lifecycle if you will), so a cross-functional group can see the whole value stream in one place.

Its purpose is simple: to make the invisible, visible. Or as my friend Nicola Sedgwick, creator of the Quality Radar tool, puts it: you cannot improve what you cannot see.

What's on the board

The Triple Diamond is a design thinking model. It extends the Double Diamond popularised by the British Design Council. Each diamond is a diverge then converge move: open up the options, then narrow to a decision.

• Idea (the half diamond). Where the idea came from and what shaped it.

• Diamond 1: Problem discovery and definition. Explore customer needs, jobs to be done, market and business context. Converge on a clear problem statement.

• Diamond 2: Solution discovery and definition. Explore and experiment with approaches. Converge on an agreed solution.

• Diamond 3: Delivery. Do the work, then watch how customers actually behave. That feeds the next idea.

The first two diamonds are about building the right thing. The third is about building the thing right.

Three supporting elements sit alongside them. Milestones are pit stops to sense check if you're still moving in the right direction. Phase Goals are the outcomes you want from each phase. Activities are how you'll get there. None of it is prescriptive. Your organisation is not my organisation, so change the labels.

Who this is for

Engineering leaders, product managers, principal engineers, designers, delivery leads, and anyone else leading from the messy middle. It works best with a small cross-functional group: engineering, product, design, analysis, and whoever else genuinely has a stake.

How to use this template

1. Duplicate the board for an initiative

2. Pull together a small cross-functional group

3. Play back the initial idea, so everyone starts from the same story.

4. Tag the Phase Goals you actually care about for this initiative. Ignore the rest.

5. Tag the Activities and their state (in progress, blocked, and so on) using the emoji legend.

6. Leave comments for open questions and updates, synchronously or otherwise.

7. Agree a review cadence that suits you (Weekly, Fortnightly, find a cadence that works for you).

The first mapping session takes about 15 minutes. It is not a big ceremony.

Other ways to use this template

Mapping a live initiative is the obvious use. It isn't the only one.

• Retrospectives. Map an initiative after the fact and the gaps tend to announce themselves.

• Mapping your existing practices. One honest picture of how work really flows, rather than how the process document says it does.

• Audit and assurance. Plot your procedures and controls against the lifecycle stages, so you can show where they actually live.

• Heat and cold mapping. See where friction concentrates, and where nothing is happening at all. Both tell you something.

• Gap analysis. Overlay a lens such as AI, security, quality, accessibility or compliance, then see which phases are covered and which are quietly hoping for the best.

• Defining new measures. Once the stages are visible, the gaps between them become measurable: lead time between stages, rework rate, time spent waiting. These are the numbers that tell you where the value stream is actually stuck.

• Optimising the lifecycle. Decide where AI or automation genuinely earns its place, instead of applying it everywhere at once and hoping.

• Onboarding. Hand a new joiner the map. Considerably kinder than "you'll pick it up as you go."

Tips and best practices

• Use the emoji legend properly. Over time, tagged activities and comments build a heat map of where friction lives. It won't predict your DORA metrics. It tells you where to look.

• Iterate. The loops are there deliberately. Move backwards when you learn something.

• Let it surface the unknowns. Most of what goes wrong was never written down anywhere. A shared board gives people somewhere to put the question they'd otherwise keep to themselves. Tags and comments catch some of it, but the real feedback loop is the conversations the map prompts, in the session and long after it.

• Nothing is wasted. Stop an initiative mid-flight and the context and audit trail are still there when you come back to it.