The flag that stayed forever
A temporary rollout control becomes permanent complexity. · PM Drills · 32 · 30 sec–2 min
The flag that stayed forever · 30 sec–2 min
Situation
A feature flag is still present a year after full rollout.
Nobody knows whether the old path is safe to remove. Tests cover only some combinations of flags.
Think before scrolling
What should have been planned, and what should happen now?
Consider ownership, usage evidence, compatibility, and removal risk.
How a strong PM thinks
Treat temporary controls as lifecycle work.
Identify the owner and actual users of each path. Review dependencies and old records before removing behavior. Plan the cleanup as a controlled change with relevant checks.
For new flags, record a purpose, expiry or review point, and removal condition. Leaving every switch forever expands the set of possible system states and makes future releases harder to understand.
Takeaway
Rollout controls need an exit plan.
The temporary safety mechanism should not become unowned permanent complexity.