Best Practices for Short-term and Permanent Flags

Serving over 200 billion feature flags daily to help software teams build better software, faster. LaunchDarkly helps eliminate risk for developers and operations teams from the software development cycle.

This post is by Dawn Parzych of LaunchDarkly

What are best practices when it comes to feature flags? The answer to that as with most questions is “it depends.”

  • It depends on whether the flag is a short-term or permanent flag.
  • It depends on the purpose of the flag.
  • It depends on your specific business needs. What works for one company may not work for you.

This blog series will dive into best practices for feature flags, starting with best practices pertaining to short-term and permanent flags.

Determine whether you need a short-term or permanent flag

The first recommendation is to determine whether a flag will be a short-term or permanent flag as that will influence future decisions and best practices.

Short-term flags

A short-term flag has a limited lifespan. Remove the flag once it has fulfilled its business purpose. When thinking of feature flags, most people think of short-term flags. Types of short-term flags include:

Release: Slowly exposing a feature to new users—moving from internal users to beta and/or canary users until 100% of users are receiving the feature. When you reach 100% remove the flag (unless it is needed as a circuit-breaker as described below).

A/B testing: Segmenting your population to determine a preference for one option over another. Once testing ends, remove the flag, and 100% of users should receive the preferred variation.

Operational interaction testing: When rolling out a new microservice, infrastructure component, or third-party tag, a flag can be used to determine the impact on systems. If the CPU spikes or there is a memory leak, or unexpected errors occur, disable the new element while further troubleshooting takes place.

Kill switches: A toggle to disable a single feature when things start to go sideways during a release.

After reading those descriptions, you may be thinking that a release flag sounds a lot like an operational interaction testing flag. And they are similar. The primary difference is in who is the controller. An operational interaction flag is controlled by the ops team to protect the systems where the release flag is controlled by the product or business owner to control how user adoption progresses.

Permanent flags

A permanent flag is designed to provide control for an extended time after the release of a given feature. In some cases, the flag will be in existence for the life of a feature. Types of permanent flags include:

Entitlements: Giving users access to certain features based on a subscription level or authentication status.

Circuit breakers/Load shedding: Having the ability to quickly turn a feature off or terminate a connection when problems arise prevents problems from impacting all users. These flags are often activated based on an event. For example, a monitoring tool generates an alert when orders fail to complete. When the alert is triggered, a flag is toggled setting the site to ‘read-only.’

White labeling: Configuring the look and feel of an application for each client for a white-labeled solution.

Accessibility: Allowing users to select which accessibility options and refinements they prefer.

Feature flag best practices for all flags

Whether you have a permanent or short-term flag, consider these best practices.

Make flag planning a part of feature design

Feature flags shouldn’t be an afterthought. If you think about feature flags during the design process, you will be setting yourself up for success. Part of the planning includes whether the flag will be a short-term or permanent flag. This decision will then impact other areas such as a naming convention, configuration settings, review and removal processes, and access control and safety checks. We suggest proper planning up front for all flags.

Standardize naming

You may have a style guide for code with conventions on how to write code for your application that includes things like when and where to use camelCase or the proper use of indentation. These style conventions make it easier to read and understand the code.

Before creating your first flag, come up with a naming convention to be used. Our first recommendation is for verbose flag names, don’t try and be brief. You want people to know what the flag does. Verbose flag names can be helpful for others to understand what the flag is doing.

Things to consider when writing the style guide or naming convention.

  • Be descriptive about the flag’s behavior.
  • Include a prefix with a project name or team name.
  • Indicate whether the flag is temporary or permanent.
  • Include a creation date for the flag. (This will be helpful when cleaning up flags, more on this below).
  • Whether or not to use flag in the name. If using a service like LaunchDarkly using flag in the name is redundant. If using a home-grown solution using flag in the name may help clarify the purpose of the code.

For example, you are creating a flag to progressively roll out and test a new chatbox widget of your UI. This will be a short-term flag. Without a naming convention in place, you may end up with a flag called “brand-new-flag” or “new-UI-widget.”

