# Some Feature Flag Best Practices

Canonical: https://brew.new/templates/flagsmith/some-feature-flag-best-practices

Brand: flagsmith.com
Category: newsletter

![Preview of Some Feature Flag Best Practices](https://cdn.brew.new/email-preview-9201f12bd70e0bf1-tracking_r57gbpzjav3t2d4xr5nr4y9g8h8dtee3-1788998194546.png)

## Email content

Hi there,

At a base level, feature flags are simple Booleans, but this doesn’t mean they can’t get complex... Keep these best practices in mind to help with technically onboarding flags, keeping them manageable, and getting the whole team feeling confident with a new way of releasing.

1. Keep your feature flag scope-specific.

Start small (e.g. on/off flags). Then introduce more advanced capabilities. Stay aware of nesting—nest multiple flags under a parent flag if needed, but no further.

2. Understand the flag lifecycle and clean up old flags.

Having old, unused features makes managing your flags more difficult and can lead to confusion or conflicts. Trimming unused/expired feature flags will help lessen feature flag debt. (NB: Flagsmith will help automate this for you by labelling “stale” flags and letting you know if a flag is safe to delete.)

Generally, a healthy feature flag lifecycle will look something like this:

• Create your flag

• Build your feature and put it behind a flag

• Deploy your code

• Release your feature

• Clean up the flag—or make it permanent

Adrian

P.S. Here’s a link to an ungated eBook with more best practices and some ways teams are scaling with flags.

Flagsmith, 86-90 Paul St, London, United Kingdom EC2A 4NE

Unsubscribe

Manage preferences

[Open and remix this design](https://brew.new/templates/flagsmith/some-feature-flag-best-practices)

[Browse email designs](https://brew.new/browse/templates)