The Not Out Man

Michael Bevan was one of the best ODI batsmen ever. During his career, he repeatedly pulled Australia out of the fire, sometimes playing with the tailenders, and dragging them over the finish line. Bevan ended up with almost 7000 runs from 232 matches with a phenomenal average of 53.58. One of the reasons for his high average was that it was really difficult to get him out – he was unbeaten 67 times in the 196 innings that he played. That is 34% of the time. Even a solid middle-order batsman like Steve Waugh has been not out only 20% of the time.

It is illuminating to look at the two players who have similar averages as Bevan. Mike Hussey’s current stats are very similar to Bevan. Hussey has an average of 53.85 (just above Bevan) and has been not out 28 times out of 75 innings (37% of the time). Both Hussey and Bevan have done well at No. 4 (56.87 vs. 59.60); This position was Bevan’s best position and Hussey’s 2nd best, Hussey having an enormous average of 117.66 at No. 7. Kevin Pietersen with an average of 48.36 has been not out 19% of the time. He has actually performed better down the order than at No. 3 and No. 4. Although Hussey and Pietersen have played similar number of innings, Kevin has more runs (3047 vs. 2531) and more consequential innings (27 vs. 18 innings over 50).

Is it useful to have a batsman who remains unbeaten? In Tests, it may be useful when such a batsman is paired with a more free-flowing batsman. Bowlers would be demoralized by a stonewall on one end and punishment on the other. If the anchoring batsman can rotate the strike, then you can have huge innings totals. Such a batsman is also invaluable in a 4th innings chase, or a batting collapse when you just want to shut out the opposition bowlers for some time. However, Bevan was never able to replicate his ODI success in Tests (a poor average of 29.07). Perhaps someone like Chanderpaul (in his recent form) would be more appropriate for a debate on the subject.

But we are talking about ODI’s, so is this useful? Bevan was able to anchor Australia to many victories, but they definitely were the ascendant team during those times. Bevan’s batting strike rate is a poor 74 runs per 100 balls. So in many cases, Australia could have made a larger score when batting first, or succeeded in the chase because their bowlers had limited the target that they had to chase. Most of Bevan’s big scores were not quick scoring innings. It can be debated whether a more aggressive batsman could have ended the match sooner during the chase.

The batting team’s Powerplay may mean that an anchoring batsman like Bevan finds no place in an ODI team. The batting team has to make tons of runs at the end, because larger targets are becoming easier to chase down. Having a batsman who is more interested in playing safe shots to preserve his wicket is less useful than someone with the more risky and unorthodox shots that has the potential to fetch 20 runs in an over.

The “unbeatable” batsman also has the danger of be hyped up over his average. This may cause two problems. One is that they keep trying to maintain their average by playing safer instead of taking calculated risks – this will have a heavy tax on the team when they are batting first in an ODI. Second is that the pressure of inflated expectations could weigh on them, so when they are in a slump, they try to hit large scores to get back into form, instead of slowing working themselves back into form. Hussey seems to suffer from that, Pietersen less so.

Weaker or improving teams have typically relied on such a batsman, because they need someone who can be there till the end. Essentially, what that means is other batsmen are not capable or ready to take responsibility for the team’s failures. For a long time, Tendulkar played this role for India, so that when he was out, the Indian batting order collapsed if the remaining task was too steep. When that changed, India started winning more.

Kevin Pietersen – Captaincy Cameo

Just when I felt England has found the right captaincy in Kevin Pietersen, someone possessing the stature and caliber of Ricky Ponting, Graeme Smith, M S Dhoni (Fast and Furious) to lead from the front, and thus provide a healthy balance among cricketing nations, guess what? KP’s relationship with the coach Moores derailed. Moores was fired and KP was “forced to resign“, as he called it.  Though he should be back playing I wonder how his performance would be affected by these drastic events.

It is physically and mentally challenging enough for any cricketer like Pietersen to work hard from the bottom to the top, proving himself game after game and achieving the proud feat of leading the side. If on top of that, all of a sudden, he is dropped, it could dramatically alter his career performance.  The analogy sounds similar to surviving a executive role in any corporate culture.

All I can wish is that others learn lessons from such incidents and resolve issues with team players, coaches, senior players in team, and the cricket management before it bubbles up. Hope KP will continue to prove a solid player for England. He still has time to lead the side in the future. Watch out for IPL shenanigans, because guess who is a free agent!

The Captain in Cricket

sydgregory1905

The Pietersen flap reminded me once again how unique the role of the captain is in cricket when compared to other games. Since cricket is a stop-start game, there are literally hundreds of decisions made by the captain throughout the entire match. Who should bowl? From which end? With whom at the other end? Try bowling short? Stop the singles or boundaries? How many slip fielders? Where to hide the poor catching fielders? How to apply pressure? Also make sure that overs are bowled in time.

Continuous games like soccer and basketball seldom allow that kind of decision making. Volleyball doesn’t have many variations in tactics. American football is based on choosing plays decided ahead of the game. Baseball, the closest cousin of cricket, is more dependent on the skill on the main pitcher.

Of course, the captain’s role is greater when the team is fielding. But even when the team is batting, the captain can make important decisions about batting order and target scores, though much of this is usually done in consultation with senior team members.

The coach is responsible for the performance of the players in the team, while the captain makes many of the real-time decisions that affect the game. This makes for greater tension between the captain and the coach. When teams are winning, this isn’t a problem because both can bask in the credit. But when faced with losses, each can point fingers at the other. That is certainly what happened in England’s recent household feud. But it could happen to any team that is placed under high expectations.