These names don’t tell us a whole lot about this flag. But with a standard naming convention in place that addresses all of the above, you can create a more descriptive flag name like “aTeam-chatbox-widget-temp-030619.” We know from the name, this is a temporary flag for a chatbox widget created by the “a team” on June 3rd, much better.

Minimize the reach of a flag

The focus of a flag should be small. Having a flag that controls more than one feature action at a time can be confusing and will make troubleshooting issues harder. Think about the smallest unit of logic needed for the most responsive flag. If there are multiple parts to a feature that have to work together, you can create a master flag as a dependency.

For example, say you’re launching a new dashboard in your application. The dashboard has three widgets. You should create a total of four flags: one flag for each widget with a dependency on a fourth flag for the main dashboard. With this scenario, if one widget causes problems the dashboard with two widgets can still be served.

Review use at regular intervals

Whether you are creating a short-term or permanent flag you need to review flag use at regular intervals. The frequency at which you review the flags may vary based on business requirements and the type of flag. To avoid accrual of technical debt, review both permanent and short-term flags at a regular cadence.

For short-term flags, look to see if the flag has rolled out to 100% of users, or if a flag is served to no users. For permanent flags, examine whether the flag is still needed—was a feature once part of a premium bundle and is now available for all users.

We will cover specific criteria related to removing short term flags below.

Best Practices for permanent flags

Establish access control and safety checks

If you have regularly scheduled flag clean-up events, you may worry about the accidental removal of permanent flags. Minimize the risk by implementing access control and safety-checks.

Within LaunchDarkly a flag cannot be deleted without confirmation, but that is a partial solution. There are two additional ways to implement access controls for added peace of mind.

  • Use tags and custom roles to assign permissions to flags within LaunchDarkly quickly.
  • Set role-based access control (RBAC) to specify who can delete flags in a given environment.

Best Practices for Short-term flags

Create a process for removing flags before you create one

Coding a flag is a two-part process. The act of removing a flag should not be a separate process from the act of creating a flag. As mentioned above, you should plan for flags during the feature design process. This includes the removal of short-term flags. An easy way to handle the removal process is to write a pull request to remove the flag at the time you create it. Schedule a Github reminder for after the feature is deployed to review and determine if the PR to remove the flag should be committed.

Conduct regular clean-up and review cycles

Avoiding and eliminating technical debt is necessary. If you don’t pay attention to your flags and conduct regular clean-up and review cycles, you can quickly end up with hundreds or thousands of unused feature flags. Here are some ways to schedule flag clean-up.

  • Schedule time at the end of every sprint to review existing flags.
  • Schedule a clean-up/refactoring sprint at a regular cadence (quarterly, semi-annually, whatever works for your business) to pull out old flags & tags.
  • Make it a competition. Hold a “Capture the Flag” day. The individual or team that removes the most flags wins. (Caution: make sure teams aren’t gaming the system and creating fake flags just to delete them.)

Within LaunchDarkly, we make it easier to identify which flags for removal.

You can:

  • Filter tags by create date to view the oldest flags.
  • View which variations of a flag were recently served. Are 100% of users receiving the same variation?
  • Filter on the last evaluation date of a flag.

Once you have identified a flag for removal, use code references to find all the instances of that flag in your code base.

If not using LaunchDarkly a consistent naming strategy can help you grep the code for instances of flags.


Although I refer to these as best practices, other practices may be better. These are recommendations that we follow and have heard from other customers. Over time these recommendations may change as we learn more. These should be seen as recommendations and suggestions, feel free to modify and alter based on your specific needs. What works well for one company or team may not work well for another team. Future blogs in this series will cover best practices and recommendations around specific use cases. If there is a best practice you would like to share please drop us a line.

Look for more best practices blogs coming soon:

Operational flags best practices

Release management flags best practices

Experimentation flags best practices

Entitlement flags best practices

