Why do people not like Dashboards?
There's a number of reasons that people push back against dashboards becoming the new norm in reporting. Over time I'll discuss in detail but some of the most common complaints are:
- They lack detail
- The raw data is locked away
- Hard to fit onto a PowerPoint slide
- The current process works fine
- People use them incorrectly and don't understand filters potentially creating misinformation
There's a solution for all of these complaints.
Data and Detail:
Dashboards should be used to quickly summarize information, prioritise new actions and re-affirm the current strategy. A lot of senior leaders however get frustrated when they can't see the detail behind dashboards. If sales fell short of the monthly estimate leaders always want to know the cause which is reasonable but the danger lies if we get pulled into the weeds and miss the key points. There's no point assigning 15 actions to 15 account managers to query 15 clients on missed forecasts, you've got to attack this issue strategically.
To avoid this, I recommend two things:
1. Clear expectation that the meeting will only share the dashboard, but that the dashboard owner will highlight and prepare key causes to missed KPI's
2. In the short term, raw data will be published alongside the dashboard until new process is strong enough to do without. Make sure to set a deadline of when this will stop, e.g. 3 months.
If you want your leadership team to lead they have to trust the details to the rest of the organisation.
Current Process is Fine:
People resist change with good reason, it costs time and effort. So it's up to us to:
1. Prove the value of dashboards
2. Highlight the failings of current static presentations
3. Provide a path to dashboards that will not inflate the preparation time vs. current process
Preventing Mis-information:
Data is rarely presented raw or whole in leadership updates with some necessary reductions preventing errors in presentation. Such as removing some previous year sales data in a product not sold in 2016... this reduces the 2015 figures but allows for like for like comparisons.
To prevent dashboards being mis-used like this, it's best to keep access restricted for a few months while people become familiar with your presenting, and then grant access following a short training session
There's a solution for all of these complaints.
Data and Detail:
Dashboards should be used to quickly summarize information, prioritise new actions and re-affirm the current strategy. A lot of senior leaders however get frustrated when they can't see the detail behind dashboards. If sales fell short of the monthly estimate leaders always want to know the cause which is reasonable but the danger lies if we get pulled into the weeds and miss the key points. There's no point assigning 15 actions to 15 account managers to query 15 clients on missed forecasts, you've got to attack this issue strategically.
To avoid this, I recommend two things:
1. Clear expectation that the meeting will only share the dashboard, but that the dashboard owner will highlight and prepare key causes to missed KPI's
2. In the short term, raw data will be published alongside the dashboard until new process is strong enough to do without. Make sure to set a deadline of when this will stop, e.g. 3 months.
If you want your leadership team to lead they have to trust the details to the rest of the organisation.
Current Process is Fine:
People resist change with good reason, it costs time and effort. So it's up to us to:
1. Prove the value of dashboards
2. Highlight the failings of current static presentations
3. Provide a path to dashboards that will not inflate the preparation time vs. current process
Preventing Mis-information:
Data is rarely presented raw or whole in leadership updates with some necessary reductions preventing errors in presentation. Such as removing some previous year sales data in a product not sold in 2016... this reduces the 2015 figures but allows for like for like comparisons.
To prevent dashboards being mis-used like this, it's best to keep access restricted for a few months while people become familiar with your presenting, and then grant access following a short training session