Calling Babar Azam the 'Backbone' Is Diplomacy — the Numbers Tell a Different Story

Hook: The Question Nobody at Rawalpindi Wanted to Answer

At the Rawalpindi Cricket Stadium press conference on the afternoon of 17 October, a reporter asked the obvious question — is Babar Azam under pressure? Shaheen Shah Afridi smiled and said Babar is the "backbone" of Pakistan cricket, that there is no pressure on him. That answer ran for twenty seconds on television. What was not said in those twenty seconds sits in three separate rows of numbers: 97 runs at 24.25 in the Test series against England; 58 runs at 14.5 in four innings for OGDCL in the President's Trophy; and 125 runs at 41.66 in the ODI series against Australia.

Watching Pakistan cricket press conferences over many years, I have learned one pattern: when a captain calls a player the "backbone," he is not talking about cricket. He is answering the question that will be repeated in every column for the next three weeks. And that is where the real story begins — because Babar's three numbers belong to three different formats, and reading them together is exactly the mistake the entire Pakistani media is making right now.

Context: The Architecture of the Tri-Series and Its Hidden Politics

From 18 to 31 October, Pakistan hosts a home ODI tri-series with England and Sri Lanka. This is the series the PCB has effectively designed as a "confidence-restoration window" for Babar. Rawalpindi's pitch has historically been batter-friendly — flat, low bounce, minimal assistance for fast bowlers. It is no coincidence that this venue was chosen to rehabilitate a batter whose red-ball record is in its worst phase.

But the real complexity of this series lies in the captaincy structure. Shaheen Shah Afridi captains the ODI side — he was the man at the press conference. Babar Azam was reinstated as Test captain in July. Two captains, two formats, two separate lines of accountability. When Shaheen defends Babar, he is defending a player who does not report to him in Tests. This split-captaincy model is not new in Pakistan cricket, but right now it is doing something specific: it keeps Babar outside white-ball captaincy accountability while he searches for form under his own Test leadership.

Pakistan's recent record sharpens the picture. They drew the Test series 1-1 in the West Indies, struggled in Tests in England, but won the home ODI series against Australia 2-1. This is the classic Pakistan profile — strong at home in white-ball, fragile away in red-ball. Babar's individual record is a miniature version of exactly that team profile.

Core: Three Numbers, Three Stories, and One Large Illusion

The first thing missing from this entire debate: Babar's Test numbers and ODI numbers belong to the same player, but they are not the same problem. The 24.25 average against England points to a technical issue — front-foot positioning against balls outside off stump, early-innings vulnerability against pace. The 14.5 average in the President's Trophy comes from four innings — statistically far too small a sample for any conclusion. But the 41.66 average against Australia shows his white-ball base has not collapsed.

The real danger here is not in the data but in how the data gets read. If Babar scores 60-70 on a flat Rawalpindi surface in the tri-series, the media will declare that "Babar is back." But batting in Rawalpindi and batting in Melbourne or Leeds are two different professions. Runs on a flat home pitch do not repair Test technical weaknesses — they cover them. This is cross-format contamination, and it has been the single biggest analytical error in Pakistan cricket over the past decade.

Shaheen's statement is part of that contamination. Saying "no pressure" is defensible for ODI — because Babar's ODI record remains serviceable. But for Test cricket the claim is indefensible, because his Test output is demonstrably poor. What the captain said is not a lie — it is half a truth, and in cricket half a truth is more dangerous than a full lie because it stops the investigation.

The second point nobody raised: Babar's return to the President's Trophy. After roughly nine years, he returned to domestic first-class cricket for OGDCL. Fifty-eight runs in four innings. Any analyst will call this evidence of decline. I read it differently: it is the player and management admitting the problem exists and is technical rather than terminal. A player who returns to domestic cricket after nine years to fix his technique is not giving up — he is repairing. But calling that repair a failure on four innings is as big an error as calling it a success.

The third angle: injury history. Babar missed the opening Test against England through injury. That fact is absent from the entire debate. A returning batter's poor record is not always technical decline — sometimes it is simply a lack of physical rhythm. So when reading the 24.25 average, the necessary question is: is this a technique problem or a body problem? The treatments are entirely different, and this report provides no dismissal-mode distribution (lbw, caught, bowled) or pace-versus-spin splits. Without that data, any technical conclusion is guesswork, not analysis.

The fourth angle, least observed: Sri Lanka's spin. Pakistan's real examination in the tri-series is not England but Sri Lanka. The Sri Lankan side is spin-dominant, and Babar's white-ball record against turning ball has always been his biggest test. If Babar struggles against Sri Lankan spin, that will be a far more important signal than the 41.66 average. If he plays spin well, that will be a genuine sign of return — far more so than runs against Australian pace on a flat Rawalpindi deck.

Contrarian: How I Could Be Wrong

What I have argued here — that Babar's red-ball record is seriously poor and the captain's defence is limited to ODI — has three clear failure points, and I am writing them myself.

First: sample size. Four first-class innings and one Test series do not establish a trend. If Babar scores 250 runs across three innings in the tri-series and then averages 40+ in Tests, my entire analysis — that this is technical decline — will be proven wrong. I am conceding that in advance. My claim is not that Babar is finished; my claim is that dismissing his Test output with "no pressure" is a comfort that stops the investigation. If he proves me wrong, cricket wins, and I will happily lose.

Second: the captain's defence may be the correct strategy. I called it "half a truth," but there is an alternative reading: Shaheen knows his job includes media management. If he had said openly that Babar is out of form, the Pakistani media cycle would have reached demands for his removal within three days. The captain's statement is a shield, and shields are sometimes necessary. My criticism is not of the shield's use but of whether technical work is happening behind it — and there is no public evidence either way.

Third, and most important: I am operating on an assumption that may be wrong — that a return to domestic first-class cricket signals technical repair. It may simply be a formality, a PCB image exercise about "valuing domestic cricket," or a way to satisfy central-contract conditions. If so, the four innings mean nothing — neither good nor bad. I have treated it as a conscious technical reset, but that is inference, not fact. And I should state it plainly: first-class cricket is not a firm, and Babar is not an employee. Central contracts in Pakistan cricket arrived after 2026, and the labour-market framework that preceded them does not apply to Babar's case. Babar has no union, but he has a marquee brand — and a brand holds different bargaining power from a worker. That gap is the limit of my entire analysis.

Takeaway: What to Watch After 31 October

When the tri-series ends, the Pakistani media will look at one number — Babar's total runs. I will look at three different numbers. First: his strike rate against Sri Lankan spinners, because that is the real examination. Second: his mode of dismissal — if he is caught outside off stump, the technical problem persists regardless of run count. Third: his first two innings in the next Test series, because batting on a flat domestic pitch and batting on a green overseas pitch are two different careers for the same player.

Shaheen called Babar the "backbone." The defining feature of a backbone is that it is invisible — its function only becomes apparent when it weakens. Over the next six months, Pakistan cricket will learn whether this backbone is currently strong or merely in need of support. And when that answer arrives, it will not be written in a press conference. It will be written in a scorecard.