My notebook has four facts from that story. Vaibhav Sooryavanshi walked in at No. 3. A former India cricketer said he should have opened. The call was the team management's. The player is a teenager. After that the page is blank. Which format, which team, which opposition, how many runs, what pitch, what date — the headline answers none of it.

Before anyone accuses me of inflating a routine cricket item, let me state my method. Writing on Indian sport from Mumbai, I have a habit: break every story down to its smallest verifiable unit, then see how much weight that unit can carry. Most stories fail that test and I leave them alone. This one fails it so completely that the failure is the story.

It started as a footnote and ended as the whole argument.

Four facts and a missing fifth question

Indian cricket's media economy produces one particular product every day: two minutes of studio comment, packaged with the verb "slams" in the headline. Slams is not a journalistic word. It is a register, a signal that what follows is confrontation rather than argument. Confrontation gets clicked; argument does not.

Look at the report the way a producer would. You have a teenage batter, the position he batted at in one innings, the opinion of an unnamed former international, and a decision attributed to "the team management". No score, no over number, no pitch report, no toss. A cricket story with no match in it — only a position.

I am not arguing such stories should not exist. I am arguing that when a story exhausts its own inventory of facts in four lines, the honest analytical move is not to fill the gap with speculation. The honest move is to make the gap the subject. Sometimes the most rigorous question in journalism is simply: why did you not tell me?

Format is the load-bearing wall

You cannot debate a batting position without knowing which game is being played, because No. 3 means something different in every format. This is not a technicality; it is the foundation of the entire argument.

In T20, No. 3 either walks in during the powerplay after an early wicket, or at the start of the middle overs against spin with the field spread. The powerplay — only two fielders outside the ring — is objectively the most forgiving environment for a young free-scoring batter, so the former player's complaint has partial merit. In ODI, No. 3 is the anchor slot, frequently in inside the first ten overs against a moving new ball, which is a poor developmental fit for an attacking teenager. In Test cricket it is the most technically exposed position in the sport, and the criticism is strongest on technical grounds while carrying the highest developmental value if the player survives it. In franchise T20, a protected slot is a match-up decision, and calling it a demotion is a category error.

I have been calling cricket on All India Radio since 2026, and covering athletics live alongside it. Athletics taught me something cricket debates keep forgetting: position and identity are different things. A 400m runner can take the first leg of a 4x400 relay or the last, and nobody says he has been moved from "his" place. Batting at No. 3 is a deployment, not a title.

The part that actually matters is role stability

The meaningful question is not opener versus No. 3. It is how much role consistency a teenage batter needs.

The biggest enemy of technical development at that age is not a lack of talent but a lack of repetition. A batter who walks in at a different position every third match never learns what his own rhythm is — how much restraint against the new ball, what tempo against spin, which shot against a spread field. I have watched this pattern in Ranji and domestic cricket for years: the 20-year-old who batted in one slot for three seasons ended up owning his role; the one shuffled between slots never worked out what kind of batter he was, even at 30.

Controlled flexibility does have developmental value, because a batter who has played three positions by 20 escapes single-position dependency later. So the real question is procedural. Was the shift planned and communicated, or decided on the morning of the match? The report says nothing either way, and that is its largest editorial omission. A planned shift is coaching. An improvised one is mismanagement. The distance between those two is the story, and the story does not contain it.

Selection is a labour market

I have read Indian selection as a hiring process for years, and the frame holds here. Making India's XI is not a talent problem; it is a staffing problem. The bench is so deep that every slot has at least four credible claimants. In that market, sending a teenager into the top order is an investment decision more than a cricket decision — you are spending a scarce exposure on a return that arrives in five years.

That logic produces a possibility the report never considers: No. 3 may have been protection rather than punishment. Shielding a very young batter from the new ball in difficult conditions, or limiting his exposure to a specific seamer, is standard modern management. To call it the wrong position you would have to show the conditions were easy, and the report does not mention conditions at all.

There is a second layer. Public second-guessing of team management by former internationals is a permanent feature of Indian cricket, not an anomaly. It carries a cost: a young player learns early that he is being wronged, and that belief is as damaging as an injury because it turns him towards defending himself instead of developing.

