“If we build it we have to test it to make sure it’s doing the right thing. When we conduct backend experiments, we have to know the system will remain reliable. We have to make sure the backend behaves in a way that doesn’t impact the user experience.”

"At the point engineers make deployments live, they want to understand how the features are performing, from a customer experience, user value, and system standpoint. We know that one of the big challenges developers face in understanding impact is how to get all of the data in the first place. …

"Split allows us to safely merge code with confidence."

"It’s powerful to think about all features launched before Split and how many of those must have cost us money that we don’t know about."

"As we improved our checkout process relying on Split to measure the impact of our changes, we saw an overall increase in conversion year over year, and that’s made a huge difference on our bottom line."

“If we built this in-house, most engineers would look at this and say ‘feature rollout, it’s not that hard’. But when you think about having multiple environments, having a UI, conditional filters, an impression data pipeline, all that—it’s a whole team working for a very long time to be able …

"One of our first experiments was a great learning experience. It prevented us from introducing something that we thought was good, but actually would have likely given us a negative impact. We’re now doing another iteration to get it right."

"We use feature flags and run experiments a lot more because it’s easier now with Split. We can target a random sample size. We can increment the size of that sample really easily, and we can toggle it off immediately if there’s an issue."

"Split has been instrumental in our push to true agile processes. The ability to divorce deployment from release via feature flags has had an outsized impact in our ability to deliver new products to market faster than our competitors. With the addition of configurations we can externalize values and settings …

"To balance rapid development with the high availability our customers demand, we needed total control over releasing new functionality. To build and maintain such a system would have taken extensive time and resources. With Split, we're getting the features we need today along with the help of a team of …

"Split is incredibly empowering for product managers. The web console consolidates and provides transparency into every release, while also enabling teams to make changes dynamically without relying on engineering. With Split, engineering and product teams can collaborate to more efficiently to create, manage, and complete rollouts that much faster.”

“We have in total about 14 teams working on our digital asset management platform. All of the teams are using Split."

"Split's controlled release capability provides us a non-disruptive and dynamic way to ship features for testing and deployment. More importantly, it provides the data we need to quickly iterate on our product features in an informed manner.”

“Split provides so much more than just a tool set change in that respect. You know, it sounds simple, feature toggles, but it’s transformative in nature. It’s transformative in terms of the teams, in terms of the culture that we adopt.”

“Split’s Azure DevOps integration has simplified our workflow by allowing our developers to create new flags directly in the boards. The linkage between work items and feature flags is a big plus because it streamlines the process of knowing when all work is completed for a single feature, helping us …