Matches (17)
IPL (2)
Bangladesh vs Zimbabwe (1)
PAK v WI [W] (1)
WT20 Qualifier (4)
County DIV1 (2)
County DIV2 (3)
RHF Trophy (3)
NEP vs WI [A-Team] (1)
Match Analysis

What ails Rohit and Watson?

Both batsmen seemingly have buckets of talent at their disposal and the backing of their captains, but soft dismissals relentlessly follow both around the Test arena

If every batsman in Test cricket made bowlers earn his wicket, almost every match would end in a draw. If the new ball, good balls, pressure, fatigue, a break, a new innings, sensational catches etc. were the only ones bringing wickets, hardly anyone would get out after crossing the score of 20 and after the first 15 minutes of a new session. There's a reason why even the most sensible of opinion polls offers the option of "others", even after exhausting every other possible option. However, if the same batsmen keep ticking the "others" box too regularly, it can be frustrating.
Surely their team-mates, their mates and their fans have expressed this frustration to Rohit Sharma and Shane Watson? There is too much batting skill in there to not inspire a feeling of reliability. We should give up on them really. But then again, when we are just about to, Watson starts to take crucial wickets and lovely catches, and Rohit scores double-centuries in ODIs. We give them another chance, and we get another set of soft dismissals.
When India are in a position to bat Australia out at their fortress, when others are making the bowlers come up with unplayable deliveries to get them out, Rohit keeps up for a bit, but gets stuck. He sees Ajinkya Rahane dink into gaps the same balls which he is defending straight to fielders. Ian Chappell says it seems like he is batting in a dream, or in the nets, where just the connection matters, not the runs. He has scored six off 19, but India have seen off the first threat, Josh Hazlewood, who has bowled a ripper to get Rahane out.
On comes Watson - oh, him again - and Rohit can't stop himself from having a lazy push at a wide outswinger. He has had to stretch to even reach it. And this is not a full-blooded drive, which can at least give him a chance of the edge's flying over or wide of the slips. This is totally premeditated. As if the first-change bowler has to go. Just like in Durban last year, when he came out with his mind seemingly made up that he was going to leave the first ball alone. He was bowled middle stump by an inswinger.
India manage just 6 for 87 on the day, giving Australia a chance to fight their way back in. Only Rohit can be blamed for a poor shot. Before the start of the match, captain MS Dhoni spoke about the persistence with Rohit.
"If you see Rohit, he has been criticised for not making the most of the chances he has got," Dhoni said. "Even in the ODIs. But we kept giving him chances because we believe that he's an excellent cricketer. Once he crosses that phase, he'll be really good for the Indian cricket team. Now you can really see that kind of performance from him in the ODI circuit. We feel he can contribute in Test cricket also. We'll have to give him ample opportunity. Not to forget in the Test matches like in England we tried a five-bowler combination, which meant Rohit had to be left out. It becomes slightly tough for batsmen when you give them couple of games and they're out for four or five games."
It makes perfect sense, and Rohit hasn't had a long, persistent run in Tests, but here is a sobering thought: he made his international debut before Rahane, and there is a reason why Rohit now bats at No. 6 in Tests and not Rahane, why he is the first man left out to suit the team's needs and not Rahane.
Watson possibly can't even be left out, such is the phase Australian cricket is going through with injuries and ordinary form of various batsmen. He comes in to bat at No. 3 after a strong foundation has been laid: 47 runs in 8.3 overs. Chris Rogers is going solidly at the other end. Watson has seen the early jitters through. Now he is creaming it, punishing every little error in line or in length. India have resorted to spin with his score 25 off 25.
Four balls later, R Ashwin tosses one up. It is a decent delivery, but it hasn't dipped alarmingly on Watson. Before reading the description of the shot, you have to keep in mind mid-on is up. Watson goes at it with hard hands, making an attempt neither to keep it along the ground nor to clear the mid-on. Almost as if he just wants to hit the man at mid-on as powerfully as he can: Shikhar Dhawan, his old mate. This is just before tea, and Australia go on to lose another before the break. Forget about dominating the last session now. This is an absolute brain freeze, the kind Watson is no stranger to.
Rohit might have beaten Watson in terms of outrageous innings in ODIs, but Watson - on a day that he got Rohit out - has outdone Rohit when it comes to a poor dismissal. A hybrid of Rohit and Watson will score quadruple-centuries in ODIs, and will keep finding new, softer ways of getting out in Tests.
Why is it always these two? That they are too talented is a lazy explanation. Uttering the word "talented" in Rohit's presence is like a red rag to a bull. He is proud of the hard work he has put into his game, and hates being called laidback and talented. Watson has had to go through a lot just to be on the park, so fragile has his body been. It is hard to imagine them taking the chances given to them for granted.
Surely they get just as frustrated? They need to keep finding ways to stay alert through their Test innings, because even the most patient, and the most desperate, captains give up some day.

Sidharth Monga is an assistant editor at ESPNcricinfo