|
A Dashboard in its construction and thinking is much simpler compared to scorecards. I always recommend that scorecard should be designed before a Dashboard. This is because a scorecard will give you a big picture to identify important Dashboard Measures.
Knowing the difference between the 'Dashboard vs. Scorecard', one can pick-up the items relevant for a Dashboard from 'Scorecard Imperatives'. Some additional imperatives are
High Visibility and pictorial
The test of a Dashboard is that one is able to make out the current situation by taking one glance on the same. Therefore maximize dials, traffic lights, numbers in large font, bright exception highlighting, bright demarcation between 'safe range vs. danger range'
Maintain Balanced Frequency of measurements
You can have different Dashboards for real time, hourly, daily OR weekly tracking. A Dashboard should have balanced frequency. While 'Average Customer Call response time' could be an hour by hour track for a large retail customer service company, the same measure may be on daily OR weekly basis for a project oriented company.
Have alerts
A Dashboard works best, if integrated with an email, voice OR SMS alert, which paces the response time.
PLEASE REFER Execution-MiHPractice Tool Dashboard Health Checklist to help you create an effective dashboard.
|
