Ad Hoc Reports First, Automated Metrics Second
Change is difficult. Value illusive. Implementation of new organizational performance measures represents both change and sought after value, either of which can render the time and resources spent creating the new measures worthless. Consequently, it is incumbent upon those seeking to introduce the new measures to effectively test for acceptance and value contribution before committing the significant time and resources required for their development and implementation.[wcm_restrict plans=”41617, 25542, 25653″]
In our experience, we found the introduction of new or updated performance measures by way of reports provided a platform for testing acceptance and value of the proposed metrics while greatly reducing the total level of effort expended on their implementation. These reports provide information similar to or illustrative of that which the final performance measure will contain and are manually developed. Leaders and contributors who would use the metric vet the report; providing critical feedback used to adjust the measure prior to its development within an automated reporting system. Savings in realized by eliminating costly programming of low value metrics that are seldom, if ever, used as well as avoiding more costly refinement of performance measures already configured within a reporting system.
Temporary reports should be used for several reporting cycles (quarterly, monthly, weekly, etcetera) to confirm their acceptance and validity prior to reporting system configuration. This practice helps further validate the performance measure’s:
- Reporting periodicity
- Trend information
- Action thresholds
- Data aggregation and calculation methods
- Data sources
- Graphic layout and design
Once these characteristics have been individually vetted and approved, a design specification for the performance measure can be written and implemented. Use of multiple vetting cycles is important as without them the organization is at great risk of going through several costly iterative changes to the system configured performance measure before obtaining an acceptable version.[/wcm_restrict][wcm_nonmember plans=”41617, 25542, 25653″]
Hi there! Gain access to this article with a StrategyDriven Insights Library – Total Access subscription or buy access to the article itself.
Subscribe to the StrategyDriven Insights Library
Sign-up now for your StrategyDriven Insights Library – Total Access subscription for as low as $15 / month (paid annually). Not sure? Click here to learn more. |
Buy the Article
Don’t need a subscription? Buy access to Organizational Performance Measures Best Practice 18 – Ad Hoc Reports First, Automated Metrics Second for just $2! |
[/wcm_nonmember]
Leave a Reply
Want to join the discussion?Feel free to contribute!