Seven Wins in Sharjah, and a Question That Runs Past the Scoreline

Five days, three matches, one venue — Sharjah. Afghanistan beat Zimbabwe by 158 runs, Bangladesh by seven wickets, and then Zimbabwe again by seven wickets in the final. Three wins, three different scorelines, and one thing missing from all of them: the panic that forces a side to spend the last ten overs fighting its own scorecard.

Richard Pybus did not mention the 158-run margin after the final. He stopped on the word responsibility — players taking ownership of their position, not leaving it to someone else to come in and pick up the pieces. The scoreline tells you who won. That sentence tells you whether the winning holds.

One trophy, three different scorelines

The structure of the tri-series was simple: Afghanistan, Bangladesh and Zimbabwe, every match in Sharjah, and Afghanistan unbeaten through the group stage. Pybus framed the trophy as the next link in a chain rather than an isolated result — a positive series in Ireland, then the Test in which Rahmat Shah made a century and a fifty while Sediqullah Atal's innings took the headlines, and now this.

His real agenda was visible in the wording: build a side that adapts to conditions, build depth so that players turn up and put in performances when the chance arrives. He said one thing that carries this entire piece — Afghanistan do not get the quality of opportunity against the top full-member sides that development demands. That is not a coach complaining. It is a statement about a calendar that moves slower than the team's capacity.

The captaincy picture comes from the same briefing. Since taking the ODI job from Hashmatullah Shahidi, Rahmat Shah has played seven and won seven. Pybus described quiet authority — calm, assured, inclusive, a captain who listens to senior players and demands participation in planning, preparation and performance. He added the part that captaincy debates usually skip: a captain has to carry that responsibility with the bat, and Rahmat has been exceptional at it.

When I was cut from Maharashtra's Under-16 probables list at sixteen after the Gahunje trial, the lesson was not technical. It was that opportunity and ability are two different variables, and that anyone with fewer opportunities has to have every number read twice. The same rule applies to seven straight ODI wins.

Trying to measure "responsibility"

I built the database before I ever trusted the eye test, so the first job is converting Pybus's word into a measurement. Call it bail-out dependency: how often in an innings the last four batters have to cover for the top order's failure. That number tells you whether a team is winning or surviving on somebody's innings.

The three wins are unusually clean on this measure. Twice Afghanistan reached the target with seven wickets in hand, which means a large chunk of the middle order never batted. In the 158-run match the top order did what its role demands. Across all three, the side never needed a rescue innings. In nine years of watching, that is the signal I trust more than any margin: not the size of the win, the architecture of it.

Three matches in five days measures something else. One side fielded roughly 150 overs across the series — fifty per match — in Sharjah heat and humidity, where evening dew changes how the pitch behaves. For a spin-led attack this is the real test, because the main weapons bowl long spells and their drift is decided in the third spell. A Russian summer taught me that tournaments are lost in the third week, when the opening enthusiasm has gone and the body is still working. Three matches in five days is that week in miniature.

Edgbaston day four is where I learned to hear the signal under the noise, when the real question inside Kohli's 149 and 51 was how England's fourth-stump line kept colliding with India's front-foot trigger. In Sharjah the noise is a 158-run win. The signal is that across three different match states the team made the same kind of decision, and that the captain carried the responsibility with the bat that his coach keeps talking about. A captain's runs pay twice: once on the scoreboard, once as a message that he holds first claim on the burden. A coach sees the error; a commentator sells it. I try to do the first.

A limitation belongs here. I do not have ball-by-ball data for this series — no field-placement log, no record of bowling changes through the middle overs. What I have is the scoreline, the shape of the attack and the coach's briefing. So the analysis is a hypothesis, not a verdict. What the data cannot see — injury, temperament, selection politics, dressing-room information — I will not fill in with guesswork.

Where the scoreline goes quiet

Seven wins in a row is a fine number, but a number is only worth its sample. Three things are constant in this sample: the venue is the UAE, the surface is slow and grippy, and the opponents are Zimbabwe and Bangladesh. It is the sample in which Afghanistan's strengths show fastest and its weaknesses hide most easily.

Adaptability is tested on quick, bouncing pitches, where swing takes wickets in the first ten overs and spin has to be flown over the infield. Read Pybus's own line backwards: if the opportunities against the top sides do not arrive, the validity of seven wins is never tested either. The number does not prove the team is better. It proves the team did nothing wrong with the sample it was given.

Reflexive denial would be just as wrong. The streak need not be purely a conditions artefact. Role clarity is a real asset and it travels — its effect simply shrinks on a quick pitch rather than vanishing. One run at Gahunje is still the cleanest proof that systems fail late, and system failure shows up in repetition, not in the scoreline. The repetition here is that no innings needed rescuing. That comes from habit, not from weather.

Where the next test sits

For anyone reading Afghanistan's next scorecard, three things are worth watching: the first ODI outside the UAE, the score at the 30th over in a chase, and wickets lost between overs eleven and thirty. If those hold, seven wins were not just a season. Seven wins are a good story. The real question is who this team hands the responsibility to on the day the surface stops helping.