"A/B testing is a side effect of controlled release. That’s what I love most about Split."

"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."

"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.”

"Split has transformed the way that we deliver software. Granular targeting of features to customers has made us more responsive, and data from Split gives us an audit trail in case any issues arise."

"Split has made us more confident in our release process and also more confident in our data decisions."

“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 …

“The thing that’s great about Split is that you can change the behavior of the product outside of a code deployment.”

"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.”

"It’s inherently collaborative and transparent, a rigorous and sound process based on the hard data we know about."

"Split gives me a lot of confidence in our releases as we are able to customize our rollouts, and even roll back quickly if needed. It also allows us to target certain segments that we’d like to release to prior to others.”

"With Feature Monitoring, our engineering team can deploy rapidly while ensuring that new functionality won’t negatively impact our core KPIs such as page load time and errors per user."

"90% of our changes are behind a split (feature flag)."

"The kill button is super easy. Now I just, ‘whoop’, kill it. If we are seeing something wonky, it makes it so easy to turn off. When we’ve triaged the feature we can go back and re-enable it."

"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."

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