Powerplay Pressure, Death-Over Ledger: A New Metric Notebook for Bangladesh Before the T20 World Cup

Mirpur, the 18th over. Taskin Ahmed with the ball. The scoreboard says the opposition needs 42 from 31 balls. The match is still open. My ledger, though, had already logged a different number: 17 dot balls across the previous three overs, two wicket-taking deliveries, a boundary-suppression rate of 68 percent.

What happened in the last three overs never appears on the scorecard. The scorecard only records that 42 from 31 became 28 from 9. Who built the pressure, which ball broke it, in which over a batter changed his shot — none of those questions have a column.

That gap is what I try to measure. The notebook I started from my home in Khulna in 2026 opened with hand-counted chances. Before the model had a name, I counted chances by hand. There was no tracking data then; there was a notebook, a pen and a television remote. Deciding which ball was a half-chance and which was a blood-chance taught me something simple: without a fixed definition you are not counting, you are guessing.

Today every delivery arrives with 360-degree tracking data. That is an advantage, and it is also a hazard — the easier the data, the lazier the definitions.

Pressing metrics can be borrowed, not copied

In 2026 I wrote a thread on Germany's 0-2 defeat — Root: PPDA and Germany. Germany's PPDA was 6.2; South Korea generated 18 shots and 2.4 xG while Germany managed 0.8 xG. PPDA works in football because pressing is continuous: while the ball is live, the pressure is live.

In cricket pressure is discontinuous. The ball dies after every delivery and is born again. Transplanting PPDA literally would be wrong. What does transplant is a single question: how much discomfort are you forcing on the opposition, and how quickly does that discomfort convert into wickets?

From that question I built three cricket-specific pressure events. They are counted, not felt.

1. Dot-Ball Cluster (DBC): three or more dot balls in one over. Isolated dots are a different statistic from clusters, because pressure is built in sequence, not in isolation. One dot teaches a batter nothing; three in a row force him to change his shot.

1. Wicket-Taking Ball rate (WTB%): the share of deliveries in an over that land on a line and length where the batter's shot selection is almost forced into error. That is not luck, it is a delivery map.

1. Boundary-Suppression Rate (BSR): the ratio of fours and sixes inside a defined over-block. BSR is naturally high in the powerplay; in the death overs it is the real examination.

Read together, these three produce a team's pressure profile — something an over-by-over scorecard never shows.

Environment: the Dhaka pitch, dew, and pre-registered corrections

I do not use the Dhaka pitch as an excuse. Environment is nobody's alibi — it is a variable, and it has to be declared in advance. Without pre-registration, any explanation can be fitted afterwards, and analysis turns into a storytelling contest.

My ledger carries four coefficients for Mirpur, written down before every match:

• Dew coefficient: when dew arrives in the second innings, spinners' grip statistics fall by roughly 12 to 18 percent. The chasing side's effective resource rises, and the captain's middle-over maths inverts.
• Pitch coefficient: on Mirpur's slow, low surface, straight deliveries at 140-150 kph lose value while 130 kph cutters and slower balls gain it.
• Opposition-quality coefficient: pressure events recorded against a top-six side cannot be compared directly with the same count against a lower-ranked side.
• Resource-gap coefficient: squad-depth difference, declared before the match, not after it.

The hand-counted ledger and the tracking model have to sit side by side. Where they agree, confidence grows. Where they diverge, the question is not which one is wrong — it is which definition is still unfinished.

The ledger's structure: why columns freeze mid-tournament

My notebook holds eight columns, and they stay frozen for the duration of a tournament. For every ball I record the bowler, the delivery type, the line, the length, the batter's shot, the field-setting zone, whether it was a dot, and whether that delivery changed the batter's decision.

That last column is the most valuable. Pressure is not a mood; pressure is a change in a decision. If a batter chooses a different shot from the one he chose on the previous ball, that belongs in the ledger.

When I started a page called BDCricTeam in 2026, match reports were written from feeling. After the Khulna data threads began in 2026, everything shifted — reports started with calculated figures rather than with results. Some readers said this was not cricket, it was an accounts book. That is fair. But without the book, six months later you cannot remember why you made a call.

The middle-over squeeze: where Bangladesh actually live

Everyone talks about the powerplay and the death overs, because that is where runs are visible. In my ledger Bangladesh's most valuable weapon sits between the 7th and the 15th over. In that block, spin and cutters push DBC to its highest and pull BSR to its lowest.

Success in that block is invisible on television. Three dot balls in the 9th over add a single zero to the scoreboard — and yet they are what leaves the opposition with fewer shots in the 18th.

That is why I log three separate scores for every match: the raw score, the pressure score, and the corrected pressure score. Without all three, Bangladesh's bowling unit gets misread — Taskin Ahmed's spells and Rishad Hossain's middle overs in particular.

A worked case: before and after correction

