5 / 67 · 06 Observability-Driven Testing · Testing in Production Using Feature Flags← prev ⊞ all next →☰ Read as one page

1.5Feature Flag Hygiene

Feature flags that remain in the code indefinitely become technical debt. Implement a cleanup process:

Flag Age	Action
< 7 days	Active rollout -- leave as-is
7-30 days	Should be at 100% or rolled back
30-90 days	Schedule cleanup ticket
> 90 days	Flag is technical debt -- prioritize removal

Consistent naming makes flags discoverable and their purpose clear:

{team}-{feature}-{version}

Examples:
  checkout-ai-summary-v2
  search-semantic-ranking-v1
  onboarding-new-flow-q1-2026