New Delhi, March 29 (IANS) Former England opener Nick Knight has criticized Chennai Super Kings’ (CSK) decision to break up their successful opening partnership of Ruturaj Gaikwad and Devon Conway in IPL 2025.
Gaikwad, who opened alongside Conway during CSK’s title-winning campaign in 2023, has been pushed down to No. 3 in the first two games, with Rahul Tripathi partnering Rachin Ravindra at the top. However, Gaikwad has been coming in early, often within the second over, leading Knight to believe CSK have “tried to fix something that wasn’t broken.”
“In my top order, I’d have Devon Conway. I’m surprised he’s not playing,” Knight told ESPNCricinfo . “I’d play both of them [Conway and Rachin]. I just feel that Gaikwad and Conway at the top is tried and tested. Conway has a terrific record.”
Knight suggested that Ravindra could bat at No. 3, with the middle order adjusted accordingly. However, he acknowledged that such a move might require MS Dhoni to bat at No. 7—something the CSK icon has occasionally been reluctant to do.
Another aspect of CSK’s batting that baffled Knight was their handling of Shivam Dube, one of the best spin-hitters in the tournament. Dube, who has a strike rate of 169.71 against spin since IPL 2023, was held back until No. 6, coming in after Sam Curran and making 19 off 15 balls.
“Why was Dube not batting higher? I was stunned when he came out after Curran,” Knight said. “They were so far behind the game at that point, they needed something to get them impetus, energy in their run chase and Dube was just held back.”
Knight referenced Dube’s recent performances for India, including a dominant showing against England in a T20I series, and argued that CSK should allow him to “boss the middle overs” instead of waiting until the game is slipping away.
“If that guy can’t do that in this tournament, I must be seeing things slightly different,” he said. “For me, Dube could be the man to take this opportunity and boss the middle section of that innings and take his game forward and take the team forward.”
CSK’s batting order came under further scrutiny when Ravichandran Ashwin was sent in ahead of Dhoni, who eventually walked out at No. 9 with CSK needing 98 off 28 balls. The legendary wicketkeeper-batter still managed to provide fireworks, smashing 30 off 16 balls, including two sixes and a four in the final over off Krunal Pandya.
–IANS
Disclaimer
The information contained in this website is for general information purposes only. The information is provided by BhaskarLive.in and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk.
In no event will we be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website.
Through this website you are able to link to other websites which are not under the control of BhaskarLive.in We have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them.
Every effort is made to keep the website up and running smoothly. However, BhaskarLive.in takes no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control.
For any legal details or query please visit original source link given with news or click on Go to Source.
Our translation service aims to offer the most accurate translation possible and we rarely experience any issues with news post. However, as the translation is carried out by third part tool there is a possibility for error to cause the occasional inaccuracy. We therefore require you to accept this disclaimer before confirming any translation news with us.
If you are not willing to accept this disclaimer then we recommend reading news post in its original language.
