Last night, many Indian cricket fans must have been scratching their heads, asking why Shreyas Iyer not playing. With Ishan Kishan’s injury sidelining him, it seemed logical to slot in another top-order batter to keep the lineup balanced. But the management did something completely unexpected. Instead of giving Iyer a shot, they went with a bowling-heavy strategy, leaving the Men in Blue slightly short on firepower with the bat. This move immediately sparked a flurry of debates on social media. Was this a tactical experiment or a subtle snub?

Related Article：Not Iyer! Why Ishan Kishan as No.3 Batter Makes Sense?

A Shocking Defeat Against the Kiwis

The outcome? India crumbled. In the India vs New Zealand 4th T20I match, chasing a modest total, the six-batter setup fell apart. Mitchell Santner, Jacob Duffy, and Ish Sodhi tore through the lineup, handing the Kiwis a 50-run victory. Skipper Suryakumar Yadav explained after the match:

“We purposely played six batters today. We wanted to have five perfect bowlers and wanted to challenge ourselves. Like for example, if we’re chasing 200 or 180, and two wickets or three wickets are down, how does it look? But then it’s fine at the end of the day. And we wanted to play all the players who are part of the World Cup squad. Otherwise, we would have played other ones.”

Many Indian fans read between the lines, seeing it as confirmation that why Shreyas Iyer not playing isn’t just a one-off. They sense he isn’t in the T20 World Cup 2026 plans.

Ishan Kishan’s Injury Changes Everything

The chain reaction started with Ishan Kishan’s injury, which ruled him out after he had been in red-hot form. Usually, losing a batter opens the door for another specialist to step in, but not this time. Instead of a like-for-like swap, the team management went with Arshdeep Singh, a fast bowler, in a bold attempt to test the team’s resilience. This decision left only six recognized batters in the playing XI, raising eyebrows and questions about priorities. Ishan Kishan’s injury directly led to this unusual experiment, and indirectly highlighted why Shreyas Iyer not playing.

Aakash Chopra Isn’t Holding Back

Former India opener Aakash Chopra had plenty to say on the subject. Speaking on ESPN Cricinfo, he expressed his frustration at the perceived disrespect. Chopra’s point was clear. He felt the team missed a golden opportunity to prepare for crunch scenarios ahead of the T20 World Cup 2026:

“I find it slightly baffling. I was of the opinion that India did the right thing by playing both Sanju (Samson) and Ishan when Tilak was unavailable even though Shreyas Iyer was picked in the team. Shreyas is not in the World Cup squad and I get it. But when you lose Ishan as well, then Iyer must play. If you’re going to go in with just six batters, I mean, that’s not right.”

Preparing for the Big Stage

The team deliberately prioritized match practice for the players already in the World Cup squad over giving Shreyas Iyer a chance. And with Ishan Kishan’s injury, the bold move reflected a short-term pain-for-long-term-gain approach, albeit one that left fans frustrated.

🇮🇳🇮🇳🇮🇳 pic.twitter.com/vh42mLpJLd

— Shreyas Iyer (@ShreyasIyer15) January 10, 2026

In the end, this quirky strategy in the India vs New Zealand 4th T20I underscores how much India is already thinking about the T20 World Cup 2026. It’s about testing pressure scenarios, trying out bowling combinations, and making sure the designated World Cup squad is ready for anything. For Iyer, the writing seems clear: why Shreyas Iyer not playing is tied to the selectors’ future plans, not yesterday’s injury shuffle. And Ishan Kishan’s injury just happened to be the catalyst for this high-risk, high-reward experiment.