Join Dafanews today and get to enjoy our Free to Play Games.
  • Coming Soon!

  • Join Dafanews

    Create Account

    Account and Contact Details

    Password strength:
    +00
    • Afghanistan+93
    • Aland Islands+35818
    • Albania+355
    • Algeria+213
    • Andorra+376
    • Angola+244
    • Anguilla+1264
    • Antarctica+672
    • Argentina+54
    • Armenia+374
    • Aruba+297
    • Australia+61
    • Austria+43
    • Azerbaijan+994
    • Bahamas+1242
    • Bahrain+973
    • Bangladesh+880
    • Barbados+1246
    • Belarus+375
    • Belize+501
    • Benin+229
    • Bermuda+1441
    • Bhutan+975
    • Bolivia+591
    • Bonaire Saint Eustatius and Saba+599
    • Bosnia and Herzegovina+387
    • Botswana+267
    • Bouvet Island+55
    • Brazil+55
    • British Indian Ocean Territory+246
    • British Virgin Islands+1284
    • Brunei Darussalam+673
    • Bulgaria+359
    • Burkina Faso+226
    • Burundi+257
    • Cambodia+855
    • Cameroon+237
    • Canada+1
    • Cape Verde+238
    • Cayman Islands+1345
    • Central African Republic+236
    • Chad+235
    • Chile+56
    • China+86
    • Christmas Island+618
    • Cocos (Keeling) Islands+618
    • Colombia+57
    • Comoros+269
    • Congo+242
    • Congo The Democratic Republic of the+243
    • Cook Islands+682
    • Costa Rica+506
    • Cote D'Ivoire+225
    • Croatia+385
    • Cuba+53
    • Czech Republic+420
    • Denmark+45
    • Djibouti+253
    • Dominica+1767
    • Dominican Republic+1809
    • Ecuador+593
    • Egypt+20
    • El Salvador+503
    • Equatorial Guinea+240
    • Eritrea+291
    • Estonia+372
    • Ethiopia+251
    • Falkland Islands (Malvinas)+500
    • Faroe Islands+298
    • Fiji+679
    • Finland+358
    • French Guiana+594
    • French Polynesia+689
    • French Southern Territories+262
    • Gabon+241
    • Gambia+220
    • Georgia+995
    • Germany+49
    • Ghana+233
    • Gibraltar+350
    • Greece+30
    • Greenland+299
    • Grenada+1473
    • Guadeloupe+590
    • Guatemala+502
    • Guernsey+441481
    • Guinea+224
    • Guinea-Bissau+245
    • Guyana+592
    • Haiti+509
    • Heard Island and McDonald Islands+0
    • Holy Sea (Vatican City State)+379
    • Honduras+504
    • Hongkong+852
    • Hungary+36
    • Iceland+354
    • India+91
    • Indonesia+62
    • Ireland+353
    • Isle of Man+441624
    • Italy+39
    • Jamaica+1876
    • Jersey+44
    • Jordan+962
    • Kazakhstan+7
    • Kenya+254
    • Kiribati+686
    • Korea Republic of+82
    • Kuwait+965
    • Kyrgyzstan+996
    • Lao People's Democratic Republic+856
    • Latvia+371
    • Lebanon+961
    • Lesotho+266
    • Liberia+231
    • Libyan Arab Jamahiriya+218
    • Liechtenstein+423
    • Lithuania+370
    • Luxembourg+352
    • Macedonia+389
    • Madagascar+261
    • Malawi+265
    • Malaysia+60
    • Maldives+960
    • Mali+223
    • Malta+356
    • Martinique+596
    • Mauritania+222
    • Mauritius+230
    • Mayotte+262
    • Mexico+52
    • Moldova Republic of+373
    • Monaco+377
    • Mongolia+976
    • Montenegro+382
    • Montserrat+1664
    • Morocco+212
    • Mozambique+258
    • Myanmar+95
    • Namibia+264
    • Nauru+674
    • Nepal+977
    • Netherlands+31
    • Netherlands Antilles+31
    • New Caledonia+687
    • New Zealand+64
    • Nicaragua+505
    • Niger+227
    • Nigeria+234
    • Niue+683
    • Norfolk Island+6723
    • Norway+47
    • Oman+968
    • Pakistan+92
    • Palestinian Territory Occupied+970
    • Panama+507
    • Papua New Guinea+675
    • Paraguay+595
    • Peru+51
    • Pitcairn Islands+64
    • Poland+48
    • Qatar+974
    • Reunion+262
    • Romania+40
    • Russian Federation+7
    • Rwanda+250
    • Saint Barthelemy+590
    • Saint Helena Ascension and Tristan da Cunha+290
    • Saint Kitts and Nevis+1869
    • Saint Lucia+1758
    • Saint Martin+590
    • Saint Pierre and Miquelon+508
    • Saint Vincent and the Grenadines+1784
    • Samoa+685
    • San Marino+378
    • Sao Tome and Principe+239
    • Saudi Arabia+966
    • Senegal+221
    • Serbia+381
    • Seychelles+248
    • Sierra Leone+232
    • Sint Maarten (Dutch part)+1721
    • Slovakia+421
    • Slovenia+386
    • Solomon Islands+677
    • Somalia+252
    • South Africa+27
    • South Georgia and the South Sandwich Islands+500
    • Sri Lanka+94
    • Sudan+249
    • Suriname+597
    • Svalbard and Jan Mayen+47
    • Swaziland+268
    • Sweden+46
    • Switzerland+41
    • Syrian Arab Republic+963
    • Tajikistan+992
    • Tanzania United Republic of+255
    • Thailand+66
    • Timor-Leste+670
    • Togo+228
    • Tokelau+690
    • Tonga+676
    • Trinidad and Tobago+1868
    • Tunisia+216
    • Turkmenistan+993
    • Turks and Caicos Islands+1649
    • Tuvalu+688
    • Uganda+256
    • Ukraine+380
    • United Arab Emirates+971
    • Uruguay+598
    • USA+1
    • Uzbekistan+998
    • Vanuatu+678
    • Venezuela+58
    • Vietnam+84
    • Wallis and Futuna+681
    • Western Sahara+212
    • Yemen+967
    • Zambia+260
    • Zimbabwe+263

    General Information

    Enable One Login. All Access.

    I am at least 18 years old and have read and accepted the Terms and Conditions.

    Welcome, !

    You have successfully created your account. You can now enjoy our FREE TO PLAY GAMES

  • Coming Soon!

  • Play Now Play Now

    Welcome, !

    You have successfully created your account. You can now enjoy our FREE TO PLAY GAMES or access our wide range of DAFABET products

  • Coming Soon!

  • Can't Login?

    Coming Soon!

    Dafanews India

    Stay in Loop!

    Join our Telegram community for the latest sports news, highlights, live scores, and more.

    Written by Jamie Alter

    The key factors behind India’s T20 World Cup failure

    November 11, 2022

     

    On October 24, 2021 the pre-tournament favourites India were jolted by a ten-wicket thrashing at the hands of Pakistan to, for all practical purposes limp out of the T20 World Cup in the league stage. On November 10, 2022 the Indian cricket team exited this years’ T20 World Cup after a ten-wicket hammering by England. This time they had done well to reach the semi-finals, given the clear problems weighing down the team, but the insipid performance against England has left many wondering just what was achieved in the 12 months that separated these two ten-wicket defeats.

    After India failed to qualify for the 2021 T20 World Cup semi-finals, Virat Kohli left the captaincy and in his place was appointed Rohit Sharma, the man who had led Mumbai Indians to five IPL trophies. The most successful IPL captain and a white-ball behemoth was entrusted with leading India into the next T20 World Cup in Australia, and along with the appointment of a new head coach in Rahul Dravid, who has achieved success with the Under-19 team in 2018 and then with various India A squads in his capacity as the head of the National Cricket Academy, there was hope of change and a revamped template because it was evident in the UAE last year that India were still playing an outdated brand of T20I cricket.

    Alas, a year on, it does not seem like much has been gained. Barring the astounding rise of the phenomenon known as Suryakumar Yadav, the critical inclusion of rookie left-arm pacer Arshdeep Singh, the failed experiment with Dinesh Karthik as finisher and the injurt-forced absence of Jasprit Bumrah, the Indian squad wore almost the same look as the one that went to last year’s T20 World Cup. And once again the team’s campaign ended with a ten-wicket hammering. Some will say that this one hurts more than the defeat to Pakistan in 2021.

    When the opposition smacks 170 runs in 16 overs without losing a wicket, something is clearly amiss. But this was not about one bad day by Rohit’s team. This was an accident waiting to happen. And here is why.

     

    THE OPENERS’ STRUGGLES

    Rohit and KL Rahul have had issues as a pair. All year, Rohit has played some aggressive cameos to underline the team’s mantra about needing to play more attacking cricket, after they struggled to put up good scores in 2021. But an improved strike-rate from Rohit did not entirely mask his inability to score sizeable innings, even though he did often contribute throughout the year to some good Powerplay scores. Because come this T20 World Cup, Rohit was a big failure. Six innings for 116 runs at an average of 19.33 and strike-rate of 106.42 is bad, but when you amplify the numbers to look at the first six overs, you see where India really shot themselves in the foot.

    In the Powerplay overs, Rohit faced 76 balls, of which 42 were dots, from which he managed just 72 runs. That is a strike-rate of 94.73. Just not acceptable in T20I cricket, from an opener and that too one of Rohit’s immense skill and experience.

    And his opening partner? Well, Rahul was worse. He scored 68 runs from 76 deliveries faced in the Powerplay block, which gives him an abysmal strike-rate of 89.47. But oh, we all know that Rahul believes strike-rates are over-rated, remember? For a batsman of Rahul’s talent, who for years has dominated the IPL run charts, to face 46 dot balls and strike at under 90 in a T20 World Cup is unfathomable. You do not win tournaments with such a conservative approach in the first six overs.

    It has been pointed out all through this tournament that the conditions and quality of bowling has not aided free scoring inside the Powerplay and that it has been difficult to bat upfront. Well then, have a look at these numbers. These are the stats for the top six teams in the World Cup, in the Powerplay.

    England scored at 8.6 runs an over in the first six, facing 78 dot deliveries. The next best was South Africa, who scored at 8.23 per over while facing 75 dots. Then came New Zealand (RPO 7.33, 81 dots) followed by Australia (RPO 6.7, 78 dots), Pakistan (RPO 6.47, 115 dots) and then India (RPO 6.02, 115 dots). It is clear as crystal that Rahul was just too timid in the Powerplay – he faced a maiden over in the match with Zimbabwe for his fifth such instance in T20Is  – and Rohit never once looked comfortable. Both of Rohit’s two noticeable scores involved several chances. Where did all the talk of being aggressive go when India’s opener were so meek inside the Powerplay?

     

    DEPENDENCY ON KOHLI AND SKY

    What this approach did was put added pressure on Virat, Suryakumar and Hardik Pandya to score more runs and faster runs. It was expected given the bowling woes during the Asia Cup and after that India’s batting would have to step up in Australia, but to see just two players in Kohli (the tournament’s leading run-scorer) and Surya (who acquitted himself well in first tour of Australia) and to a lesser extent Pandya do all the heavy lifting was to wonder what this team got from its poor selection and rigid thinking in regards to their openers.

    No doubt, the lack of runs from Rohit and Rahul’s conservative approach were factors in why India did not reach the final. It has been said before that there is no room for Rohit, Rahul and Kohli in this 11 and it was once more underlined. Kohli played the innings of his life against Pakistan and four fifties in six innings, and while you can argue about his strike-rate at times, the man finished the World Cup with 296 runs while striking at 136.40. Kohli can remain India’s anchor, and if need be he can be asked to open.

    Surya dazzled with fifties against South Africa, Netherlands and Zimbabwe but failed, again, versus Pakistan and then in the semi-final when he faced just his fifth delivery of legspin all tournament. Pandya played a pivotal role in guiding Kohli and India to that tense win over Pakistan, and then stepped up against England with a dazzling half-century. But this dependency on these three batsmen shows how flimsy India’s batting was.

     

    MISGUIDED FAITH IN DK

    Which brings us to Karthik’s role in this T20I setup. To my mind, there has never been a more outlined or precise selection in Indian cricket’s white-ball history. That is to say, no player has ever been picked – or recalled, in this case – with as specific a role as Karthik’s. After a super run for perennial play-off chokers Royal Challengers Bangalore in this year’s IPL, where he finished off innings and matches repeatedly, Karthik was recalled at the age of 36 with the exact job outline of being India’s finisher at the World Cup.

    Hence he was played in almost every T20I match India played across six months, and trained for a very explicit role: to hit balls into the stands when there were only a couple of overs left in a match. In this high-risk role, where finishers stand to fail more than succeed, Karthik was backed unanimously by the team management.

    In 19 innings from the time he was recalled and before the start of this World Cup, Karthik scored 273 runs at a strike-rate of 150.82. In this period, he faced more than 15 deliveries on just five occasions and the results were scores of 30* off 21 balls, 55 off 27, 12 off 17, 41* from 19 and 46 from 21. He failed in 10 innings, and in these there were six instances where Karthik’s strike-rate was less than 85 and as low as 66.66.

    Clearly this was a struggling experiment, but India backed him for the World Cup while keeping Rishabh Pant out. Come the first match of the World Cup, against Pakistan at the MCG, and Karthik failed in the exact role and situation for which he had trained with this team for six months. He walked out in the last over and made one run from two balls, out stumped against the kind of bowling he has statistically struggled the most when facing: left-arm spin.

    Then on that bouncy Perth surface, where South Africa’s pace attack had reduced India to 49/5 inside nine overs, Karthik was taken out of his familiar finisher’s role and asked to bat for time in the presence of Surya. Here too his vault of experience came up short, for he pottered about 15 deliveries for just six runs before a terrible shot saw him walk back. Then against Bangladesh, Karthik was run out for seven off five and was not played again.

    How did the team management that backed him for 28 T20Is this year suddenly go back to Pant for India’s final league game and then the semi-final? What did the misguided faith in Karthik, aged 37 and recalled only with this World Cup in mind, ultimately get India?

     

    A WEAK MIDDLE ORDER

    All this time India were focused on Karthik as their finisher, they failed to locate other middle order options. A top four of Rohit, Rahul, Kohli and Suryakumar meant that no one could bat higher than five. Deepak Hooda, whose call-up to India’s squad was based on a strong IPL season where he batted at only No 3 and 4, was shunted down to five, six and seven when the preferred top four was reunited. Pant was tried and failed to use his chances. Shreyas Iyer was given a long rope and then dropped, Venkatesh Iyer was briefly tried and discarded, Sanju Samson was tried and also not persisted with and Ravindra Jadeja was used and looked a good bet until he inexplicably injured himself while ski boarding in Dubai during the Asia Cup. This chopping and changing on account of big players being rested left India with a shaky middle order and saw Axar Patel being batted as high as No 5.

    AND WHAT ABOUT THE BOWLING?

    Yes, Bumrah not being there was a big blow. And yet India’s bowlers did not too badly to help the team into the final four. During the Super 12 stage, India’s bowling unit had better numbers in the Powerplay than the two teams boasting the best pace attacks, South Africa and Pakistan. Bhuvneshwar Kumar’s natural style of bowling might not suit Australian conditions and he is not quick at all, but he ended the World Cup with an economy rate of 6.16. Mohammed Shami, recalled for the World Cup in place of Bumrah, took six wickets while conceding runs at 7.15 per over. Arshdeep, the find of 2022, was India’s leading wicket-taker with 10. Pandya was next best with eight wickets and an economy of 8.11, which is fine for your sixth bowler.

    Ashwin, who before this World Cup had played just seven T20Is all year, took six in six at an economy of 8.11. The weak link was Axar, whose role in India is to start in the Powerplay and run rings around visiting teams. He managed three wickets in five matches, conceding runs at 8.62 an over.

    Why did India not play Yuzvendra Chahal for even one match in Australia, where the grounds are bigger and legspin has succeeded? No one has come forth with answers. Where did the faith shown in their death-overs specialist Harshal Patel disappear? Why was Ravi Bishnoi, who has a superb record in 2022, discarded from the reserves in place of two seam options who were not called on in Australia?

    The abiding image of India’s bowling at the World Cup, unfortunately, will be Adelaide Oval against England, where Bhuvneshwar gave away 25 runs from two overs, where Shami bled 39 from his three and where Ashwin conceded 27 off 12 balls. What did the vast experience of these three veteran bowlers achieve, in the end?

    About the Author


    Written by Jamie Alter

    Jamie Alter is a sports journalist, author, commentator, anchor, actor, and YouTuber who has covered multiple cricket World Cups and other major sporting events while working with ESPNcricinfo, Cricbuzz, Network 18, the Zee Group and as Digital Sports Editor of the Times of India. Follow Jamie on Twitter, Youtube and Instagram.

    ×
    Embed Code