English for Feature Flag Rollouts: Talking About Progressive Delivery
Vocabulary and phrases for discussing feature flag rollouts in English: canary releases, percentage rollouts, ramping up, kill switches, and rollback decisions.
Feature flags let teams ship code to production but control who sees it, and when. Instead of a scary all-at-once release, you roll a feature out gradually — to 1%, then 10%, then everyone. Talking about these progressive rollouts requires specific English: ramping, cohorts, kill switches, and the diplomatic phrases for deciding when to push forward or pull back. Here’s the vocabulary.
Core vocabulary
| Term | Meaning |
|---|---|
| Feature flag / toggle | A switch that turns a feature on or off |
| Rollout | The process of releasing to users gradually |
| Canary | A small initial group that tests the change |
| Ramp up | Gradually increase the rollout percentage |
| Cohort / segment | A defined group of users |
| Kill switch | An instant off-switch for emergencies |
| Dark launch | Deploying code that’s off by default |
The verbs matter: you flip or toggle a flag, roll out to a percentage, ramp up (increase) or dial back (decrease) exposure, and kill a feature instantly if it misbehaves.
“We dark-launched the new search last week — the code’s in production but toggled off. Today we’ll flip it on for the canary cohort.”
Describing the rollout stages
A typical progressive rollout has stages. Narrating them clearly keeps everyone aligned.
“Here’s the plan: dark launch today, then canary at 1% tomorrow. If metrics hold, we ramp to 10%, then 50%, then general availability (GA) by Friday.”
Useful phrasing:
- “We’re currently at 10%.”
- “Let’s bump it up to 25%.”
- “I’d hold at this percentage until we see a full day of data.”
- “We’ll go to 100% once the error rate stays flat.”
General availability (GA) means the feature is fully released to everyone — important vocabulary.
Talking about who sees the feature
Rollouts target specific groups. The vocabulary of targeting:
| Term | Meaning |
|---|---|
| Allowlist | Specific users who get the feature |
| Percentage rollout | A random X% of users |
| Internal-only | Just employees / dogfooding |
| Beta cohort | Opt-in early users |
| Sticky bucketing | A user stays in the same group consistently |
“Let’s start internal-only — dogfood it with the team — then open it to the beta cohort before any percentage rollout.”
Dogfooding (using your own product internally before customers do) is essential tech vocabulary. “Eat your own dog food.”
Phrases for the go / no-go decision
The heart of a rollout meeting is deciding whether to ramp up. This needs confident, data-driven, yet diplomatic English.
Pushing forward:
- “The canary looks healthy — error rate’s flat, latency’s unchanged. I’m comfortable ramping to 10%.”
- “Metrics are green across the board. Let’s proceed.”
- “I don’t see any red flags. Happy to bump it up.”
Holding or pulling back:
- “I’d hold off until we see more data.”
- “Let’s pause the rollout — I’m seeing a small uptick in errors.”
- “I’d rather dial it back to 1% and investigate.”
- “Let’s hit the kill switch and regroup.”
“We’re seeing a slight uptick in 500s in the canary. It’s not catastrophic, but I’d pause here rather than ramp. Let’s give it an hour and reassess.”
The contrast between ramp up / bump up (increase) and dial back / pull back (decrease) is the core verb set.
The kill switch conversation
When something goes wrong, clear, fast language matters.
“The new flow is throwing errors for a chunk of users. I’m killing the flag now — we can debug with it off.”
Phrases:
- “Kill it. We’ll figure out the cause offline.”
- “Flag’s off. Users are back on the old path.”
- “Good news — because it was flag-gated, the blast radius was tiny.”
Flag-gated (controlled by a flag) is a useful adjective. The whole value of flags is that recovery is instant: “we just flip it off.”
Before and after: a full rewrite
Before (vague and anxious):
“the new feature is on for some people. I think maybe there are some errors? should we make it for everyone or not? or turn off?”
After (structured, decisive, diplomatic):
“Status: new checkout is at 10% via percentage rollout. The canary was clean, but at 10% I’m seeing a small uptick in timeout errors — about 0.3%, up from baseline. It’s flag-gated, so we’re safe. My recommendation: hold at 10%, don’t ramp further, and investigate the timeouts. If it worsens, I’ll hit the kill switch. I’d hold off on GA until this is resolved.”
Common mistakes
- Confusing “roll out” and “roll back.” Roll out = release gradually (forward). Roll back = revert (backward). They’re opposites; don’t mix them.
- “Ramp up” vs “ramp.” You ramp up (increase) or ramp down (decrease). “Ramp the feature” alone is ambiguous.
- Saying “open the feature” wrongly. Natives say “open it up to the beta cohort” or “turn it on for,” not “open the feature to users.”
- Forgetting “GA.” General Availability is the standard term for “released to everyone.”
Mini-glossary
- Targeting rules — conditions that decide who sees a flag
- Stale flag — an old flag that should be removed
- Flag debt / cleanup — removing obsolete flags
- A/B test — comparing two variants for impact
- Holdback — a group deliberately kept on the old version for comparison
- Bake time — how long you wait at a stage before ramping
“Let’s give it some bake time at 50% — a full business day — before we go to GA. And remind me to schedule flag cleanup once it’s stable.”
Key takeaways
- The verb pairs are everything: roll out / roll back, ramp up / dial back, flip on / kill.
- Narrate the stages: dark launch → canary → percentage rollout → GA.
- Make go/no-go calls with data: “canary looks healthy, ramping” or “small uptick, holding here.”
- Remember the feature flag superpower: it’s flag-gated, so rollback is instant.
Progressive delivery is calmer than big-bang releases — and so is the language. Speak in stages, lead with the metrics, and always know where your kill switch is.