Listening: Feature Launch Demo Call
An internal feature launch demo call. 3 questions on phased rollout vocabulary, feature flag language (gated, kill the flag), and post-launch monitoring terms.
Feature launch vocabulary — key terms
- phased rollout — gradual release to increasing user percentages; lower risk than big-bang
- gated behind a flag — feature only accessible when the feature flag is enabled
- kill the flag — urgently disable the feature flag as an instant rollback
- spike in tickets — sudden increase in support tickets; signal of user-facing problems
- pause the rollout — stop expanding; hold at current % while investigating
0 / 3 completed
1 / 3
Internal launch demo: "We're not doing a big-bang release on this one — we're going with a phased rollout. We'll start with internal users this week, then five percent of prod traffic next week, and full rollout two weeks after that if metrics look good."
What is a phased rollout, and what is the alternative implied by "big-bang release"?
What is a phased rollout, and what is the alternative implied by "big-bang release"?
Phased rollout = releasing a feature incrementally to progressively larger groups of users — reducing risk by limiting the blast radius of any issues that emerge.
Big-bang release = deploying to all users simultaneously. Higher risk — if something goes wrong, everyone is affected immediately.
Typical phased rollout stages:
Big-bang release = deploying to all users simultaneously. Higher risk — if something goes wrong, everyone is affected immediately.
Typical phased rollout stages:
- Internal / dogfooding — team members use it first
- 1-5% of traffic — small real-user cohort; monitors for unexpected issues
- 10-25% → 50% → 100% — progressively wider rollout
- rollout — the process of deploying to users gradually
- "if metrics look good" — conditional: the next phase only proceeds if key indicators are healthy
- prod traffic — real production users (not test or staging)