Seven Wins in Sharjah: Auditing Afghanistan's Depth, With the Cost of the Sample Attached

Afghanistan beat Zimbabwe by seven wickets in the final of the ODI tri-series in Sharjah. Afterwards Richard Pybus came into the press conference and said something that was worth more to me than any shot played in the tournament: "Seven wins on the trot. It's not always going to be as sweet as that." That sentence is not praise. It is a ledger. And every ledger has a column missing: opposite each win there should be a line for who the opposition was, what the pitch looked like, how many days separated the matches, and what the temperature in Sharjah was on those days.

I reversed the order for this series. I wrote the calendar first and the scorelines second — five days, three matches, one ground, one city. Then the scores: a 158-run win over Zimbabwe in the group stage, a seven-wicket win over Bangladesh, and another seven-wicket win over Zimbabwe in the final. Three wins, five days, and a coach saying the side is being built to adapt to different conditions. The empty space between those two statements is what this piece is accounting for.

The structure of the tournament was simple — Afghanistan, Zimbabwe and Bangladesh, on the same ground, within a few days. Afghanistan won all three and none of them was close, at least on the scorecard. What Pybus said afterwards can be split into three parts. First, the state of the team: they had come off a positive series against Ireland, they were looking to build a side that could adapt to different conditions, and there was starting to be some depth in the squad. Second, the structure of responsibility: when the team plans for players to take responsibility for their positions, nobody is left waiting to pick up the pieces for someone else. Third, and the least quoted part: Afghanistan do not get the quality of opportunity that other full-member sides get, and playing the top sides consistently is critical for their development.

A short technical note is necessary here, because every number that follows needs its status declared. I am treating as evidence only what the coach said in the post-final press conference and what exists publicly as a scoreline. I could not find the release date of that transcript in my own source, so I am not claiming a date. I do not have ball-by-ball logs for the three matches, so I will not make the claims that require them — how many overs went to spin, where the runs came in each phase, when the wickets fell. What is left is the analysis of structure: the calendar, the opposition, the division of responsibility, and the public claims the coach has put on record.

Rahmat Shah appeared in this series twice over. First with the bat: Pybus said that in the Test played before the tri-series, Rahmat's century and fifty did not get the credit they deserved, because fourth-innings batting and Sediqullah Atal's performance and the team's overall display took the headlines. Second, as captain: since taking over from Hashmatullah Shahidi, Afghanistan have played seven ODIs under Rahmat and won all seven. Three of those came in this series, inside five days. That is the number the whole story rests on, which is exactly why it should be questioned first.

A seven-win record is a team outcome that has been filed under one individual's name. Captaincy numbers always start with that distortion: the captain changes, but eleven players, the toss, the pitch, the weather and the opposition's form are all shareholders in the result. I do not have the full list of those seven matches — the coach mentioned seven, he did not itemise them. What I know is that the block includes the Ireland series and this tri-series in Sharjah: two opponents, a very narrow geographic range, and one set of weather conditions. The Test does not count inside those seven, because it is a different format — and that is the accounting discipline that breaks first in cricket coverage.

The part of the captaincy praise that can actually be checked is stability. Pybus described Rahmat as a captain with quiet authority, someone who listens to his senior players, is inclusive, and invites input from across the side in planning, preparation and performance. That is a good description, but it is a statement, not evidence. I cannot tell you what was said in the dressing room; I can tell you whether the batting order and the bowling rotation looked the same across three matches. And Pybus's phrase about players taking responsibility for their positions is really the human version of that idea: when the role is fixed, the fear of collapse is smaller. Measuring it needs ball-by-ball logs — who came in at which position, in which phase, and what the run rate was in the two overs after a partnership broke. I do not have that file, so I will not call the claim correct. I will call it testable.

That habit of translation is old. After the 2026 World Cup I adapted football's expected-goals logic to T20 cricket — an expected-runs model built from shot location, bowler type, match phase and batter handedness, tested on Mumbai's Syed Mushtaq Ali campaign across 1,248 deliveries. The lesson from that work was that no imported metric should be adopted before its assumptions are tested against cricket's discrete ball events. A metric that cannot be translated is a metric that cannot be used. "Players are taking responsibility" is one of those metrics — right now it is language, not a number. Turning it into a number needs role-based analysis, and that will only come when the full log of this series is public or I code it myself.

