Feature Flags: The Decisions That Matter
Switches that turn features on or off at runtime, for gradual rollouts, testing and quick rollbacks.
Marcus Adeyemi
Why does it matter?
Flags separate deploying code from releasing features, which reduces risk, but unmanaged flags become permanent complexity.
What are the numbers?
- Gradual rollout features can be enabled for a percentage of users
- Kill switches problem features can be disabled without a deploy
- Debt old flags accumulate in the codebase
- Testing both flag states need testing
What should I do?
- Name flags clearly with owners
- Set removal dates when creating flags
- Test both states
- Use flags for risky releases
- Audit and remove stale flags
What should I avoid?
Avoid:
- Flags that live for years
- Nested flag conditions
- Flags with no owner
- Untested off states
When should I get help?
Short answer Bring in help when releases need staged rollouts.
Where this comes from
- Microsoft Learn — Feature management
- Laravel Documentation — Pennant
The figures and practices above come from the sources listed.
Working on something like this?
We take on Web Design & Development work for teams who want it done once, properly. Tell us what you are building and we will tell you honestly whether we are the right studio for it. Start a project.
Where to go next
Spotted something wrong? Report an error on this page. We correct on the page and say what changed.
