Going into the first Twenty20 International (T20I) of the three-match series against Australia, Team India were undoubtedly favourites considering the hosts have seen their worst phase in limited-overs cricket in recent times.
Going into the first Twenty20 International (T20I) of the three-match series against Australia, Team India were undoubtedly favourites considering the hosts have seen their worst phase in limited-overs cricket in recent times.
However, the visitors got a reality check when they fell short by four runs and Australia snatched a much-needed victory and went 1-0 up in the series.
India have themselves and no one else to blame for this result as the captain and the rest of the boys made errors that could have been easily avoided but eventually, cost them the match.
Here are five reasons why India lost the first T20I at the Gabba, Brisbane on Wednesday:
1. Kohli's bowling strategy wasn't the best
)
Knowing Chris Lynn's image of giving his team flying starts, especially in the shortest format, Kohli should have brought in the spinner much early than he actually brought. Kohli brought Kuldeep Yadav into the attack only in the seventh over but by then Lynn had done the damage. Kuldeep dismissed D'Arcy Short first before bagging Lynn's wicket. Lynn had by then done his job with a contribution of 37 crucial runs off just 20 balls. Kohli made the same mistake when Maxwell was on fire. Maxwell's struggles against wrist spinners are not hidden and the Indian captain should have used Kuldeep more against him. PC: AFP
2. Poor fielding
)
There were plenty of misfielding by both the sides but it hurt the Indians the most in the end. The Indian skipper himself was not at his best on the field as he not only did quite a few mis-fields but also dropped Finch's catch when the latter was just one six runs. Finch eventually ended up quick-firing 27 off 24 balls. The other Indian fielder who dropped a catch was Khaleel Ahmed. PC: Twitter
3. Rishabh Pant's failed finishes
)
Even the Indian skipper Virat Kohli has admitted that Pant's dismissal was the turning point of the match or in a harsher way, that cost India the game. Pant has been in situations like this quite a few times in recent times but he has repeatedly failed to show maturity and responsibilty. Like today, he got out because he attempted to play the stylish scoop-shot which was not the demand of the situation. More than going for the big shots, India needed him to save his wicket and provide Karthik the required support from the other end. PC: AFP
4. Kohli should have batted at No. 3
)
The No. 3 slot in a team calls for the best batsman of the side and face as many balls as possible. Batting at No. 3, Kohli has scored 16 out of his 18 half-centuries so it was a terrible decision to send Rohit at No. 3 and not himself. PC: AFP
5. Did India miss MS Dhoni?
)
This final point is not exactly the reason but it is not wrong to consider how things would have changed had Dhoni been in the XI. When DK made the terrible choice of giving Krunal Pandya, the new and inexperienced batsman the strike in a demanding situaion, that's when social media went berserk about how Dhoni would have never done that and would have taken the responsilbity on his own shoulders. Maybe, Kohli missed Dhoni's tips as a captain too on the field? Meanwhile, Dhoni was busy inaugurating MS Dhoni Residential Cricket Academy in Nagpur! PC: PTI
