Compression in Tournament Cycles: Baselines, Deviations and the Squad-Depth Ledger

Hook

On 24 October 2026 in Mumbai, the Wankhede scoreboard carried two numbers: South Africa 382/5, Bangladesh 233. A 149-run defeat. Below that scoreboard hangs a line almost nobody reads: 111, Mahmudullah. Nearly 48 percent of the team total, alone. Television called it a fight. Headlines called it a failure. Both are narratives. My table says something else: the result was settled before that innings began — not by the 382, but by two wickets inside the first six overs.

In tournament cricket that gap is the whole story. In a bilateral series a mistake costs little, because next week there is another match. A World Cup cycle does not work that way — nine group games, one wrong position, four years to carry it. Tournament cycles compress emotion, and inside that compression numbers speak louder than narrative.

Context

Across the last several tournament cycles I have done one thing before every match: build a baseline first. I watched this one on a screen and had the table open by the tenth over. The eye test is a witness; the data is the cross-examination. The witness gives you feeling, the cross-examination gives you a timeline.

Where does the baseline come from? Three editions of group-stage cricket, two years of bilateral series, and pitch-adjusted phase splits. I divide every innings into three bands — overs 1–10, 11–40, 41–50 — and compute expected runs per wicket, a dot-ball pressure index, and a strike-rotation baseline for each. Cricket has no PPDA, but dot-ball pressure does the job: it measures how much of the opposition's structure you are actually breaking.

In 2026, when stadiums stood empty, the same method showed me that part of home advantage comes from structure, not emotion. Every empty stadium was a controlled experiment we never asked for. Tournament cycles work the same way: from five or six matches we manufacture form, luck and big-match temperament. Kazan 2026 taught me the arithmetic — Germany did not lose to South Korea; they lost to 28 shots and no goals. Seventy-four percent possession, 2.7 xG, two goals conceded. Numbers and narrative do not describe the same match.

Core

Mechanism one: a powerplay wicket does not cost the same as a wicket anywhere else. In my calibration, a wicket in overs 1–10 removes roughly 18 expected runs from the batting side's projection. Between overs 11 and 30 the price sits near 12, between 31 and 40 near 10, and in the last ten overs it falls to around 7. Bangladesh lost two wickets inside the first ten in Mumbai, which pushed the baseline below 233 immediately. Mahmudullah's 111 was a real positive deviation inside a system already priced out of the contest.

Mechanism two: middle-over dot balls are deferred loss. A dot at over 25, with a set batter at the crease and the ring open, costs differently from a dot at over 46 with fielders on the rope, which is close to free. We usually count total dots and never split them by phase, and the raw number then misleads. What a side calls middle-over control is often a silent six- or seven-over run drought between overs 11 and 30, a passage that never appears on the scoreboard as a moment. That drought is what later forces the batting side to buy risk at the death.

Mechanism three: the death-over baseline has inflated. Average scoring in the final ten overs has risen over the past five years, so saving three or four runs now earns praise that the baseline says is ordinary. Skip the baseline audit and both praise and blame land at the wrong address.

Stack the three mechanisms and the Mumbai match becomes legible. The damage came in phase one, the erosion in phase two, and the acceleration at the end could not climb 149 runs back from the baseline. Mahmudullah's innings is the real story precisely because it is an isolated deviation inside a collapsed system.

Contrarian

The trap here is easy to fall into. The top order failed, therefore the team lost — that is correlation, not cause. A powerplay wicket matters so much because it lowers the expected runs of everyone who follows; the mechanism is order depth, not a bad innings. Pre-specify the mechanism before the match, or every defeat will find itself a handsome story afterwards.

Squad depth enters at the same point, and we usually measure it in the wrong place. Depth lives at numbers 13 to 15 — who is sitting on the bench, how many overs that player can bowl, and in which phase he is usable. The 2026 data showed that part of any edge is structural. In a tournament, that structure is sitting outside the eleven.

One more thing I track: injury return timelines. Week-to-week often means the statement was drafted before the scan, not that the injury is close to healed. The shape of bench usage gives the gap away. Review protocols belong in the ledger too. A long DRS check cuts the rhythm of a match; a two-minute wait cools a wicket celebration and breaks a bowler's over. Marginal in the run column, decisive in the rhythm column.

Takeaway

I do not chase narratives; I build a table and wait for them to arrive. Next round I will be watching three things: how many powerplay wickets fall and what they cost in phase-adjusted runs; how the dot-ball pressure index behaves between overs 11 and 30; and how many overs the thirteenth player actually bowls.

One question to leave behind: if your team's century arrives in a lost match, is that proof of excellence, or the side effect of a system that had already written the result?