Two Captains, Two Identities: The Verdict on Babar, Shaheen and Salman in Pakistan's White-Ball Reset Ledger

Two Captains, Two Identities: The Verdict on Babar, Shaheen and Salman in Pakistan's White-Ball Reset Ledger Hook: The announcement that left out the year Rawalpindi Cricket Stadium. 9, 11 and 13 October — three T20Is. Then a seven-match ODI tri-series, with the first three games also at Rawalpindi and the remainder of the league stage plus the final in Lahore. The Pakistan Cricket Board's release had venues, it had dates, it had two separate squads of twenty names, and it had two captains. It was missing only one thing — the year. Nowhere does the announcement state which year 9 October belongs to. The ODI tri-series dates are omitted entirely. A squad announcement often speaks loudest through its own gaps. Which fact it gives, and which it forgets to give — that is the real clue. Here there are T20I dates but no ODI timeline. There is no year. This document is not a chronicle; it is a declaration of intent. And in a declaration of intent, the most telling reading comes not from who is named, but from who is left out. I do not count checks to find blame. I count them to find patterns. And the pattern here is brutally clear: Pakistan is now running two separate white-ball teams at once — two different captains, two different philosophies, two different futures. What nobody is quite saying yet is that this two-track architecture is not a plan. It is a compromise. And a compromise is always judged on the results table, never in the press release. Context: T20I and ODI are both white-ball, but they are not the same T20I and ODI are both white-ball, both limited-overs, yet their internal logic is entirely different. T20I cricket runs on the powerplay, the middle overs and the death overs — every decision compressed into twenty overs. ODI cricket runs on two new balls, spin control through the middle, and acceleration in the final ten. One format's success cannot explain another format's decision. This simple rule applies letter for letter to the PCB's latest announcement, because the two squads have been deliberately constructed apart. The PCB has named two lists. One for a three-match T20I series against Sri Lanka; another for a seven-match ODI tri-series involving Pakistan, England and Sri Lanka. The T20Is are at Rawalpindi, three in a row at a single venue. The first three ODI tri-series matches are also at Rawalpindi, with the remaining league games and the final in Lahore. So the T20I series is locked to one venue, while the ODI tournament is spread across two. A seven-match tri-series means each side plays at least three league games and then a final. A final means knockout-adjacent pressure — a different psychological test from a bilateral T20I series. A structural difference stands out. Three T20Is at one venue means a stable pitch character; a two-venue ODI tournament means a pitch-condition variable enters between the Rawalpindi leg and the Lahore leg. A side built for Rawalpindi's pace and bounce that cannot adjust to Lahore's slower, spin-friendlier surface will stumble at the business end. That variable is this tri-series' hidden examination. One admission up front: this is a squad announcement, a pre-match document. Not a single ball has been bowled. No phase data, no result-versus-process verification is possible. What is possible is to test the logic of the decisions — who came in, who went out, and why. And that logic tells me more about the true state of Pakistan's white-ball setup than any scorecard could right now. Core: Opening the two-track architecture ledger Watching matches year after year, I have learned one thing — you cannot read a team's strength from its squad names, but you can read its philosophy from its squad structure. In this Pakistan announcement the philosophy is split in two. On one side the ODI squad holds Babar Azam, Fakhar Zaman, Salman Ali Agha and Saim Ayub — a spine of experience. On the other, the T20I squad holds Sahibzada Farhan, Hasan Nawaz and Mohammad Imran Randhawa — a rebuilt, almost inexperienced structure. The ODI side is still running on the old anchor-reliant model; the T20I side has already entered a power-hitting rebuild. At the centre of this split is the captaincy question. In the ODI squad, Shaheen Shah Afridi survives as captain; in the T20I squad, he is absent. The T20I captaincy has gone to Sahibzada Farhan. Salman Ali Agha was removed as T20I captain and retained only in the ODI squad. Pakistan has effectively divided white-ball leadership by format. That can be a legitimate management choice, but it can equally be the beginning of tension inside a long captaincy ledger. History suggests that when two captains' results diverge, cracks in the dressing room rarely take long to appear. Farhan's captaincy: a small sample from the Asian Games Sahibzada Farhan is a right-handed opening batter, elevated to T20I captaincy on the back of leading Pakistan at the Asian Games. Here lies my first doubt. The Asian Games is not a full-strength cricket event — it is a multi-sport occasion where teams frequently send second-string squads. Reading a full T20I captain's credentials from leadership experience in that event is a weak predictive base. This does not make Farhan unqualified, but it does raise questions about the quality of the reasoning behind the leadership decision. I have no T20I strike rate, average or situational split for Farhan. No performance data was supplied. So on merit, I can neither endorse nor challenge the appointment. What I can do is read the trend. Elevating a T20I-specialist opener to captaincy means the selectors chose a deliberate reset, not continuity. An opener-captain leads from the front, but in T20I cricket, when an opener's performance pressure and leadership pressure arrive together, a small cameo sometimes pays the price for another's failure. The leap from a small Asian Games sample to the big stage — that leap is the risk in this appointment. Shaheen's double burden: ball in hand, band on arm Shaheen Shah Afridi is a left-arm new-ball swing bowler, retained as ODI captain. His value is most concentrated in the powerplay — new-ball swing, the left-arm angle, an opener's nightmare. But captaincy adds an extra layer of mental load onto a fast bowler's shoulders. When a frontline pacer becomes captain, he must think about field settings, bowling changes and his own spell selection all at once — precisely when his body is at its most fatigued. Shaheen's workload concern is nothing new. Pakistan's ODI attack rests largely on three frontline quicks — Shaheen, Naseem Shah and Haris Rauf. All three have long histories of injury. A seven-match tri-series, including a final, preceded by three T20Is — the calendar is dense. If these three are played without rotation, then by the tournament's back end Pakistan's greatest strength could become its greatest risk. I do not count checks to find blame; I count them to find patterns — and in Pakistan's injury ledger the pattern is long-standing. Babar's absence: a shift in T20I identity Babar Azam is in the ODI squad only, absent from the T20I squad. This is the loudest silent sentence in the announcement. Babar was long the face of Pakistan's white-ball batting, and now the T20I side is being rebuilt without its batting spine. In ODI, Babar's anchor profile — high average, moderate strike rate — is format-appropriate; but in the modern T20I template, that very profile is the centre of criticism, which is the reasonable explanation for his omission here. There is a subtle point that tends to get lost in the debate. If Babar's omission is purely down to a template-misaligned profile, then who fills that gap in the T20I side? Farhan, Fakhar, Saim Ayub, Hasan Nawaz — the senior experience in that list is thin. Removing a figurehead is easy, but whoever replaces him will feel the absence of that figurehead in the first few matches — especially under pressure. The absence of Babar, Mohammad Rizwan and Shaheen from the T20I squad points to a genuine rebuild, not cosmetic tinkering. But the price of a genuine rebuild is sometimes paid by losing a series. Razaullah: a white-ball ticket from one Test cameo Razaullah has received his maiden white-ball call-up, and the source says he impressed with his batting in the third Test against England. Here is my biggest structural objection. Projecting white-ball value from a single Test batting cameo is a cross-format projection — red-ball conditions and white-ball conditions are entirely different. In Test cricket you can take your time; in white-ball cricket you cannot. In red-ball cricket fields are set aggressively; in white-ball cricket defensively. Predicting one format from a small sample of another is exactly the kind of leap that is hard to support with evidence. I am not saying Razaullah is unworthy. I am saying the evidence offered for his worth is insufficient. He has been named in both squads — T20I and ODI — signalling the selectors see him as a multi-format asset. But writing a cricketer's white-ball future from one Test innings means keeping the sample size smaller than the decision size. That is exactly where the gap between public hype and real capability opens. In a seven-match tournament, that gap will show. Salman Ali Agha: evidence of a forced transition Salman Ali Agha, after being removed as T20I captain, was dropped from that format's squad entirely, though retained in the ODI squad. Removing a captain and then omitting him from that format altogether is a clear sign of a forced leadership handover, not routine rotation. His retention in the ODI squad confirms the decision is format-specific, which again reinforces the two-track identity theme. A timeline signal is hidden here. The source's phrasing — "left out after being removed as captain" — implies the captaincy change was decided before this announcement. The document we are seeing is the result of a final decision, not the start of a process. Keeping a captain in one format while dropping him from another sends a message: the leadership change is T20I-scoped, and probably performance- or style-driven. The question is how that message landed in the dressing room. The wicketkeeping uncertainty: two different calculations The ODI squad carries two wicketkeepers — Mohammad Ghori and the newly added Saad Baig — while the T20I squad carries one, Nafay. Meanwhile Usman Khan and Usman Tariq were omitted. Two different keeping calculations across two formats means the keeping slot is not settled — it is an open question the selectors want to test. The double omission of a keeper-batter like Usman Khan, previously a fan favourite, suggests the selectors are looking for a different balance behind the stumps. One keeper increases batting depth; two increase flexibility. Keeping one keeper in T20I is an aggressive choice — it prioritises batting depth; keeping two in ODI is a defensive one — it seeks safety. This small calculation, too, is part of the two-track philosophy. The four omitted pacers: form or workload? Four pacers from the Asian Games squad — Ali Raza, Mohammad Wasim Jr, Akif Javed and Ahmed Daniyal — have been left out. At a glance this looks like a form-based omission. But I would propose a different reading. Dropping four pacers at once while simultaneously retaining Shaheen, Naseem and Haris in the ODI squad may actually be a workload-protection signal dressed up as form-based selection. This explanation is not certain, but the structure points toward it. The reason is simple. On a dense calendar, if you want to protect your frontline pacers, you need a pool of alternative pacers — but that pool must be given experience. With the combined load of a seven-match tri-series and three T20Is, piling the whole burden on two or three pacers would be self-destructive. Selectors dropping four young pacers either have a conscious rotation plan, or are accumulating a workload risk — one of the two. Results will tell which. Venue and home advantage: unquantifiable, yet present The entire contest is on Pakistan's home soil — Rawalpindi and Lahore. Pakistan's home record is markedly stronger than its away record, a well-documented home-away gap in world cricket. But home advantage has a subtle dimension: it is not just the pitch, it is the crowd, the familiar environment, the night dew. Rawalpindi's surface has historically offered pace and bounce, favouring Pakistan's fast-bowling core. If Lahore's pitch turns spin-friendly, it may favour Sri Lanka's traditional strength. An October schedule means autumn conditions. Day-night matches can introduce dew that materially weakens the side bowling second. Dew is a silent killer — it influences the toss decision, ruins spinners' grip, and often makes second-innings batting easier. The source says nothing about this, so it is my analytical knowledge, not announcement fact, and it is pending verification. But anyone projecting this tri-series cannot ignore the dew variable. Contrarian angle: the story everyone is missing The natural reaction will be this — everyone writes about who dropped out, who came in. Babar absent from T20I, Shaheen absent from T20I, Salman losing the captaincy — these three headlines will dominate. But I would point in a different direction. The real story is not who was dropped; the real story is that the selectors have declared two squads as two different philosophies, yet there is no bridge between those two philosophies. Consider it. The ODI squad says: experience, anchors, consistency. The T20I squad says: youth, aggression, risk. If any player sits in both squads — Razaullah, Saim Ayub, Shadab Khan, Naseem Shah — he must step within a week into two completely different mental frameworks. When a player carries two philosophies' demands at once, his biggest opponent becomes his own internal doubt, not any opposition bowler. That doubt does not appear on the scoreboard, but it is felt in the fluctuation of the run rate. In my familiar territory I have seen this kind of situation — a decision framework where the rules are clear, but in application two philosophies blend. I began with a check ledger and ended with a question about who built that ledger. Here too. The question is not "why was Babar dropped"; the question is — on what logic did the PCB split one series into two philosophies while announcing no clear plan to reconcile them? The second contrarian reading concerns Razaullah. Everyone will be excited about him — a new face, a Test cameo, a white-ball call-up. But in my ledger, this is a risk warning. A hype built from one Test innings is exactly the kind of story where the gap between expectation and capability widens fastest — and Pakistan's fan base is as reactive when senior players are dropped as it is ruthless when a new player fails. Razaullah must play in the space between those two reactions. That is not his fault; it is the system's pressure. Takeaway: the question ahead I began with a 455-check ledger and ended with a question about the watchers. This announcement, too, has a ledger — a ledger of two captains, a ledger of two philosophies. The table is not written yet, because no ball has been bowled. But when it is written, it will not merely show match results — it will show whether the PCB could hold its own compromise together. My forward view is simple. If the T20I reset succeeds and the ODI side holds the trophy, the two-track architecture will go down in history as a bold plan. But if the T20I side stumbles and the ODI side loses the final, then today's announcement will be remembered as that captaincy-split decision that cut Pakistan's white-ball continuity in two. The question now sits before Pakistani fans: are you ready to accept two teams as two philosophies, or do you want to see one team return to one identity?