Bangladesh's Real Asia Cup Gap Isn't the Powerplay — It's Overs 7 to 15

In the stands at the Dubai International Stadium, Bangladesh's supporters were given one corner — a small block, a few red-and-green flags, and beside them a sea of India and Pakistan shirts. I opened my notebook that evening to keep the over-by-over tally, because for several years now I have been breaking Bangladesh's T20 innings into separate blocks rather than reading them as one narrative. The first ball of the seventeenth over arrived; the batter pushed it to mid-wicket for a single.

The scoreboard at that moment demanded more than nine an over. So that single was not a mistake. It was an output. And the decisions that produced it were not taken that evening in Dubai. They were taken two or three years earlier, in a meeting room in Mirpur, around a calendar and a selection sheet.

The shape of the Asia Cup has to be established first, because the format itself alters batting arithmetic. Six teams, two groups, a Super Four, then a final. A side plays between two and five matches inside a fortnight. In that fortnight you are forced to write out the full justification of your batting order, and there is almost no time left to correct it.

But the preparation for those two weeks is manufactured across a whole year's calendar. For Bangladesh that currently looks like this: the franchise T20 league in December and January, the domestic long format in spring, and the main international T20 window in September and October. Which means the pitch on which you rehearse T20 batting for two months is a winter Dhaka pitch, while the pitch you travel to is a September pitch in Dubai or Colombo. The behaviour of the ball differs, the soil differs, the pace arithmetic differs.

I have watched this system closely since 2026, starting in radio commentary and later moving to television. One thing has surfaced repeatedly across that time: decisions taken inside the board, the selection panel and franchise ownership show up on the field two to five years later. A culture of fast batting at international level is not a decision, it is an institutional habit. And habits take time to move.

A further layer has been added over the last five years, which I have seen with my own eyes. I watched the pandemic empty the stadiums, then fill the screens. The chairs in Mirpur returned slowly, but in the meantime a new audience formed that does not come to the ground and watches on a stream. This audience keeps a different ledger: it remembers the strike rate of every innings, not the habits. So for a side that is structurally slow, the streaming era is a continuous punishment; for a side that is fast, it is a reward.

Now the actual arithmetic. I read a T20 innings in three blocks — overs 1-6, overs 7-15, and overs 16-20. The three blocks have three different jobs. The first block exists to stop the fielders from getting inside the circle. The second block exists to hold the run rate against spin, so that there is fuel left on the back for the final block. The third block exists to burn that fuel.

In recent editions of the Asia Cup, Bangladesh's weakest block has not been the first one. The weak block is the middle nine overs — seven to fifteen — and that is where the match quietly walks away.

Why this argument differs from the standard powerplay complaint needs stating. Two or three boundaries in the first three overs make a powerplay strike rate look respectable. Powerplay strike rate is an easy number, and it is the first graphic a broadcaster puts on screen. But read the dot-ball percentage of overs 7 to 15 alongside the boundary frequency in those same nine overs and the picture flips: the ball is turning over often enough, but the rope is barely being reached. You are not losing wickets, but you are not advancing the match either. That is the most dangerous state in T20, because the absence of loss gets mistaken for the absence of cost, and that mistaken belief settles into the team's head.

When batters of the quality of Litton Das and Najmul Hossain Shanto bat at the top, the question is not ability. The question is role. If a batter makes 25 off 25 between overs seven and fifteen while holding his wicket, you end that block on roughly 45 to 50. The best sides in the tournament routinely make 70 to 80 in the same passage. The difference is 25 to 30 runs, and that gap is what forces unnatural shots in the last four overs. Towhid Hridoy, Jaker Ali or whoever takes the finisher's slot then has to do two jobs at once: lift the rate and protect the wicket. No batter does both well on a regular basis.

The last overs lose the match, but the decision that loses the match was taken long before them.

On the bowling side the picture is the exact inverse, and this is where Bangladesh genuinely compete. The four-over block of spinners works almost mechanically on Asia's slow pitches. Rishad Hossain's leg-spin, Mehidy Hasan Miraz's flatter trajectory and Mahedi Hasan's quicker left-arm all frequently keep the middle phase under seven or eight an over. At international T20 level that is a good figure, and in Asian conditions it is excellent.

But that block was not a wall; it was a timed counterattack. The block only works when you retain the option of breaking it later with a power hitter. Blocking without losing wickets turns the block into pure defence, and defence has no value in T20.

