For twenty years, the Double Diamond has been the dominant mental model for how products get made. Two diamonds in sequence: the first for understanding the problem, the second for building the solution. Each one a cycle of diverge, then converge. Each one measured in months.
It is a good model, and it was right for the world it was built in — a world where building was slow and expensive, where the phases had to run in sequence because no team could afford to do everything at once, and where the people who make products handed the work off to each other like runners in a relay. Business and research ran the first diamond. Design led the early part of the second. Engineering carried it home. Product managed the handoffs in between.
That world is ending. And the relay race is ending with it.
Hidden inside the Double Diamond is an assumption we stopped noticing: that understanding a problem and building its solution are separate activities that happen one after the other. You understand first. Then you build. That assumption made sense when building took months — you couldn't keep engineers in the discovery room when they were needed elsewhere, building the last thing you decided. The phases existed because time was long and people were scarce.
AI coding tools have collapsed the economics of building so completely — from sprints to hours — that sequential phasing is no longer the right shape. And once you remove the constraint that forced the relay race, a different shape appears.
Not two diamonds. One.
One diamond, with four edges you continuously travel — Decide, Build, Ship, Learn, clockwise — wrapped around an interior you continuously inhabit: a team that never leaves the problem, always sharpening its sense of what it is solving and why.
The interior: a permanent posture, not a phase
In the Double Diamond, Discover and Define were phases. You finished them. You wrote a brief, declared the problem framed, and crossed into the second diamond. The research was done. The definition was set. You did not go back.
In the Signature Diamond, they are not phases at all. They are the inside of the shape — the space the team lives in through every cycle, no matter which edge is active.
Discover is staying genuinely curious about the problem: who has it, how badly, in what situations, and why the solutions that exist fall short. This is not a quarterly research sprint. It is a continuous, low signal from the real world — interviews, behavior, support tickets, sales calls — a live feed rather than a snapshot.
Define is staying honest about what success means. Not the product spec, but the underlying problem statement: what exactly are we solving, for whom, and how will we know when we have? That definition should be plain enough for everyone on the team to repeat from memory, and it should change the moment the evidence demands it. A definition that never changes is a sign the team has stopped listening.
Together, Discover and Define form a continuous inner loop — not a room you enter and leave, but a discipline you hold. Everything you learn on one edge feeds back into it. Every decision you make is quietly updating it.
The edges: the execution circuit
If the interior is about understanding, the edges are about acting. Travel them clockwise.
- Decide is where the team chooses what the next cycle will test — not just what to build, but which hypothesis to build against. "If we make onboarding one step instead of four, we believe first-week retention will rise, because today most people drop off at step two." A Decide without a hypothesis is just a to-do list.
- Build is where the hypothesis becomes working software. This is the edge AI has changed the most: a well-framed hypothesis can go from idea to deployed code in a single session. Its compression from weeks to hours is the thing that makes the whole model possible.
- Ship is where that software reaches real people — not a staging environment, not a recruited test, but people meeting real software in the middle of their actual lives. Staged feedback tells you what people say; shipped software tells you what they do, and what they do is always the more honest answer. (What "real people" means depends on where you are: before you have a market, it might be a few design partners or yourself; at scale, it is a deliberate slice of your users rather than the whole base. The principle holds at every size — only the audience changes.)
- Learn is where the team reads what actually happened. Not instinct, not what you assume users intended — behavior. What did they click? Where did they stop? What did they ignore? Out of that evidence, the next hypothesis takes shape, and the circuit turns back to Decide.
Each lap of the diamond is one cycle. In the old world, a cycle took months. Now it can take days. You run more of them, you learn faster, and the learning compounds.
The triad and the diamond
The deepest change the Signature Diamond asks for is not in the shape. It is in how the people who make products work together.
In the relay race, each discipline owned a phase. Business and research owned the first diamond, design the middle of the second, engineering the end, and product managed the seams. The structure of the work set the structure of the team — which meant that at any given moment, different people were working on fundamentally different things. The Signature Diamond dissolves that, and the dissolving is the point.
- Product moves from orchestrating phases to authoring hypotheses. With the handoffs mostly gone, product's contribution becomes the quality of the questions that drive each Decide — living inside the interior, close to the signal, sharp on the definition. Product also keeps the hypothesis backlog: a prioritized queue of what the team does not yet know but needs to find out.
- Design moves from producing prototypes to translating signal. When the Build edge takes hours, design's center of gravity shifts upstream — closing the loop between what the last cycle taught and what the next one should test, turning raw behavior back into a sharper understanding of the problem.
- Engineering moves from implementation factory to build partner. When building took sprints, engineers were decoupled from the thinking. When it takes hours, they can sit in Decide and Learn and shape the next hypothesis, bringing a precise sense of what is newly possible and at what cost — knowledge that should inform what gets tested, not just how it gets built.
- Business moves from quarterly stakeholder to cycle participant. In the old model, business spoke at the beginning and the end. When cycles are days, business can be present at every Decide — with revenue hypotheses, market timing, an instinct for the cost of delay — instead of reviewing something already built.
Business here is a function, not a chair. On a small team the founder or the product lead wears it; in a larger organization it lives with leadership and operations. The work is the same either way.
The hypothesis backlog
If product's job is to author hypotheses and keep the team aimed at the right questions, the hypothesis backlog is what makes that job visible.
A hypothesis backlog is not a feature backlog. A feature backlog says what to build. A hypothesis backlog says what to find out, and makes plain what building something is meant to prove or disprove. The difference sounds small. In practice it changes every prioritization conversation a team ever has — from "what should we build next?" to "which of these is most worth testing this cycle?" The second question is almost always the better one.
A shared interior
In the old model, discovery was something you delegated. A researcher did it and reported back. The interior was processed by one function and passed to the next.
In the Signature Diamond, the interior has to be genuinely shared. Everyone needs contact with the raw signal — the actual user, the actual behavior — not a summary filtered through someone else's notes. Business needs to hear what people say about price and value firsthand. Engineering needs to understand why users struggle with the current flow, not just receive a ticket that addresses it. Design needs to feel the commercial constraints, not only the user's needs.
A team that holds the interior in common makes better bets. They catch each other's blind spots. They argue better. They are far less likely to ship something that delights users but starves the business, or hits the number but fails the user, or is technically elegant and beside the point.
The cadence
There is no single right cadence. The cycle should be as short as a team can sustain without losing the discipline of the interior.
For a large team with many dependencies, a week is a good rhythm — short enough to feel urgent, long enough to do real discovery and ship something worth learning from, and matched to how people already feel the shape of a working week. For a small, nimble team, the cycle might be a single day, or several loops within one. The faster you can responsibly close the loop, the more you can learn in a given week.
But speed is not the hard part. The hard part is scope. When you ship every cycle, you are almost never shipping the whole feature — you are shipping the smallest slice that tests the current hypothesis. The discipline the framework demands is declaring, out loud and in advance, exactly which slice is in this cycle and which is not. A team that ships fast without declaring scope is not running the diamond. It is just moving quickly in the dark. That clarity is the line between rapid iteration and expensive motion.
The temptation, and the antidote
The temptation of building this fast is to run the diamond so quickly that the interior disappears. When a cycle from idea to shipped software takes only hours, it becomes easy to treat Decide as a reflex — a hallway call, a gut feel — and skip the understanding that should be underneath it. That is how teams build the wrong thing at remarkable speed. Rapid cycles without a living interior are just expensive busywork wearing the costume of progress.
The antidote is structural. Someone — usually product, often alongside design — has to own the health of the interior as an explicit responsibility: keeping the hypothesis backlog alive, holding the questions open before they harden into feature requests, keeping the definition legible to everyone. The interior does not maintain itself. Left alone, it goes quiet exactly when speed makes it matter most.
A different theory of working together
The Signature Diamond is, in the end, a different theory of how people with different expertise should relate to each other while they build. The relay race says: do your phase, hand off, step back. The Signature Diamond says: stay in the room for the whole circuit, bring your expertise to every edge, and never leave the problem.
One diamond. Four edges. A living interior.
The relay race was a sensible adaptation to a world where building was slow and expensive. That world is dissolving. What replaces it — a team that shares the interior, moves around the edges at pace, and compounds its learning — is built for what making things actually costs now.
Find your edge on the diamond
The diamond is a team's shape, but no one person lives in all of it at once. Each of us leans somewhere. Some are never quite satisfied in the interior, always sharpening the problem. Some come alive on Build, turning a clear hypothesis into working software by the afternoon. Some have an instinct for Ship — for getting real work in front of real people. Some do their best thinking on Learn, reading the evidence for exactly what it says. A strong team needs all of it, and the friction where those instincts overlap is where good products are made.
The diamond is a map of the work, not a map of the worker — so you can lay any honest read of your own tendencies over it and see where you naturally create value. Whatever language you already use for yourself, whether a strengths assessment you have taken or simply the handful of things you know you are good at, you will find some edges feel like home and others feel like effort. Naming your own shape honestly is the first step to placing yourself where you are strongest, and to building a team whose shapes complement each other instead of collide.
If you want to make that concrete, you can generate your own Signature Diamond profile — a personalized read of where you and your strengths land across the interior and the four edges.