Another real-life scenario where Feature Flags minimized revenue impact by allowing on-time behavior change.
On our previous blog post we showcased a real-life scenario where Remote Flags can solve possible delay issues on e-commerce sales cycles, by allowing deploys and tests to be done beforehand and putting the control of the Sale Season start on the hand of the business, product or sales manager which, with a switch of a feature flag, is able to turn it on instantly.
In this scenario, we can clearly understand the advantages of using a feature flag to guarantee that a specific "go-live" is achieved at the expected moment without hiccups. But you might be thinking, "what if my development teams prepare a change, beforehand, that applies automatically at that specific time? Why would I need a feature flag?"