Gary Ballance’s virtues are found in terms of outputs, not process. Four hundreds and four fifties in his first ten Test matches make him one of the faster starters of England batsmen at this stage of their career.
He isn’t elegant. Amongst the many left-handers who defy the stereotype of graceful shot-making he doesn’t repel the eye as much as, say, Graeme Smith or Kepler Wessels. But it’s solid, focused, unexceptional batting at which he excels.
Now, in this series in the West Indies, he’s starting to look scruffy – because of his bat. Last summer, his New Balance blade was clear, pale willow. Then, it was his cheeks that attracted comment for their rosiness. His newer New Balance bat looks like it has been used to protect him from assault by flying tomatoes. Bright red splodges from one edge to the other, thickly spread from splice to an inch above the toe of the bat.
To his credit, there’s something honest and straightforward about leaving the marks where they appear on the bat. I have been known to sand-off those close to the edges of my bat. Perhaps the appearance of Ballance’s bat is a sign that he is free of any such insecurities about his own batting.
When Ian Bell became England’s all time leading run scorer in ODIs, while scoring a century against Australia in Hobart, I imagined cricket followers performing a sport-wide double-take. “He’s what? Bell? Is that right?” before making a mental note to themselves to check on statsguru when they got home and found a quiet moment with a computer.
The only Bell innings in an ODI that I have any sort of memory of (barring those in the current series) was at Southampton and it involved lots of lofted drives. I don’t follow ODI cricket with the forensic attention I pay to Test matches, but I would expect England’s leading scorer in the format to have made a stronger imprint on my memory. How then did Bell come to break this record and, other than the quantum of runs, how does his ODI record compare?
Bell’s first ODI was played in Harare in November 2004 – three months after his Test debut. He opened the batting with Vikram Solanki and scored 75 (115 balls) in a successful chase of 196. His most recent match, at Perth, was his 155th. Amongst batsmen, Bell is the third most capped English player – behind Paul Collingwood (197) and Alec Stewart (170). Quantity of cricket is clearly a large part of the answer to the question ‘how did Bell break this record?’ But my instinct is that Bell has not been an ODI regular over the last ten years.
Since his debut, Bell has played fewer than two-thirds of the 234 ODIs played by England. He has had two lengthy periods out of the team – Feb-Dec 2005 (16 matches) and Nov 2008 – July 2010 (33 matches) – as well as numerous ins and outs typical of a fringe player or of a Test certainty being rested between five day series. His longest continuous run of appearances is 35, from July 2007 to Nov 2008.
Bell’s first ODI century came in his 48th appearance. There have only been three more, but Bell has recorded the most scores of 50+ in ODIs for England: 36.
Two years ago I wrote about Bell, the Test batsman.
I have reconciled myself to Bell as a very good international batsman… he has reached the plateau of his level of accomplishment… I don’t expect him to dominate a major series or change the flow of too many contests… Bell is really very good and that is good enough.
Since then Bell distinguished himself as the outstanding batsman of the 2013 Ashes, recording three tons. It was a peak above the plateau, to which he seems to have returned. And as a Test batsman, Bell has always had one or other of Strauss, Cook or Pietersen as his senior. He is now the senior ODI batsman, yet I stand by my appreciation of his contribution from that earlier piece. He has rarely been dominant in ODIs. Of the top 30 ODI series run aggregates by England batsmen, Bell appears once, in eighth place – scoring 422 runs in a seven match series against India in 2007.
It might be helpful to place Bell amongst his peers. Of the 22 England batsmen with over 2000 ODI runs, Bell has the seventh highest batting average and eighth swiftest scoring rate. The players whose record Bell’s most closely resembles are Allan Lamb and Paul Collingwood, two of England’s most respected short-form batsmen.
In the ten year span of Bell’s international ODI career, 28 other players have scored 4,000 runs or more. Bell is in 15th place and has the third highest aggregate of those averaging under 40. Only two batsmen in this group have scored fewer hundreds than Bell.
The scatter diagram of batting averages and scoring rates shows Bell is in the lower half of the range for both measures. Graeme Smith and Mahela Jayawardene are the batsmen closest to Bell on the chart.
A number of factors have helped propel Bell to this record. He has stayed fit, physically and mentally, over ten grueling years of international cricket. He has maintained good relations with the England team management and, as pointed out to me by @ballsrightareas, avoided the sometimes career-shortening office of captain.
The gap at the top of the England batting order created by Marcus Trescothick’s exit from international cricket in 2006 has given Bell more opportunities than he would have had. Kevin Pietersen’s and Jonathon Trott’s absences have also created space for Bell. The curtailing of Trescothick’s and Pietersen’s careers prevented those two players, more suited than Bell to short-form cricket, setting a more stretching total runs record for England.
In this period, England’s selection policies have not been consistent. Bell may have suffered some omissions because of this lack of clarity about what the best team is. I suspect that is balanced by some of his recalls being down to the same inconstancy of selection.
On reflection, I don’t feel ignorant to have been taken by surprise by Bell’s recent achievement. He’s played a lot of matches, but many fewer than a leading exponent of this form of cricket would have done. He has a good ODI record, certainly by England standards, but not a great one. I will be surprised again if Bell’s future performances force me to alter that view.
Graeme Smith’s Test career ended in defeat and South Africa’s first series loss in five years and 15 series. He must have drawn satisfaction from his final, albeit unsuccessful, day of Test cricket as his middle and lower order battled and came so close to eking a draw from a game in which they were profoundly outplayed.
Smith’s records as captain – most matches, most victories – have been celebrated. There’s another record he holds, less well known, but which makes the denouement of his final Test ironic. Australia won at Cape Town with time almost, but not quite, up after declaring in the third innings. Smith is the most prolific declarer in Test history, having called time on South Africa batting in the third innings of a match 25 times. Yet, only eight of those declarations were converted into victories – producing a success ratio of 32%, below the average for the game and a long way short of the proportion achieved in recent years of Test cricket.
South Africa have become known for being a team hard to beat and one that finds it hard to speculate to accumulate if the victory isn’t coming comfortably their way. Smith’s statistic of only converting 32% of declarations – made when ahead in the game – into victories gives fuel to this notion of a risk averse South African side. The purpose of this post is to assess whether, from the perspective of the target-setting declarations, this is a fair assessment of Smith’s career, which in so many respects deserves to be remembered for the effectiveness of his leadership.
Smith’s third innings declarations spanned from his third Test as captain (v England at Edgbaston in July 2003) to his 107th and penultimate Test (v Australia at Port Elizabeth). In total, these declarations yielded eight victories, 16 draws and a single defeat. How many of the draws were likely victories spurned through over-caution?
Three of the draws can be discounted immediately. These weren’t ‘target-setting’ declarations, but decisions to close the innings to end a match that hadn’t progressed beyond the third innings. Adjusting for these, Smith’s win rate increases to 36%. A further adjustment, to take out two games where the fourth innings was prevented by rain from running its course, lifts the success rate to 40%.
The chart below shows the target set and estimated number of overs remaining in the match for each of the 22 ‘live’ declarations (including the two rain-affected games). Matches that were won by South Africa are green, defeats in red and draws in blue. The dotted turquoise line indicates the current record fourth innings chase in Test cricket (418). On ten occasions, Smith has challenged opponents to set a new Test fourth innings record.
Smith’s teams have won each of the matches where they have given themselves over 150 overs (five sessions) to bowl out the opposition. They have won only one-third of the nine games when they had 100-150 overs. Not a single game has been won with the declaration leaving a day’s play (90 overs) or less.
To test for examples of over-cautious captaincy, it makes sense to start with the four matches where Smith set a target of over 400 and gave his team over 100 overs to secure the victory (a fifth, when the final day was rain affected is excluded). Should he have declared earlier?
In only one of the matches (v England, Cape Town – Jan 2010) does it appear, with the benefit of hindsight, that more overs could have delivered a victory. England were nine wickets down and 170 short of the target after the 141 overs were delivered. In the other matches, the opposition were three, four and five wickets down at the close of play. In each case, bringing forward the declaration by an hour would not have substantially increased the chance of a South African defeat, but may have helped a victory push, although that seems unlikely given the position of the game at the end of day five.
Teams batting third create time to bowl the opposition out by batting, if not aggressively, then enterprisingly. The chart below shows the run rate per over achieved by South Africa for each of the 22 ‘live’ declarations. The colour of the bar indicates the match result: green – win; blue – draw; red – defeat.
The picture is mixed. Three of the four third innings with run rates below 3 per over presaged draws. But three of the five third innings with the highest run rates were also in matches that concluded in draws.
Smith has earned praise for several of his declarations. The defeat against Australia at Sydney in 2006, when South Africa were 1-0 down in the final Test of the series, came about following a “sporting declaration” by Smith – and tremendous attacking innings by Ponting. His next declaration, against India at Durban in December 2006, showed no signs of being scarred by defeat. Smith set the visitors 354 at a rate of almost one run per over slower than his team had amassed their third innings total. He was rewarded with a comfortable victory and a squared series. At Headingley six years later, Smith was credited with “happy daring” when 1-0 up in the series with two to play, he set England 253 in 39 overs.
Taken together, these observations point to criticism of Smith’s negative approach as a captain when setting the opposition a target being overstated. There are examples where he could have ventured more in pursuit of victory. But there are also examples of bold declarations, just as there are of frustration in the face of stubborn, unanticipated fourth innings salvage jobs.
Where Smith’s team appears to vary from the norm in Test cricket declarations is the failure to convert the majority of situations where 100-150 overs remain in the game into victories. In an earlier analysis of target-setting declarations in Tests between 2009-11, All the time in the world, I found that only four of 17 (24%) declarations made with 100-150 overs left in the game resulted in draws. Smith’s career record is 67% (six of nine).
The key to Smith’s apparently low conversion of declarations into victories has not been the timing of his declarations, nor has it been the urgency with which his side has batted in the third innings of the match. If there is a deficiency it lies with the concoction of factors that have made South Africa relatively ineffective at dismissing sides in the fourth innings. In that mix may be: the lack of top quality spin bowling, unhelpful wickets, unadventurous captaincy in the field and, of course, ill-fortune. What do you think accounts for Smith’s mediocre record of driving home match advantage into victory?
Michael Clarke, in his first full year of captaincy, has the honour of ‘declaration of the year’. At Bridgetown in April, Clarke declared Australia’s first innings 43 runs behind West Indies, curtailing a 77 run tenth wicket partnership. The following day, in their second innings, Australia chased a target of 192, making Clarke only the second captain in test history to win a match after declaring behind.
Other significant declarations in 2012 will follow after an overview of target-setting, third innings declarations (which Clarke’s was not).
In an earlier review of target-setting declarations, I have shown that they occur in approximately one-quarter of all Test matches. 2012 fell into line with this long-term average, with 11 of the 42 matches in the year featuring this kind of declaration. The proportion of victories arising from these declarations (30% – excluding one declaration made to bring a game to an end) was considerably lower than the typical figure achieved in recent decades: 40-50%.
This brings us to an apparent paradox. Declarations tend to occur when one team is on top in the game. Yet 80% of the drawn matches in 2012 involved a target-setting declaration, while only 9% of the victories did so. The longer-term picture is more balanced, with target-setting declarations featuring in 21% of victories and in 27% of draws.
It revives the question posed in my post, Making the Game Safe, over whether the captains of sides batting third take too long over bringing their innings to an end. Mike Brearley, in The Art of Captaincy, concedes:
most of us already err on the side of caution; fielding is hard work (so postponements are tempting); and we enjoy watching our batsmen demolish the bowling.
Eliminating two games ushered to draws by fifth day rain and a third where the match’s third innings began 40 overs into the final day, four merit review.
SA v NZ at Wellington (Mar 2012)
SA skipper, Graeme Smith, declared 15 overs into the final day, setting a target of 389. Overnight, the lead had been 280, but had built rapidly in the opening hour of the day five. Smith’s declaration did not maximise the time available for pursuing the victory in the fourth innings, where Kane Williamson’s obdurate century and some sloppy SA fielding contributed to the result.
Pak v SL at Pallekele (July 2012)
Misbah-ul-Haq set SL 270 in 71 overs. This was a well-balanced target, although Pakistan may have wanted to risk more given they were one-nil down in the final match of the series.
SA v Eng at Leeds (Aug 2012)
Leading the series and having experienced Kevin Pietersen at his destructive best in the first innings, Smith’s declaration was justifiably cautious but managed to create an exciting final afternoon.
Aus v SA at Adelaide (Nov 2012)
Clarke declared with a lead of 430 and almost 150 overs left in the game. That the game was drawn had very little to do with his declaration judgement and a lot to do with the determination of debutant Faf du Plessis, a flat track and the Australian attack being a man down.
So, in only one instance – Smith’s declaration at Wellington – was the judgement awry and culpable in the match being lost. It is also worth noting that rain had taken time out of this match, as it had in the Headingley and Pallekele examples.
The other noteworthy target-setting declaration was made by Mahela Jayawardene at Galle against Pakistan in June 2012. Sri Lanka’s second innings happened as Jayawardene opted not to enforce the follow-on when 370 ahead after dismissing Pakistan in 54 overs. By batting again, a lead of 500 was established and a declaration made. Jayawardene was criticised for opting to bat again. The decision whether to enforce the follow-on has been analysed by academic statistician Philip Scarf, whose work informed my earlier pieces on declarations. Scarf’s conclusion is that the decision makes no significant difference to the outcome of the match.
I end this round-up where it began: with a record-holder. Graeme Smith set a record in 2012 when he became the captain who has made the most target-setting declarations in test history. With 23 he is two clear of Ricky Ponting, the previous record holder. Their fortunes are quite different as Smith has only converted 26% into victories, compared to Ponting’s 81%. Smith hasn’t always been over-cautious, but as at Wellington in April, his reluctance to get out in the field has on occasions cost the South Africans a win.
Barely one in fifty target-setting declarations in Test cricket results in a loss for the team who make the declaration. Just eleven in Test cricket history. With the odds seemingly so heavily stacked against it happening, a match-by-match review should produce some treasures – and numbers six to eleven of this series throw up some magnificent innings and even a turning point in the history of the game. The first five were described in Who dares is occasionally defeated.
Clive Lloyd West Indies v India, Port-of-Spain (April 1976)
Lloyd’s 13th match as captain was to have a far-reaching impact on test cricket. His team had been well ahead from early on day 1 of this match. With a comfortable lead of 400 on a slow turning pitch, with three spinners in his side, Lloyd declared after lunch on the fourth day. India had almost five sessions to score the runs.
Generous or not, it required a magnificent, record-breaking effort from India’s upper order – centuries for Gavaskar and Vishwanath and a sheet-anchor 85 from Mohinder Armanath. The other triumvirate whose role was significant were the three West Indies spinners – Jumadeen, Padmore and Imtiaz Ali. Their impotency – absolutely (two wickets in 105 overs) and relative to the Indian spinners – set Lloyd on the path to the all pace attack of the next two decades. It was a rapid transformation with four quick bowlers in place two tests later.
Bishen Bedi Australia v India, Perth (December 1977)
The calculation made by captains approaching a declaration is between size of lead and time available to win. In this case, Bedi’s calculation was how long he dare bat on without an injury to a key bowler. With nine wickets down, himself and Chandrasekhar at the crease and Thomson at full-throttle, he was not sacrificing much run-scoring potential cutting short the innings.
The match had been closely fought with neither team able to secure a telling advantage. This was true through most of the fourth innings, where a nightwatchman’s century (AL Mann) played a major part in a creating a dramatic finish with Australia reaching their target of 339 with two wickets to spare and time running out. Bedi became the second captain in test history to have both suffered and benefited from a loss after a declaration.
David Gower England v West Indies, Lord’s (July 1984)
This is the only one of the eleven matches that I saw any of in the flesh – day 3 when Botham’s bowling took England to the unusual position of a first innings lead against the West Indies. One of his eight wickets in the innings was Richards, given LBW after a half-hearted appeal. At the time it felt as though the umpire, Barry Meyer, was as carried away as the crowd with England’s competitiveness.
Gower declared with nine wickets down early on day 5, setting a target of 342. More controversial than this decision was Lamb’s, and presumably Gower’s, to leave the field for bad light the previous evening when England’s lead was building. Greenidge’s response would have made any such cavils academic as he powered to 214* and a nine wicket victory. The West Indies’ progress was updated on my classroom blackboard by a chemistry teacher who was invigilating some low key afternoon-long test, wearing headphones.
Despite the defeat, this was England’s highpoint of a five-nil series defeat. Lloyd became the third captain in test history to have both suffered and benefited from a loss after a declaration.
Adam Gilchrist England v Australia, Headingley (August 2001)
Stand-in captain Gilchrist brought his attacking frame of mind to Test leadership setting England a target of 314 in a possible 110 overs. Poor weather meant that the full allotment would not be bowled and an inspired innings from Mark Butcher (174*) took England to a rare and unlikely victory when the loss of early wickets on day 5 had made a draw a more reasonable aspiration.
Asked about how he had prepared himself for the afternoon assault on Australia’s magnificent four bowlers, Butcher memorably explained that at lunch he had sat in the shower with a fag and cup of coffee.
Of losses following declarations, this was one of the most comprehensive turnarounds: 1st innings lead of 139, which became a lead over 300 with four wickets down on day four when Gilchrist waved his batsmen in. Steve Waugh was fit for the next test and Australia continued on their winning ways.
Graeme Smith Australia v South Africa, Sydney (January 2006)
Graeme Smith holds the test record for most target-setting declarations (23) and the most drawn matches (16) following those declarations. This is his single defeat.
Losing one-nil, on the final morning of the series, Smith gambled: setting Australia 287 in 76 overs. An onslaught from Ponting saw the target swallowed in just 60 overs, for the loss of only two wickets – setting a new record for a fourth innings winning total at Sydney. Smith’s positive outlook was evident throughout the game as he had declared the 1st innings, becoming the second captain to lose a match after declaring both innings.
Kevin Pietersen India v England, Chennai (December 2008)
Oh the ups and downs of KP. In this, his second (of three) test matches in charge, he cut short England’s innings and set India’s galacticos a target of 387 in around 110 overs. The declaration wasn’t reckless, or even particularly bold, as nine wickets were down and Panesar due to join Anderson.
In sharp contrast to England’s meandering afternoon of batting on the 4th day, Sehwag launched India that evening with 83 from 68 balls. On day 5, Tendulkar and Yuvraj guided India on a record-breaking run-chase.
Despite the loss, Pietersen’s stock was high, having led his team back to India after the Mumbai terror attacks. Within months, at loggerheads with Coach Peter Moores, he had had to step down. Perhaps more significant for his current predicament, at least one of his teammates was unimpressed by his conduct.
The difficulty chasing a substantial total in the fourth innings is the cricketing truism that informs every captain setting a target. These six examples, despite the success of the run-chase, support that belief, as each was driven by one or more outstanding batting performance.
Only Lloyd and Gilchrist made declarations that allowed a fundamental alteration to the course of the game. In three of the matches featured, the declaring captain probably sacrificed little as his team was already nine wickets down. In the remaining case, Smith’s was motivated by the need seize the last opportunity to draw level in the series.
Did you follow, watch or even attend any of these matches – perhaps as one of the sparse fifth day crowd rewarded with a brush with cricket history? Your recollections would be a very welcome addition to this project.
This article is the sixth in a series investigating target-setting declarations in Test cricket. The full series is found by selecting ‘Declarations’ from the top menu bar.
Not a post about the advisability of batsmen wearing helmets, teenage quicks bowling eight over spells or crowds being prevented from ambling across the ground at the end of match. No, safe here means cannot be beaten, having an unassailable lead. I am returning to my theme of Test match declarations.
The story so far: in the history of Test cricket 37% of third innings declarations end up in victories and only 2% as defeats. Looking at the last three calendar years, successful declarations are associated with major nations playing minor nations, many overs remaining for the fourth innings, higher targets and lower target run-rates. This post looks at the drawn matches in the sample period to query whether the declaring captains were over-cautious.
I am going to draw on, and so want to prominently acknowledge, the fascinating work of Dr Philip Scarf and Sohail Akhtar of the University of Salford. I came across Dr Scarf’s work while researching this piece and am very grateful that he has allowed me to draw on some of it. In brief, Dr Scarf is an academic statistician who has analysed ten years of Test matches to model their results. The statistical proofs used are beyond me, but the conclusions illuminating. A full reference to the paper I borrow from is at the end of this post. I am making use of a table on p8 of his paper which calculates the probability of the three outcomes of a third innings declaration. For example:
Scenario – Target: 300. Overs remaining: 100.
Result probability – Win: 0.465 Draw: 0.274 Defeat: 0.261
What follows is a distillation of a review of the 18 drawn tests following third innings declarations in the sample period. Distilled out are: three declarations made to end the match early without a fourth innings getting under way; four declarations which were made for the purpose of nuisance – i.e. to discomfort the opposition late in the game, rather than as a serious attempt at winning the game (England at Brisbane in November 2010 is the archetype.)
The review comprises three perspectives:
- hindsight – how close to victory (or defeat) did the declaring captain get and so would an earlier declaration have made the crucial difference? I calculate and depict closeness to victory as a percentage – for the bowling team, not of the 10 wickets required, but using the average duration (in balls) of each completed wicket partnership (1st to 10th) in the sample period. This gives a more meaningful weighting of the significance of top order wickets and the proximity to victory when amongst the tail – on average!
- anecdotal – did the captain appear to delay the declaration? What was in it for the captain to make a bold declaration (e.g. Series situation, relative strength of the two teams)
- Scarf predictive analysis – according to Dr Scarf and Sohail Akhtar’s model, how much could the skipper have altered the balance of odds in favour of a victory (or defeat) with an earlier declaration?
And then I judge: Captain Cautious, Skipper Intrepid or just Captain Sensible. Five captains were the decision-makers and each is dealt with in turn.
Eng v WI in Antigua (February 2009)
Strauss declared mid-way through the second session of the fourth day, over 500 ahead. Just one West Indian wicket remained between England and victory (96% of the target requirement) the following evening. Hindsight says that any additional time could have secured a win for England, who had the incentive of being behind in the series (although two more matches were to be played).
Dr Scarf’s analysis doesn’t consider targets above 450. However, the likelihood of winning has peaked for fourth innings with 140 overs remaining with a target of 400. The model suggests that batting on for 20 overs cost England a 90%+ probability of winning, reducing the probability to below 80%. Captain Cautious
Eng v WI in Port-of-Spain (March 2009)
Two matches later and Strauss was able to set a total of 237 at lunch on the final day of the series. England had the West Indies eight wickets down (91% of target requirement) at the close of play. Just a few more overs and Strauss may have had the satisfaction of levelling the series.
Dr Scarf’s table shows that Test matches are rarely won by sides setting totals below 250. With as few as 66 overs remaining, a draw was the most probable result, but a successful chase more likely than the side being bowled out. The model indicates there was little to be gained from an earlier declaration. Captain Sensible
Eng v SL at Lord’s (June 2011)
Strauss made this declaration during the final afternoon of the match. England’s three wickets and Sri Lanka’s total of 127 both represent 37% of their respective targets. While this suggests Strauss required a lot more time, his attack had skittled Sri Lanka on the final day at Cardiff the previous week. One-nil up with two to play, Strauss had no incentive to gamble.
The model would have given England a one-in-eight chance of victory. Declaring 20 overs sooner would have more than doubled the probability of an England success, but given Sri Lanka a 15% chance of squaring the series. Captain Sensible
Ind v NZ in Wellington (April 2009)
Dhoni set New Zealand 617 in 160 0vers. They survived due to the loss of 70 overs to the Wellington weather when eight wickets down before play was ended ahead of lunch on day five. India were defending a one-nil lead in the final game of the series, which influenced their decision to carry on batting, setting a target over 30% higher than the record fourth innings chase.
Dr Scarf’s model doesn’t cater for targets so large, but he does conclude: “if a very large target is set, the team batting last will not attempt to play for a win and a draw becomes more likely.” Captain Sensible
Ind v WI in Bridgetown (June 2011)
Dhoni’s declaration set the West Indies 283 in 83 overs. With 15 overs lost to rain, India still managed 85% (7 wickets) of their target. Dhoni was praised for his boldness, which gave a filip to a rain-affected match with a tense final day. What’s more, India led the series one-nil with the third Test still to play. On the debit side for the Indian captain, he was fined for a slow over rate, which may have reduced his team’s chances of winning.
The probability table suggests a pretty even chance of each of the results and nothing to be gained from an earlier declaration. Skipper Intrepid
Pak v SL at Colombo (July 2009)
Pakistan declared three overs into the afternoon of the fourth day, with their tenth wicket pair at the crease. A day later and 15 overs before the scheduled close, Sri Lanka were closer to victory – 79% of the way towards their target of 490 – although both teams attracted criticism for not pursuing victory more urgently. The game was a ‘dead rubber’.
Extrapolating from the probability table, Pakistan were very heavy favourites (c.90%), giving themselves 160 overs to bowl Sri Lanka out. Captain Sensible
SA v Eng at Centurion (December 2009)
Smith set England 364 in 96 overs and came within 4% (or one wicket) of the victory on a fifth day of swinging fortunes. It was the first match of the series and Smith was without Steyn, the spearhead to the attack. The England tenth wicket pair survived three overs, with number 11, Graham Onions, facing 12 balls (shown at the head of this post).
The probability tables suggest a victory as the most likely outcome, and defeat at under 10%. Chances of victory grow steadily however, with the more overs available with targets between 300-400. Captain Cautious
SA v Eng at Cape Town (January 2010)
Three weeks later, now one-nil down in the series and Smith again declares to set England a target: 466 in 141 overs. 47 more overs than South Africa had available at Centurion. The result, in graph form, is identical, but England’s dogged defence more consistent than in the earlier Test.
Scarf’s table put the chance of a South African victory at over 80%. The same probability as if Smith had declared 20 overs earlier and set a target 100 runs fewer (as would have been the case). The probability of an England victory would have been much higher, however, with the earlier declaration. Captain Sensible
SA v Pak at Dubai (November 2010)
Smith set Pakistan 451 in 131 overs in the first of this two match series. While the declaration was seen at the time as ‘on the conservative side’, Smith’s side were the clear favourites. As the graph shows, however, Pakistan were closer to their target than South Africa with the largest percentage point advantage to the batting side in these drawn matches (76% v 37%).
The probability table suggests a c.70% chance of victory and only 1% chance of defeat. A declaration at lunch on day four would have lifted that probability to 80% but increased the chance of defeat to 16%. Captain Cautious
SA v Pak at Abu Dhabi (November 2010)
One week later, Smith again set Pakistan a total, but from a less commanding position: early on the fifth day with a lead of 353. The value of batting for five overs on day five was questionable, but seems unlikely to have tipped the balance as Pakistan lost only three wickets before the match was brought to a close. The series ended in a ni-nil draw.
Scarf’s table suggests a two-thirds chance of a draw, with only marginal improvements to South Africa’s odds (and larger increases to Pakistan’s chances) with an earlier declaration. Captain Sensible
SL v Pak at Sharjah (November 2011)
Rain delayed the start of day five, with Sri Lanka 237 ahead with 67 overs remaining. The slow scoring rate in the match would mitigate the risk to Dilshan, whose outfit were one-nil down in the last of three tests. But Dilshan batted on for four overs, increasing the target by 18.
The probability tables show the draw was the favourite (50-60%), with a successful chase more likely. With lower targets rarely producing victories, Sri Lanka’s chances would not improve with an earlier declaration. Captain Sensible
Acting as judge of the positive intent of these Test captains, I’ve concluded that on three occasions (out of eleven) the timing of the declaration was over-concerned with making the game safe, reducing the chance of victory. There were two other tests where declarations came later than appeared to be necessary, but I judge the delay as having little impact on the result.
There exists some evidence, from a minority of declarations, to support my original contention that ‘losing feels worse than winning feels good’. None of the delays to declarations was flagrant, but each were in series still ‘live’ and so could have made a difference beyond the match itself.
In this review, I have isolated the timing of the declaration decision, but do acknowledge that what followed in the fourth innings, e.g. quality of bowling, fielding, determination of the batting, umpiring decisions, pitch and weather conditions, all played a part alongside the declaration in bringing about result.
Acknowledgement: An analysis of strategy in the first three innings in test cricket: declaration and the follow-on. Philip Scarf and Sohail Akhtar. Salford Business School Working Paper Series. Paper no. 337/10.
Graeme Smith called in his batsmen 40 minutes into the afternoon session of the fourth day. Smith’s declaration left England 141 overs to survive, and a target of 466 to chase. Three weeks earlier, Smith’s South African team had been defied by England’s tenth wicket partnership, which had batted out the last four of 96 overs. Smith wasn’t going to leave anything to chance this time, one down in the series and only one further match to play.
Roll forward 28 hours and improbably England had once again clung on to draw, nine wickets down.
Ask Graeme Smith if there is a formula to a successful declaration and I suspect he’d answer with a withering look. The pitch condition, weather, fitness of bowlers, state of the series and tenacity of the opposition are all complicating factors. This post continues a series that began with the psychological insight that captains may be hindered in their search for victory as ‘losing feels worse than winning feels good‘; and continued with a high level survey of third innings declarations in test cricket that showed a victory conversion rate of only 34%.
In this post, I start to assess, through a series of charts and brief comments, whether there are features of declarations that are associated with success. I use a non-random sample, but one that is most relevant to Test captains of today. It takes in the 38 third innings declarations made in the last three completed calendar years of Test cricket.
53% (20) of the declarations in this period led to victories – a higher proportion than in the history of Test cricket. Three of the declarations leading to draws are excluded from the analysis as they were made to end the game early, with no fourth innings occurring, leaving a sample of 35. There were no defeats for the captain who made the declaration in this sample.
Chart 1 shows how results relate to match-level factors: venue, state of the series and strength of the two teams (minor = Bangladesh and Zimbabwe; Major = the rest).
There’s a lot of inter-relationship between these factors, but they point to stronger teams and home teams being more likely to turn the advantage of being in a situation to set a total into victory. I’ll move on quickly as I sense Graeme Smith’s attention wandering at the predictability of those results.
The remainder of the analyses look at the match situation at the point of the declaration being made.
Chart 2 shows the size of the target set in each declaration, team by team. The black diamonds represent the targets, with the highest ever fourth innings total conceded by each team in defeat shown as a blue square.
Captains are, as predicted, risk averse. 57% of targets set required Test record breaking chases of the side batting last (i.e. above the 418 hit by an inspired West Indies in Antigua against Australia in 2003). 80% of the targets, had they been achieved, would have set new national records for totals conceded in the fourth innings of a match in defeat.
Chart 3 sets the result of the game against the target total and required run rate.
The higher the target set in this sample of matches, the greater the chance of victory. None of the ten lowest targets produced a victory (or a loss). The lowest target to result in a victory was 366 set by New Zealand for Zimbabwe to chase in Bulawayo last November. In a tight finish, Zimbabwe fell 35 runs short. There was also a strong relationship to run rate required. Only one total with a required run rate above 4 runs per over had a winning outcome for the declaring captain: Jayawardene had set Bangladesh a target of 624 at 4.22 runs per over in Chittagong in January 2009. The remaining victories came in chases where required run rates varied from 2.33 to 3.91.
Chart 4 refines this analysis, by providing a context in which the target is set. The horizontal axis shows the ‘relative target’ – i.e. difference between the target and the highest innings of the three earlier in the game. The vertical axis plots the ‘relative run-rate’ – i.e. difference between the required run rate and the run-rate achieved across the first three innings of the match.
Victories were more likely to occur if the ‘relative target’ was high (i.e. above or not much less than the highest score in the match at that point). An exception (the red diamond furthest to the left) was New Zealand’s victory over Bangladesh in Hamilton in in February 2010 having set a target of 404, some 149 below the hosts’ total of 553.
Victories are associated, however, with lower ‘relative run-rates’. Over half required a lower run rate of the team batting last than had been achieved in the match to that point. This was true of only two of the draws.
Chart 5 depicts the overs available for the fourth innings.
There is a very clear association of victories with having more time to dismiss the opposition. The drawn match furthest to the left (India v New Zealand at Wellington in April 2009) is misleading as 70 of the fourth innings overs available, were lost to poor weather. Sri Lanka were the team that survived the longest fourth innings without defeat, lasting 150 overs (the match was declared a draw after 134 overs) at Colombo in 2009 against Pakistan. Not a single Test was won in this period with a team declaring on the final day.
In summary, this analysis of results following declarations shows that:
- captains are conservative, generally only being prepared to set targets that would establish new national records for sides batting fourth were they to lose
- higher totals, lower run rates and more overs are all positively associated with victories.
Does this mean that, as I hypothesised, captains are too cautious and are missing out on victories, fearing defeat? In the next article in the series, I’ll look in detail at the drawn matches in this sample to ask whether their caution is costing their team success.