Earlier this year, in the last Test match of India's tour of Australia in Sydney, whispers of internal conflict started doing the rounds within the Indian camp. The spotlight was on a reported tension between captain Rohit Sharma and newly-appointed head coach Gautam Gambhir.
What fueled the rumors was Gambhir replacing the traditional pre-match media interaction – a task normally performed by the captain. The sudden change of guard raised eyebrows, and some even went to the extent of opining that Rohit's position in the playing XI was under threat after a loss of form.
The buzz took a dramatic turn at the toss when, to the surprise of all, Jasprit Bumrah stepped out to partner Australia's Pat Cummins, confirming that Rohit had decided against playing the match.
During a mid-match broadcast chat, Rohit spoke about the move, clarifying that the decision to rest was his own, a result of his battle with form. Alas, the tactic failed. On Day 2, Bumrah got injured, badly denting India's bowling attack. Without their strike bowler, India collapsed in Sydney and lost the series 3-1.
Nearly three months on, Rohit has gone into great detail about the build-up to that moment, giving fans an insight during an open appearance on the Beyond23 Cricket Podcast with former Aussie captain Michael Clarke. He took listeners through his mindset and thought process leading up to the Sydney Test.
Having taken paternity leave for the series opener in Perth, a match India had won convincingly, Rohit returned to the team for the Adelaide Test. There, he conceded, things did not go his way.
I didn't play well (in Adelaide). Then I went to the room, and I was like, I should have opened man. I would prefer to fail at doing what I am doing and where I am doing it. I mean, that's my place, that's my position. I would prefer to go there and bat, whether I succeed or not, it's a different thing. But I'm playing in my natural position for the team," Rohit opined.
Nevertheless, he chose not to press the panic button yet.
"And I said, no. It's just one game. Let's not overcomplicate, let's play another game. It's 1-1. We can attempt and do something different around Brisbane. And then, it was a draw. When we returned to Melbourne, we changed our mind. I went back to open the innings, and in the final Test match. I had to tell myself the truth. I wasn't striking well. I did not want to put myself in that position only because we had dropped the other guys who were not striking either," he added.
When the discussion shifted to Sydney Test, Rohit revealed that the team was eager to provide young Shubman Gill an opportunity, particularly after he had been left out of the Melbourne game. Rohit believed it would be best for the team's equilibrium to step aside.
"We somehow felt that Gill should play, he is such a fine player. He was missed out in the last Test match. I'm like. okay, if I am not playing with the ball in hand properly. things can shift five days later, ten days later," he said.
His proposal wasn't, however, accepted unhesitatingly.
"I talked to the selector and the coach, and there was a debate around it. You try and put the team first, you see what the team desires, and make the call accordingly. Sometimes it will succeed, sometimes it won't. That's the way it is. Every choice you try and make, you aren't assured success," Rohit admitted.
Even though the Test series was a disappointing one for India, Rohit's captaincy saw a revival shortly thereafter. Leading India to a 3-0 whitewash of England at home in an ODI series, he then won the Champions Trophy title, beating New Zealand with a dominating final performance.
Read also| IPL 2025: DC Edge Past RR in Super Over Thriller to Claim Top Spot on Points Table
Read also| IPL 2025: Tilak and Bowlers Shine as MI Halt DC’s Winning Streak with 12-Run Victory