The Geometry of 106: Seven Matches, Eighteen Days, and Bangladesh's Wrong Map at the T20 World Cup

June 16, 2026. Kingstown, St Vincent. The old pavilion at Arnos Vale has thrown half the ground into shadow, and Bangladesh's innings has just ended in the 19.3rd over for 106. Walking back towards the dugout, Towhid Hridoy's shoulders give away nothing about whether his side will win or lose — because on paper, a total like that guarantees nothing. Two Nepali reporters sitting near me in the press box are already doing the arithmetic: Kushal Bhurtel's fifty should arrive inside two hours.

I am sketching Bangladesh's bowling field on a blank notebook page. To defend 106, every zone has to be covered, no gap can be left — that was my assumed rule. Slip, point, cover, mid-off, mid-on, square leg, deep. Seven marks. The classic textbook diagram.

Three hours later, the scoreboard reads: Nepal 85 all out. Bangladesh win by 21 runs.

My map was wrong. The first arrow I drew was wrong, but it taught me where to look. Bangladesh defended that 106 not with a packed slip-and-point cordon, but with the slowness of the pitch, two guards either side of the wicket, and a geometry that effectively outlawed the sweep shot.

Context: two continents, two pitches, one template

The 2026 ICC Men's T20 World Cup was the first major cricket event split across the United States and the West Indies, with 20 teams and 55 matches between June 1 and June 29. From Grand Prairie in Dallas to Nassau County in New York, from Arnos Vale in St Vincent to the Sir Vivian Richards Stadium in Antigua — the geography of the venues was the tournament's most under-analysed character.

The two US venues used drop-in pitches. Soil, grass and rolling were all imported. In Dallas and New York the new ball found seam, bounce was irregular, and batters who drove through cover lost wickets in clusters as the ball climbed or skidded. On those two grounds even 140 became a heavy score.

Arnos Vale in St Vincent was the opposite story. An old, used, slow surface. The ball did not come onto the bat, the sweep and the cut were the only reliable boundary routes, and spinners could force batters to generate all their own power. The lowest-scoring matches of the group stage happened here.

Antigua was the most batting-friendly. There, even 196 was not safe, because sides like India put up 200 on that surface.

Bangladesh were in Group D — South Africa, Sri Lanka, Netherlands, Nepal. Per the ICC's official calendar, the schedule ran: June 7 versus Sri Lanka in Dallas; June 10 versus South Africa in New York; June 13 versus Netherlands in Kingstown; June 16 versus Nepal in Kingstown. Then, in the Super Eight, June 20 versus Australia in Antigua, June 22 versus India in Antigua, and June 24 back in Kingstown against Afghanistan.

Seven matches, eighteen days. Four internal flights, five venues, a constant change of hotels. Bangladesh have never had such a rapid sequence of venue changes in a single series — at least not in my nine years of watching matches.

The squad was built for Caribbean conditions. Of the 15, as many as six offered spin options — Shakib Al Hasan, Rishad Hossain, Mahedi Hasan, Tanvir Islam, plus the part-time spin of Mahmudullah and Soumya Sarkar. There were only three frontline seamers: Taskin Ahmed, Mustafizur Rahman and Tanzim Hasan Sakib.

The captain was Najmul Hossain Shanto, the head coach Chandika Hathurusingha. Shanto's team had a painfully clear character: slow the game with spin, bat safely to 140–145.

And then came the cruellest part of the schedule. Mustafizur Rahman had played the full 2026 IPL season for Chennai Super Kings. The IPL final was on May 26; Bangladesh's World Cup camp in the USA began in the final week of May. In other words, the buffer between finishing a franchise league in India and bowling on Caribbean pitches was measured in days, not weeks.

That single line, for me, is the most important tactical fact of the whole tournament. Because the arithmetic of fixtures and recovery never appears on a scorecard — yet it sits underneath every delivery's pace, every cutter's grip, every death-over yorker.

Core analysis: the geometry of defending 106

