2. Create
Create converts a framed hypothesis into an executable artefact. Once the problem is sharply defined, Create makes it tangible. This phase combines human design judgement with AI-assisted generation to build the smallest artefact capable of producing meaningful feedback. In the AI era, this may include interactive prototypes, thin-slice coded MVPs, workflow simulations, or service experiments.
Design and code do not operate sequentially. They co-exist. The goal is not polish or completeness, but testability. If an idea cannot be expressed in executable form, it cannot be validated. Create makes risk visible by embedding assumptions into something real.
What you'll get
- Interactive prototype or thin-slice working build
- Clear mapping from hypothesis → solution components
- Documented assumptions embedded in the artefact
- AI-assisted technical and design documentation
- Defined validation plan (what will be measured and how)
The objective is not completeness. The objective is testability.
Signal you're searching for: Test Readiness
You can move on to Validate once:
- The artefact can generate behavioural evidence (not just opinion).
- Core assumptions are embedded in something executable.
- Measurement mechanisms are defined (telemetry, interviews, KPIs).
- The team agrees the artefact is sufficient to expose to reality.
If the artefact cannot generate a measurable signal, it is not ready.