Serving over 200 billion feature flags daily to help software teams build better software, faster. LaunchDarkly helps eliminate risk for developers and operations teams from the software development cycle.
Tools mentioned in article
Open jobs at LaunchDarkly
Solutions Engineer
Oakland, CA
As a Solutions Engineer, you will educate and guide prospects on the proper implementation of LaunchDarkly's SaaS product and Private Instances. You are passionate about trends and technologies involved in modern application development. You will be the technical voice during our sale and ensure our customers are comfortable with the way our systems work. You are passionate about the developer tools space and helping development teams eliminate risk and deliver value. LaunchDarkly is a rapidly growing software company with a strong mission and vision carried out by a talented and diverse team of employees. Our goal is to help teams build better software, faster. You'll join a small team from companies like Atlassian, Intercom, and GitHub, and you'll have an immediate impact on our product and customers. Software powers the world and LaunchDarkly empowers all teams to deliver and control their software.
  • Evangelize and advise customers on the importance and different uses of feature flags and how to administer them
  • Create solutions to customer's challenges implementing feature flags across large monolith and microservice applications, large organizations, and different technology stacks
  • Become a domain expert on LaunchDarkly architecture
  • Demo LaunchDarkly product to technical and business audiences
  • Become a subject matter expert on LaunchDarkly and communicate our value and features to potential customers
  • Be the voice of the customer by translating, aggregating, and representing customer feedback to the Product and Engineering teams

  •  4+ years of experience consulting with enterprise customers and large development teams
  • You led successful technical proof of concepts 
  • Proven success in building strong customer relationships
  • Ability to learn and synthesize large amounts of information with little context
  • Effective communicator with the ability to simplify complex technical concepts
  • A self‐starter and problem solver, willing to take on hard problems and work independently when necessary.
  • Experience working with teams that underwent development process transformation
  • Familiarity with at least one of our supported languages: Java, .NET, GO, JS, Python, PHP, Node, Ruby, Rails, iOS, or Android
  • Experience with data persistence technologies like Varnish or Redis
  • Developer Advocate
    This Developer Advocate role blends expertise from engineering, marketing, and product with the mission of developer engagement. This is done by engaging our community of developers and driving excitement around developer-related technologies. This is a great opportunity to help improve awareness and usage of LaunchDarkly’s technologies through both marketing programs and in-depth engagement with our key accounts. LaunchDarkly is a rapidly growing software company with a strong mission and vision carried out by a talented and diverse team of employees. Our goal is to help teams build better software, faster. Software powers the world and LaunchDarkly empowers all teams to deliver and control their software. About You You love solving problems with software and have an enthusiasm for educating and sharing solutions with your community. You have a background in engineering and a passion for the community. You have passion, curiosity, technical depth, and extraordinary written communication skills. You should have the ability to converse with a broad range of programming language communities (Java, .NET, Node.js, Python, Ruby, iOS, Android, etc.), and have a real passion for modern application development trends at the intersection of development and operations. Our Developer Advocates can be responsible for anything from organizing developer events, to writing production-quality code and contributing to LaunchDarkly’s SDKs. Ultimately, your goal is to empower developers with the tools they need to make their job better. We meet developers wherever they are and support their journey, wherever that may lead.
  • Develop demo applications against our integrations and/or SDKs to showcase the product use case.
  • Collaborate with our Partnerships team to advocate for the developer voice and create impactful content in the form of demos, blog posts, webinars, and workshops.
  • Write about technology trends focused around feature management, modern application architecture with the goal of engaging developers, developer managers, and senior technical leaders.
  • Lead conversations in the community around best practices for feature flag management.
  • Articulate the technical value proposition of LaunchDarkly experience vs competitive solutions
  • Provide cross-audience support and in-depth technical enablement
  • Plan, own and launch technical enablement programs and training course materials
  • Be the local subject matter expert on identified technologies that are meaningful to the company.
  • Minimum 3 years of production-level software development or operations experience
  • Ability to independently build apps, craft solutions, interact with developers and operators to help them learn through the articulation of your experience.
  • Engaging written and verbal communication skills
  • Ability to work autonomously, willingness to travel when need be.
  • Ability to speak on a variety of topics ranging from deep technical talks to strategy and culture. 
  • Known leader or contributor in your community
  • Preferred Qualifications
  • PM experience and/or have experience building communities.
  • A history of successful speaking engagements, industry influence and / or recognition in technology publications
  • Technical Support Engineer (London)
    Note: This Technical Support Engineer position is located at the LaunchDarkly office in Hoxton, London. The hours will be London-based; however there is an expectation of overlapping some Pacific Time hours as well. * At this time our offices are closed due to COVID-19. We are looking for a Technical Support Engineer who will take end-to-end ownership of customer issues, including initial troubleshooting, identification of root cause, and issue resolution. To best serve our customers, you will become an expert in the LaunchDarkly product and develop tools to improve the LaunchDarkly customer experience. You should be a self-starter who works well with little supervision; we trust you to do the right things with little oversight. LaunchDarkly is a rapidly growing software company with a strong mission and vision carried out by a talented and diverse team of employees. Our goal is to eliminate risk and deliver value for development teams. You'll join a small team and have an immediate impact with our product and customers.
  • Become a technical expert on the LaunchDarkly platform (including SDKs)
  • Use this expertise to troubleshoot customer issues and answer questions internally
  • Communicate with customers in a friendly, timely manner
  • Reproduce and document bugs with Engineering for product issues that are impacting customers
  • Create process or troubleshooting documentation in the support knowledge base
  • Contribute to process improvements and new ways to delight customers
  • Represent customers in internal company discussions
  • 2+ years of customer support, technical support, or related customer facing role
  • Technical fluency with one (or more) development platforms: Python, Node.js, Java, JavaScript, Ruby/Rails, Go, .NET, PHP, iOS, and Android
  • Passion for solving customer issues and advocating for their success, in a fast paced, highly technical environment
  • Experience working with APIs or building integrations between SaaS services
  • Ability to learn new technologies quickly
  • Excellent relationship management, customer service and communication skills in variety of forms (written, live chat, conference calls, in-person)
  • Ability to work independently with little direct supervision and as a part of a team
  • Ability to remain calm, composed and articulate when facing tough customer situations
  • Interest in working on technical side projects to validate what you’ve learned
  • Excellent time management skills and ability to balance numerous projects at once
  • Backend Software Engineer
    Oakland, CA
    Software powers the world, and LaunchDarkly empowers all teams to deliver and control the best software. We serve trillions of feature flags daily to help teams ship better software faster and eliminate risk for companies big and small. We're based in downtown Oakland and growing quickly. We're looking for a backend engineer to help us build features, design and implement API methods, and improve the performance and reliability of our systems. We're looking for someone who knows what it takes to deliver value to customers and takes pride in the quality of their work. The core technologies we use daily include Golang, React, Redux, MongoDB, ElasticSearch, Redis, HAProxy, and NATS. LaunchDarkly is a rapidly growing software company with a strong mission and vision carried out by a talented and diverse team of employees. Our goal is to help teams build better software, faster. You'll join a team from companies like Atlassian, Intercom, and GitHub, and you'll have an immediate impact with our product and customers.
  • Build and expand our APIs and services, written in Go
  • Collaborate with frontend engineers to deliver user-facing features
  • Monitor and improve server-side performance
  • Write unit, integration, and load tests as necessary
  • Actively participate in code reviews
  • Write and review technical proposals
  • Improve engineering standards, tooling, and processes
  • 4+ years of experience and fluency with server-side web development (e.g. in Java / Scala, Ruby, Python, Golang, Node.js)
  • Experience building RESTful APIs
  • Strong computer science fundamentals: data structures, distributed systems, concurrency, and threading
  • Strong communication skills, a positive attitude, and empathy
  • You write code that can be easily understood by others, with an eye towards maintainability
  • You hold yourself and others to a high bar when working with production systems
  • You value high code quality, automated testing, and other engineering best practices
  • Experience with NoSQL databases (MongoDB, ElasticSearch)
  • A deep understanding of networking technologies (TCP, HTTP, websockets, server-sent events, etc.)
  • Verified by
    Engineering Lead
    Director Marketing
    VP of Product and Engineering
    You may also like