The Rawalpindi Silence: Shaheen's 'Backbone' and the Distance to Babar's Scorecard

The press conference room at Rawalpindi Cricket Stadium makes a particular sound in an October afternoon. The old air-conditioner grumbles in its own rhythm, the plastic chairs creak every time someone shifts, and there is that faint rasp of a finger across a microphone grille that is identical in every board's media room on earth. I have kept a sound log at every ground for the past few years — the exact length of the hush before the first ball, the first noise after a wicket, and the pause between a question and its answer. The biggest event in that room that afternoon went undrafted. It was two seconds of silence.

The question was direct and it had earned its place: is Babar Azam under pressure? Shaheen Shah Afridi looked at the microphone, then at the glass of water on the table, then said there is no pressure, that Babar is the backbone of Pakistan cricket. The answer was as clean as anyone expects from a captain. But that pause — that pause belonged to a man who knows the scorecard is already open on every phone in the room.

The shape of the tri-series

The matter at hand is a home ODI tri-series running from 18 to 31 October, with England and Sri Lanka as the other two sides. It is a 50-over tournament on Pakistani soil, and its first important fact is this: the numbers on which the entire debate rests do not belong to that format. Babar's Test and first-class figures were present in the room; the tri-series format was not. That gap is the centre of the story.

There is a second structure attached to it, and it has been under-covered — split captaincy. Shaheen Shah Afridi holds the white-ball command; Babar was reinstated as Test captain in July. Two captains, two separate accountabilities, and a player whose red-ball form is being questioned by a captain who does not captain him in that format. When a player's failure in one format is defended by the captain of another, the defence is always worth a little less than it sounds.

Three scorecards, one name

The first scorecard is red-ball. Against England in the Test series Babar made 97 runs at 24.25. It is the series in which he missed the opening Test through injury. For a batsman who was handed the Test captaincy again during that same period, 24.25 is not a statistic; it is a political problem.

The second scorecard is domestic first-class. Playing for OGDCL in the President's Trophy, he made 58 runs in four innings across two matches, an average of 14.5. It was his return to first-class cricket after roughly nine years — the move a batsman makes when he believes the fault lies in technique, or confidence, or both.

The third scorecard is white-ball. Against Australia in the home ODI series he made 125 runs at 41.66 and Pakistan won the series 2-1. He was his side's leading run-getter.

That is the real finding: form divided by format. Babar's red-ball numbers are unambiguously poor; his ODI output remains serviceable. Shaheen's sentence is a defensible white-ball endorsement and an indefensible red-ball claim. The captain who said it was captaining in the correct format — and that is the truest thing about the press conference, and the part no headline carried.

The size of the sample: four innings

An honest pause is required here. Declaring the decline of a 31-year-old batsman on the basis of four innings is like writing a weather forecast after three minutes of rain. The President's Trophy chapter is a signal of a technical reset, not proof of anything. Those presenting 14.5 as evidence of collapse are making the same error as those treating 41.66 as evidence of rebirth. Both samples are small; both conclusions are large.

What matters is not the size of the sample but its direction. The England Tests and the first-class return point the same way. When two different stages, two different bowling attacks and two different sets of conditions produce the same result, calling it coincidence becomes difficult.

The number nobody gave

The most important information in this debate is missing: dismissal modes. How many lbw, how many caught, how many bowled? What are the splits against pace and against spin? That is the diagnostic that separates a technical fault from a confidence dip. A habit of playing from the front foot, hands reaching outside off stump, or simple shot-selection pressure — each has a different cure. The available information contains no such breakdown, so claiming access to the technical root would be dishonest. As a reporter, I will say this much: that data should be published, because without it every analysis is a guess wearing a suit.

Accounting for the injury

Babar missed the opening Test against England through injury. It is the least weighed fact in the argument and possibly the most important. A batsman returning from injury always plays a rust-tinged first stretch — footwork half a step slow, timing half a ball late. I watched India's 36 all out at the Adelaide Oval in December 2026 — Hazlewood 5/8, Cummins 4/21 — and what that night taught me is that a collapse should be written as acoustics, not statistics. By the same logic, the numbers of a batsman back from injury should be read with the sound of rust alongside them, not the number alone.

The Rawalpindi surface: a hidden gift

The press conference was held at Rawalpindi Cricket Stadium, and that detail is not decoration. Rawalpindi's pitch has historically been a batsman's friend — flat, quick outfield, and a ruthlessness for bowlers in which 350 looks ordinary. On such a surface the statistical risk of dismissal for a top-order batsman falls. Which means that if Babar piles up runs in the tri-series, it will not prove that his red-ball problem is solved. That is the trap the entire cricket media can fall into at once.

The age question

Thirty-one is the maturing phase of a batting career, not the declining one. It is therefore reasonable to read the current trough as form or mentality rather than age. That is good news — form returns. But form returns on one condition: that the problem is acknowledged as a problem. The day a captain's defence turns into a denial, the clock on the repair starts running backwards.

The real contest of the tri-series

Sri Lanka are a spin-dominant side, and Pakistan's top order is the one whose anchor is under scrutiny. Babar's white-ball technique against the turning ball is the genuine examination, and it will look least difficult on a flat Rawalpindi deck — which is itself a warning. On the other side is England, one of the fastest white-ball batting units in the world. England's tempo will press Pakistan's bowling, and if the anchor starts slowly, that pressure doubles on the scoreboard.

The contrarian angle: 'backbone' is a press-box word

In five decades I have heard any number of captains use that exact word about their most embattled colleague. Backbone means nothing in cricket; it is a management word whose job is to change the ground of the question rather than answer it. The real question was never how important Babar is to the team — that is universally known. The real question was whether his selection is being made on performance or on reputation. The word backbone does not answer that.

The second contrarian point: cross-format contamination. The biggest strategic hazard is that ODI runs made on flat home pitches get read as Test readiness. If Babar averages 60-odd in the tri-series and then returns to 20-25 in Tests, the system will profess surprise when the signals were already there. There is a finer point too: Test accountability and white-ball accountability arrive through different doors. Red-ball failure will be answered by the captain who is himself the batsman; white-ball failure will be answered by Shaheen. That structure leaves unclear whether the two formats' failures will be reconciled in one ledger.

Credit where it is due

It is easy to say Pakistani cricket media is emotional. But the reporters in that room asked exactly the question that needed asking — the pressure question. The data desks in Karachi and Lahore have been taking format splits seriously for several years now, and the Urdu commentary tradition carried this game to an audience that never had an English newspaper. I remember the Hyderabad night in 2026, watching Krunal Pandya make 47 while thirty metres away Hardik sat utterly still on the dugout rail. I did not need an English feed to understand that stillness; the commentary that explained it was in a local language. The old press box remembers what the new feed forgets — and that applies to Pakistani cricket journalism too.

What actually needs watching

In the tri-series I care less about Babar's run tally than about how he gets out, if he does. His footwork against spin, his shot selection against pace, his level of calm in the first ten balls. If he makes 90 on a flat Rawalpindi pitch and then offers a catch outside off stump in the next Test, the tri-series will have meant nothing. I came for the match and stayed for the people who carry it home — in this case, the analysts who count the deliveries behind the scorecard.

Looking forward

If the selection committee and the captain are both proceeding on the belief that one good home ODI series is a cure for Test form, they may pay for it within six months. The column lost its paper, but the story found a louder room — and in that room the question now echoing is on what basis Pakistan chooses its backbone: performance, or the reassurance spoken at a press conference. The answer will not be in a scorecard after 31 October. It will be in the selection made in November.