Fewer Dots, Same Runs: Where Bangladesh's Middle-Overs Maths Went Wrong

31.8. The spreadsheet began to hum, and I knew the broadcast was over. It was 1:20 in the morning in my Hackney flat, and the figure on screen was the dot-ball percentage Bangladesh's batters had produced between overs seven and fifteen. Before this series the same number read 42.6. More than eleven percentage points of dot balls had vanished. The expectation writes itself: those vanished deliveries should turn into runs. Instead, the middle-overs strike rate moved from 119.4 to 121.2, a gain of 1.8 points. One dot ball disappeared every six deliveries, and less than half a run per over arrived in exchange.

That gap is the story. Treating dot-ball reduction and run-scoring as the same act was the biggest error my own model exposed. A dot ball is visible; runs are not visible in the same way, because runs get paid for in wickets.

Why am I not talking about the powerplay? Because everyone talks about the powerplay. The first six overs carry fielding restrictions, swing, the two most technically trained batters in the side, and every six that lands in a highlights package. The media economy rewards the powerplay because that is where events live. But 54 balls of a 120-ball innings sit in overs seven to fifteen — 45 percent of the innings, and roughly 70 percent of the decisions that decide a Bangladesh chase.

The geometry of Bangladesh's T20 problem is simple. They survive the powerplay, stall through the middle, and gamble in the last five overs, trusting whatever comes back. Of those three phases, the middle is the least discussed, because nothing dramatic happens there — only dot balls and one-and-two rotation. And that is exactly where this series produced a large shift that looks like good news on first reading.

My model is simple but labour-intensive. Across the three matches I tagged 612 legal deliveries faced by Bangladesh, one at a time, into four buckets: controlled scoring shot, false shot (mistimed, edged or beaten), dead ball (defensive, no intent), and wicket ball. I did the tagging off the broadcast feed, ball by ball, with my own notes beside the scorecard.

Let me be plain: these numbers are not the output of an official stats provider. They are the output of my own tagging model, and the method note sits in a public ledger, including how anyone can challenge it. The first condition of data journalism is transparency of method; the second is admitting your limits before somebody else does.

Now the single metric that stood up most cleanly in this series: the Dot-Ball Conversion Rate, or DBCR. The question is simple. Of the dot balls that disappeared in the middle overs, how many actually turned into boundaries? The answer was 0.19. Of every 100 dot balls removed, only 19 became a four or a six. The other 81 became singles, twos, or nothing at all.

Reducing dot balls does not mean increasing runs; reducing dot balls means increasing risk — and that risk is settled in wickets, not in runs. That one line sat at the centre of my series report.

Look at the match-by-match picture. In the first match, middle-overs dots ran at 39.2 percent, the false-shot rate was 17.8, and the strike rate was 126.7. In the second, dots fell to 28.9, but the false-shot rate jumped to 24.1 and the strike rate dropped to 114.3. In the third, dots were 27.3, false shots 26.4, strike rate 122.6.

The pattern is not a straight line; it is a pair of scissors. As dots fell, false shots rose, and the strike rate swung between them. In the first match the side was slow but controlled. In the second it tried to be fast and lost control. In the third it reached for balance again, with the false-shot rate still above 20.

The cause of that scissor is pre-meditation. Chasing dot balls, a batter commits early. He plants his front foot towards cover, steps out of the crease, or goes for the scoop before the ball is released. In the powerplay that gamble has a shield — only two fielders outside the circle. In the middle overs the shield is gone; four fielders wait in the deep, and a false shot becomes a straightforward catch. Litton Das, Najmul Hossain Shanto, Towhid Hridoy and Mushfiqur Rahim form a combination in which middle-overs rotation is a structural question, not a personal weakness.

One number stood in front of me that I want to isolate. A middle-order batter in this series saw his dot share fall from 41 percent to 29 percent. Over the same span his false-shot rate climbed from 18 to 27. His strike rate barely moved. That is not a batter failing; that is a wrong solution. In fixing a visible problem — dots — he manufactured an invisible one — false shots.

History is unkind here. Around 2026, when Soumya Sarkar was emerging, I was a reporter at The Daily Star and my first verifiable byline was that interview. Even then I noticed one thing: the tempo of a Bangladesh T20 innings is set after the 12th over, not after the sixth. Ten years later the data says the same thing in a different vocabulary.

