India vs. England: Former Cricketer Calls for Shardul Thakur's Omission, Favors Kuldeep Yadav in Second Test

Friday - 11/07/2025 05:23
Following India's Test defeat against England, Sanjay Manjrekar suggests a bowling lineup change. He wants Kuldeep Yadav to replace Shardul Thakur. Manjrekar highlights the need for quality spinners in the team. He notes that English conditions are now favorable for spin bowling. Manjrekar also expects more tactical awareness from Ravindra Jadeja, especially on pitches offering assistance.

Former India Player Urges Pacer's Removal After Test Defeat

Following India's defeat in the first Test against England, former Indian cricketer Sanjay Manjrekar has advocated for changes in the team's bowling strategy. He suggests replacing Shardul Thakur with left-arm wrist spinner Kuldeep Yadav to address the bowling deficiencies exposed during England's successful run chase of 371 runs.

Jadeja under scrutiny after first Test *Ravindra Jadeja faced criticism for his performance in the first Test against England.*

While Jasprit Bumrah managed to take a five-wicket haul in the first innings, the other pace bowlers, including Mohammed Siraj, Prasidh Krishna, and Shardul Thakur, struggled to create a significant impact. This allowed England to secure a victory with five wickets remaining.

Manjrekar, speaking on 'Match Centre Live', stated, "Kuldeep Yadav has to come back. I'm sorry to say, but Shardul Thakur has to go out."

He further added, "That is one change India will have to make. As for Nitish Kumar Reddy - I backed him for the first Test purely based on what he did in Australia. It's an unpopular choice, because when he comes in, the balance does get affected a bit. He won't quite bowl like a fourth seamer, so India need to take a hard call: even in English conditions, they must go with quality bowlers."

Thakur faces potential axe after underwhelming performance *Shardul Thakur's place in the team is now under scrutiny after a lackluster performance.*

Manjrekar emphasized the increasing suitability of English conditions for spin bowling due to drier summers. "If that means playing two spinners, so be it. Pick your best bowlers, irrespective of the conditions. You don't have the luxury of someone like Mohammed Shami available, or the full-strength pace battery, so I'd go one seamer short and bring Kuldeep into the XI. He has to play."

"Let's also acknowledge that English summers these days are largely dry - thanks to global warming, perhaps - and that does open the door for spin. In a way, it's time to reintroduce the idea of India playing spin in England. Ben Stokes has already changed the narrative with common-sense, aggressive cricket. India need to embrace the same clarity."

He further explained, "There was a time when India would play three spinners no matter what — whether in New Zealand or England. If Kuldeep is in your squad, play him. Don't go with seamers just because you're playing in England. I'd drop one seamer and bring in Kuldeep Yadav."

Expectations from Jadeja

Manjrekar also shared his expectations from Ravindra Jadeja. "It's not fair to be overly critical of younger players like Prasidh Krishna - there are obvious areas for improvement. But I am going to be critical of Ravindra Jadeja. This was a final-day pitch with rough patches for him to exploit. And while there were a couple of chances, we have to expect more from someone of his experience."

He added, "I felt he didn't use the rough nearly enough — especially against Ben Duckett. Against Ben Stokes, yes, he did make an effort. But it was only much later in Duckett's innings that Jadeja started using the rough properly. When you're dealing with experienced bowlers and seasoned batters, you expect a higher level of tactical awareness. Somewhere, I felt Jadeja was disappointing. The seamers had no help from the surface — but Jadeja at least had something in the pitch working in his favour."

Total notes of this article: 0 in 0 rating

Click on stars to rate this article
You did not use the site, Click here to remain logged. Timeout: 60 second