Successful Scorecarding (part 4 of 5) – Best Practices
Tuesday, June 30th, 2009Craig Colangelo, Sr Consultant at PerformanceG2
June 30, 2009
In this week’s post, I’d like to cover just a few general best practices I’ve discovered along the way. These are simply my conclusions as a project manager and technical leader in a data warehousing group. They are based on my scorecarding implementation experiences at several companies.
I think it’s important to call your first implementation a pilot or proof of concept and to treat it like one. This helps to set the tone for the effort and lets everyone know that this is really the first touch with the technology and methods involved. The implicitly lowered expectations (by calling it a pilot), greater dedication of time (by both you and the business), and greater visibility (allowing for a more focused effort) should help you to achieve a successful first implementation. Be sure to set the expectation that this is a dual benefit effort. Good for the business area you’re scorecarding for as it gives them greater visibility into their own performance and allows them to actively influence outcomes. Good for the IT group as it gives you practical experience with this new tool and the ability to better support it in the future.
Pick a strong subject area. New, important strategic imperatives or aggressive growth plans are usually good candidates as they get the focus that they should. Well defined metrics (both leading and lagging), focused business leaders and analysts, and committed joint effort by IT and the business (make sure it’s stated) are also important success characteristics.
Allow for proper due diligence. There’s always a struggle between faster time to market and a more deliberate, well thought out implementation. A decision should be made upfront as to what’s more important. Make no mistake, scorecarding tools are actual applications. This is not just another means of displaying information. The purpose of the tool is to drive performance. It is not enough to simply build a scorecarding app and release it. Employing the tenants of accountability using the tool, giving the application high visibility, and use of the app during staff meetings all help to ensure that performance is being driven towards the desired outcomes and ultimately aids in the acceptance of the technology.
There are many, many factors involved in determining the success of a scorecarding solution. This is certainly not meant to be an all inclusive list, but rather some of the more important factors I’ve encountered. We’ll continue on with more best practices next week.