Define the problem, build against agreed priorities, test real integrations, then decide what should happen next. Scope and timing are set from evidence, not assumed upfront.
Four stages, one chain of decisions.
Delivery Circuit
Active: Discover. Make the outcome, users, operating context, dependencies and constraints explicit. Related items: Input: A decision owner, the business outcome, user context, current systems, and relevant technical access and documentation., Work: Map constraints, dependencies, operating responsibilities, and acceptance scenarios with the people who own the decisions., Output: An agreed brief and a visible dependency map., Next decision: Approve the delivery direction and the priorities that move into design.. Connections: Discover leads to Design and Build. Launch and Evolve returns evidence to Discover.
Diagram details
Discover
Make the outcome, users, operating context, dependencies and constraints explicit.
Input: A decision owner, the business outcome, user context, current systems, and relevant technical access and documentation.
Work: Map constraints, dependencies, operating responsibilities, and acceptance scenarios with the people who own the decisions.
Output: An agreed brief and a visible dependency map.
Next decision: Approve the delivery direction and the priorities that move into design.
Design and Build
Translate agreed priorities into architecture, interfaces and reviewable software.
Input: The approved direction, priorities, system constraints, and agreed acceptance scenarios.
Work: Shape architecture, interfaces, and reviewable software around the agreed operating model.
Output: A reviewable increment with its implementation decisions documented.
Next decision: Approve what moves into integration and which evidence is required.
Integrate and Test
Connect required systems and verify agreed scenarios, including errors and recovery.
Input: The reviewable increment, technical access, provider documentation, and acceptance scenarios.
Work: Connect required systems and verify normal, error, and recovery paths against those scenarios.
Output: A release candidate with test evidence and unresolved decisions made explicit.
Next decision: Make the release decision and confirm operational ownership.
Launch and Evolve
Coordinate release responsibilities, observe real operation and choose the next change.
Input: The release candidate, release decision, operating ownership, and observation points.
Work: Coordinate release responsibilities, observe real operation, and review feedback with the decision owner.
Output: Operational evidence and a prioritised record of what should change next.
Next decision: Choose the next change or hold the current state.
Discover leads to Design and Build.
Design and Build leads to Integrate and Test.
Integrate and Test leads to Launch and Evolve.
Launch and Evolve returns evidence to Discover.
What each stage resolves.
01
Delivery stage
Discover
Make the outcome, users, operating context, dependencies and constraints explicit.
Input
A decision owner, the business outcome, user context, current systems, and relevant technical access and documentation.
Work
Map constraints, dependencies, operating responsibilities, and acceptance scenarios with the people who own the decisions.
Output
An agreed brief and a visible dependency map.
Next decision
Approve the delivery direction and the priorities that move into design.
02
Delivery stage
Design and Build
Translate agreed priorities into architecture, interfaces and reviewable software.
Input
The approved direction, priorities, system constraints, and agreed acceptance scenarios.
Work
Shape architecture, interfaces, and reviewable software around the agreed operating model.
Output
A reviewable increment with its implementation decisions documented.
Next decision
Approve what moves into integration and which evidence is required.
03
Delivery stage
Integrate and Test
Connect required systems and verify agreed scenarios, including errors and recovery.
Input
The reviewable increment, technical access, provider documentation, and acceptance scenarios.
Work
Connect required systems and verify normal, error, and recovery paths against those scenarios.
Output
A release candidate with test evidence and unresolved decisions made explicit.
Next decision
Make the release decision and confirm operational ownership.
04
Delivery stage
Launch and Evolve
Coordinate release responsibilities, observe real operation and choose the next change.
Input
The release candidate, release decision, operating ownership, and observation points.
Work
Coordinate release responsibilities, observe real operation, and review feedback with the decision owner.
Output
Operational evidence and a prioritised record of what should change next.
Next decision
Choose the next change or hold the current state.
The inputs that keep delivery moving.
01A decision owner
02Relevant technical access and documentation
03Agreed acceptance scenarios
Make the next decision explicit.
Share the outcome, system context and decision you need to make. We will use that information to frame a focused technical conversation.
