The Dot-Ball Ledger: Bangladesh's T20 Middle Overs Need Evidence, Not Excuses

New York, June 10, 2026. Bangladesh needed 114 at under six an over. I sat in the corner of the press box charting ball by ball against the raw feed, because a delivery watched twice is a delivery charted once. At the end of seven overs one number jumped off the page: 23 dots from 42 balls, eight of them in one unbroken stretch with no single and no boundary. Bangladesh finished on 109/7, a four-run defeat. The scoreboard puts the blame on the batting order; my ledger points somewhere else — an inability to rotate strike in the middle overs.

I built my first ball-by-ball ledger in Chattogram in 2026, starting with 22 BPL matches, charting every delivery for Chittagong Abahani and Sheikh Jamal Dhanmondi. In football the xG column sat empty; cricket has no such problem. Cricket is the rare sport where every delivery is a recorded event — runs, wickets, batter, bowler, fielding position. That should make analysis easy, and it does the opposite: too much data means more room to ask the wrong question.

My template splits an innings into three phases: powerplay (1–6), middle (7–15), death (16–20). Each phase carries four columns — dot-ball percentage, balls per boundary, rotation rate (singles and twos), and wicket cost — plus two flags: batting or bowling, and wickets in hand. The sample is 27 Bangladesh matches at ICC tournaments from 2026 to 2026, calibrated against 22 BPL charts. Small sample, mixed venues, uneven opposition quality; those caveats stay written at the top of the sheet.

The clearest pattern sits in the middle overs. Bangladesh's powerplay dot rate is around 41 percent, competitive. At the death it is near 30 percent, as expected. But between overs seven and fifteen it climbs to 47–48 percent, against a top-four average of 34–36 in my ledger. Bangladesh's real T20 deficit is middle-over dot-ball rate — not a shortage of boundaries.

Run-rate makes the gap sharper. In the middle overs Bangladesh score 0.78 runs per ball; the leading sides score 1.12. Most of that difference comes from singles and twos, not power hitting. Falling behind at six an over forces the big shot, and that is where wickets fall.

Individual numbers can mask a structural problem. Litton Das strikes above 135 in the powerplay but closer to 110 in the middle — the same batter, two different players. Towhid Hridoy clears 140 between overs seven and fifteen in my sample. Jaker Ali is effective at the death, yet his deployment in the middle is inconsistent. The issue is not one batter's form; it is instability over who bats where.

The bowling column reads backwards. Bangladesh's middle-over economy is around 7.2, and Mustafizur Rahman's death economy sits under seven. In at least three matches the opposition's middle-over dot rate was higher than ours. With ball in hand the skill is there; the batting plan is not.

None of these numbers hold without venue control. New York's drop-in pitch offered seam movement; Antigua was slow; Kingstown's wind-crossed ground has quick outfield edges. The same batter with the same plan produces three different outcomes. Skip venue and game state and you measure the scoreline, not the skill.

Here sits the easiest error — mistaking correlation for causation. Middle-over dot clusters are often the consequence of a wicket in the previous over. Bangladesh's opening stands average around 31 in my sample, so two wickets tend to fall before the seventh over. A new batter thinks about both team position and personal strike rate, and rotation dips for fifteen balls. The slowdown is a top-order structural result, not a missing T20 mindset.

The second trap is sample size. Thirty balls or twenty innings cannot settle a strike rate; without an uncertainty interval the number is decoration, not a weapon. Dhaka club coaches say the pitches are slow and the ball arrives late. That is a hypothesis to be tested with venue-split data, not a belief to be trusted.

“I keep clean columns so the messy truth has somewhere to land.” That is the whole reason for the sheet.

My signal for the next tournament is numeric. Cutting middle-over dot rate from 47 percent to 40 percent should add 18 to 22 runs per innings — but only if Hridoy or Jaker Ali is given a fixed role in overs 7–11 and the opening stand climbs toward 40. “The ledger does not replace the match; it remembers what the match forgot.” “I built Chattogram’s first ball-by-ball ledger before anyone asked for it,” and it taught me this: the scoreline says who won, the phase split says who did not. If Bangladesh drops below 38 percent dot rate in the middle overs next cycle, the conversation changes. Otherwise we will say again that the wickets fell.