3 Reasons Why Rohit Sharma Should Be Sacked As Test Captain

Anurag Dasgupta

Why Rohit should be sacked as captain [Source: AP Photos] Why Rohit should be sacked as captain [Source: AP Photos]

The year 2024 started on a positive note for Rohit Sharma the Test captain, however, fast forward to almost 300-plus days later, the same captain is facing the consequences for his baffling decisions and is on the verge of getting sacked as the Test captain.

His decision-making in the ongoing Test series has been strange and as a result, the Australian side have taken a 2-1 lead in the series, with a match still to play. Rohit's body language looks lethargic and this is not the Rohit the world witnessed in the T20 World Cup.

His team selection, and every decision has come under scrutiny and here are 3 reasons why the veteran should be sacked as the Test captain

3) Next captain already ready in Jasprit Bumrah

Team India already has the next ready in Jasprit Bumrah and from the next Test match onwards in Sydney, he should be made the permanent captain. Bumrah may not be an option for the next 5 years, but he can easily lead the team for the next 2 years, till the time the next captain is ready.

He leads from the front with the ball, understands the game well and already showed his captaincy mettle in the Perth Test match, which India won, rather convincingly. He is someone who loves to perform under pressure and will thrive if made the permanent captain?.

2) Captaincy taking a toll on Rohit's batting

Ever since the New Zealand Test series, Rohit's Test batting has gone down. Team India lost that series, 3-0, and captain Rohit was made the scapegoat for that embarrassing defeat. Since then, he has not been the same player.

Rohit missed the Perth Test match and Bumrah led India to a win. The original skipper returned back from the Adelaide Test and since then India has lost two out of the three matches. In those three matches, Rohit has not even crossed the 20-run mark, as captaincy is taking a toll on his batting.

1) Embarrassing decisions as captain

When Rohit returned for the Adelaide Test match, he decided to play in the middle-order to find his lost form. However, after failing in Adelaide and Gabba, the skipper decided to ruin the opening pair of Yashasvi Jaiswal and KL Rahul.

Both the openers complimented each other well, but Rohit decided to open in the Melbourne Test as KL Rahul was demoted to number 3. KL, who had done so well in the BGT lost his confidence and was dismissed for a duck in the second innings.

Despite abruptly promoting him at the top, Rohit failed once again and could only score 3, and 9 in the combined two innings. Plus, decisions like not playing a swing bowler like Akash Deep in the Pink-Ball Test and instead, throwing him in deep waters at the Gabba was under blunder by the captain.