- Engineering, R&D, or operations leaders with one blocked technical question
- Teams comparing approaches before funding a larger build
- Decision owners who need a prototype supported by test evidence
Sprint / 00 · Flexible technical prototype
Rapid Prototype Sprint
A focused 5–10-business-day build for teams that need useful evidence quickly.
- 01Scope
- 02Investigate
- 03Review
- 04Handoff
How evidence is built
From the initial question to the handoff.
A small prototype can test the key idea before a team funds the larger system.
- 01
Define the question and scope
Translate the blocked question into one primary workflow, success measures, and a written stop condition.
- 02
Build a controlled prototype
Build the smallest useful prototype using approved inputs and documented system interfaces.
- 03
Test and decide
Test the prototype against the agreed measures, document limitations, and recommend whether to proceed, revise, or stop.
Included work
One idea. A testable prototype.
- Problem, decision owner, and success criteria
- Approved data and system boundaries
- A controlled prototype
- Tests, demonstration, and limitations
What you receive
A prototype, test results, and known limits.
- A working, evaluable prototype
- Test results and known limitations
- Architecture notes defining the prototype's scope and interfaces
- A next-stage recommendation or documented stop decision
Engagement fit
The decision this Sprint informs.
Whether the idea can become a useful technical capability—and what should happen next.
- One decision owner
- A safe, representative input path
- Agreed success measures
- Open-ended discovery without a decision owner or success measure
- Production deployment, enterprise rollout, or continuous operations inside the Sprint
- Work that depends on unavailable or unapproved data and system access
5–10 business days