How Experian Increased Release Velocity by 50x

Experian Case Study

With 3,000 Experian employees working in product management and software engineering, cross-functional teams relied heavily on one another to ensure their feature releases were safe and had little exposure to risk. Read the case study to learn more.

Illustration

Discover how people are using Split to improve their lives.

Download Experian Case Study

Discover the whole story

What Problem Did Experian Need to Solve?

Experian needed to coordinate large releases to happen all at once. Their previous process left team members stressed about “big bang” releases that often occurred at the end of the day. Their goal was to implement small releases continuously throughout the workday. Before Split entered the picture, it was debilitating for teams to collaborate simultaneously across the company’s multiple time zones. Now, releases are happening seamlessly, around the clock.

From Two to 100 Releases Per Month

Mirza Baig, VP of Engineering, talks about the value of adopting feature management best practices and the ROI he has seen from empowering and enabling teams with Split. Get insights on how Mirza skyrocketed his team to increase releases from two to 100 per month!

Mirza Baig Experian case study
“Split provides so much more than just a tool set change. 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.“

Learn Why Agile Businesses Choose Split

Watch this engineering-focused session to explore the Experian team’s process to drive culture change, speed up deployment cycles, and scale operations at such an impressive scale.