Sanju Samson Gave Up His Slot, Abhishek Sharma Made 113 off 38 Balls: The Tactical Ledger of a Seven-Over Blitz

Seven overs, 133 runs, no wicket. Nineteen an over. That is not a scorecard entry; it is the post-mortem of a plan — and the plan was drawn before the toss, when a captain moved his own name down the batting order. India chased to win the third T20I by six wickets. Abhishek Sharma made 113 off 38 balls, a strike rate of 297.4, eleven sixes, the hundred arriving in 35 balls. The figures come from The Tribune's quote-driven report and are yet to be cross-checked against the official scorecard, so I will argue about their direction rather than their precision.

The anomaly is not the score. My notebook holds two entries from this series that refuse to talk to each other. In Christchurch, Vaibhav Sooryavanshi batted at No. 3 and made 4 off 8. In the third T20I, the same batter opened and made 45 off 19. The batter did not change. The slot changed, and the ground changed. Hagley Oval's early-season seam movement fits this story comfortably, and cricket usually blames the pitch first. But when a captain vacates his own position, a second reading is owed — one in which the decision was made before the toss and merely ratified on the field.

T20I batting is filed in three blocks: powerplay (1-6), middle overs (7-15), death (16-20). Watching matches for fifteen years, I have added a fourth block, which I call the seven-over window: the last powerplay over and the first over the fielding side needs to reorganise should be booked to the same account. The restriction lifts after the sixth over, but the captain's reaction lands an over later. A deep cover takes ninety seconds to appear; a bowler's line takes two overs to change. Runs made in that gap are the cheapest and the most expensive. India spent that window in full.

A six-wicket win necessarily means New Zealand batted first and set a target. The report never states the target, and that is the largest hole in the analysis. 133 for none in seven overs is 'dominant' only if the chase was around 185-200; if it was 155, the start was merely ahead of the rate. No pitch report, no toss, no dew, no DLS question. I will not manufacture certainty out of that silence. But the architecture of Abhishek's innings is clear enough to interrogate.

I charted it by hand, ball by ball, then asked the data to disagree. Of his 113, sixty-six came from eleven sixes — at least 58 percent of the runs. The other 47 came off 27 balls, a strike rate near 174. That split inverts the conventional hundred. A normal T20 hundred is built from a base line: survive twenty balls, then swing. Abhishek took risk from the first ball and stayed in that risk for 38 balls. A century inside 38 balls means he never played a settling innings — the rarest thing in T20 cricket, because it means the wicket's price was never once paid.

During the stand Sooryavanshi made 45 off 19, which puts Abhishek's share of those seven overs at roughly 88 off 23, a strike rate around 380. That figure is an estimate, since the report does not confirm the entire stand was the opening partnership. The direction, though, is unambiguous. This pair did not run the old template of the senior anchoring while the junior attacks. Both attacked, and the junior attacked harder. The standing rule for new-ball batting is that one end holds for ten overs. Here both ends opened, which is why by the seventh over the fielding captain had no containing setting left to set.

Now the decision. Sanju Samson dropping himself down the order. Abhishek's quote — that Sanju bhai showed his character by moving himself down — is a good quote, and team sport should value such gestures. I just cannot find the tactics inside the tribute. No. 3 is the most awkward slot in T20 batting: sometimes you get the last over of the new ball, sometimes the spinner's first, and you have six deliveries to decide. Sanju's real value sits against spin in the middle overs, where the ball is slow and the fielders are on their toes. If that was the reasoning, this is not sacrifice; it is role-fit arithmetic — and calling role-fit sacrifice is not credit, only convenience.

Watch the second line, not the ball; the game hides there. When a third fielder is still being pushed out in the seventh over, the bowler is left with two options, a yorker or a wide, and both punish the bowler for the smallest error.

India's selection debate has been misfiled as a talent argument for years when it is a load-and-role argument. From outside the bench looks deep; from inside, the side orbits the same eleven who keep playing and who have already moulded themselves to fixed roles. In that structure a senior vacating a slot is rare, because the system treats a position as accumulated load rather than as form. Sanju's call deserves recording for breaking that logic, at least for one match.

Here is where I argue with myself. First, we are grading a tactical decision by its output. The quote is lovely, but an honest reading also notes the target was never disclosed. Without it I cannot say whether 133 for none was dominance or merely par-plus. If New Zealand made 205, the start was excellent but not decisive; if they made 155, the contest ended in the seventh over. The quote reads the same either way; the value of the innings does not.

Second, milestone-first grading. Broadcast hands you 'hundred off 35 balls' because it types easily. The mechanism is that Abhishek faced 38 balls across an entire innings — 38 in a twenty-over match. A No. 3 in the same game might face twelve. Any selection argument that omits balls faced is grading the wrong column. And I do not trust a heat map I could not rebuild myself; before any vendor metric, I audit my own footage.

Third, the word 'selfless' erases load. If Sanju bats below the top three every game, his volume falls and India's most experienced middle-overs hand against spin faces fewer balls. Three matches will not show that cost. Six months will turn it into data. Maturity in captaincy is not measured by willingness to bat lower; it is measured by what information the decision rested on. If Sooryavanshi was promoted because he plays spin better against the new ball, the call is sound. If he was promoted because Abhishek had hit sixes last week and the mood was good, that is not a sound decision, only a good outcome. My notebook has more arrows than adjectives, and those arrows will eventually say whether the seven-over explosion was the slot or the surface.

The Christchurch counter-example is what unsettles me. Same batter, No. 3, 4 off 8. Two innings, two grounds, two outcomes. The sample is one innings against one innings, so I cannot claim the slot changed the performance — and I cannot claim the pitch explained everything either. What I can say: India have found an opening pair that can both survive the new ball and attack it; the second quality was over-supplied in the third T20I, and the first is still untested. Note also that India won by six wickets, which means work remained after the openers departed. The margin was settled in the last ten overs, and nobody wrote two lines about that passage.

Next time this pair walks out, watch three overs and ignore the rest. My pre-registered terms: if the ball is moving and the pair is under eight an over after 18 deliveries, Christchurch's 4 off 8 was conditions, not the slot. And if a wicket falls in the fourth over and Sanju quietly returns to No. 3, the decision will have reverted to its original shape, as T20 decisions usually do. Data's job is not to prove a sacrifice; it is to establish how much of it was necessary.