How they fit together

Teams often ask whether Discover equals Discovery, or whether Alpha is the same as Develop. The honest answer is: partly, but not exactly. The Double Diamond describes thinking modes — when to expand and when to narrow. The GDS phases describe delivery stages with governance, funding, and assessment attached. Mapping them helps communication; treating them as identical creates confusion.

Discovery and the first diamond

Discovery aligns most closely with the first diamond. Early Discovery is Discover work — broad research, mapping the landscape, surfacing unknowns. As the team synthesises findings, Define work emerges: agreeing the problem statement, scope, and recommendation. A Discovery that ends without a converged view of the problem has not finished its first diamond.

Alpha bridges both diamonds

Alpha is where the frameworks overlap most. Teams may still refine the problem frame (Define) while also prototyping solutions (Develop). Alpha's purpose — test the riskiest assumptions cheaply — means the dominant mode shifts from understanding to exploring options, but convergence begins as the team decides what Beta will build.

Beta and Deliver

Beta is primarily Deliver: building the real service, testing with real users, and converging on something that can scale. Iteration continues, so pockets of Develop appear when new features are explored, but the organising question is whether the service works in production.

Live is ongoing Deliver

Live extends Deliver indefinitely — operating, measuring, fixing, and improving. Major changes may trigger mini-cycles of Discover and Develop within Live, even if the team does not formally restart Discovery.

Why the mapping is not one-to-one

Diamonds can recur inside a single sprint. Phases span weeks or months. A team in Beta can still do Discover-style research on a new user group. A Discovery can include throwaway prototypes to test understanding. The frameworks answer different questions: the Double Diamond asks “are we exploring or deciding?” The phases ask “what stage of delivery are we in, and what evidence do we need to proceed?”

Using both on the same team

Name both dimensions in planning. Example: “We are in Beta (delivery stage), running a Develop spike for the new notification flow, and we will converge by end of sprint.” That clarity helps researchers, designers, and engineers align on what kind of decision the team is trying to make.

The Service Standard sits alongside both — it is the quality bar regardless of which diamond mode or phase you are in.