What does readiness really mean?

At Habañero we offer a .NET Readiness program that improves the way an organization's development team uses Microsoft development tools and languages. This could be through a migration to Visual Studio Team System 2005 or by moving to a patterns-based development environment using the Microsoft Enterprise Library and its supporting Application Blocks.

Each time we've worked with a development team through some sort of readiness exercise, there is a tendency to focus on the tools, or the .NET Framework, or the C# language itself. What I find interesting is that each team approaches readiness in their own way and from their own perspective. How does an organization measure success of this kind of effort? If you look at the definition of readiness – "the state of having been made ready or prepared for use or action" – it's not so much about results, but it would certainly help to create buy-in if some kind of measurable benefit could be attributed to this investment of time and money. I'm still searching, and will post more details when I find something useful.