The Case of the Evolving Dashboard Part 2 | 2012

THE CASE OF THE EVOLVING DASHBOARD PART 2

In another effort for performance analysis transparency (see link and link) and to demonstrate my work, I have revealed my season reports for Cardiff Celts.  Cardiff Celts is a volleyball team I coached and analysed for last season.  I have written about my evolving dashboards in the past but I could not display every dashboard I have created due to confidentiality.  However, I have been given consent from all Cardiff Celts players to post these particular dashboards.

MID-SEASON REPORT

This was a mid-season report I built during the Christmas break.

Good Points:

* The use of the team logo and photo to personalise the report.

* Showing a minimum line of performance as a guide for what is a good or bad performance.

* The text box in the “Points Efficiency Ratio (PER) Tracker” to explain the importance of the PER statistic.

Bad Points:

* Overall it looks cluttered and data-heavy.

* The “Efficiency Ratios (ER)” and “Percentage-In Statistics” graphs does not reveal the importance of the data.

* The “Service and Reception Rating” graph is good that the bigger the circle the better.  However, it is hard to understand what it means as an individual player.

* The overuse of the conditional formatting, i.e. the bars showing the value in the cells in the “Player Statistics” and “Match Tracker”.  I originally liked it but upon player feedback and self-reflection, it does not add any value.

* The use of the maximum, minimum, 25% quartile and 75% quartile  performance level in the “Points Efficiency Ratio (PER) Tracker” graph is interesting but no effect in its understanding.

* The audience was not taken into account.  The dashboard should have been simpler and data-light because player knowledge of volleyball statistics was virtually non-existent.

Good Points

* All of the data is there.

Bad Points

* The conditional formatting does not look great. * Too much colour?

END OF SEASON REPORT

I created this End of Season Report to complete the season.  I made some changes to make it player friendly.

How it was improved?

* Graphs and data removed to make it data-light and simpler. * Both graphs explain what it was trying to show. * Player Statistics is simplified to total counts of the scoring skills.  The conditional formatting was moved to the neighbouring cell to make it look like a neat bar graph.

What could still be improved?

* The best performer and fifth best performer in the Player Statistics always have a full bar and a slim bar respectively.  It needs to consider the worst performer too so the bars differ. * An explanation of why the hitting percentage is important.

How it was improved?

* The conditional formatting is gone. * Less colour adds to the perceived simplicity.

What can be improved?

* Empty data (all the zeros) can be replaced with blank cells or with dots to again make it look less data-heavy. * Players can be organised according to shirt number?

THOUGHTS?

I would be interested to know what other people’s thoughts are.  There aren’t many dashboards out there to compare it to (Jamie Ensom has a nice example on his blog) so I would appreciate any comments (see below).