#T20WorldCup @Indianmourinho reflects on @BCCI 's campaign so far:

Q: What has resulted in India's campaign turning out the way it has so far? Is it the uncontrollables - toss & decks getting better to bat in the second innings?

No doubt they have played a role. But you can
@IndianMourinho only completely shift the blame to that if you got the controllables right. India didn't do that.

India vs spin in WC 2021:

16-0-76-3 - that's not even 5 RPO. And India are a subcontinental team. Even if they are set back by pace, they should be able to reconstruct innings
@IndianMourinho at 7-7.5 against spin. At 7.5, that would be a difference of 44 extra runs the bowlers could have had.

There was plenty of evidence that this batting unit was going to struggle against spin even ahead of the start of the tournament.

This comment sums it up all. Look at the
@IndianMourinho conclusion that was arrived at after looking at the numbers of 3 of India's biggest batters:


At least in the first game, two of them were opening - one way to minimize the potential damage. In the second, Rohit and Kohli were positioned at 3 & 4 -
@IndianMourinho - two positions that demand your most skillful players/hitters of spin.

Instead of splitting them with left-handers and/or better players of spin, India lined them up like lambs to slaughter.... and well, got slaughtered.
@IndianMourinho On Ishan Kishan opening: 

This is the first thing that hits you when you try to fit Ishan Kishan in this setup at Dubai against an attack that is set up the way Kiwis are:

Except, however, for India it didn't. They fed him to pace, lost him, and
@IndianMourinho and then came out of Powerplay with two of their weakest attackers of spin facing Santner and Sodhi at a venue that provides some assistance for them and had big boundaries.

If Kane Williamson was asked to set the innings up after PP in a way it suits them, he would have gone
@IndianMourinho 35/2 in 6 with KL and Ishan dismissed and Kohli and Rohit at the crease looking at each other in shock at having to accelerate against spin.

The shots they played were a result of it.
On Bhuvneshwar Kumar:

If you back out from something you were very confident of after one result that doesn't go your way, you are either admitting you have got it wrong all along or just gone into a panic mode and reacting as a result.

Be it fitness wise or on numbers, there
was, again, enough evidence that this move was going to cost him.



India continued to be in denial about it. It finally hit them after looking at the warm-up performances and the opener vs Pakistan.

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Global Spot League

Global Spot League Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @GlobalLeagues

31 Oct
#T20WorldCup @IndianMourinho on Team India:

India could keep the same XI, in the same order, and ace the rest of the group games, but if they want to tap all that they have out of their batters, the order should be:

Rohit
Kohli
SKY
Pant
KL
Hardik
Jadeja

What it does:
@IndianMourinho Taps into Kohli's PP value 
Gives India an added dimension of range vs pace down the order in the form of KL, in addition to power vs pace that they already have
Pushes SKY up to a role he would be more comfortable at, where his value vs spin and PP pace kicks in
@IndianMourinho But there is a catch: at the moment if you introduce spin in PP, KL (Ind) tries to take them down. Pairing Rohit and Kohli will force one of them to go out of their way and weaken each other.

That's fine because the benefits far outweigh the disadvantage.
Read 4 tweets
30 Oct
Matchdays with @IndianMourinho: #T20WorldCup #PAKvAFG

Pak's bowler management: I found that a bit too one dimensional.

Ov 1-12: 67/5
Ov 13-20: 80/1

This happened as a result of two reasons:

1. Pak going full (read: full here - anything that isn't BoL at least) &/ slow.
@IndianMourinho In the last 4 overs, the team bowled a grand total of 2 fast short balls. This is something you can't do against subcontinental sides.

Hasan Ali was struggling, so even if he had tried, 135kph wouldn't have made a difference. But Rauf and Shaheen were persistent
@IndianMourinho with the full and/or slow tactic too, despite hitting high 140s at ease.

2. Babar Azam backed himself into a corner with his bowling changes.
Read 15 tweets
29 Oct
Matchdays with @IndianMourinho: #T20WorldCup

Offspin vs West Indies: West Indies have time and again relied on a sole right-hander to split a slew of left-handers and counter off-spin. Simply put, they need more than one - be it Simmons & Chase or Holder & Chase or Pollard at 4
@IndianMourinho and Chase as opener, they just need more than 1 in the first 12-15 overs.

Chase's innings: 6 balls into his innings, Chase was on strike the first ball of the 4th over vs Mahedi Hasan. He took an intended single and moved to the other end, which exposed Gayle to his biggest
@IndianMourinho weakness and got him out. As the sole right-hander, that's the exact opposite of what he was supposed to do.

But I think there is a reason for it. The management might be expecting him to do the classic anchoring role, where irrespective of who bowls and what is bowled,
Read 13 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

:(