28 Matches vs 5: The Real Arithmetic of India's No.3 Problem Is Written in Kishan's Name, Not Sooryavanshi's

When Vaibhav Sooryavanshi returned to the opening slot in the second T20I and helped Samon put together a record powerplay show, the message from the dressing room was clearer than the scoreboard. One innings earlier, the same batter had been described as "out of sorts" at No.3. Upon returning to his natural position, he changed the direction of the match inside six overs. The press called it a triumph of the flexible batting order. That night, when I opened my workload ledger — the one in which I record every innings of every Indian batter at every position — what I saw was not a triumph of flexibility, but an injury-forced compulsion that had been dressed up in the language of doctrine.

This entire debate begins with Ishan Kishan's groin injury. He was unavailable for the second T20I against New Zealand, and the team management had two options: break the settled Samson-Abhishek opening pair and send Sooryavanshi to open, or keep the pair intact and push the young Sooryavanshi down to No.3. They chose the second. To call this flexibility is technically incorrect — it was the default of "minimum disruption," in which the burden of disruption was placed on the least experienced player. This pattern is not new in my ledger: whenever an injury removes a senior, the cost of the positional shuffle almost always lands on the batter with the fewest matches. The question is not whether this happened; the question is whether it should be accepted as doctrine.

The Arithmetic of No.3: Kishan Has Proof, the Rest Have Only Innings

Of all the numbers being thrown around in this debate, one thing must be settled first — which player has a sufficient sample at which position, and who does not. The data available to me (source attribution pending, so I treat these as directional, not claims of precision) says this:

Kishan has 933 runs in 28 matches at No.3, at an average of 35.9 and a strike rate of 171.2. As an opener, he has 176 runs in 5 matches, at an average of roughly the same (35.2) but a strike rate of 193.4. The sample is small, but the direction is clear — Kishan is the only batter with credible production records in both roles. The 28-match No.3 data is sufficient for a conclusion; the 5-match opening data is not, but it offers a signal that his game can adapt to both roles.

Tilak Varma's numbers dictate the direction of this entire debate. At No.5: 348 runs in 17 matches, average 38.7, strike rate 145.0. At No.3: average 16.4 and strike rate 108.5 in 7 matches. That is a strike-rate swing of roughly 36 points — not a minor difference, but a crisis of role fit. Varma's game is built for the tempo of the middle overs and the finishing of the death overs; the pace of the new ball is not for him. If the doctrine of "universal flexibility" were applied to him, you would burn 36 strike-rate points by placing a settled finisher in his weakest role.

Samson has 27 runs in 3 matches at No.3 — an average of 9.0. Using this figure as evidence would be intellectual dishonesty. Three innings do not decide a batter's capability. But the figure is directionally interesting: one former cricketer (Raman) argues that the disruption should be absorbed by the senior player, not the youngster. His argument is not about performance but about culture and leadership — and it is a valid argument. But note that Raman's argument and the team management's behaviour are opposites: the management moved the youngster, Raman says the senior should be moved. Both cannot be right at the same time.

The Consensus of Legends Looks Like Consensus, but Is Actually Half a Dispute

Jaffer, Amre and Raman — three former internationals — are reported to endorse flexibility. The reporting presented this as unanimity. When I read it again, I see not unanimity but a qualified split on implementation. Jaffer and Amre say flexibility is a necessity of modern T20 — that is the general principle. Raman also favours flexibility, but adds that the senior player should absorb it. These are two different things. The first says "the system must be flexible"; the second says "who pays the price of flexibility." When you agree on principle but are divided on implementation, it is not consensus — it is an open question.

And here I must say something sharp about the role of the media. A large part of the data being presented in this debate comes from samples of 3 to 7 matches — Samson at No.3 (3 matches), Varma at No.3 (7 matches), Kishan opening (5 matches). Building policy on these samples is like proving climate change from five days of temperature. The Hindi and Tamil desks have repeatedly raised the point that positional splits should only be treated as a trend after 15+ matches — and they are right. I am not repeating their point; I am extending it: the measure of honesty in this debate is not who said what, but who has how much sample.