What I have seen repeatedly on pitches in Dubai or Kandy is that the length of the tournament itself changes the surface. A pitch that yields 160 to 165 in the first match drops towards 145 in the second week — the ball grips more, the boundary effectively lengthens. That property is absent in European conditions, where a surface usually behaves the same throughout a tournament. A side carrying a fixed score in its head makes two kinds of error late in a tournament: it either chases a big shot without reason and loses wickets, or it stalls without reason and loses out of fear of losing.

There is only one way to handle this issue — the comparison has to be drawn inside the same match, against the opposition innings, not against a tournament average. Because the pitch, the light and the dew are identical, and if the opposition makes 80 in overs seven to fifteen, there is no explanation available for your 50.

Now the role of the franchise league, and I think the least discussed root of Bangladesh's T20 problem sits here.

Across several years of over-by-over notes, one pattern keeps returning: in the domestic franchise league, Bangladesh's leading local batters frequently bat at three, four or five, because the top two or three slots are often filled by overseas openers and overseas finishers. Then they return to the national side and are sent straight to the top, where they are asked to perform a role — fast top-order batting — that they have not rehearsed once in two months of their own league.

This is not a shortage of talent, it is a mismatch in role accounting. A batter who has played forty matches in one position has his fastest decision-making in that position; in another position his first ten balls are usually calculation, not instinct.

There is a measurable dimension to this habit — fielding. In the last five overs the ball travels towards the boundary more often, and the quality of running towards the rope is where the real difference is made. Taskin Ahmed, Mustafizur Rahman or Shoriful Islam bowling the death overs is not the problem; the problem is the ball after a dropped catch. A drop is not four runs, it can be six, plus an extra delivery the bowler must find. That loss is not written in a separate column on the scorecard, so it never enters the conversation.

On selection, one habit has stood out across several cycles. Squads stay stable before a major tournament, and then two or three changes happen midway through it. That habit is not courage; it is the cultural imprint of risk aversion. Imagine a selection panel picking three aggressive top-order batters before the tournament. Two bad matches and those players cannot be removed — that is the real political cost. So the squad is assembled in a way that lets everyone justify his place somehow, and the burden of aggression does not land where it belongs.

The decision then becomes about the security of a position rather than the ordering of talent.

And this is where the difference between compounding and coincidence matters. Over the past decade, most of Bangladesh's big T20 wins have rested on the accumulated output of one or two individuals — an innings, a spell. Almost every defeat has rested on the same structural ground: slow middle overs, weak accounting in the final five. The structure returns every time; the individual innings does not.

Coincidence arrives suddenly and leaves suddenly; compounding accumulates slowly, and then holds.

Now the argument needs to be turned against itself, because the cleaner an analysis looks, the more it should be suspected.

Assume I am wrong. Assume the problem is not structure but the reading of data — that the team management and the selection panel are watching the same match as I am but seeing different things. That is possible, and this possibility is the weakest joint in my argument. Because the data I hold is entirely public: over-by-over scorecards, strike rates, fielding logs. The balanced data and the physiological data the team holds are not in my hands. Perhaps they know that batting slowly between overs seven and fifteen is a conscious decision, because there is no batting depth after number seven. Then the problem is not batting approach but squad construction. And squad construction is also structure — meaning I am looking for the door in the wrong place, not that the door is absent.

The second possibility is that what I call the middle-nine-over gap is actually variance. Here I have to be strict with myself: how often and how widely that gap has recurred, I am not putting a number to in this piece, because I have not been able to verify it independently. Throwing a decimal-point figure without verification is the easiest route to abusing the authority of data, and in my profession that carries a real risk of becoming a habit. What can be said is that the gap has recurred — and in recent tournaments it has recurred in the same place.

And a third trap, which I keep writing in my own notebook: powerplay strike rate is the easiest number to obtain, so the conversation stalls there. What is easy to obtain becomes the most visible candidate for a problem — for analysts, that error is the rule, not the exception.

So what will I watch in the next cycle, and what evidence would break this reading?

In the next major Asian tournament, if Bangladesh's run rate in overs seven to fifteen, its dot-ball percentage and its boundary frequency do not move together, then I will not count a change of captain, a new coach or a new opener as having touched the structure. And if one big innings arrives in a single match, that will prove nothing either, because it was an event, not compounding. The real question is not about the batter in the final over. The real question is in a meeting room in Mirpur, around a calendar and a squad sheet — which, so far, has not happened.