"A/B testing is a side effect of controlled release. That’s what I love most about Split."
"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 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.”
"Split’s full-stack experimentation platform has been built with engineering and product teams in mind. Its robust architecture and rich feature set integrates into our internal platforms and helps power experimentation across our entire engineering organization."
“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.”
“By decoupling experimentation decision-making from engineering Resources [with Dynamic Configuration], product teams become empowered to make fast and flexible changes to the product with little to no technical knowledge.”
"Using Split with FullStory allowed us to humanize our experiments and empathize with our customers by validating the quantitative results with real user sessions that revealed how customers felt when interacting with our features."
"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 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.”
"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."
"Leveraging Split with our existing tool stack, we’ve been able to consolidate our agile deployment strategies to deliver every three weeks from an original 1.5 months."
"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. Together with Split, we can now make that easy."
"Our team uses Split feature flags to deploy quickly and experiment with new ideas. Feature Monitoring gives us a safe way to release features to our global user base with less risk."
“We had the intention to change the password field, but we didn’t have a way to know how good it was effectively, and to be able to control it in-house, within our product team. Split allowed us to do all of that and more.”