Feature Flags and Rollouts
Separate deploying code from exposing behavior to users. · Execution & Communication · Lesson 67 · 3 min
Feature Flags and Rollouts · 3 min
Situation
The code is live for only a few accounts.
Engineering deploys a new search experience behind a feature flag. Internal users see it first, then a beta group, then a small percentage of eligible accounts.
Deployment places code in the environment. Rollout determines who receives the behavior. Keeping those separate can make release risk easier to manage.
Mental model
A flag controls a defined branch of behavior.
Flags can enable a feature for specific users, accounts, or cohorts. A gradual rollout increases exposure as evidence supports it.
The unit of assignment matters. A collaboration feature may need consistent account-level behavior. Random changes between sessions can confuse users and corrupt measurement.
Example
Expand with explicit gates.
Start internally to catch obvious workflow issues. Use a beta group to inspect realistic cases. Expand to a small eligible share while monitoring error rate, task success, support contacts, and operational load.
Agree on the observation period and stop conditions. “No one complained in the first hour” is weak evidence for an infrequent workflow.
Failure case
A flag cannot undo every effect.
Turning off a feature may hide the interface but leave data, messages, or external actions created while it was on. New records may also be incompatible with the old path.
Test disabling and re-enabling behavior, including users mid-task. A flag is a control, not a universal rollback mechanism.
PM decision
Plan the flag's lifecycle.
Name its owner, intended cohorts, monitoring plan, and removal condition. Old flags multiply combinations that are hard to reason about and test.
Also distinguish rollout from experimentation. Exposing a feature to 10% of users does not automatically create a valid A/B test; assignment and measurement need appropriate design.
Remember this
Gradual exposure buys evidence and limits blast radius.
Use that opportunity deliberately. Define who sees the feature, what you monitor, how you stop, and when the temporary control should be removed.