The unnamed ex-player is an amplifier, not a source

Anonymity has rules. It is justified when the value of the information exceeds the cost of not being able to verify it — a corruption document, an internal selection message, a real injury report. An opinion about batting order does not qualify.

Here anonymity does two jobs. It protects the speaker from accountability if the decision turns out to be right, and it preserves the authority of the "former India cricketer" credential. The result is a combination Indian cricket media produces constantly: high emotional payload, zero verifiability.

The tape remembers what the broadcast decided to forget.

I have no doubt the remark came out of two sentences in a studio and was lifted into a headline. That process is unfair less to the player than to the reader, who is entitled to know which format the argument is about.

Media volume runs ahead of verified output

Now the part that makes this a story at all, and which has little to do with cricket.

In the Indian market, the media volume around a teenage batter systematically leads his verified performance. This is not a conspiracy; it is demand structure. The appetite for a next-Tendulkar or next-Kohli narrative is insatiable, so supply must run ahead of it. Commercial value — auction price, endorsement pipeline, coverage density — is a demand-side signal, not a performance signal. This report is a data point in that economy as much as a report about it.

Which is why I classify it as engagement product rather than analysis, and treat it as noise in any selection-related judgement.

In 2026, from the Kalinga Stadium tribune in Bhubaneswar, I learned a version of this lesson. India topped the Asian Athletics Championships with 29 medals and my editor wanted a golden-generation listicle. I counted instead: only four of the twelve golds came in events with more than eight entrants. The piece was spiked and I published it on my own blog that night. The medal table is a story someone chose to tell — and so is a batting-order controversy.

The question the headline never asked

Here I disagree with the former player and with the publication that headlined him.

First, the criticism is position-essentialist. It treats "opener" as the player's identity when modern cricket treats it as a match-up. In a game where bowlers are changed by over, not changing batters by situation would be the strange choice.

Second, and more seriously, the claim is unfalsifiable as published, because it names no condition under which it would be wrong. So let me pre-register the falsifier: if it can be shown that Sooryavanshi was sent in at No. 3 in conditions where opening was objectively easier — a flat pitch, a weak new-ball attack, powerplay field restrictions available — the criticism stands. That evidence is not in the public record. Until it is, this is an opinion, not a principle.

Third, the question that should have been asked about a teenager is workload and safeguarding, not batting order. The stacking of domestic, age-group, franchise and international commitments is a real risk, and it arrives during physical maturation. I have seen the cost in athletics often enough: the athlete returning from an ACL injury usually loses to the mind before the body, and the same logic applies here, except the pressure comes from the volume of matches rather than one. Were his innings and balls being tracked over that period? Is there a protocol between board and franchise over his availability? None of this appears.

Fourth, batting order sits outside cricket's rulebook entirely. It is selection and tactics. Whatever the merits of the criticism, no regulation has been broken, and framing it as governance failure takes the argument somewhere it cannot survive.

Base case, confidence, tripwire

I will not end with a four-branch scenario tree. I have a base case, a confidence level, and a named tripwire.

Base case, 80 percent confidence: this was a routine, planned tactical call converted into a controversy by the media cycle. The comment is forgotten within days, the player's development is unaffected, and he bats somewhere else next series without a headline. The reasoning is not faith in Indian cricket but the absence of any structural hook that could sustain this story beyond a month.

What flips it: if over the next six to twelve months Sooryavanshi is used in three or more different batting positions with no publicly stated plan, while his aggregate workload climbs, this stops being a story about a batting order and becomes a story about planning — and that one would deserve the headline.

Forward

I went looking for the second screen and found the story.

The missing voice in this entire debate is the player's. Nobody asked him how batting at No. 3 felt, whether he was told in advance, or whether he prepared differently for it. Until that question is asked, the debate is about him rather than by him.

And that is where the real work starts. Next time a headline tells you a teenage prodigy has been wronged, do not ask who said it. Ask which format it was. If there is no answer, you have not been given a story. You have been given a package.