We write about feature management, continuous delivery, and experimentation.
Product teams that don’t take into account a user communication and user feedback collection strategy as part of their experiments risk not getting enough data to evaluate results. This article walks through a couple key communication steps that products should follow to ensure effective and timely product experiments.
Feature flags are just one piece of the puzzle when it comes to adopting a data-driven feature release strategy. By running controlled experiments, your team can make informed decisions before rolling the feature out to the rest of your userbase.
Starting today, you can use Split Feature Flags and Feature Experimentation to drive a consistent experience across devices when developing mobile applications. Read on to learn about the challenges that were unique to developing a mobile SDK and how we ultimately addressed them.
We are thrilled to announce that Twilio has chosen Split as a key component of their experimentation capability to drive faster product decisions.
We are thrilled to announce that Surfline has chosen Split to improve phased rollouts and to help their engineering team scale.
As our software development processes have evolved we’ve mostly said goodbye to the idea of defined product versions. Many modern product delivery teams are taking this a step further – even the concept of a “product release” is starting to fade. Instead our products are becoming a fluid, rapidly evolving set of features, assembled uniquely for any given user.
Following up from the excellent post by Pete Hodgson on Retiring Your Flags, and his presentation at the Meetup we recently sponsored, I wanted to dive into how Split plays a role in managing your flag debt. Feature flags (aka toggles, flips, gates, or switches) are a software delivery concept that separates feature release from […]
Teams working with feature flags usually come to the conclusion that a large number of active flags isn’t necessarily a good thing. While each active feature flag in your system delivers some benefit, each flag also comes with a cost. This blog post explains those costs and how to avoid them.
Feature flagging systems can sometimes become victims of their own success. The benefits of feature flagging along with the broad applicability of the technique can lead to rapid adoption within an organization, and pretty soon the number of active flags can start to feel overwhelming. One way to keep your flags manageable is to introduce a categorization system.
Our product and engineering teams recently did a deep dive with our customers to understand how they used the current Split editor. We discovered several ways that the editor could be improved to save customers time and make it easier to use. Here’s a list of improvements we made to the Split editor.