An external force also shapes the tempo of these innings, one I recognise from football. Franchise leagues now take young cricketers on a loan-with-obligation model — play them in one league, hold an option to buy them into another. In football that structure has wrecked the financial planning of smaller clubs; in cricket it erodes a young batter's batting identity. A batter who plays one fixed role for three months goes looking for that role in the middle overs, rather than for what the team needs.

In the fight between data and the eye, I do not stay neutral; I put both sides under cross-examination. I do not trust the eye test until it can survive a scatter plot — but I do not trust a scatter plot either, until it can survive a human being's story.

So the contrarian question has to be asked: was the fall in dot balls actually progress? Two competing explanations exist. The first says the batters have deliberately learned to avoid dots, and that this is a coaching outcome. The second says that when a side loses wickets and falls behind, batters start to slog — dots fall and false shots rise together, because they are two faces of the same event.

The second explanation is the more expensive one, because it means the apparent improvement is an artefact of match state rather than a gain in method. A batter who starts swinging after four wickets have gone down reduces his dot count easily — but that is the pressure of circumstance, not evidence of skill. Correlation and causation sit skin to skin here, and the only way to separate them is to publish a counter-metric in advance.

This is where my ethical kill switch comes down. I once built a model over six days — pressure-adjusted value per delivery — and deleted the whole thing one morning. It had turned a 19-year-old into a 26.4 percent false-shot rate, and it could see nothing of his name, his age, or his shaking hands. There is a monastery in every dataset, and its silence is not empty.

So before this series I published a counter-metric, precisely so that I could not control my own narrative. The metric is balls per dismissal — the number of deliveries spent per wicket — alongside a pressure-adjusted strike rate. If dots fall but balls per dismissal do not rise, the improvement is self-deception.

The best sides kill middle-overs dots through field manipulation, not pre-meditation. They rotate one-and-two, move fielders, and take twos instead of boundaries. That is Bangladesh's weakest modern T20 skill: running between the wickets. It is a training and fitness question, not a talent question.

And this is where a regular-season undercurrent does its work, invisible on the scorecard. Back-to-back travel, different climates, the schedule of returning from franchise duty to national duty — all of it leaves marks on middle-overs intensity. Patience in the middle overs is a fitness event, not only a technical one.

The opposition's plan has also walked into my dataset, and admitting that matters. When Bangladesh fall behind, bowlers build dot-ball pressure with slower balls, cutters and wide lines. Part of the fall in dots is therefore the opposition's bowling error, or the product of match state — not proof of self-improvement.

So what can be concluded from three matches? Something careful: the intent to rotate strike in the middle overs has risen, but its execution still leans on risky shots rather than controlled ones. Dots fell; outcomes did not improve.

A metric that shows improvement while outcomes stay flat is often a forecast of coming damage. For the next series I am therefore writing down two numbers in advance: the middle-overs false-shot rate, and boundaries per false shot.

The model did not predict the six; it predicted the regret of ignoring it. In the second match, at the 14th over, where a single would have done, the batter went for long-on and holed out — that delivery was a failed metric in my tagging, and only a reduced dot ball on the scorecard.

One usable rule falls out for training plans. In the middle overs the target should be a false-shot rate under 20 percent, not a dot-ball count. A dot ball is a symptom; a false shot is a cause. Chase the symptom and the cause hides, and when the cause hides it returns next series wearing the shape of a wicket.

One thing I want to say clearly, because I know and respect the language of Bengali cricket media. Criticising a national team with data and understanding a national team with data are two different jobs. The first brings traffic; the second changes decisions.

This is also where blockchain enters cricket's data infrastructure. Official ball-by-ball logs are meant to sit on immutable ledgers — once an entry is written it cannot be altered, only interpreted. During this series I was also watching the public ledger of a fan-token marketplace. Trading volume jumps the moment a wicket falls, and its correlation with dot balls is zero. The market does not measure dots either; it measures events.

That is evidence of my metric correction from outside the model: people measure what is easily visible. Blockchain does not change that instinct; it simply makes the visible mistake permanent. An immutable ledger can preserve a wrong metric forever.

So even in an on-chain future for cricket data, my kill switch stays necessary — who tagged the ball, and under which definition, must also be written on the chain. Transparency does not equal truth; transparency only removes the room to dodge accountability.

I will leave a question rather than an answer. Are we teaching the side to avoid dot balls, or to play the right shot? If next series the middle-overs dot rate sits under 32 while the false-shot rate sits above 22, the number will look better and the team will be standing in exactly the same place.