Forty-Three Percent Dot Balls in Sharjah, and a Captaincy Silence Outside the Room

At twenty past six in the morning, the hose at the north-west corner of the Sharjah Cricket Stadium is left running. Nobody comes to close it for twenty minutes. The water keeps falling on a strip of outfield where no fielder will stand that day. Four people are there — a groundsman, two daily-wage labourers, and the man who drives the roller, whose name appears on no scorecard.

This is the ground where Afghanistan and Zimbabwe begin a T20I series on 27 October. And this is the city from which, last week, in a closed room, I read Jonathan Pybus's long interview — the one whose headline promised dot balls and strike rates, and roughly half of which was about something else entirely.

The number arrives in the third paragraph, with no introduction: over the past year, Afghanistan's dot-ball percentage is 43, their strike rate 136.4. Which series? Which grounds? Against which attacks? None of it is stated. In a piece about a technical problem, the technical foundation is the weakest link — and that is not an accident.

The dot-ball question was asked. What came back was not a bowling plan or a batting map. It was administrative language — the language that turns defeat into "data acquisition", and the language that gently installs a new captaincy. The 43 percent sits above the piece, in the headline. It does not sit at its centre.

Afghanistan's T20 side is in an awkward place. A team that reached the semi-final of the 2026 T20 World Cup is no longer a team anyone calls emerging. It has proved it owns two of the world's best spinners and, on certain nights, one of the world's least frightened batting line-ups. But knocking on a semi-final door once is one thing; knocking on it every cycle is another. And the second job is done with rotation, not with shots.

Playing at home in Sharjah means playing on the pitch the roller was pressing at six in the morning. The ground is small — boundaries around 65 metres — the bounce is flat, and evening dew is heavy enough that a spinner wipes his hand before he can read his own delivery. On this ground, 136.4 is not acceptable under any reading. Here a dot ball is not a condition. It is a choice, or a miss.

Afghanistan played three T20Is against India in the past few months and lost all three. Pybus called them "benchmarking" — the exercise of standing in front of a bigger side to measure where you are. In his words, a better gift could not have been received as a coach. From a desk in Mumbai that sentence sounds cheap; from a coach's mouth, on the Monday after, it is a considered strategy.

But benchmarking has a rule this statement left out: you also report what the benchmark told you. Three matches, three defeats, and the lesson is that "strengths and weaknesses both came to the surface" — a sentence that means the same thing read backwards. And the 43 percent does not mean Afghanistan bat slowly. It means something far more specific, and I think it is the real technical story here.

Look at the arithmetic. In a 120-ball innings, 43 percent means roughly 52 balls on which not a single run is scored. Around two-fifths of the innings is removed from the business of scoring. And yet the team's strike rate is 136.4 — meaning the remaining 68 balls produced about 163 runs. There is only one conclusion: Afghanistan's runs come, but not in sequence — in clusters. Twenty-eight in two overs, then nineteen in four. That is not slow batting. It is swinging batting.

You do not need an analytics dashboard to see it; you need to have sat in that ground. I have watched matches in Sharjah for years, and you can identify the state of an innings by a particular sound. When a side is taking singles, the ground carries a low, continuous hum — the scorer's pen, the crowd's muttering, the keeper's gloves. When a side is waiting only for fours and sixes, that hum dies. The stadium is still there; only the crowd has become a rumour. Forty-three percent of dot balls is that silence, written as a number.

On a ground this small the problem doubles, because the opposing bowler has nothing to fear. He must only hit a line and set his field. If you do not rotate strike, the short boundary stops working for you and starts working for him, because he knows that if one big shot is missed, five balls will quietly disappear.

Return to the interview. Asked about technical improvement, Pybus said batting and its nuances must be developed. It is a true sentence and a useless one. No target is named — not 43 percent down to 36, not singles, not strike rotation through the middle. No comparison is offered — where the rest of the world sits. When a coach answers a technical question with a defence of his captain, you suspect the technical question was never really asked.

