Stupid… Stupid…Stupid

Stupid… Stupid…Stupid !!!

These were the words of Gavaskar during commentary after Rishabh Pant played an ill-advised scoop shot despite fielders stationed at third man and fine leg, precisely to counter that stroke. Predictably, Pant’s attempt resulted in a mistimed hit, landing safely in Lyon’s hands at third man. Shots like these, with inherently low control, are risky, and attempting one against a medium pacer like Boland on the expansive boundaries of the MCG was outright stupid.

But this wasn’t the only stupidity during the match. When we reflect on India’s performance in the 4th Test of the Border-Gavaskar Trophy at Melbourne, a series of avoidable stupidity stands out.

 

Stupidity 1: Team Selection

The debacle started with questionable team selection. Dropping Gill in favor of two batting all-rounders (Sundar and Reddy) seemed like an overcompensation for the poor form of Kohli and Sharma in the XI. Covering for one out-of-form batter is manageable but carrying two in a high-stakes series against Australia, in their backyard, proved disastrous.

 

Stupidity 2: Disruption in the Opening Pair

Rahul and Jaiswal were good as openers in the first two Tests. However, Rohit Sharma, returning at No. 6 without meaningful contributions in the 2^nd and 3^rd test, forced his way back to the opening role and disturbed a fruitful pair. This reshuffle demoted Rahul to No. 3, affecting both players’ form. With Rohit and Rahul faltering and Kohli offering little at No. 4, the top order became a glaring hole, leaving the lower order an uphill battle with both bat and ball.

 

Stupidity 3: Run Out Disaster

In the first innings, India was cruising at 151/2, chasing Australia’s mammoth 479. A solid partnership between Jaiswal (82) and Kohli (36) had flourished. Then came the turning point—Jaiswal attempted a suicidal single to mid-on while Kohli was ball-watching, resulting in a needless run-out. This moment of recklessness caused a collapse: Kohli edged behind soon after, the night-watchman fell cheaply, and India slid to 159/5 from a commanding position.

Why does this keep happening? In Test Cricket, run outs are unpardonable. If Sharma had been Jaiswal’s partner, would this have occurred? Kohli has been involved in few costly runouts recently.

 

 Stupidity 4: Night Watchman Mismanagement

Sending in a night watchman with 30 more minutes of play left—when Kohli was well-set on 36—was a puzzling decision. Kohli don’t need protection. This was tried earlier in the series against New Zealand to protect Kohli, and it was no different here. Just as before this time too the outcome was no different.

 

Stupidity 5: 3 Dropped Catches

Pant’s dismissal in the first innings already made the highlight of this write-up, so skipping to the rest. Three Dropped catches in Australia’s second innings each of Khawaja, Labuschagne and Lyon robbed India of any chance to wrest control.

 

Stupidity 6: Sharma’s Recklessness

On the final day, chasing 340, a draw was India’s best hope. Sharma dug in admirably during the first hour, showing patience and discipline. Then, out of nowhere, he attempted a leg-side whip off Cummins, edged the ball, and was caught by Marsh at slips. The moment of folly ended his resistance, further deflating India’s hopes. Runs are low priority at this point and playing time was utmost. What forced Sharma’s recklessness at a crucial juncture.

 

Stupidity 7: Kohli’s Endless Off-Stump Chases

In the last over before lunch, Kohli chased a wide delivery outside off-stump from Starc, edging to Khawaja. The sight of Kohli nicking deliveries to the slips or keeper has become a painful and all-too-familiar occurrence for Indian fans. When is the end to this agony for Indian fans?

 

Stupidity 8: Pant’s Uncharacteristic Misstep

Pant played a very uncharacteristic innings in the second outing. Farmed a brilliant partnership with Jaiswal that lasted between Lunch and Tea. Just when it all looked good, the part-timer Head dished a half cracker that tempted Pant to play the pull only to find the fielder stationed at midwicket. Having showed immense maturity to play a patient innings, one would wish he continued in the same tone and curbed the instinct to pull that could have saved India the TEST.

The rest of the batting lineup crumbled, unable to survive the remaining 38 overs. This dismissal shattered any chance of salvaging the game.

 

Stupid… Stupid… Stupid is the only way to describe India’s performance in this Test. The team management and selectors must address glaring issues ahead of the final Test in Sydney.

 

Should Team Management/Selectors step up and drop Kohli & Sharma from the 11? Or play them as scapeGOATs for series defeat?

 

The anger is currently at tipping point. This series would have panned different if Sharma had not returned from paternity leave. There is no way to sweep this under the carpet. Sharma and Kohli must go. But when is the right time to bring down the axe. Now? Or at the end of the series?

 

Where did India fall Short

With New Zealand coming off a series defeat to Sri Lanka, it was easy to assume they wouldn’t pose a serious challenge to India, especially in similar conditions. But one of India’s main adversaries turned out to be complacency itself—a mindset that often undercuts even the best teams.

Complacency and Selection Questions

The No. 4 batting spot is traditionally given to the most skilled batter, as it’s considered the ideal position to make an impact. However, despite nearly four years of underwhelming form, Virat Kohli’s place in this position has largely gone unchallenged due to his reputation.

Adding to this, Rohit Sharma’s recent statements about “big runs being overrated without tournament wins” may have hinted at a shift in focus, valuing impactful cameo contributions over sustained innings. While this approach may work in shorter formats, it doesn’t lend itself well to Test cricket, which could explain some inconsistency in his recent performances.

Skill Development and SENA-Focused Approach

Over the last decade, India’s strategy has heavily emphasized winning series in SENA (South Africa, England, New Zealand, and Australia) countries. To succeed in seaming conditions, Indian batsmen adapted their skills, often at the expense of their proficiency against spin—a traditional strength. The emphasis on international pitches has also limited the time players can spend in domestic circuits, which are critical for honing homegrown skills, especially against spin.

This oversight became evident in matches like Pune and Mumbai, where spin-friendly surfaces exposed the team’s weaknesses. Additionally, a rare failure on a seaming pitch, where India was bowled out for 46, indicated broader issues.

Mumbai Test Decisions

Heading into the Mumbai Test, it was known the pitch would be bone-dry, yet management chose to play with two seamers. This decision was puzzling, as only one seamer was likely needed on such a surface. Such tactical choices hinted at a lack of alignment between strategy and conditions, something even the average fan could question.

Looking Ahead

These points are only the most visible of India’s struggles. It’s time for a thorough introspection—identifying root causes, refining strategies, and making balanced, long-term decisions to strengthen the team’s overall health and resilience.