Image courtesy the BCG |
Rick Weaver posted an article about measuring project success and the impact Cloud services could have on these measures. One of his measurements focused on an "Innovation Ratio" where we consider how much we are spending on reducing technical debts versus the amount of new capabilities we are adding. More simplistically put:
Amount spent on reducing technical debts
Innovation = ------------------------------------------------------------
Amount of new capabilities added
To me we could keep this very simple on figuring out hard numbers of Innovation. Consider what are you spending to ensure your current technology does not become obsolete? Are we buying the latest and greatest versions or upgrading legacy equipment? Are we removing manual systems that lead to errors?
And then capabilities are easily accounted from a basic features list. What can you do now that you could not do before is a great measurement for any change project or initiative. Those are the benefits that are quickly tangible! You can worry about culture change and measuring shifts in dynamics later once you have buy-in with your metrics!
So where to look for these things? Again, keep it simple - where are you manually addressing processes? Where are you using outdated technology (easy answer is where do people ignore the technology provided and instead use their own manual process - these are anyone creating their own spreadsheets and databases or emailing items or worse, printing!!)?
What ideas do you have? Again, this equation struck me as a great way to help MEASURE INNOVATION and the value that you are bringing to an organization!
No comments:
Post a Comment