India's T20I 'Flexible Batting Order' Experiment: Where the Data Ends, Cricket's Real Debate Begins

I opened my notebook and pulled out the batting-order column I have kept for the last three T20I seasons the moment I heard about Ishan Kishan's groin injury. My habit is to build a 'position log' before every series—who faces how many balls at which slot and what his strike rate looks like there. Vaibhav Sooryavanshi was sent in at No.3 in the second T20I against New Zealand. That was not a strategic experiment; it was a forced move. Kishan was injured, and the team management chose to keep the Sanju Samson–Abhishek Sharma opening pair intact rather than break it. The scoreboard showed the cost of that innings. The real story runs deeper.

Lead audit line: before calling one match's failure a systemic failure, I want to know how large the sample behind that system actually was.

Context: India's T20I identity is powerplay aggression, and this is the pressure of that identity

The window of Indian T20I batting that has drawn the most attention in recent years is the first six overs. The powerplay is the most expensive phase of modern T20I—only two fielders are allowed outside the inner circle, and it is the phase where openers cash in on their technique. The 'record powerplay show' that arrived when Sooryavanshi and Abhishek returned to opening is evidence that India's T20I model rests on aggression against the new ball, not on caution through the middle overs.

But there is a structural knot here that few notice. India have four batters who have spent most of their careers at one or two—Abhishek Sharma, Sanju Samson, Vaibhav Sooryavanshi and Ishan Kishan. Putting all four on the field at once means someone has to go to No.3. This is not a new debate; it is the arithmetic of a surplus of top-order talent, the classic 'luxury problem'. Kishan's groin injury brought the debate to the surface, but the seed was sown long ago.

In this context the New Zealand series is a workshop. Not a World Cup, not an ICC tournament—low-stakes fixtures where the cost of experimentation is low. This is the right window for the team management to test whether 'flexible batting order' is a genuine doctrine or just another name for hierarchy.

Core analysis: all three former cricketers are right, but their data do not agree

Statements from three former internationals have dominated the headlines over the past few days—Wasim Jaffer, Praveen Amre and a third figure whose endorsement of flexibility has been widely quoted. All three backed a flexible batting order. But when I put their claims against position-wise numbers, all three were saying the same word, 'right', while pointing at data that collided with each other.

Start with Ishan Kishan. At No.3 he has 933 runs in 28 matches at 35.9 with a strike rate of 171.2. As an opener, in only five matches, the average stays almost identical—35.2—but the strike rate jumps to 193.4. This is the most important number in the whole debate. Kishan is the only batter with a credible record in both slots, at least with the large 28-match sample at No.3. The five-match opener sample is small, but the direction is clear: at No.3 Kishan has to make a slightly more conservative start, while as an opener he is free.

Now Sanju Samson. As an opener he has 783 runs in 27 matches at 30.1 with a strike rate of 177.6—solid. But at No.3 he has only three matches, 27 runs at an average of 9.0. This is where I stop. Using three matches to declare Samson 'unfit' for No.3 is like forecasting the weather from three raindrops. The data neither convicts nor acquits him. It is simply a blank space, and filling it with a conclusion would be dishonest.

The third and most striking number belongs to Tilak Varma. At No.5 he has 348 runs in 17 matches at 38.7 with a strike rate of 145.0—an anchor-finisher profile. At No.3, across seven matches, the average is 16.4 and the strike rate 108.5. A 36-point drop in strike rate is not coincidence; it is evidence of a game built for the slow middle-overs and the pace of the death, not for the raw speed of the new ball. If the team applies a blanket 'everyone flexible' doctrine, Varma's biggest weapon gets destroyed.

And Sooryavanshi? His failure at No.3 is a single-innings observation, not a data trend. But when you connect it to the fact that young openers' techniques are built around new-ball pace, it becomes a plausible—if unproven—mismatch. I believe declaring a young batter a 'No.3 failure' on one innings is premature; but keeping him there repeatedly would be just as premature.

There is another layer few are seeing. Samson's No.3 data are negligible, yet Raman's argument—that the senior player should absorb the disruption—rests on culture, not data. It is a leadership and fairness argument: when a player like Kishan returns from injury and a spot must be made, does the youngest player always pay? That question matters more than any strike rate, because it concerns trust inside the team.

Contrarian angle: 'flexibility' is not a doctrine but a selection bias that data is not rescuing

Now the point the headlines are missing. The weakest link in this whole debate is that all three legends endorse 'general' flexibility, while their own reasoning points to 'selective' flexibility. Jaffer and Amre say flexibility is necessary in T20. Raman says flexibility is fine, but the senior player should absorb the disruption. There is a world of difference between these two statements, yet the coverage presented them as consensus. This is not agreement; it is a qualified split on implementation.

More important still: the flexibility standard has been applied asymmetrically. When Kishan was injured, the youngest player—Sooryavanshi—was sent to No.3 while the Samson–Abhishek opening pair was preserved. That is a 'least disruption' principle, not a flexibility principle. If the team truly believed in flexibility, Samson should have gone to No.3 or someone else should have opened. Instead, the player at the bottom of the hierarchy was moved up.

There is also a statistical trap I call 'small-sample overconfidence' in my notebook. Samson at No.3 (3 matches), Varma at No.3 (7 matches), Kishan as opener (5 matches)—building any lasting policy on these three figures is dangerous. My rule: require at least 15 matches at a position before treating any split as a doctrine. Below that, we are not proving anything about the game; we are proving our own prejudices.

And do not forget Kishan's injury. A groin injury is a soft-tissue injury with meaningful recurrence risk for a wicketkeeper-opener. If it lingers, the 'flexible order' experiment could harden from a temporary fix into permanent policy—simply because one player's body will not cooperate. That is the risk the team management should watch most closely.

Takeaway: the next signal is not Kishan's return but Samson at No.3

When Kishan returns fit, the biggest question will be whether he plays at No.3 or goes back to opening. If he stays at No.3, it means the team has recognised his dual-role data—and that is flexibility used correctly. But the real test is Samson. If the team management plays Samson at No.3, it will be the first practical test of Raman's 'senior absorbs it' principle. If not, it will prove the whole experiment is just a respectable name for pushing youngsters into instability.

I am creating a column in my notebook for the next five T20Is—'batting order: continuity versus experiment'. If Sooryavanshi is seen repeatedly at No.3 over the next five matches, it is a warning bell for talent development. And if Varma is played at No.3 despite his numbers, it will prove the team is putting doctrine above data.

In sport everything can be accounted for—except the trust a young player places in his slot. When that trust breaks, the strike rate will fall whether you send him in at over one or over fifteen. That is the biggest lesson no former cricketer puts in his statement.