Not Out for a Duck — Out by 23 Dot Balls: What the Sylhet Spreadsheet Refuses to Tell You

Not Out for a Duck — Out by 23 Dot Balls: What the Sylhet Spreadsheet Refuses to Tell You

When he walks back under the Mirpur floodlights, the scoreboard reads 0 (4). Four balls, no runs. The commentator calls it an 'early jolt.' But the spreadsheet I had open in Sylhet carried another column next to that four — 23.

Twenty-three dot balls in the first innings. Out of a 42-ball stay, 23 scoreless deliveries means he failed to rotate strike on 54.8 percent of the balls he faced. That number is the story. Four balls for zero is noise. Twenty-three dot balls is a structural failure.

Why this matters: Cricket's conventional metrics — strike rate, average, boundary percentage — capture none of those 23 dots. Strike rate throws 23 dots and 19 singles into the same bucket. So what we call a 'slow innings' can actually be two different things: an innings where the batter was leaving well, and an innings where the batter was searching. The solutions for each are entirely different.

When I launched Half-Space Notes in 2026, Ajax's 578 passes against Manchester United's 8 shots taught me that possession and penetration are not the same thing. In football we map half-spaces to identify which pass is actually progressing the ball. In cricket that space sits empty. Nobody draws the spatial fingerprint of a dot ball.

I published a falsifiable claim before kickoff: if deliveries outside off on a length-plus-line exceeded 40 percent against him, his strike rotation would drop below 35 percent. It finished at 33.7. Hypothesis held. But the win isn't mine — it belongs to the framework.

Why this innings is so easy to misread:

Broadcast cameras show the batter, show the ball. Footwork, bat angle — all visible. What stays invisible is the distribution of line and length. When a batter plays 23 dots, the question is not 'why did he bat slowly' — the question is 'which zone was he pinned into.'

In this match he played 11 dots in the corridor outside off-stump. Seven on pull length, where the ball had passed his bat before the swing arrived. As a control group I placed the other opener's numbers alongside: only four dot balls outside off against the same attack. One variable changed — the batter's front-foot trigger. Everything else held constant.

This is where football's shadow falls. In Lisbon 2026, timing Bayern's counter-press recoveries in an empty stadium during the 8-2, one thing became clear: the scoreline is output, the rest-defense is input. In cricket, the batter's runs are output. Dot-ball zone mapping is input.

But the analogy has a boundary I want to mark clearly. In football, possession-without-progression can be measured through pass-based networks because a pass is a discrete event. In cricket, a dot ball is not an event — it is the absence of one. A ball was played, but no run came. Absence is far harder to measure, because you must prove the ball was either playable or not.

This is why I say data does not lie, but the absence of data frequently does. Twenty-three dot balls is a number. How many of those 23 were good balls and how many were poor decisions — that is the real question. The coach is not accountable for the first category. He is for the second.

Now to the part nobody wants to look at.

I have run this spreadsheet for four years. Every series, I update every batter's dot-ball zone map. A pattern keeps returning, and it is uncomfortable.

In Bangladesh's dot-ball zone maps, moving from domestic to international cricket triggers a specific shift — dot percentage in the off-stump corridor rises by roughly 14 points. That shift does not appear against domestic bowlers, because domestic seamers cannot sustain that length. Meaning: the problem is not the batter's technique. The problem is the exposure his technique gets.

I am not speaking from inside Dhaka here — I am looking through eyes born in London. Over fifteen years I have watched Bangladesh cricket debate 'lack of talent' endlessly and 'lack of exposure' rarely. The gap between the two, I see in numbers from Sylhet.

How many players get 100 balls against international-standard bowlers in domestic cricket? The number is small. And those who do — their dot-ball zone maps don't stay small. They stay different.

What about the counter-argument:

Someone will say reducing dot balls requires risk, and risk means getting out. That is not wrong, but it is incomplete. A dot ball and a dismissal are both bad — but they are not the same currency.

My spreadsheet has another column: 'intent dots.' Dots the batter plays consciously — leaving a wide, seeing out a new bowler's first ball. These dots are not harmful; they are investment. Today's three dots buying tomorrow's twenty singles.

The damage begins when 'intent dots' and 'helpless dots' accumulate in the same column. In this match, of those 23, by my count only 5 were conscious. The other 18 came from positions where the batter could not score because the ball was not in his bat's zone.

And here a simple truth hides that we do not want to say: the opposing bowling unit arranged those 18 balls. This was not accident. This was plan.

Where to watch in the next match:

Count how many deliveries land in the right-hander's off-stump corridor in the first 20 balls. If it crosses 10, and the opener's front foot stays inside the crease — I am predicting strike rotation below 40 percent. The ledger stays open.