Beta goals and the decisions they inform
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most betas fail quietly because nobody wrote down what they were meant to prove, so they run for months and end when someone gets impatient.
First tasks
- List the product decisions still open before general release
- Rewrite the riskiest three as questions a beta could answer
- Name the evidence that would settle each question
- Agree the final goals with the design and engineering leads