41 Split Testimonials

Industry
Company Size
15 per page
  • 15
Reset
  • "A/B testing is a side effect of controlled release. That’s what I love most about Split."

  • "Split gives us an easy and fast way to pull the plug if something goes wrong without a heavy involvement from engineers."

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

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

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

  • “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.”

  • "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 …

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

  • “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.”

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

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