In a candid revelation that has stirred the cricketing world, veteran Indian spinner Ravichandran Ashwin has disclosed the underlying reason behind the surprising decision to send pace bowler Akash Deep as a nightwatchman ahead of specialist batsman Rishabh Pant during India's chase in the Lord's Test against England. Ashwin stated that Pant has a long-standing aversion to batting in the final few overs of a day's play.
The incident occurred on Day 4 of the 3rd Test at Lord's, with India chasing a target of 193 runs. After losing captain Shubman Gill's wicket with approximately 20-25 minutes remaining for stumps, many expected Rishabh Pant, the designated No. 5 or 6, to walk out. Instead, Akash Deep emerged, leading to widespread speculation and some criticism from fans.
Pant's Past Reluctance and Ashwin's Anecdote
Speaking on his YouTube channel, Ashwin narrated a couple of instances where Rishabh Pant had expressed his discomfort with batting in the dying stages of a Test day.
"I'll tell you a story," Ashwin began, recalling a Test match in Mirpur (Bangladesh) where India was chasing around 140 runs to win. "I was sitting and relaxing in the dressing room after bowling. It was all hot and humid. I was sitting next to the analyst, and Rahul Dravid (head coach) was there a little further."
Ashwin continued, "After we lost the first two wickets, Rishabh said 'main nahi ja raha batting karne' (I am not going out to bat) to Rahul bhai. There was a good 30-40 minutes left. But he said I am not going. When the next wicket fell and the No. 4 batter was supposed to go in, he went inside and they had to send Axar Patel first, I guess, and then Jaydev Unadkat to go in as the nightwatchman."
Ashwin cited another similar instance when Virat Kohli got out against New Zealand, and Pant again was "not in a mood to go out," leading to Mohammed Siraj being sent in.
The Team's Strategy to Protect Key Batsmen
According to Ashwin, this pattern from Pant is the actual reason for the team management's decision to send Akash Deep at Lord's. "Rishabh does not like batting in the last 30-40 minutes of the day. That's why they sent Akash Deep," Ashwin explained.
He acknowledged the inherent risks of such a move: "But see, it is about protecting your best batter, yes. But when you send a batter like Akash Deep and then he gets out, it puts you in even more of a situation." Akash Deep was eventually dismissed on the penultimate ball of Day 4 by Ben Stokes, for just 1 run off 11 balls, leaving India at 58/4 at stumps and adding to the pressure on Day 5.
However, Ashwin defended the overall strategy, especially given Pant's current form and importance to the team. "It is a catch-22, but today it was okay because it was only 20-25 minutes. Because you want 190 (the target), and protecting Rishabh is important. So it's a good decision that he made. But all in all, I want to see how Rishabh goes about his business. The right strategy was to ensure Rahul bats long, but Rishabh could have gone in. 30-40 runs is crucial in such a low-chasing total."
Head coach Gautam Gambhir and the team management seemingly endorsed this strategy, prioritizing the protection of a key batter like Rishabh Pant for the start of the next day's play, even if it meant risking a tail-ender for a few crucial overs. While the move at Lord's didn't entirely pay off with Akash Deep's late dismissal, Ashwin's comments offer a rare insight into the dynamics and decision-making within the Indian dressing room during critical Test match situations.
Related Articles
Leave a Reply