Because the interview's real subject, judging by its length, was the captaincy. Pybus called Ibrahim Zadran's appointment a baptism of fire — a lovely phrase that converts every poor performance into a rite of passage. Ibrahim's batting returns were not coming, and the defence was that he is the team's leader and cannot be judged on runs alone.

This is where the piece cracks, and I think the crack is its most honest feature. The reporter wrote, in his own voice, that Rahmat Shah impressed while Ibrahim Zadran did not impress with his batting returns. That line belongs to no source. It is the writer's assessment, and it collides head-on with the defence the coach mounted in the same piece. Pybus's case rests not on measurable performance but on unmeasurable leadership — and unmeasurable things stay unmeasurable forever.

Rashid Khan enters the interview the way a door is opened, glanced through and shut. The report says there had been speculation that Rashid was unhappy. That sentence is attached to no named source, and Rashid's direct comment appears nowhere in the piece. Pybus called him a model professional who holds nothing back, and described a close relationship between the two captains.

Here I want to name a habit of my own trade, because I have fallen into it. Journalism collapses three different things into one verb: refused to answer, was never asked, and no access granted. On Rashid's discontent we know only that the coach dismissed suggestions. We do not know who raised them, on what evidence, or whether Rashid was asked what he thought. Rashid's silence is not evidence here. It is silence. And in a room where the questioner and the respondent are sitting together, treating silence as evidence is the easiest and most wrong thing you can do.

I should say plainly that I was not in that room. I was not four hours away in Dubai; I was in Sharjah, and still not in the room. I read the piece on a screen after a night shift, and I do not have the recording that would tell me whether Rashid was raised by the interviewer or volunteered by the coach. I learned the night shift by listening to what the building refused to say — but refusal and absence are different documents, and what we have here is absence.

So what is the real story? Not 43 percent. The real story is that a technical crisis was converted into a leadership conversation, and the purpose of that conversation was atmosphere, not performance. That is not wrong — every new captain needs installing, and in a side like Afghanistan, where captaincy has always been an emotional question, it is necessary. But if you are going to Sharjah on 27 October to find out whether the dot balls fell, this report will not tell you, because it was never built to ask.

My second, less comfortable suspicion is that the 43 percent is not a habit but a structure. Afghanistan's middle order is made of players comfortable lifting the ball and uncomfortable pushing it for one. That is selection, not mentality. And you cannot change a dot-ball percentage without changing selection; you can only disguise it. A team that can make 20 in an over and then 6 in the next two is very easy to beat in a knockout: take away three big shots and the rest of the match belongs to you.

Which is why the baptism-of-fire language is the weakest link. A baptism happens once. Not a season, not a year. When every bad innings becomes a rite of passage, no evaluation date survives. In a captain's first months that is fair; in his second year it becomes an excuse. Afghanistan cannot afford the luxury. Their T20 calendar is thin, their players spend months in franchise leagues, and every assembly is an audition.

That is what makes the Zimbabwe series interesting: it is the series where the excuse does not travel. A loss to India can be called benchmarking. What do you call a loss to Zimbabwe in Sharjah? Pybus will have an answer, and it will be a good answer. The question is whether a good answer improves a scorecard.

One more thing is missing from this debate: the bowling. Afghanistan's strength has always been spin, and Sharjah's dew blunts it every evening. If part of the 43 percent problem is that opponents have begun playing Afghanistan's spinners the same way — singles, no risk — then the conversation is not only about batting. It cuts both ways, and the interview only looked at one.

On the morning of 27 October I will be in that corner again. Six o'clock, the same hose. I will not be counting Afghanistan's runs. I will count the balls in the first six overs on which the batter did nothing, and then the balls between the seventh and the fifteenth on which he declined to run one. Because the pitch remembers footsteps longer than it remembers names, and this team has not yet decided what kind of footsteps it wants to leave on Sharjah — those of fear, or those of running.

That answer will not arrive at a press conference. It is not with the man on the roller either. It exists only in those 120 balls, and none of us will be in the room.