Product planning
Choose a workable first release for a product idea
A first release gets smaller by dropping features, not by dropping steps the user needs. Pick one task a person can finish from start to end, list every step it requires, and cut only what sits off that path.
A text to start with
My product idea is [description]. The one task a first user should complete is [task]. Walk through that task step by step from the user's side, from where they arrive to where they have what they came for. For each step, say whether it must be in the first release and why. List dependencies on other teams, systems or decisions. Write one sentence saying how we would know the task was completed.
Example request. Change the details to fit your situation.First release scope sheet
User and the one task: [ ] Starting point for the user: [ ] End point (what they have when done): [ ] Step 1 (included or excluded, and why): [ ] Step 2 (included or excluded, and why): [ ] Step 3 (included or excluded, and why): [ ] Step 4 (included or excluded, and why): [ ] Work explicitly left out: [ ] Reason it can wait: [ ] When it will be reconsidered: [ ] Dependencies (system, team or decision) and owner: [ ] How the user recovers from a mistake: [ ] Completion criterion, observable: [ ]
Exclusions that break the task
Trace the proposed task using the included steps. Look for missing actions such as signing in, correcting input, seeing confirmation or getting help. If the release stops before the task is complete, specify the remaining manual process and confirm it is acceptable for the intended use. Check the reason for each exclusion. Identify dependencies whose owners have not agreed to deliver them. Define completion in terms of what a person can accomplish, with evidence you can check in the build.
Ask another agent to check the result
Act as a first user and attempt the stated task using only the included steps. Quote the first step where an exclusion, missing dependency or missing recovery path makes completion impossible. Then flag any completion criterion that cannot be observed.
Walk the scope with the people who build it
Read the step list aloud with the people who will build and support the release, and ask them to find any missing step or any dependency they cannot meet. Update the sheet with their answers. For each excluded item, note when it will be reconsidered so exclusions do not turn into silent promises. Keep the completion sentence at the top of the sheet so later scope debates can be measured against it.