Hook

Melbourne Cricket Ground, November 13, 2026. The final's powerplay ended, and Pakistan's two openers were still at the crease. The colleague beside me shook his head: "Both of them are there, but they're losing the match." What the scoreboard wasn't showing was crueler still: Pakistan would finish on 137/8 from 20 overs, and England would chase 138/5 in 19, winning the final with five wickets and six balls to spare.

Standing in the mixed zone, I watched people whisper about Babar Azam's strike rate, wondering how the tournament's finest batter had sunk his side in a final. I stayed in the silence to hear what the scoreboard could not say. Forty minutes after the last ball, the real story finally stood up — and in that story, Babar was no villain.

Context

Two decades of international T20 have never settled one argument: should a team bat slowly to "build a platform," or attack from the first ball? After the inaugural 2026 World Cup, sides followed a simple rule — save wickets, swing late. After 2026, England broke it. Under Eoin Morgan they decided batters would stop fearing early wickets; that philosophy won them the 2026 ODI World Cup final — the tied match at Lord's against New Zealand, decided on boundary countback.

But when a philosophy wins, it often hardens into superstition. The reason is simple: teams copy the method of whoever wins, without asking whether that method worked only for that squad, that pitch, and that skill set. This is where the anchor-innings trap is born.

As someone raised in Bangladesh's domestic cricket culture, I grew up hearing one instruction — "keep wickets in hand, hit at the end." Only after becoming a professional analyst in London did I realise that advice is really the language of an economy. Wickets are capital; balls are time. The question was never "how many wickets do you need in hand to win" — it was always "how many runs per ball do you need, and how much risk must you take to get them."

Based on my years of watching matches, I can say that when an anchor settles in during the middle overs (seven to fifteen), the team's scoring window starts to contract. This is not one batter's personal failure — it is the output of a system in which the order's very design forces one batter to be slow and hands the rest an impossible acceleration target.

Core Analysis

Geometry: where the anchor lives

Before every big match I draw a pitch map — a zone chart plus three arrows. In T20, two areas matter most: the inner ring of the powerplay, and the compressed central corridor of the middle overs. The anchor lives in the second. Its scoring zones run from square leg to long-on — singles and twos. But the problem is that by the middle overs, the fielding side has already plugged those zones: deep midwicket, long-on, deep square.

So what the anchor does is not score runs, but spend balls. It saves deliveries without storing them. And the arithmetic of T20 is brutal: unless a side scores more than six an over across 20 overs, the late hitting cannot make it up.

The math: the hidden cost of "building a platform"

Take an example. Say the score is 40/1 after the powerplay, the anchor unbeaten on 22 off 25. It doesn't look bad — wickets in hand, a platform built. But do the sum: in the remaining 14 overs and 59 balls, the team needs roughly 11.5 an over to reach 160-plus. Because the anchor is still in, that tempo must come from the other end — an enforcer who must now make 70 off 30.

Here is the trap. The anchor's slow rate does not itself waste runs; it forces the other batter's risk upward. The enforcer knows boundaries are mandatory, because balls are dying at the other end. That obligation raises his dismissal probability. Once he falls, the anchor tightens further, the side collapses faster. It is a feedback loop — and the loop devours the team.

Case: Pakistan's system

One could explain Pakistan's 2026 final as the failure of Babar Azam or Mohammad Rizwan. I won't. The whole tournament design of that side rested on two anchors. Babar and Rizwan were batters of extraordinary averages — the classic "build a platform" model. But on the Melbourne pitch, where strike rotation is hard and boundaries are rare, the model broke down.

The gap with England was one of order design. England's top order did not play merely to survive — Jos Buttler and Phil Salt set the tempo in the powerplay itself. Their system had no designated seat for an anchor; every batter was an attacker. One failure could not stall the team's pace.

Pakistan's problem was the exact inverse: the anchor's seat was treated as sacred. That is the system's real fault — a system that forbids a batter to take risk also denies him the chance to win the match.

Why the system survives: the economy of fear

Now the least-asked question: why do coaches and selectors cling to the anchor? The answer is cultural, not tactical. When a wicket falls, the batter is blamed. But when a team loses batting slowly, the system is blamed — and blaming a system is hard, because a system has no face. So the safe path for the individual is not losing your wicket, and the safe path for the system is picking that individual.

This is exactly the mental block I see in players returning from injury. The physical injury heals; the fear remains. It is the same for a batter: the technique is fine, but the fear of getting out slows him. And that fear is far harder to fix than technique. That is why selection committees choose the safe batter — they do not want to own the task of curing a mental block, only to avoid the risk of a mistake.

Who pays the cost

Before any tactical claim, I now ask who pays for it. In an anchor-reliant system, three people pay. First, the young enforcer, who must bat at a strike rate above 150 every match and is dropped after one failure. Second, the spinner or seamer who bowls at the death, under pressure every over because batting depth is missing. Third, the spectator who buys a ticket and watches a 137-run final.

Contrarian Angle

Now I want to flip my own argument, because my profession rewards the counter-intuitive read — and that reward is itself the biggest trap.

I never reach a contrarian conclusion before testing the obvious explanation. So: did Babar Azam really play a bad final? No. On that Melbourne pitch, 137 was close to a realistic score, and England had to fight until the 19th over. Babar did not fail — he played exactly as well as the system allowed him to.

Here the old football lesson applies: in 2026-17, everyone said Chelsea's 3-4-3 was the reason for their winning run. The formation was not the problem — the players' mutual understanding inside it was. Cricket is the same. The 3-4-3 was never the fault, and neither is the anchor. The fault is the system — one that forces a batter to survive and makes the other ten pay for his slowness.

Consider the reverse, too. If the anchor system always failed, why do sides like South Africa or Sri Lanka sometimes succeed with it? Because successful sides do not protect the anchor; they use him according to conditions. On a slow pitch the anchor's value rises; on a true pitch it is zero. If a system ignores the pitch and decides in advance, that is the error — not the batter.

Takeaway

So where do we look next tournament? Not at a batter's strike rate — at the order's design. The difference between a side that sends an attacker at number three in the powerplay and one that keeps two anchors through the middle is visible on the scorecard before the result is. Go into the next big match with one question: is the team reading the pitch, or only reading its own fear? Because you can keep wickets in hand, but a slow innings never compounds — it only traps the team in time.