There is no smoke without fire. But sometimes the wind can throw us a googly and make it difficult to find out where the fire really is. As India crashed to 244 all out in the Sydney Test, the focus once again shifted to India’s bizarre approach to batting in away Tests.
Those 244 runs came off 100.4 overs on a pitch that wasn’t exactly poor for batting. The odd ball did do something but most experts reckoned it was a new-ball pitch and batting should have gotten easier after that. All eyes invariably moved to Pujara, who made his slowest fifty in Test cricket before being dismissed for 50 off 176 balls – a strike-rate of 28.41.
From 85/2 after 32.1 overs (when Gill was dismissed), India crawled to 142/4 after 67.2 overs (when Vihari was dismissed) – that is 57 runs in 35.1 overs for the loss of two wickets when the ball wasn’t new and hard. Batting should have been at its easiest at this point but by not showing any intent to score runs, India’s batsmen once again shot themselves in the foot.
At one point, Pujara had 16 runs off 100 balls, and to former Australia skipper Ricky Ponting, it was a counter-productive effort.
“I don’t think it was the right approach,” said Ponting on Twitter. “I think he needed to be a bit more proactive with his scoring rate because I felt it was putting too much pressure on his batting partners.”
Some argued that this is how Pujara plays. Others felt the rest of the batsmen need to score at a better rate. A few grumbled about how Pujara needs to be more aware of the match situation. Still more started comparing him to Rahul Dravid and saying that the former India skipper had at least more strokes at his disposal. But that isn’t exactly true.
In fact, Pujara has a higher career strike-rate than Dravid but perhaps our cricketing sensibilities are a product of the times as well.
With matches hardly going the full distance these days, Pujara’s efforts come into focus even more. The thinking, for most batsmen, clearly is that if you are in, you need to make the most of your time in the time. In Pujara’s case, as it perhaps was in Dravid’s case too, though, the thinking seems to be that if you are in, then try and stay in for as long as possible.
Dravid vs Pujara (career numbers)
| Mat | Runs | Ave | SR | 100 | 50 | |
|---|---|---|---|---|---|---|
| Dravid | 164 | 13288 | 52.31 | 42.51 | 36 | 63 |
| Pujara | 80 | 5953 | 47.62 | 45.57 | 18 | 26 |
A look at the country-wise breakdown of Dravid and Pujara also reveals that there is little to choose between the two. So why do we hold one in such high esteem but continuously doubt the other?
One reason for that could simply be that there’s a certain way Kohli wants this team to play. He continuously searches for intent, even from a batting line-up that has proved to be brittle away from home. The fragility of the batting line-up brings Pujara’s efforts into focus even more because it looks like he has played a lot of balls but done nothing concrete with his time in the middle.
Ganguly wasn’t as demanding in terms of intent. He wanted to win Tests too but he was prepared to wait and had absolute confidence in Dravid. It also helped that Dravid had four of India’s greatest modern-day batsmen batting all around him – Virender Sehwag, Sachin Tendulkar, Sourav Ganguly and VVS Laxman.
So while India batted around Dravid, they simply collapse around Pujara. From that perspective, it might be argued that the current Indian team hasn’t found a way to truly utilise Pujara’s ability to occupy the crease for long periods.
Dravid (in bold) vs Pujara
| Mat | Runs | Avg | SR | |
|---|---|---|---|---|
| in Australia | 16 | 1166 | 41.64 | 39.57 |
| in Australia | 10 | 835 | 46.38 | 38.89 |
| in England | 13 | 1376 | 68.8 | 44.66 |
| in England | 9 | 500 | 29.41 | 40.45 |
| in India | 70 | 5598 | 51.35 | 42.38 |
| in India | 41 | 3471 | 59.84 | 50.61 |
| in New Zealand | 7 | 766 | 63.83 | 43.69 |
| in New Zealand | 4 | 160 | 20 | 29.96 |
| in South Africa | 11 | 624 | 29.71 | 37.63 |
| in South Africa | 7 | 411 | 31.61 | 38.88 |
| in Sri Lanka | 12 | 662 | 33.1 | 40.61 |
| in Sri Lanka | 4 | 454 | 90.8 | 53.03 |
| in West Indies | 17 | 1511 | 65.69 | 38.4 |
| in West Indies | 5 | 122 | 20.33 | 32.62 |
Dravid vs the rest
| Mat | Runs | Avg | SR | |
|---|---|---|---|---|
| in Zimbabwe | 5 | 475 | 79.16 | 46.11 |
| in Pakistan | 6 | 550 | 78.57 | 51.06 |
| in Bangladesh | 7 | 560 | 70 | 59.44 |
One key difference between the two players is how Dravid has a slightly better strike-rate away from home (44.57 across 9 countries) as compared to Pujara (38.97 across 6 countries).
At home, Pujara has a SR of 50.61 at home to Dravid’s 42.38. But that comes down largely to how the two play.
Dravid had a good backfoot game, could play the horizontal bat shots with authority and that helped him away from home. He also adapted his game to play well in England against the moving ball and could rotate the strike that little bit better.
Pujara, on the other hand, actually looks to take the initiative against spinners but away from home, against pace, he waits for the bowlers to come to him.
If they, as the Australian bowlers have this series, can stay away from Pujara’s zone then there are no runs on offer. They can keep banging it in short of length and the right-hander will continue to defend resolutely. Patience isn’t an issue for him but for the batsman at the other end, it is perhaps proving to be.
Dravid over the years
| Mat | Runs | Avg | SR | |
|---|---|---|---|---|
| year 1996 | 7 | 436 | 39.63 | 37.42 |
| year 1997 | 12 | 984 | 61.50 | 36.93 |
| year 1998 | 5 | 413 | 45.88 | 37.85 |
| year 1999 | 10 | 865 | 48.05 | 42.44 |
| year 2000 | 6 | 624 | 78.00 | 49.44 |
| year 2001 | 13 | 935 | 46.75 | 40.28 |
| year 2002 | 16 | 1357 | 59.00 | 41.92 |
| year 2003 | 5 | 803 | 100.37 | 51.37 |
| year 2004 | 12 | 946 | 63.06 | 42.49 |
| year 2005 | 8 | 640 | 53.33 | 45.58 |
| year 2006 | 12 | 1095 | 60.83 | 42.26 |
| year 2007 | 10 | 606 | 35.64 | 41.79 |
| year 2008 | 15 | 805 | 30.96 | 38.60 |
| year 2009 | 6 | 747 | 83.00 | 48.60 |
| year 2010 | 12 | 771 | 42.83 | 44.56 |
| year 2011 | 12 | 1145 | 57.25 | 44.74 |
| year 2012 | 3 | 116 | 19.33 | 34.62 |
Pujara over the years
| Mat | Runs | Avg | SR | |
|---|---|---|---|---|
| year 2010 | 2 | 105 | 26.25 | 54.40 |
| year 2011 | 1 | 2 | 2.00 | 14.28 |
| year 2012 | 6 | 654 | 81.75 | 47.94 |
| year 2013 | 8 | 829 | 75.36 | 56.24 |
| year 2014 | 10 | 483 | 24.15 | 41.49 |
| year 2015 | 5 | 347 | 49.57 | 48.59 |
| year 2016 | 11 | 836 | 55.73 | 48.43 |
| year 2017 | 11 | 1140 | 67.05 | 45.89 |
| year 2018 | 13 | 837 | 38.04 | 38.46 |
| year 2019 | 8 | 507 | 46.09 | 51.52 |
| year 2020 | 4 | 163 | 20.37 | 27.48 |
| year 2021 | 1 | 50 | 50.00 | 28.40 |
Much of the criticism that we now see for Pujara was there for Dravid too. Too slow... kills the momentum... allows the opposition back into the game, but all of this would only be heard in good batting conditions.
In tough conditions and against quality bowlers, Dravid and Pujara are worth their weight in gold but the problem arises in better conditions when the team is looking to move the game forward.
Ordinarily, strike-rates in Test cricket should not be a talking point but given that it comes so soon after Adelaide, one must go back to Kohli’s words in the press conference after the defeat.
“Probably didn’t have enough intent in the batting today. It’s something that needs to be reflected and learnt from,” Kohli had said.
He had added: “There were some good balls. But I don’t think it did anything drastic. Just the atmosphere was created where runs were difficult to come by.”
With Pujara in the middle, there is no denying that run-scoring does become more of a chore and while he has his own method, he, like Dravid, needs to figure out a way to make the most of his time at the crease.
Some might argue that he’s already doing that. Others will say he can do more. Either way, this debate isn’t going away anytime soon. It didn’t for Dravid. It won’t for Pujara. Together they are, joined by their similar method and their love for batting on and on.