The textbook says that to defend a low total you must attack: bring in catchers, hunt wickets. On paper the argument is sound. But on the Kingstown pitch the argument fragments, because an attacking field means gaps in the ring, and when the ball does not come onto the bat those gaps bleed singles.

What Bangladesh actually did was split the innings into two distinct phases. Phase one, overs 1 to 6 — full attack. Phase two, overs 7 to 20 — boundary protection.

In phase one the seamers held the ball outside off stump, pulled their length back, and kept one catcher close to the bat. The mechanism is simple: on a slow pitch, a back-of-length ball cannot be driven, cannot be cut, it can only be pushed. Nepal's top order repeatedly pushed at balls on the front foot towards mid-off, and the ball gripped, held and took the leading edge.

The geometry of phase two is the real story. Bangladesh said: two deep fielders, one either side of the wicket — long-on and deep midwicket. No sweep cover, no fine leg. In plain terms, the two easiest boundary routes out of a batter's hands — the sweep towards square leg and the scoop towards midwicket — were both closed.

The consequence was counter-intuitive: Nepal were pushed into trying to hit boundaries with straight drives or lofted shots through long-off — precisely the shots that are hardest and most edge-prone on a slow pitch. The real art of defending a low total is not protecting the boundary, it is choosing the right boundary to protect and leaving the rest open.

In my own shape notebook I charted where every Nepal shot in the final ten overs went — line, length, shot direction. The reverse calculation was striking: the more Nepal tried to hit through the midwicket–square leg arc, the more the ball died in the surface and lost its pace. That single factor broke their middle-order strike rotation.

One thing must be made clear. Bangladesh did not adopt this plan out of bravery; they were forced into it. The side had nobody who could bowl a 90mph yorker and take a wicket outright. So geometric control became the only weapon. The fatigue of the fixture list, the thinness of the pace bank and the nature of the pitch — three uncontrollable variables combined to turn the bowling innings into a problem of geography.

Rishad Hossain and the broken textbook

Bangladesh's T20 bowling template was long fixed: seam in the powerplay, finger spin in the middle, Mustafizur's cutters at the death. At this World Cup the template was broken by one name — Rishad Hossain.

The historical reason for not bowling a leg-spinner in the powerplay is real: with a new ball there is no flight, and on a small ground one error in line is a six. But on slow, worn Caribbean surfaces the calculation inverts. Until a new batter can read a wrist-spinner's wrong'un or top-spinner, his footwork stays unsettled. And with two fielders outside the ring in the powerplay, a mishit becomes a straightforward catch.

Watching the matches, one thing stuck with me that no scorecard records: when Rishad bowled, his slider or googly landed several inches outside the stumps, and batters, reacting to the same delivery a second time, folded their back leg towards the stumps. That habit is dangerous on a slow pitch, because power dies and the bat plays alone.

This analysis has one limitation and I accept it. If I had seen Rishad repeat the same success on a flat Antigua surface and Bangladesh win there with the same template, my entire argument would have been disproved. That did not happen, and that is what gives the argument its weight.

The batting template's hole: overs 7 to 15

The most repeated line after the World Cup was: Bangladesh have no power hitters. That is true but incomplete. A lack of power hitting is a problem — but where it actually cost the side was not merely an absence of big hitting, it was a structural error.

I broke down the innings of all seven matches into sections. That Bangladesh batted slowly in the powerplay is common knowledge. But the real collapse in strike rate came between overs 7 and 15 — where the ball was not changed, the field was spread, and yet two set batters were playing the same template: front foot, straight bat, single, rotate strike.

The problem was structural. Strike rotation in the middle overs only works when a side has at least one left-hander, because that forces the finger spinner's angle and the field placement to break. Bangladesh's middle-over core was almost entirely right-handed pairs — Shanto, Hridoy, Mahmudullah, Jaker Ali. As a result, setting a field became easy for the opposing captain: two on long-on, slower balls into the surface, and not one gap in the inner ring to concede a single.

There is more. Bangladesh's two top-order batters had almost identical roles — both anchors. A side needs one anchor; two is a luxury. In T20, an anchor's job is not only to protect wickets but to give the aggressor at the other end room to play. Two anchors together inevitably squeeze the run rate, and when chasing 140 the required tempo is never reached.

