Idea Validation¶
ORCA Framework validation planning turns startup uncertainty into short, explicit experiments.
Purpose¶
Use this workflow to design tests for:
- problem validation
- solution desirability
- willingness to pay
- reachable initial wedge
- early traction signal
Bias¶
Bias toward:
- the smallest credible next experiment
- short feedback loops
- assumption reduction
- reversible learning steps
Validation Artifacts¶
- templates/validation-plan.md
- templates/assumption-test.md
- templates/customer-interview-plan.md
- templates/smoke-test-plan.md
Common Validation Methods¶
- problem interviews
- customer discovery calls
- concierge service tests
- prototype walkthroughs
- landing page or smoke tests
- waitlists
- preorders
- manual MVPs
Decision Rules¶
Good validation plans answer:
- what assumption is under test
- what observation would increase confidence
- what observation would weaken the idea
- what success threshold is good enough for the next decision
- what the team will do if results are mixed
Bridge To Product Work¶
Do not jump into orca-spec just because the solution sounds buildable. Use product-spec work when the team has:
- a clear enough user and problem
- at least one credible wedge
- a first validation path that justifies implementation effort