Product Task
Plan a controlled product release
A change is ready for real use, while broad exposure could reveal a product or operational problem too late.
“This is costing me release confidence because one failure could reach every user before the team can respond.”
Outcome
The result to aim for
Choose the initial audience, stages, health signals, owner, and stop or rollback response before exposure grows.
Best practices
- Bring a release-ready flagged change, technical rollback path, health signals, support capacity, and accountable owner.
- Choose the initial audience and each later stage from product risk, support capacity, and the evidence needed before expansion; then record exclusions and known representation limits.
- Enter the approved stages and durations in LaunchDarkly; then have a second authorised reviewer compare the configuration with the plan before starting; then monitor health outside the rollout control.
- Confirm that every stage has a purpose, owner, health review, and expansion decision.
- Do not start when stopping cannot protect users from the material risk.
Related sources
Further information
- Documented guidance: Hacker News: Ask HN: How to properly manage a product roadmap?
- Related guidance: GOV.UK Service Manual: How the beta phase works
- Related guidance: LaunchDarkly: Creating and managing progressive rollouts