I've worked as a team lead/developer in a large financial enterprise environment for the better part of three years. Our production release process is a nightmare because it revolves around Clearcase. We have a change management group who executes all releases and who will only allow code into production that was taken from it.One of the first things I did when joining was to set my team up with Git. Everyone agreed that Clearcase was awful and was impractical for handling day-to-day source control matters. So we set up a sort of unofficial repository on my local machine and I wrote a script to sync our git and Clearcase repos around release time.Word of this spread to other teams and several have adopted the same process. Using git in an unofficial manner for day-to-day activities and officially using Clearcase for releases. I've become sort of the go to guy for any issues with Git.So I have a meeting this week with the SVP in change of infrastructure who specifically wants me to explain to her the merits of Git. Word apparently got to her of my frequent rants on Clearcase. If she accepts my arguments, I will have a real shot at helping my employer rid themselves of this abomination. My experience with executives tells me they a) want extremely terse explanations for everything b) are only interested in facts that involve dollar figuresTo a developer I can explain the merits of Git over Clearcase (or ANY other version control system over Clearcase for that matter), but I'm drawing a blank on how to do this to a technical executive without a technical background (she has an MBA and did her undergrad in geography). I feel any argument I make to her is either going to sound like technical gibberish or that I'm evangelizing my personal preferences.What I'm trying to find are concrete facts demonstrating developers work more effectively with Git, or ANY modern source control system. I think that the fact the other teams have started using Git internally is a meaningful sign, but it's still not strong enough because it can still be dismissed as personal preference.What I really need is something powerful enough to break through the This process has worked for 20 years, why should we change it? argument. 
Quantifying the advantages of a modern version control system
version control;business process