"Any team is bound to miss a bowler like Shami": Mohit Sharma after GT's loss

Gujarat Titans pacer Mohit Sharma feels that it is hard to replace any bowler having Mohammed Shamis calibre after the side faced defeat against the defending champions Chennai Super KingsIndias star speedster Mohammed Shami will not feature in IPL 2024 as he is still not fully recovered from his ankle surgery He is expected to make his appearance during the home test series against Bangladesh Shami will also likely miss the T20 World Cup 2024 which will be jointly hosted by the West Indies and the USA in JuneAny team is bound to miss a bowler like Shami and you cant replace him with anyone But injuries are uncontrollable and you must see how to move ahead with it said Sharma who played for CSK between 2013 and 2015 and has been with the Titans since 2022 during the postmatch press conferenceAlso Read IN PHOTOS IPL 2024 MI vs SRH Heres all you need to knowAs for GT its the first year for Spencer Johnson and Azmatullah Omarzai They havent played much cricket yet Therefore we must be patient with them and not become too resultorientedWe must not bother about the runs leaked or the result of the contest but how successful we are with our plans and how we are working on it backstage These things would come in handy in the second half of the event opined SharmaWith youngsters like Rachin Ravindra Ruturaj Gaikwad and Shivam Dube leading the batting charge Chennai put on a huge taret of 207 against Gujarat Titans No mercy was shown on GT bowlers as Umesh Yadav conceded 27 runs in just two overs followed by ace spinner Rashid Khan for 49 in four overs Khan also bagged two wicketsMohit Sharma added that CSK milking runs in powerplay also contributed to the big loss Not much of a difference in CSKs strategy It used to be the same when I used to play for CSK and we usually tried to get the maximum out of the powerplay overs he saidWe knew it was going to be a similar scenario especially with Rachin Ravindras batting of late However we failed to execute our plans properly and also failed to judge the width and length during our bowlingAlso Read Hats off to him and he is playing with confidence now Michael Hussey on DubeWe failed in executing our plans properly We began to bowl the slower ones too early and too wide off the off stump leading to them scoring freely It happens that the plans always dont get executed properly every timeBut its a big tournament and we have ample time to go back to the drawing board rectify our mistakes and start afresh We had a target of 200 as the par score on this wicket and CSK played just the way we had thought They were on course for 225230 before settling for 206 but since we failed to implement our plans we believed we gave away 1520 runs extraSharma also defended the visitors decision to bowl first stating that dew is always a factor in night games though interestingly there was hardly any dew on Tuesday nightDont think the pitch has a role to play Generally if we win the toss and decide to bowl its because we know that the dew might play a factor later during the gameBut there was no dew Tuesday As usual we decided to bowl and restrict them to a par total while dew would have been an added positive for usHad the wicket been drier CSK would have moved in with two spinners But had the GT pacers bowled in the right areas it would have been tough for them to hit he consideredDespite the 63run loss Mohit refused to blame the batters for the poor show CSK bowlers implemented their plan to perfection to restrict GT to 1438 with Sai Sudharsan 37 being GTs top scorerI wont say we failed to score runs but credit to the CSK bowlers for bowling brilliantly Deepak Chahar started well and at the end of the day it all boils down to the number of variations you possess and when and how to use themDont think it was a pressure scenario for us The wicket was good and 200 was a gettable total here But the wickets that we lost initially leading to lack of partnerships followed by CSK bowlers bowling the right length led to our inability to up the run rate and we began lagging in every over he signed offWith PTI Inputs