“Without Split, rollbacks could take a couple hours to a day. And after that, there might still be a lot of code cleanup. Split helped us increase our engineering velocity and code stability.”
“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.”
"Split gives us an easy and fast way to pull the plug if something goes wrong without a heavy involvement from engineers."
“We have in total about 14 teams working on our digital asset management platform. All of the teams are using Split."
"Split plays a key role in Invoice2go's feature rollout process. By using their product for targeted rollouts, we have full control over any release and an increased confidence in our ability to easily scale over time. In addition, Split's collaborative nature and their focus on their customer's success have made working with them so easy and enjoyable.”
"Thanks to Split, we were able to learn that the risky version actually had the highest adoption by our customers while keeping overall signup conversion steady."
“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 save time, increase our speed-to-market, and ensure a drama-free release.”
"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."
“Split provided the platform and integrations we needed to run full stack experiments for key technical and customer experience questions.”
“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 to do all of that.”
"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 in split directly allowing our product team to pivot quickly and make changes immediately.”
“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.”
"Before Split, our feature releases were cumbersome and time-consuming, requiring our product managers to make special requests to developers every time we wanted to launch new functionality."