The Dot-Ball Ledger: Bangladesh's Unfinished T20 Batting Account

ONE — WHERE THE SCORECARD ENDS, THE LEDGER BEGINS In Kingstown that night the dressing-room lights had gone out long before the players reached the tunnel. The scoreboard held one fixed number — 105. Afghanistan had made 115 for 5; Bangladesh were all out for 105. On television one phrase was bouncing around: batting failure. Three words to fold eight months of preparation, four or five bilateral series and dozens of net sessions into a single line. I decided that night that the word 'failure' would not enter my writing until I knew which ball it started from. Back home I opened my laptop. I started with a blank spreadsheet and a suspicion about the numbers. The suspicion was simple: is Bangladesh's T20 batting genuinely weak, or is it an unfinished system — one with talent, but sections that do not join at the seams? What follows is an audit trail, not a match report. It is a ledger: every ball an entry, every run the output of a decision, every wicket a cost. The data did not shout; it waited until the noise left the stadium. TWO — CONTEXT: WHY T20 ACCOUNTING IS DIFFERENT A T20 innings is a budget of 120 balls. Inside it a side must do four separate jobs: convert the open spaces of the powerplay, rotate strike against spin in the middle, hold the rate between overs 11 and 15, and take risk in the last five. Each phase has a different unit of success. In the powerplay success is boundaries; in the middle it is dot-ball suppression; at the death it is accepting risk deliberately. Bangladesh's batting set-up has been built on a specific mould for years — playing spin off the back foot in the middle overs, keeping bowlers outside the arc, and letting the quicks squeeze at the death. That mould inflates bowling numbers and erodes batting numbers, because bowling success is measured on one axis, economy, while batting success sits on three — run rate, dot-ball rate and wicket cost. Team management tends to look only at the first. A second piece of context matters. Transfer-market pressure has entered the national team. Franchise leagues, overseas drafts and central-contract slabs each value a player differently. If a young batter strikes at 140 in the powerplay domestically and is then used at number seven internationally, his market price and his national-team usage become two separate things — and that gap is the least-discussed part of Bangladesh's T20 batting problem. THREE — METHOD: WHAT I COUNTED AND WHAT I DID NOT My main sample is three Super Eight matches at the T20 World Cup plus two completed Bangladesh matches at the 2026 Champions Trophy. Fewer than six matches, fewer than two thousand balls. That sample produces an inference, not a verdict. I split the innings into four phases: overs 1-6, 7-10, 11-15, 16-20. In each I counted runs per over, dots per over, boundary rate and wicket cost. What I did not count matters as much. I did not count fielding mis-fields, because broadcast angles differ and one dropped catch sounds like five different events. I did not count umpiring decisions. I did not fully separate dew, rain and day-night effects; I only noted them. Each number therefore carries a declared error margin. Barishal taught me that a model is only as honest as its missing rows. FOUR — THE CORE: THE DOT-BALL LEDGER 4.1 Powerplay: the cost of balls spent In my log, Bangladesh's batters leave or defend 55 to 65 per cent of deliveries in the first three overs. That is normal in Test cricket and expensive in T20. The real damage is not the dot ball but the ball after it: having spent a delivery, the batter tries to recover strike rate, and the success rate of that shot falls. In my log, roughly half of shots played immediately after two consecutive dots did not find the boundary, and about a quarter created a wicket or a catchable chance. 4.2 The middle: the gap nobody measures Overs 7 to 15 are 54 balls — 45 per cent of the innings. If those balls yield six an over, that is 54 runs. Good sides take seven to eight, which is 63 to 72. The difference is nine to eighteen runs an innings, and in T20 that difference is the match. I track a variable I call rotation delay — the time two batters spend at the same end — and Bangladesh's is slightly longer than their opponents'. The deeper reading is that the middle-over slowness is a coaching output, not an individual weakness. Batters are not playing the wrong shot; they are playing the right shot late. 4.3 The death: who pays for the risk Bangladesh take risk at the death and their boundary rate improves, but their wicket cost rises at the same rate. If a batter strikes at 160 for 15 runs and is out within two balls, the contribution is net negative. We do not run this accounting in Bangladesh; we look at strike rate alone and never at what the strike rate cost. 4.4 The table I update every series Phase | Bangladesh runs per over | Good sides | Gap 1-6 | about 6 to 7 | about 8 to 9 | about minus two 7-15 | about 6 | about 7 to 8 | about minus two 16-20 | about 9 to 10 | about 11 to 13 | about minus two to three Minus two everywhere. That is the finding. Bangladesh do not collapse in one phase or explode in another — they accumulate small deficits, and small deficits compound. 4.5 Role-adjusted output Strike rate is not a measure of individual skill until the role is fixed. I split roles into top order, middle and finisher. The recurring problem is not talent but assignment: a Test-profile batter is placed at the top of a T20 order, while a domestic finisher is asked to build at number five. Litton Das's dot-ball profile is the price of a role that only pays if someone at the other end buys his time. Towhid Hridoy and Jaker Ali show the reverse mismatch when they are asked to finish. 4.6 False-shot rate I do not grade batters on whether they were dismissed. I grade whether the ball they attacked was attackable. If pitch, line, length and release angle say the correct shot was defence, I log a false shot — boundary or not. Bangladesh's false-shot rate is higher than their opponents' in the middle and higher still at the death. Much of that is timing: a false shot in the 14th over costs more than one in the 12th, and the scorecard does not say so. 4.7 Why the bowling ledger hides the batting problem Bangladesh's bowling numbers are genuinely good, especially spin in the middle overs. But good bowling data conceals batting problems because dots are credited to bowlers. Both sets of players avoid proactive attack; in the bowling column that reads as discipline, in the batting column as timidity. Same habit, two names. 4.8 Transfer valuation of young output A transfer is a number with a birthday, a contract, and a hidden clause. In cricket those become debut age, contract length and release conditions. In Bangladesh a player carries three different prices — domestic league, national side, overseas league — and very little connects them. Selection usually follows the first price only, and then the result is blamed on talent. 4.9 Franchise cricket and the loan clause Football's loan-with-obligation mechanism has a structural cousin in franchise cricket. A smaller side develops a player, a bigger franchise signs him, and his role changes. Retention rules reward the flashy and punish the moderate. Add this to the minus-two ledger and part of the deficit is not born on the pitch at all — it is taught in a system that rewards the safe shot. FIVE — CONTRARIAN: CORRELATION IS NOT CAUSATION HERE First objection: pitch. The slow, low surfaces in the USA and the Caribbean naturally suppress scoring; I compared Bangladesh's numbers against opponents on the same surfaces, but innings happen at different hours and in different conditions. Second: opposition quality. Afghanistan, India and Australia were among the best sides in that window, so separating 'Bangladesh were poor' from 'the opponent was good' is not possible in this sample. Third: the limits of analogy. I borrow cross-sport checks because a clean number elsewhere organises the thinking. Morocco's Sofyan Amrabat in the 2026 World Cup against Spain — 12.7 kilometres covered, three tackles, one interception, never dribbled past — worked because seven team-mates rotated with him. In cricket that is a hypothesis, not proof. Overs are limited and so are balls per over. Fourth: the press. 'Our batters have a mental problem' is a sentence that looks good in a mirror and fails in a table. The same batters hit boundaries in the next tournament — only at the death, when the side has fewer balls left. Before I trust a press, I count the passes allowed per defensive action. SIX — TAKEAWAY Across the next T20 series I will watch three things: Bangladesh's dot-ball rate in the first three overs (one per over or fewer would signal system change, regardless of result), the speed of strike rotation in the middle overs, and where batters are willing to send the ball in the air. A team that depends on the opponent, on luck and on safety will keep producing minus two. Right now my table reads minus two. How far it is from zero is the best question of the coming season.