We are pleased to announce QuanticMind has selected Split’s feature flag and experimentation platform to streamline development work and deliver innovation faster.
As a growing cloud-based predictive ad management platform, QuanticMind needed to aggressively increase their release cadence, but they saw risk in rapidly releasing new features across their diverse enterprise customers. Their internally-built feature flagging system wasn’t robust enough to meet their needs at scale, which meant diverting engineering resources to make the necessary upgrades. Building new capabilities such as audit trails for changes made to feature flags or establishing access control would take months of effort.
Their engineering team also needed a less cumbersome branching strategy. Reliably merging branches of code into the main branch was a big issue that hindered release velocity, often causing rewrites of existing code to accommodate a new feature.
Split helped QuanticMind separate code deployment from feature release, letting them press the gas pedal on release cadence while gaining full control over the customer exposure to new functionality.
“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.”
Engineers now put all new code behind a feature flag, making every feature rollout an experiment to ensure production stability. They have also significantly improved their branching strategy to reduce the risk of production failure. Code is incrementally merged into the trunk and kept dark from customers until fully functional and thoroughly tested.
The engineering team works hand-in-hand with the Product Management and Quality teams to define feature flags and establish rollout plans. With Split, QuanticMind can safely phase in new functionality across their customer base.
QuanticMind has achieved the following benefits from using Split:
- Reduced their release cadence from 3 months down to a high-velocity continuous delivery model
- Eliminated a 1 week delay of new feature rollouts with an improved branching strategy
- Avoided 3 months of engineering effort to update an in-house feature flagging system
Learn more by reading QuanticMind’s customer story.
Stay up to date
Don’t miss out! Subscribe to our digest to get the latest about feature flags, continuous delivery, experimentation, and more.
At Split we believe in the power of metrics, and are always striving to improve the ways we help our users make more data-driven product decisions. In this previous post we talked about the importance of understanding the impact of a new feature release via key and guardrail metrics. With…
Find faulty features before your customers do One of the most common reasons, our customers tell us, for moving towards feature flags is risk mitigation: the need to make sure releases don’t cause errors for users. Given how frequently organizations are now deploying features, the ability to limit the blast…
Last week we walked The Path To Progressive Delivery. This week, we go deeper. What goals can we meet with the Four Shades of Progressive Delivery? After you read or watch this week’s episode, you will be better equipped to choose a Progressive Delivery approach that works for you. My…