The top Indian one-day batsmen

I’ve always been curious… who among India’s prolific one-day run-getters had a good strike rate. This picture below shows you the top 50 ODI run getters for India.

batting-plain-summary

The little squares indicates one player. The size indicates the number of runs scored, and the colour indicates the average strike rate. (Red is poor, green is high).

Firstly, you can see that Sachin, apart from being a prolific run-getter, is slightly above average. The same can’t be said of the next three: Saurav, Azhar and Rahul. The next three however, Yuvra, Sehwag and Dhoni, are as fast or faster run-getters than Sachin – especially Sehwag.

We do have a few low scorers there – Sunil Gavaskar, Ravi Shastri, Mohinder Amarnath, Dilip Vengsarkar, etc.. but allowance must be made for the increase in run rate over time:

In the 1975 World Cup, for instance, the average run-rate in the entire tournament was 3.91 runs per over; in the next edition, in 1979, it dropped to 3.54. Compare that with the run-rate in the most recent edition of the World Cup, when the overall tournament scoring rate exceeded five for the first time, and it’s obvious that the way the ODI is played has changed hugely over 35 years.

For Indian batsmen, the strike rate seems to go up at about 3.4% every decade. Adjusting for that, this is what the picture looks like:

batting-adjusted-summary

These players do look a bit better now, but they’re still fairly slow. The big exception of that generation was Kapil Dev. His strike rate is the only one that rivals Virender Sehwag’s rate today.

Based on this picture, if I were to pick the top 3 fast run-getters across time, I’d pick Kapil Dev, Sehwag and Yusuf Pathan. The slowest would probably be Mohinder Amarnath, Manoj Prabhakar and Sadagopan Ramesh.

We can drill a little deeper into their performance, at a match-level. In the picture below, each box is a match, colour coded by strike rate.

batting-plain-detailed

A pattern emerges here: higher totals (on the top left for each player) are scored at a higher strike rate. This isn’t particularly surprising, however.

Another interesting view is to see how our batsmen fare against the rest of the world. On an adjusted basis, this is what it looks like:

batting-adjusted-world

Shahid Afridi, with an average strike rate of 115 stands way above the rest – and the second player on this list is Sehwag. Interestingly, Afridi has just a few less runs than the legendary Viv Richards, but these have been scored at a much faster rate than even the master blaster.

Visit gramener.com/cricket to see the cricket visualisation live.

The visualisation you just saw is a Treemap. It’s a very powerful way of comparing elements in a hierarchy with relative importance. Some other ways you can use treemaps in a business context are:

  • Profitability by business unit. The colour indicates profits, and size indicates sales. Large unprofitable units stand out clearly.
  • Sales growth by category. The size indicates the category sales, and colour indicates growth over a period.
  • Risk by customer segment. The size indicates the exposure to each segment / sub-segment. The colour indicates degree of risk.