launch-planlisted

Launch based on the size of the bet, not the size of your ambition. Most features deserve a silent or soft launch. Save the big-bang for genuinely new products or major pivots. Linear's principle: launch early, launch often, launch multiple times. ## Launch Tiers ### Tier 1: Silent Launch Ship it, turn it on, see what happens. No announcement. **Use for:** Bug fixes, minor improvements, internal tools, infrastructure changes, experiments. **Checklist:** - Feature is behind a flag or gradually rolled out - Monitoring/alerting is in place - Rollback plan exists - One person is on point to watch metrics for 24 hours ### Tier 2: Soft Launch Ship it, tell existing users, collect feedback before going wide. **Use for:** New features for existing users, significant UX changes, pricing changes, beta programs. **Checklist:** - Changelog entry or in-app notification written - Help docs updated (or created) - Support team briefed with FAQ - Feedback collection mechanism in place (survey, feedback button, Slack channel) - Known limitations documented - Rollback plan exists - 1-2 week feedback period before going wide Example: Launching real-time collaboration — Changelog: "Edit together, see cursors live." Support FAQ covers latency expectations and max concurrent editors. Roll out to 20% of teams for 3 days via feature flag, then 100%. Rollback: disable WebSocket sync, fall back to polling. Feedback widget live for 2 weeks. Success metric: % of teams with 2+ simultaneous editors