Player Performance Dashboards

In this lesson you will learn the purpose of a player dashboard. A dashboard is a single view that shows how a player is performing against the things that matter for their role. It should answer a question at a glance, such as is this batter's scoring tempo improving, or is this bowler controlling the death overs. A dashboard is not a list of every statistic. Too many numbers hide the message. The best dashboards are designed with the player and coach, focus on a handful of measures, show change over time and make it obvious what to work on next.

• One view of role-relevant performance
• Answers a question at a glance
• Fewer numbers, clearer message
• Shows what to work on next

In this lesson you will choose measures that fit a player's role. For an opening batter you might show runs, strike rate, powerplay strike rate, dot-ball percentage and how they get out. For a finisher, death-overs strike rate and boundary percentage matter more. For a bowler, economy and dot-ball percentage by phase, wickets, extras and boundaries conceded. For everyone, fielding contributions such as catches, run outs and runs saved. Pick four to six measures, explain each one in plain words, and avoid measures that reward the wrong behaviour, such as average alone for a finisher whose job is quick runs.

• Match measures to the player's role
• Openers, finishers and bowlers need different views
• Include fielding for everyone
• Four to six measures, explained plainly

In this lesson you will learn to show performance over time. A single season figure hides whether a player is improving or struggling. Plot each match, or use a rolling figure such as the strike rate over the last five innings, to smooth out the ups and downs. Show the season total alongside, so readers see both the long-term level and the recent direction. Be careful with very small samples, because one innings can swing a rolling figure sharply. Mark matches where context was unusual, such as rain-shortened games or very slow pitches, so nobody draws the wrong conclusion from a dip.

• Show change over time, not just totals
• Rolling figures smooth ups and downs
• Pair recent form with season level
• Mark unusual matches for context

In this lesson you will add context that makes numbers meaningful. Compare a player's figures with a sensible benchmark, such as the league or team average for the same role and phase, rather than with professional cricketers. Split figures by phase, by pace versus spin, or by batting first versus chasing where you have enough data. Note the sample size beside every figure, for example strike rate from eighty-four balls. Context protects players from unfair judgement and helps captains understand what a number really means. If the evidence is thin, say so on the dashboard rather than hiding it.

• Benchmark against league or team averages
• Split by phase, pace or spin, setting or chasing
• Show sample size beside every figure
• Admit thin evidence openly

In this lesson you will learn simple design rules for dashboards. Put the most important message at the top, ideally as a short headline such as death-overs economy improving. Use a small number of clear charts, for example a line for trend, bars for phase splits and a wagon wheel or pitch map where useful. Keep colours consistent, label axes and units clearly, and make sure the layout works on a phone, since most players will view it there. Avoid red and green as the only way to show good and bad, because many people have colour vision deficiency. Test the dashboard with a player and simplify it again.

• Headline message at the top
• A few clear charts: trend, phase, zones
• Consistent colours and clear labels
• Works on a phone and for colour-blind readers

In this lesson you will learn to handle dashboards responsibly. A player dashboard is personal data about an individual. Share it with the player first, then only with coaches and captains who need it, and follow the WFA's data protection and safeguarding policies, taking particular care with under-eighteens. Do not publish individual dashboards publicly or use them to compare players in front of the group. Keep the data accurate, correct mistakes quickly and let players ask questions about how figures were calculated. Used well, a dashboard is a tool for the player's own development, not a league table of people.

• Dashboards are personal data
• Share with the player first, then need-to-know
• Follow WFA data protection and safeguarding
• A development tool, not a ranking