Feature Flag
A feature flag is a switch in code that lets a team turn functionality on or off at runtime, without changing the deployed software.
A flag wraps a piece of functionality in a conditional that can be controlled from outside the codebase. Teams use flags to decouple deploying code from releasing it: a feature can ship to production switched off, then be enabled gradually, for specific user segments, internal staff, or a percentage rollout, and switched back off instantly if something goes wrong.
Feature flags matter because they make releases safer and more flexible. They support gradual rollouts, instant kill switches, and targeted access without a new deploy. They also power experimentation: the same mechanism that gates a feature can split traffic for an A/B test or open a beta to a select group.
Flags pair naturally with feedback. Rolling a feature out to a small cohort first lets you gather reactions before everyone sees it, and a flag gives you an instant way to respond if that feedback turns negative. Releasing to those who asked for a change, then listening, keeps the feedback loop tight.