The framework
A decision-making operating model built for the AI era.
The Build Loop is a structured four-mode cycle that moves product teams from uncertainty to measured impact. It replaces informal debate with a repeatable protocol that produces evidence at every stage.
Read the full overview in DocsAI removed the build-cost bottleneck. Teams can now ship prototypes in hours. The new constraint is decision quality — building the wrong thing fast is still expensive.
Existing frameworks — Design Thinking, Design Sprints, Lean Startup — were built for a world where speed was scarce. None were designed for the speed-abundant, decision-constrained world we’re in now.
The Build Loop gives teams a four-mode cycle that starts with a framed decision, creates evidence, validates it with real people, and closes with a documented outcome. Every time.
The operating model
Four modes. One complete loop.
Frame
Define the problem before you move. Frame captures the context you're operating in, the person feeling the pain, the business signals making inaction costly, the one decision that needs to be made, and the single metric you'll use to judge the outcome.
Framing well is the hardest part of the loop. Most teams skip it — they start building before they’ve agreed on what problem they’re solving. Frame forces that agreement.
Read more in DocsCreate
Build the smallest working artefact capable of generating real behavioural evidence. Not a deck. Not a Figma file. Something a real person can interact with — a prototype, a landing page, a conversation — that produces signal.
Speed of creation is no longer the constraint. What you choose to create is. The discipline is building the minimum version that will actually teach you something.
Read more in DocsValidate
Test with real people in real conditions. Capture behavioural evidence — what people do, not what they say. Structured observation, not surveys. The goal is to separate anecdote from signal before you commit resources.
Validation without structure is just opinion collection with extra steps. The Build Loop gives you a repeatable protocol for running tests that produce trustworthy evidence.
Read more in DocsLearn
Read the evidence and make a formal decision: Go, Pivot, or Stop. The Learn mode converts behavioural signals into a documented outcome that replaces opinion in future discussions.
Learning without deciding is the most common failure mode in product teams. Loop closes that gap — every cycle ends with a recorded decision, not a meeting.
Read more in DocsBefore you start
The three signals.
Every loop is anchored by three business signals — the real pressures that make inaction costly. Without signals, a loop is a hypothesis. With signals, it's a decision with commercial stakes.
What we mean by signalsA business metric — churn, conversion, ARR growth, margin — is moving in the wrong direction and the team is being asked to act.
Real users are encountering the problem repeatedly and the evidence (support tickets, interviews, drop-off data) has reached a threshold that demands action.
A competitor move, a regulatory change, a platform shift, or a strategic commitment has created a deadline that makes continuing without a decision costly.
Free to start
Frame your first
decision.
Five inputs. Five minutes. A structured document your whole team can act on — and a Loop Plan that follows from it.