Follow the data Validate before build
What did people do, and what should change?
A fast build only proves that software can be made. Protopilot makes the costly problem, the claim that could fail, and the smallest testable experience part of one evidence chain.
Direct answer
Use what people do to decide what changes next.
- Question
- Will product leads create a tester flow before asking engineering to build?
- Method
- The costly problem, claim that could fail, and smallest testable experience in one evidence chain.
- Expected signal
- Returned evidence changes the assumption that requested it—or honestly keeps the claim open.
Build-first interruption
Output is not a decision.
Speed compresses the build, not the uncertainty. Without an explicit audience, costly situation, and falsifiable claim, polish is only harder to question.
Move the question ahead of the build.
One transforming artifact
How the decision is tested.
Each space changes the same research object. Nothing downstream floats free of the assumption it is meant to test.
-
Problem space source material
Make the expensive guess visible.
- Purpose
- Help product teams test the assumptions beneath an idea before they commit to building it.
- Audience
- Product teams using AI-assisted builders who need evidence before committing engineering time.
- Persona
- Product lead — Leads a small product team and worries that AI speed turns untested assumptions into commitments.
- Blocking problem
- Teams turn untested assumptions into polished software too early, making it expensive to learn whether a real problem exists.
-
Hypothesis space risk turned into a claim
Give the belief a way to lose.
H-03 Solution claim · usage test“After framing a problem and hypotheses, product leads will create a tester flow before asking engineering to build.”
If the action does not happen, do not add features. Revisit the claim or the problem framing.
-
Solution space minimum test instrument
Build only what the claim requires.
01 screen Establish Context
Capture the audience, persona, and costly situation before choosing a solution.
02 screen Make assumptions falsifiable
Turn beliefs into linked hypotheses with a confidence and test method.
03 screen Compose a tester flow
Connect a prototype journey and screener to the assumption it should test.
Domain objects Project → Assumption → Test flow
Design language Connected space switcher + evidence status
Stop condition The tester can attempt the H-03 action