Naman Dhir's 'rise' and the arithmetic of one wicket: where is the data inside the jugaad story

In the first T20I against West Indies at the Ekana Stadium in Lucknow, Romario Shepherd was dismissed, and within seconds the photograph of Naman Dhir embracing Arshdeep Singh travelled further than the scorecard did. I went from the photograph to the card, looking for the over number, the runs conceded in it, the moment the captain first handed him the ball, the economy. The card had the wicket. The column beside it was empty.

This piece is about that empty column.

My habit is to log every ball before I allow myself an opinion. In March 2026 at the MCA Stadium in Pune, Australia beat India by 333 runs and India were bowled out for 105 and 107; instead of repeating the prepared 'rank turner' story, I built a sheet of every delivery — spin deviation, bat-pad, shot type, release point. Fourteen of India's twenty wickets had come from spin or bat-pad pressure. Since that day I have had one method: log first, conclude second, and if the log is incomplete, do not publish.

So I print my threshold before the analysis, not after, so that I cannot move it later. Fifteen innings before I say anything about a batter. Twenty overs before I say anything about a bowler. What sits on my desk for Naman Dhir is two fixtures and one wicket. Two matches, one wicket — so far below the threshold that the question itself changes shape.

The first finding, then, is insufficiency. In my trade that is also a finding; it is just rarely printed. I went hunting for a pattern and came back with its absence.

The two addresses in the file are structurally informative on their own. One is a T20I against New Zealand in Christchurch, where Shreyas Iyer was captain. The other is the first T20I against West Indies in Lucknow. Two different series, two hemispheres, one compressed window. That is not accident for a new cap; it is the fingerprint of a rotation-and-experiment selection policy.

The two venues are near opposites. Hagley Oval generally offers pace, bounce and seam movement with a wind that is part of the game. The Ekana is large, slower and two-paced, a surface that assists spin and demands hard running. The source supplies no pitch or weather line at all — what I have written above is general venue knowledge, and I will keep it in the inference column, because I did not log either pitch myself.

The captaincy detail is worth reading carefully. Iyer led in Christchurch. If India's first-choice T20 captain was elsewhere at that time, the team was running a split-captaincy or rest-and-rotate policy. Such a policy is a gift to a utility player, because slots keep rotating, and a tax on the specialist, whose place is fixed. That is inference, not assertion — I will publish the series-and-captain confirmation only when my sheet matches it.

And then the word in the headline: jugaadu. In cricket language this is not praise for a dominant skill; it is a scouting claim about adaptability. Players described this way are valued for flexibility — bat anywhere, bowl an emergency over, field in three positions. That profile survives in a fifteen. It is also the first profile dropped the day a specialist returns.

Now the ledger I actually built.

What the file has: one wicket, Shepherd's. Two matches in two series, one home and one away. Arshdeep Singh as a teammate. Iyer as captain. And a good-luck message from the author, which he calls a ritual.

What the file does not have: a batting average. A strike rate. An economy rate. A bowling strike rate. An innings score. A series result. A toss. A DLS intervention. Dew. An age. A domestic record. An IPL price. A central contract. And — the omission that stings most — a publication date.

The missing age is the strangest gap in a 'rise' story. A rise happens from somewhere, at some age. Two T20Is at 23 and two T20Is at 29 are the same sentence and not the same story. The file leaves that distinction blank.

One clarification matters here, because this is where the slip happens. The single hard performance fact in the material is a bowling fact, not a batting one. In a piece narrating a batter's emergence, that is an inverted signal. The one number that exists says he was handed the ball in international cricket — a management endorsement far heavier than any net report. A captain does not burn a real over on a non-bowler in a match he is trying to win.

Shepherd's role sharpens the inference. He is a lower-middle-order power hitter, the kind who is usually faced in the middle or death overs. If Dhir dismissed him, the likeliest reading is that his over came in that phase rather than as a token. I am recording this as inference, not fact, because the over number is not on my sheet.

Then the other side. If he is being used as a bowler, what is his batting slot? The file is silent, and that silence is the real hinge of the story. When a player's bowling role is defined and his batting role is not, his ceiling is set by team structure rather than by talent. The jugaad is his strength; it is also his ceiling.

And here my old complaint has to be filed. Naman Dhir's domestic record — Ranji, List A, Syed Mushtaq Ali — does not appear in a single line of the material. That is not unusual in India; that is the problem. Our first-class competition is argued about with anecdotes because its ball-by-ball and fielding data is thin, and where data is thin, reputation becomes the currency of selection debate. 'Jugaadu' is exactly that kind of reputation word: it explains how someone arrived, not what he did once he got there. A player whose domestic numbers are absent from public argument will inevitably be valued on two international evenings. Two evenings are not a career.

The commercial side is the same empty column. No auction price, no franchise retention, no central contract reference. In today's Indian ecosystem, that silence inside a 'rise' profile is itself information: either the piece predates that milestone, or the author chose a personal register over a market one. Both readings point to an early-stage career.

Now the part where I have to be most careful.

The source's sentiment is that when the author texts, Dhir plays well. That is warm, and I will leave it in the author's column. Treating it as a performance claim is exactly the habit my method was built to prevent. Two matches, two texts, two good days — the sample is too small even to call it coincidence with confidence. Correlation is not causation, and here not even correlation is logged; only memory.

Second: 'jugaadu' is a commercially useful label, not a sporting measure. In the Indian market it codes as self-made, non-academy, relatable, and such labels have historically carried endorsement value disproportionate to on-field output. That is a brand observation, not a cricket one, and merging the two in one sentence shortchanges the reader.

Third, structural: the most fragile squad category in Indian cricket is the utility player. His value peaks during rotation and expires on the day a full-strength XI is named. If this is a rise, it is worth recording which door it came through — the rotation door or the settled-selection door. My sheet currently shows a door, not a wall.

Fourth, format: two T20I moments say nothing about ODI or Test readiness. That is obvious enough that it should not need writing, except that we make the error weekly. A utility signal in one format can be zero in another.

On workload, this is a column I keep open, not a charge I file. A player carrying bat-and-ball load, trialled in home and away conditions in a short window, has a risk profile different from a specialist's. That is not an injury forecast; it is a line I monitor.

And now the question I actually want to ask.

If I learn one thing from this file, it is that we have a way of writing about young cricketers that runs on access rather than on data. Being close, texting, blessing — all legitimate parts of reporting, and I do not dismiss them. But when proximity replaces the number, the reader cannot tell whether he is reading about a career or about a writer's ritual. The log remembers what the highlight reel edits out — and here the reel has one wicket, and the log has nothing after it.

So what should we watch? Three signals, already written into my sheet. First: does he get a defined batting slot in a full-strength XI, or does he remain in the wherever-needed column. Second: his List A and first-class output, kept in a separate register from the T20I signal, because reading the two together is the error we repeat every season. Third: the next auction or retention cycle — if the market prices this profile, it is worth seeing which skill it is paying for.

Before the roar, there is a spreadsheet nobody thought to film. Naman Dhir's spreadsheet is two rows long. Calling it a rise would be premature. Keeping it open, and waiting for the next row, is the honest work available right now.