Big News! Split to be acquired by Harness. Read More

On a Mission to Kill Release Nights

Split - unnamed-1

It’s known that modern companies, especially the ones that have adopted agile principles, have achieved a faster degree of delivery cadence, deploy many times per day, diminished the risk of each release, and lowered the time to fix defects in production environments.

Feature flags are one of the few key technologies that enables this transformation because it allows you to decouple pushes from releases, but do they really deliver the benefit of “killing the release” night? Do they make it so that software delivery is more of a day-to-day thing when more people are around to help and not the stuff of late night heroics?

Most people are using feature flags to release software during business hours.

I decided to look at the data we gathered a sample from our customers who run more than 300 billion feature flags per month to see what I could find.

For the analysis we show several actions done to a feature flag in production environments, such as creation, updates, rollbacks -aka kills- among others, for the last six months. All timestamps have been normalized to the timezone of the user making the change.

Below you can see that the majority of the feature flag changes take place within the usual work hours of 8 am to 6 pm. Notice the dip in activity mid-day. I joked to my coworkers that feature flags changes also take a lunch break!

In the first graph, we have feature flag changes by hour of the day. You can see Updates (red) include changes to rollout plan and targeting, Create (orange), Kills (green), and Resets (light green).

Split - On a Mission to Kill Release Nights - 1

In the second graph, we focus just on kills to see the clear trend throughout the work day.

Split - On a Mission to Kill Release Nights - 2

Feature flags changes also take a lunch break!

This third graph displays the feature flag change distribution by the day of the week in which they were made. It shows that, indeed, the majority of the changes take place during work weeks and not on weekends.

Split - On a Mission to Kill Release Nights - 3
Feature flag changes by day

Some articles out there talk about the absolute worst time for a deploy (in this context deploy==release). They often mention Monday morning (not enough time to prepare properly), at the end of a work day (as no one will be around to help) and Friday afternoon (similarly, not many people around to help if something goes wrong). Needless to say that the data has shown that companies that use feature flags do indeed release software often and at every hour of the day.

Cheers for a better quality of life after work hours with feature flags! Try Split and feature flags for free.

Get Split Certified

Split Arcade includes product explainer videos, clickable product tutorials, manipulatable code examples, and interactive challenges.

Switch It On With Split

The Split Feature Data Platform™ gives you the confidence to move fast without breaking things. Set up feature flags and safely deploy to production, controlling who sees which features and when. Connect every flag to contextual data, so you can know if your features are making things better or worse and act without hesitation. Effortlessly conduct feature experiments like A/B tests without slowing down. Whether you’re looking to increase your releases, to decrease your MTTR, or to ignite your dev team without burning them out–Split is both a feature management platform and partnership to revolutionize the way the work gets done. Switch on a free account today, schedule a demo, or contact us for further questions.

Want to Dive Deeper?

We have a lot to explore that can help you understand feature flags. Learn more about benefits, use cases, and real world applications that you can try.

Create Impact With Everything You Build

We’re excited to accompany you on your journey as you build faster, release safer, and launch impactful products.