Take a sample from the matches I have logged ball by ball at Mirpur over the past three seasons. Suppose the home side made 148 in 20 overs and the visitors stopped at 144 — a four-run win.

The raw ledger reads: home side DBC 9, WTB% 14, BSR 11 percent. The spinners conceded 58 in eight overs, with decent middle-over control. Read that way, the home side looks like the side under pressure.

Apply the dew coefficient and the picture moves. Dew arrived in the second innings from the 11th over. Spinners' grip statistics fell, and the chasing side's effective run rate rose. After correction, the visitors' effective score sits near 148.

The result was therefore not a home win built on pressure. It was a race against dew, and the home side crossed the line two balls early.

That single correction changes the preparation call for the next match: chase more wickets in the powerplay, or carry an extra spin option for the death overs.

Template exceptions: when the game breaks the notebook

Not every match fits the same mould. When a game breaks the structure, I write a separate template-exception section, and I have to justify it — which variable is new, and why the existing eight columns could not capture it.

Example: on days of unusual humidity the ball does not grip, so spinners' WTB% falls while DBC stays flat. That requires a new column — grip-failure deliveries. I cannot do this every match, or the ledger becomes unusable. But writing the exception down makes the explanation testable next season.

Where the errors hide: heatmaps, aura, and the eyewitness

Heatmaps have become the new tea leaves — everyone looks, few can read. If a leg-spinner's heatmap shows he bowls more towards mid-off, that does not explain his role. Is he doing it because of the field setting, the batter's weakness, or the captain's instruction? The heatmap does not answer the last question.

The second trap is reading correlation as causation. If a side takes two powerplay wickets in three matches and wins all three, that does not prove powerplay wickets are the formula. The sample is small, the opposition differs, the pitch differs, the dew differs.

The eye test is a witness, not a judge; the model keeps the transcript. Discard the witness and you err; give the witness the power to rule and you err again.

There is a further point rarely written about. Stadium aura is a real variable. Big team, big ground, big crowd — when those three combine, marginal calls tilt in one direction. That is not a conspiracy; it is the product of pressure. My ledger has a separate column for umpire's call, and against the bigger sides it shows a small but consistent lean. On a small sample that is not proof, but it is not so random that it can be waved away. A side that refuses to accept this is leaving a variable outside the ropes unaccounted for.

The athletic-pressing trap in cricket

In football, gegenpressing was solved by mid-table sides through athleticism. Cricket's parallel is arriving in fast-bowling spells and fielding rings — who runs more, who dives more, who throws harder.

None of that is bad, but it becomes a problem when it substitutes for craft. A 130 kph cutter that wrecks a batter's shot selection is often worth more than a straight 145 kph delivery — especially on a surface like Mirpur.

I stopped reading transfer stories when I learned to read risk profiles. In the same way, you have to stop being dazzled by spell speeds and start asking: what was this spell's WTB%?

Opposition scouting: building a profile in four steps

I move through four steps. First, the opposition's powerplay BSR, split by right-hand/left-hand combinations. Second, their middle-over DBC — how quickly dot-ball pressure makes them change shots. Third, their death-over WTB% — the share of deliveries that force an error. Fourth, their squad depth, specifically the quality of their fifth bowling option.

When those four steps are done, a profile exists in numbers rather than in impressions.

T20 World Cup 2026: the frame is already fixed

The 2026 ICC Men's T20 World Cup runs from 7 February to 8 March in India and Sri Lanka. That is confirmed, and it sets the frame for every calculation from now on. Subcontinental pitches mean spin, dew and humidity — meaning any comparison without environmental correction is incomplete.

One historical fact matters for Bangladesh here: the country's first T20 international was played on 28 November 2026 at the Sheikh Abu Naser Stadium in Khulna, against Zimbabwe — and Bangladesh won it. Khulna's start, Khulna's ledger, Khulna's arithmetic.

Shakib Al Hasan will enter this conversation. In international T20 cricket, the double of 100 wickets and 2,000 runs was first achieved by him. That is not only a record; it is evidence of a profile — a player who can create pressure and absorb it in the same match.

Taskin Ahmed, Mustafizur Rahman, Rishad Hossain and Nahid Rana: within that bowling unit the split between powerplay specialists and death specialists needs to be made explicit. Mustafizur's cutters are worth more on a Mirpur surface than his run-concession figures suggest — the number that shows it is WTB%.

Litton Das, Towhid Hridoy and Jaker Ali face one question: what is their BSR between the 12th and 16th overs? A powerplay fifty is worth nothing if a cluster of four or five dot balls forms in the middle.

The signal for the next round: the side that can raise its powerplay DBC while holding its WTB% will carry the lowest risk on dew-corrected, Mirpur-style surfaces. Not wickets alone, not dot balls alone — the ratio between them is the real metric.

And if, midway through the tournament, one of my columns fails to capture what the match actually did, I will not hide it. I will write the exception down, because writing it down is what lets someone verify it next season.