One Innings I Watched Without a Single Number

The previous three paragraphs contain not a single mention of a delivery. That is my habit and also my risk — the grid and the ledger sometimes cover the cricket. So here is one innings, without any numbers. In the second T20I, when Sooryavanshi returned to the opening slot, his first shot was a controlled drive toward cover, with the bat coming down straight and the body balanced. In contrast, in his innings at No.3, his shoulders had opened on the very first ball — a movement that belongs to an opener facing new-ball swing, not to a No.3 who often faces spin or slower pace on the first ball. This is a technical mismatch, not a temperamental one. So when it is said that Sooryavanshi was "out of sorts" at No.3, my correction is this: he was not out of sorts, he was in the wrong posture against the wrong ball. In one innings.

This is why I look at this entire debate through the lens of role-fit mapping, not "selection philosophy." India have four batters — Abhishek, Samson, Sooryavanshi, Kishan — whose primary preference is positions 1-2. This is not scarcity, it is surplus. There is hardly a team in world cricket with four quality openers at once, forced to place one of them at No.3. This is a luxury problem, not a crisis. And the solution to a luxury problem is not a universal doctrine but selective adjustment.

The Counter-Intuitive Side: Why Is Flexibility Applied to the Youngest?

Here is something you will not find in any commentary. If flexibility is a necessity of modern T20 — as Jaffer and Amre say — then it should be tested on the most experienced player, because an experienced player has more room for correction after failure, while a youngster has nothing to lose but confidence. Yet in practice, the opposite happens: Sooryavanshi was sent to No.3, while Samson was protected at the opening slot. This is not flexibility, it is the asymmetric distribution of risk. And in my experience — since 2026, when I was logging bowling loads at a Delhi sports-science lab — teams always do this: they place risk on the one whose voice is heard the least.

Raman's suggestion — that the senior should absorb the disruption — matters because it directly challenges this asymmetry. It is not an argument about performance; it is an argument about leadership. And an argument about leadership cannot be dismissed with data, because it lies outside the domain of data. This is where I think the weakest part of this debate is the part being treated as the strongest: the consensus of three legends. If they agreed that the senior should be moved, would the team management do it? Probably not, because the team management's criterion is performance, and Samson's 3-match sample at No.3 neither proves performance nor proves inadequacy. This is a decision that data leaves neutral and culture decides — and culture should be debated, not hidden behind the name of data.

What to Watch Next: Kishan's Return and a Question the Scoreboard Will Not Answer

Kishan's groin injury is a soft-tissue injury, and the risk is higher for a wicketkeeper-opener because they must both run between wickets and crouch. If the injury recurs or lingers, this "flexibility" experiment will last longer than intended — and the role instability around young Sooryavanshi will begin to set. My workload ledger's rule is exactly this: injuries do not come from load spikes, they come from sudden role changes. So the next T20I is a natural experiment.

I will watch: if Kishan returns, does he bat at No.3 or open? If at No.3, the team management has embraced the doctrine — and then I will have to say that keeping a player with a 171.2 strike rate across 28 matches in his most proven role is not a collapse, it is common sense. If he opens, it will prove that this whole experiment was an injury-forced compulsion, not a doctrine. Whether Samson is tried at No.3 will be the real test of Raman's argument. And whether Varma is left at No.5 will tell us whether the team listens to data or to doctrine.

If you ask me which is the most honest sentence in this whole debate, it will not be found in the numbers. It is this: India have four openers and three slots. The way to solve it is not "make everyone flexible," but "adopt Kishan in both, place Varma in his slot, and let the youngster flourish in his own." Flexibility is a tool, not a religion. And until the next scoreboard tells us who was right, I will keep my ledger open — because samples of 3 matches do not make policy, no matter how many legends sign off on them.