In Kingstown this structural problem was masked, because on that pitch even 110–120 was enough to win. But on the flat Antigua surface, facing India's 196, the same template exposed the hole. The pitch changed; the template did not.

Workload arithmetic: seven matches in eighteen days

Now we come to the place where the least discussed and most frequently occurring truth of my whole career is hidden.

A player's injury is largely not a medical team's failure; it is a consequence of the schedule. Seven matches in eighteen days, with four journeys between different cities in between, means the frontline seamers never had a full 72-hour recovery window. Airports, hotel check-ins, bus transfers — none of this is written on a match schedule, but it eats directly into the tissue-repair time of a fast bowler's shoulder, back and hamstrings.

Second, the irregular bounce of the New York and Dallas pitches. These surfaces have a perverse reality: when the ball bounces unpredictably, a seamer cannot release it at his natural length, because at normal length the ball goes line-less. So he has to drop a fraction short, shorten his stride, and load the shoulder to bowl a bit faster. Over one or two overs there is no damage. Across three consecutive matches the load accumulates.

The link between the IPL franchise block and the international block ignites exactly here. There is no reset button on a seamer's workload meter. The delivery load accumulated for Chennai Super Kings in May has to be carried across Caribbean pitches. Changing hotels and flying does not physiologically reduce that load — it disrupts recovery.

I do not want to suggest Bangladesh did not know the solution; the point is that in this tournament's structure there was nowhere to apply it. Fifteen players, three frontline seamers, seven matches. There was rotation, but never within a workable range.

For this reason I consider the real test of Bangladesh's campaign to be the final two matches — India in Antigua on June 22 and Afghanistan in Kingstown on June 24. By then there was a three-day gap, yet travel had already eaten the familiarisation time. Watching those two matches, the body language of the side and the stride of the bowlers in the first five overs suggested the biological clock was working harder than the tactical board.

Contrarian: one template, two ecosystems

Now the gap I noticed during the tournament but hardly ever saw on editorial pages.

Across this eighteen-day campaign Bangladesh carried a single playing template — spin-heavy, slow, venue-neutral. But the tournament contained two completely different pitch ecosystems: the drop-in squares of the United States, and the old, slow island wickets of the Caribbean. On the first, seam-up deliveries were king; on the second, the sweep and the cut.

What Bangladesh could have done: manage pace differently across the two legs. In Dallas and New York, increase the seamers' overs and look for the extra seamer. In Kingstown, keep the spin core unchanged.

My favourite example is the four-run defeat by South Africa in New York on June 10. On that pitch the ball did not hold, the seam moved, and the opposing pace attack trapped Bangladesh's top order inside the line within the first five overs. Bangladesh's plan was to reach 85 to 90 and squeeze late. The plan was not wrong — the language of the pitch was different.

And here that most personal memory returns. My first lesson, learned in forty minutes in the Luzhniki press box in 2026, was this: when a match's map does not match the ground, the air in the whole room changes. In a Camden bedroom, every formation I drew was a door — but I would never write a line without checking whether that door opened onto the actual field. In Bangladesh's case, that check was missing.

One other questionable decision. After seven matches, I wanted to look separately at which section of the tournament Bangladesh conceded the most runs. Because succeeding on slow pitches and then bowling the same way on flat ones means the plan was not pitch-specific — it was a habit. And when a habit becomes a plan, one map is written across an entire tournament, and the error becomes permanent.

Takeaway

For the next cycle I want to leave one question open. On the ICC calendar, the 2026 T20 World Cup goes to India and Sri Lanka — a hot, dry, spin-friendly tournament with a completely different geography. Bangladesh will have day after day of similar pitches.

The single verification point is this: will the side walk out with a venue-specific second bowling plan, or will it fold up the wrong map from the last tournament and pack it into the hotel bag again?

No question is more honest than that — and in the next tournament, the most-read thing will be the small tear in the left elbow of every one of our seamers, the one no scorecard will ever show.