IPL 2019, MI vs RR: Failure to seize opportunities led to Mumbai Indians' defeat against Rajasthan Royals

In hindsight, Mumbai should have accelerated earlier, they should have taken at least two of the catches that they spilled and also picked the playing XI based on conditions rather than basing it on recent past.

Gaurav Joshi, Apr 14, 2019 09:12:42 IST

The first six overs of the Mumbai Indians innings went perfectly to script. They had been inserted to bat on a benign deck and after first powerplay overs had raced along to 57 for no loss. Even the attention to detail in those powerplay overs was so precise. In the first two overs, Rohit Sharma and Quinton de Kock assessed the conditions, restricted any fate of attempting a big shot and trusted their defence. Then the pair exploded by scoring 18, 14 and 12 respectively of the next three overs to seize the momentum. All the stars seemed to be aligning and it looked like a vintage batting display was on the cards.

In the end, Mumbai posted a competitive score of 187, but still managed to lose the match by four wickets. Sportzpics

In the end, Mumbai posted a competitive score of 187, but still managed to lose the match by four wickets. Sportzpics

In the end, Mumbai posted a competitive score of 187, but still managed to lose the match by four wickets. It wasn't like they bowled poorly either, so where did it go wrong? Firstly, one cannot discount the calibre of Jos Buttler. The dynamic batsman was top notch, but it was the Mumbai Indians' inability to apply the finishing touch with the bat and ball that had cost them the match.

After the openers had added 97 in first 11 overs and with the hitting prowess of Hardik Pandya and Kieron Pollard perhaps Mumbai were guilty of not pushing hard enough through the middle overs. Between 11 and 15 overs, Mumbai only managed 29 runs for the loss of one wicket. While it is difficult to point the finger at Pollard, his innings of six from 12 balls will not go unnoticed by the coaching staff.

Had Mumbai stated their assault earlier then they could have put Rajasthan bowling unit under more pressure. Coming into the match, the Royals were ranked as the worst bowling side in the overs 16-20 in terms of economy-rate, so had Mumbai attacked earlier there was potentially a chance that they could have posted a score beyond 200.

However, in the post-match presentation, Rohit Sharma stated 187 was an adequate total. "Without dew, 175+ is a good score and we had a decent score to defend, but we failed to take early wickets".

Rohit was one of the reasons Mumbai failed to make early inroads. The Mumbai captain dropped a sharp chance off Ajinkya Rahane in the first over of the innings. Rahane had yet to open his account at the time and ended up adding a further 37 from 18 balls to give the Royals a breezy start. It was such small moments that summed up Mumbai's inability to cash in at the crucial phases of the game.

Twenty20 cricket is dependent on luck and Ishan Kishan at the press conference after the match stated the same. "It was few lucky shots and some good batting that went against us tonight."

But the good teams make their own luck. Mumbai dropped three more catches, albeit each one of them was tough. In all the tight matches that Mumbai have won this season, they have managed to seize one of the tough opportunities.

Apart from all the misfortunes, Alzarri Joseph had a poor outing with the ball. Perhaps it was the nature of the pitch or the pedigree of the opponent. But a surface that was showing signs of holding up, it was bizarre that the pacer didn't attempt one slower ball.

At the toss, Rohit had stated that spinners generally tend to get more out of the surface during a 40-over match. If that was the case then it was difficult to understand why an experienced campaigner and the master disguiser of the slower cutter in Lasith Malinga was not part of the playing XI.

In hindsight, Mumbai should have accelerated earlier, they should have taken at least two of the catches that they spilled and also picked the playing XI based on conditions rather than basing it on recent past. But such is the nature of the T20 game that minor lapses ended up costing matches and one over can change the course of the match. Joseph was smoked for 28 runs in one over, but eight of those runs were from edges from perfectly executed yorkers. The over had changed the match.

Mumbai will learn that playing 85 percent does not guarantee victory and it is important not to get complacent. The fact that it was one splendid innings that took the game away will hurt, as will the fact that the opposition was missing Ben Stokes. But that is the nature of the T20 game and Mumbai had lost due to minor mishaps that can be fixed overnight.

ll the latest news, opinions and analysis from IPL 2019, click here

For the full schedule, date, time and venue of all the matches of IPL 12, click here

Check out the full points table for IPL 2019, including holders of Orange and Purple Caps

Updated Date: Apr 14, 2019 09:12:42 IST


IPL 2019 POINTS TABLE

Pos. Team P W L D Pts.
1
Chennai
11 8 3 0 16
2
Delhi
11 7 4 0 14
3
Mumbai
10 6 4 0 12
4
Hyderabad
10 5 5 0 10
5
Punjab
10 5 5 0 10
6
Kolkata
10 4 6 0 8
7
Rajasthan
10 3 7 0 6
8
Bangalore
10 3 7 0 6
See Full Table





Top Stories

Rank Team Points Rating
1 India 5007 116
2 New Zealand 3570 108
3 South Africa 4397 105
4 Australia 4566 104
5 England 5490 104
6 Sri Lanka 4737 93
Rank Team Points Rating
1 England 7259 123
2 India 8508 120
3 New Zealand 6071 112
4 South Africa 6181 112
5 Australia 5701 108
6 Pakistan 5147 97
Rank Team Points Rating
1 Pakistan 5280 135
2 India 5726 122
3 England 3036 121
4 Australia 3613 120
5 South Africa 3366 120
6 New Zealand 3367 116