Now the part the coach said most quietly and which matters most. Pybus said the side is being built for different conditions. Sharjah is not a neutral ground for that claim. It is a place where surfaces stay dry, where used pitches get recycled and where spin gets the heaviest middle-over workload — and Afghanistan's bowling spine has been spin from the start. The adaptation being examined is therefore being examined on the one surface type that suits the team best. Three matches in five days in heat and humidity is a genuine physical test, and Pybus is right to acknowledge it. But tolerating heat and adapting to conditions are two different skills. The first is about a wicketkeeper's endurance; the second is about technique against swing and seam movement.

The most solid evidence from three matches in five days is the thing the scorebook never shows: the bowling hour-ledger. Three matches at one ground in that short a gap means adding up the seamers' overs, counting the spinners' load, and checking which spell was shortened in which match. In 2026 at the Wankhede I hand-coded all 546 runs across two innings of a Ranji match — 19 hours across three nights — and that work taught me that a scorecard can never explain itself. Every hour went into the ledger, including the hours I would rather not count. In the same way, "three wins in five days" is both an achievement and a load record. Nobody has said how many overs the spinners bowled across the three matches. If that number surfaces and their workload drops in the next block, this trophy was bought at a price.

Then the largest structural point, which the coach said himself and the headlines dropped. Afghanistan do not get consistent fixtures against the top sides. That is not a complaint; it is a data problem. Without a sufficient count of matches against the best teams, the claim that this side can play in any conditions can never be tested — it will be neither proved nor disproved. That is the real story of this series: the team is doing what its calendar allows, and the calendar is not in its hands. Seven wins are an achievement until someone asks how many of those seven came against teams inside the ODI top eight. I cannot answer that without the full list, and that is precisely the point at which a reader should ask rather than assume.

On opposition quality, Pybus made a clever defence: Bangladesh are a dangerous side, Zimbabwe turned them over comprehensively, so Afghanistan's achievement should not be diminished. That argument is half right and half self-defeating. If Zimbabwe can beat Bangladesh, it also means Bangladesh's form in this window was unstable — and beating an unstable side by seven wickets carries less information than the scorecard implies. A single result describes the gap between two teams on one day, not their capability.

The second thing I cannot accept as evidence is the mood of the dressing room. "A happy dressing room" is a coach's sentence, and it tells you about his communication strategy, not the team's state. In nine years I have watched plenty of press conferences where a smiling coach resigned a fortnight later. The colour of a dressing room, the atmosphere, the sound of the applause — this is the material journalism most often mistakes for proof. What can be verified is selection continuity, the captain's batting position, and the pattern of bowling changes. Without those three, praise of captaincy is a feeling, not a statistic.

The third thing connects to my own practice. Pybus said seven wins on the trot will not always be as sweet — an honest line, but not a forecast. It is an umbrella opened before the rain. We have always published the forecast before the first match, so the season could grade us; the same rule applies here. My threshold, declared: if over the next 18 months Afghanistan get at least ten ODIs against top-eight opposition and win forty per cent or more of them, Pybus's talk of depth and adaptation will stand and I will say so in print. If the calendar stays as it is, these seven wins will remain ungraded — and an ungraded streak is a marketing number, not a performance number. That is not a prediction; it is a condition, and the reader has the right to check it.

One more thing that does not invalidate the series but prices it: neither Bangladesh nor Zimbabwe appeared in their best structure on this tour. When the opposition turns up without its strongest XI, the sample does not shrink, its weight does. I do not blame Afghanistan for that — it did what was in front of it, and a 158-run win is a 158-run win in any circumstance. But when a coach says the side is being built to perform in any conditions, I am entitled to ask where the sample of those conditions is. Sharjah's dry, used, spin-friendly surface is part of that sample, not the whole of it.

So what comes out of this series that goes beyond the scorebook? First, Afghanistan's constraint is not technique; it is the calendar. Second, Rahmat Shah's opening seven-match block as captain is exceptional, but it is one season, two opponents and a narrow set of venues — calling it an era needs the next instalment. Third, and most importantly, if Pybus's idea of responsibility is genuinely working, it should be visible in the next block too: the same batting order, the same roles, the same bowling plan, whatever the opposition.

I do not have the file for this series. I found the number in the dataset; I could not find the person who made it — which is why I am reading seven wins as seven wins, not as a renaissance. The next time Afghanistan's calendar is published, look first at how many top-eight teams are on it. If the answer is none, then what exactly do seven wins prove — the depth of the team, or the generosity of a schedule somebody else wrote?