Fast bowling played a far larger role in South Africa than spin did in India
Kartikeya Date25-Feb-2018A review of the ball-by-ball control record for India’s Test series in South Africa earlier this year showed that the hosts won a bowlers’ series because they were able to create uncertainty with greater consistency. The visitors had a bad day first up and lost. This essay is intended as a follow-up to the conclusions of that review. It offers a comparative look at South Africa’s four-Test series in India in 2015-16 and India’s three-Test series in South Africa in 2017-18.The overall comparison between the two series is summarised in the table below. ESPNcricinfo’s control measure classifies each delivery according to whether or not the batsman was in control (IC) or not in control (NIC). The data in the table is organised by bowling team. BB is the number of balls bowled by each bowling team. IC_PER_NIC is the number of in-control deliveries per each not-in-control delivery. IC_ECON is the economy rate conceded from the in-control deliveries. %NIC_RUNS is the percentage of the total runs conceded from the not-in-control deliveries. NIC_BB_PER_W gives the number of not-in-control deliveries required on average for one wicket. %NIC provides the same information as IC_PER_NIC as a percentage. Some readers may find it easier to interpret uncertainty as a percentage rather than as a frequency. The frequency measurement is useful if one keeps in mind that an over includes six deliveries. So IC_PER_NIC above 5 means that uncertainty may not be created every over, while IC_PER_NIC under 5 means that uncertainty is created every over.The series in India was dominated by spin, while the series in South Africa was dominated by pace. The comparative extent of this domination is notable. Pace played a far larger role in South Africa than spin did in India. In India, the host spinners bowled three out of every four overs overall. In South Africa, the host pace bowlers delivered nine out of ten overs. For comparison, in the 2017-18 Ashes, England’s fast bowlers bowled 73% of England’s overs, while Australia’s fast bowlers bowled 69% of Australia’s overs.
SeriesBowling team% pace% spin2015South Africa43572015India26742018South Africa9192018India8317The series in South Africa was dominated by the ball to a far greater extent than was the series in India. Both sides used occasional bowlers in India, while all the overs were bowled by specialists or allrounders in the South African series. The overs delivered by non-specialist bowlers (JP Duminy, Stiaan van Zyl, Shikhar Dhawan, Stuart Binny, M Vijay, Virat Kohli and Cheteshwar Pujara) on both sides have been ignored in the data below. Overall, a wicket cost 19 runs in the 2015 series, and 21.6 runs in the 2018 series. But a wicket fell every 48 balls in the 2015 series, compared to one every 46 balls in the 2018 series. The batsmen were not in control 17.2% of the time in 2015 and 24.5% of the time in 2018. Whatever complaints they might have had about the pitches in India in 2015-16, South Africa returned the favour with interest in 2017-18.Taken together, the data from both series reinforces the view that the difference in quality and depth between the Indian and South African spin attacks is far greater than the difference in quality and depth between the Indian and South African pace attacks. The South African pace attack is better than India’s, while India’s spinners are better than South Africa’s. India’s specialist batting in South Africa was better than South Africa’s specialist batting in India, but this difference is arguably fully explained by the difference in bowling attacks.
Specialist battingBBIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W% NICIndia, 201522346.33.17.09.613.7SA, 201523814.82.011.310.917.3India, 201816013.92.619.411.620.4SA, 201819774.23.112.413.619.2As might be expected, the series in South Africa, dominated as it was by pace, produced a higher share of inadvertent runs (i.e., runs from deliveries where the batsman was not in control) than the series in India. More interestingly both sides found wickets easier to come by in India when they beat the bat than they did in South Africa. In general, pace could be said to create greater all-round uncertainty. Spinners beat the bat less often than fast bowlers, but when they do, they are more likely than fast bowlers to get a wicket.Note that for the purpose of this essay, “beat the bat” may be considered synonymous with “not in control”. It refers to the bowler beating the middle of the bat.
All bowlingBBIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W%NICSA, 201530685.43.078.915.6India, 201529084.32.2118.318.8SA, 201825062.92.92211.225.6India, 201827673.33.11611.423.5A comparison of the two pace attacks in India and South Africa is instructive. It underlines the overall superiority of the South African attack. This can be seen from the greater uncertainty in India’s selection of fast bowlers. But mainly, it is evident from the fact that South Africa’s fast bowling created more trouble for India’s batting in India than India’s fast bowlers did for South Africa’s batting in India.
All fast bowlingBBIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W%NICIndia, 20157565.61.91116.415.2SA, 201513225.22.31010.716.1India, 201823083.03.21711.525.0SA, 201822902.72.82310.926.7Similarly, India’s spin bowling was superior to South Africa’s both home and away. Though R Ashwin and Keshav Maharaj played a limited role in the series in South Africa, Ashwin troubled the South African batting far more than Maharaj did India’s batting. In India, the difference was decisive. Ashwin, Ravindra Jadeja, and to a lesser extent Amit Mishra, allowed India to dictate proceedings in India in a way that Imran Tahir, Simon Harmer, Dane Piedt and Dean Elgar were unable to match, either in terms of creating uncertainty or in controlling the scoring.
All spin bowlingBBIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W%NICIndia, 201520923.92.3117.220.4SA, 201516675.53.468.115.5India, 20184595.43.0910.315.7SA, 20182166.43.61129.013.4In the series in India, the superiority of the Indian spin attack was decisive in the first innings of the matches. This left South Africa playing catch up, often leaving them with no option but to play for a draw. In South Africa, this was not the case. India stayed in the games over the first innings. However, they were unable to control the scoring as well as South Africa did. With the pitches wearing later in the game, the extra pace and height of South Africa’s bowlers proved decisive.
All 1st inns bowlingBBIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W%NICSA, 201517305.53.079.215.4India, 201512663.83.0126.920.7SA, 201814623.12.82212.924.6India, 201815243.13.51413.924.5
All 2nd inns bowlingBBIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W%NICSA, 201513385.33.078.415.8India, 201516424.71.6910.217.4SA, 201810442.73.1229.726.9India, 201812433.52.7199.222.1Four bowlers – Ashwin, Ishant Sharma, Kagiso Rabada and Morne Morkel played at least two Tests in both series. The comparison between Rabada and Ishant is especially instructive. In India, the former beat the bat 54 times for two wickets, while the latter beat the bat 46 times for a solitary wicket. But Rabada created far greater uncertainty than Ishant, beating the bat 18% of the time, while Sharma beat the bat only 12.1% of the time. Morne Morkel beat the bat 83 times for nine wickets in India, and 150 times for 13 wickets in South Africa. He created about the same amount of uncertainty as Rabada did. Despite collecting only a couple of wickets in India, Rabada troubled the batting consistently.Ashwin beat the bat 198 times in India for 31 wickets, and 72 times in South Africa for seven wickets. His most significant effort came in the second Test in South Africa, in Centurion. In the first innings there, he beat the bat 31 times in 233 deliveries and returned took wickets. In the second, he beat the bat 33 times in 177 deliveries for a solitary wicket. In contrast, on the opening day of the series, he beat the bat six times in 43 balls and took two wickets. Much like Rabada in India, Ashwin created significant uncertainty for less than ideal returns in South Africa. Even though the conditions did not favor his style of bowling, the control numbers reveal Ashwin’s class. Over a longer series, Ashwin’s returns would probably have improved and been commensurate with the amount of difficulty he created for South Africa’s batting.
BowlerSeriesBBIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W%NICIshant Sharma20153817.31.710.446.012.1Ishant Sharma20184143.42.316.711.822.7Kagiso Rabada20153004.62.39.527.018.0Kagiso Rabada20186282.73.022.411.527.4Morne Morkel20154764.72.59.59.217.4Morne Morkel20185963.02.720.211.525.2R Ashwin20159884.02.310.76.420.0R Ashwin20184595.43.09.310.315.7The records of the batsmen who played at least two Tests in each series suggest that the batting records are largely determined by the quality of the bowling (and consequently, the match situation) each batsman is likely to face. In India, AB de Villiers and Hashim Amla were led by the match situation into a tactical decision to defend. In the first innings of the matches in India, de Villiers scored 174 runs from 224 deliveries where he was in control (4.6 runs per over). In the second innings, he made 57 runs from 281 deliveries where he was in control (1.2 runs per over).Similarly, in South Africa, Pujara and Vijay made the tactical decision to defend. Pujara made 84 runs from 275 balls where he was in control, and Vijay 81 runs from 291 balls where he was in control. For South Africa, Elgar adopted a similar approach, making 159 runs in 409 balls where he was in control. In contrast, both Kohli (237 in 383) and de Villiers (196 in 272) chose to attack the bowling. Elgar could be considered the most fortunate batsman in the series. He survived 134 deliveries where he was not in control and was dismissed only five times.
BatsmanSeriesBFIC_PER_NICIC_ECON%NIC_RUNSNIC_BF_PER_W%NICAB de Villiers20156084.92.710.514.716.9AB de Villiers20183364.34.37.110.719.0Cheteshwar Pujara20154236.13.17.910.014.2Cheteshwar Pujara20183434.01.816.017.019.8Dean Elgar20154123.72.117.512.421.1Dean Elgar20185423.02.323.226.824.7Faf du Plessis20152844.51.410.08.718.3Faf du Plessis20184204.22.813.113.519.3Hashim Amla20155766.31.310.213.213.7Hashim Amla20184525.02.910.315.016.6M Vijay20154875.12.615.713.316.4M Vijay20183594.31.720.611.318.9Rohit Sharma2015752.32.419.25.830.7Rohit Sharma20181904.12.324.49.319.5Virat Kohli20153879.23.35.07.69.8Virat Kohli20184794.03.717.116.020.0Finally, consider these respective core batsmen (I include Ajinkya Rahane to the list for this next data set) against pace and spin in India and South Africa respectively. This is the core contest in each series, the main batsmen against the specialist bowlers. In India, India’s five core batsmen conceded a wicket every 86 balls to the South African pace attack. In South Africa, despite conditions being 50% more difficult (21% not in control as opposed to 14% in India), they managed to keep the South African pace attack at bay for 64 balls per dismissal.South Africa’s problem in India was not that their spinners were not ably supported by their pace bowlers. Rather, it was that their pace bowlers were not ably supported by their spinners. Tahir, Piedt, Harmer and Elgar were unable to control the scoring in India any better than Maharaj was able to in South Africa. Given how spin-friendly conditions in India were, this does not reflect well on Tahir and company. South Africa would probably have been better off playing three or four fast bowlers and the solitary spinner in Tests in India, much like India in the past found success overseas by fielding their best bowlers, even if two of those were spinners. As it happened, South Africa ended up having to use their fast bowlers far more than they planned to in that series in India. They might well have won a Test somewhere had they played to their strengths and been prepared to bowl 70-75% of their overs with pace.India’s bowling options are not similarly lopsided. Their spinners are currently world-class, and their fast bowling has greater depth and experience than it has ever had, with the depth to compete and stay in the game. With a little bit of luck, they can be competitive in a Test match anywhere in the world thanks to this depth (they now have four competent bowlers, even if none of them is currently of the quality of a truly elite international bowler like, say, Ryan Harris).
SummarySeriesBBWICKETSIC_PER_NICIC_ECON%NIC_RUNSNIC_BB_PER_W%NICv SA pace2015863106.32.49.411.913.8v SA pace20181353213.72.520.613.821.4v SA spin2015983156.93.66.78.912.6v SA spin2018114111.73.61.69.07.9v Ind spin20151337254.32.012.811.018.8v Ind spin201827416.03.38.539.014.2v Ind pace201548336.71.81..021.013.0v Ind pace20181476213.72.914.515.021.3Control is not a retrospective measurement. It is recorded ball by ball. The overall picture it creates is therefore significant, since it is not coloured in any sense by the outcome of the game, or by any other summarised conclusion. It successfully separates performance from outcomes and provides a picture of the game that is not available simply by watching.Watchers are prone to cognitive biases. For a classic example of this, consider two cases. In the first, the batsman scores 110 not out in a run chase and his team wins. In the second, the batsman scores 98 and his team loses by 25 runs. The first 98 runs in each innings are remembered differently, and more importantly, are characterised as being of different quality after the result. This despite the fact that for those first 98 runs, player and watcher alike were equally unaware of what the final result might be. This is not to say that the ball-by-ball team that creates the control record is not prone to biases. Rather, it is to say that the discipline imposed by having to consider one ball at a time localises these biases.A look at the ball-by-ball record also allows the relative importance of different aspects of the contest to be considered. For instance, dropped catches tend to stick in the memory. But consider a session in which a team created 20% uncertainty (or 36 balls in 180), and dropped a catch. Consider another team, which created 12% uncertainty (or 22 balls in 180), and dropped two catches. The team that dropped two catches is likely to be considered by observers to have (a) done worse, and (b) created more trouble than the team that dropped just one catch. Among mistakes (or chances), a dropped catch is a loud, obvious one, which sticks in one’s mind. Other chances, like beating the outside edge four or five times more, are not similarly memorable, even though the batsman has the same amount of control when the result is a the play-and-miss as he does when the result is an edge or miscue, and plays and misses happen more often. But it is difficult to convince observers that creating chances is more significant (albeit less obvious) than converting each chance. Things that are obvious are not always more significant than things that are not. Bowling sides that create more uncertainty are more successful in the long run (such as the course of a Test match or series). But not all of this uncertainty is equally obvious. The control measurement, by systematically recording uncertainty, can help make this point to observers who are otherwise learned watchers of the game.The order in a contest can be identified from the control record. This is not always possible from the scorecard. Control should become a mainstream measurement in the cricketing record as soon as possible.
