43% Dots and a 136.4 Strike Rate: Afghanistan's Problem Is Not the Dot Balls, It Is How They Are Distributed

Sharjah at six in the evening: the heat still pressing down, the scoreboard moving as if someone forgot to turn a dial back down. From October 27, Afghanistan begin a T20 series against Zimbabwe at exactly this venue. For four days I have been opening the ledger of Afghanistan's last twelve months of T20 batting, and the same two numbers keep returning — a 43 percent dot-ball rate and a strike rate of 136.4.

Both numbers were put on the record by head coach Pybus in his interview with Cricbuzz. That is to his credit; he did not bury the figure, he placed it on the table. But something else happened in that conversation. Two paragraphs went to dot balls and strike rate. Roughly half the interview went to captaincy politics. A 3-0 defeat to India was relabelled "benchmarking." Ibrahim Zadran's batting returns as captain were wrapped in the phrase "baptism of fire." And the speculation about Rashid Khan's unhappiness was created and extinguished inside the same passage.

So the question I keep coming back to is simple: if dot balls are the real problem, why did half the interview go somewhere else?

Context: a team at war with its own identity

Afghanistan's T20 side has stood in an awkward place for several seasons. Spin is their currency and the currency holds. But the direction T20 batting has travelled — powerplay aggression, a middle-overs singles machine, controlled risk at the death — is a direction their batting structure never fully took. They still bat like a team that believes 160 will be defended, and often it is. Against an attack and batting line-up like India's, 160 stops being enough and the fractures show.

The 3-0 defeat was the fracture. Pybus did not call it a defeat; he called it a benchmark, a reference point against which you discover your true length. In his words, no better gift could have arrived for a coach. There is a real argument in that sentence and it is not wrong. In my own decades on this beat I have seen three matches against a strong side teach more than six wins against weak ones.

The trouble is not the argument. It is the silence after it. Benchmarking implies you measured something. A year of 43 percent dots and 136.4 was measured — that much we know. What the India series measured never arrived in a single sentence. "Strengths and weaknesses" is not technical analysis; it is press-conference upholstery.

Meanwhile a quieter thing was happening that got less room: the captaincy handover from Rashid Khan to Ibrahim Zadran. When it happened, on what reasoning, decided by whom — none of it was ever stated plainly in public. When that kind of silence sits over a decision, speculation fills the space, and then the coach has to pick the speculation up himself and deny it. That is exactly what happened here.

Core: the arithmetic of 43 and 136.4

A ball-by-ball record is a biography of the game, not a highlight reel. So I stop looking at the two numbers separately and place them inside one innings.

Take 120 balls at a strike rate of 136.4. That is roughly 163.7 runs. In the same innings, 43 percent dots means about 51.6 balls on which nothing was scored. That leaves 68.4 balls. Those 68.4 deliveries produced 163.7 runs — about 2.39 runs per scoring ball.

That number tells the whole story. A rate of 2.39 runs per scoring delivery means Afghanistan's innings is not being built on rotation; it is being carried by boundaries. While the fours and sixes arrive, the strike rate looks fine. The moment they stop, the dot balls are still there with nothing to absorb them. A 43 percent dot rate is survivable only if the boundary rate on the other 57 percent stays abnormally high. That rate is not durable, because it depends on the ground, the quality of the bowling and the day's conditions — not on the batsman's method.

This is where the India series becomes legible. India's bowlers did what a good data desk would have flagged in advance: they suppressed the boundary rate and left the dot balls untouched. The result was exactly what the arithmetic predicts — the dots stayed, the runs vanished.

Now take the fix everyone agrees on: bring dots from 43 to 35 percent. That is about 9.6 extra scoring balls per innings. At the same 2.39 runs per ball, the total rises by roughly 23 runs. On paper it is beautiful. On grass it happens only if the boundary rate survives on those extra deliveries.

The danger is right there. The easiest way to cut dot balls is to convert them into singles — and for this team, a single is a far more expensive purchase than a boundary. Turn 9.6 dots into nine singles and you have added nine runs while forgoing roughly 23, because those deliveries are no longer available for boundaries and they were played under risk besides. The dot percentage improves. The strike rate falls. The metric wins; the match is lost.

So the real question is not how many dots. It is where the dots fall. Dots in the powerplay are lost balls, because the field is up and boundary probability is at its peak. Dots in the seventeenth and eighteenth overs are mortal wounds. And dots between overs seven and fifteen against spin are the deepest structural weakness, because that is where the engine of an innings runs. None of that distribution exists in the available account, and that is the largest gap in the story.

Sharjah's flattery: when the ground rewrites the metric

Sharjah can break this arithmetic, and that is the trap. Short boundaries, a flat deck, the ball coming nicely onto the bat. Here a strike rate of 136.4 does not look poor; it looks average. That same 43 percent could read 38 by the end of the series without a single batsman changing his method — the ground simply provided the subsidy.

In 2026, when COVID pushed the IPL into empty stadiums in the UAE, I ran an audit of all sixty matches and found powerplay scoring up by 0.42 runs per over against the previous season, with the same players and the same laws. I wrote a short "no-crowd adjustment" note for the desk warning that a changed environment, not just talent, shifts the baseline. Sharjah is the second edition of that principle. The model does not predict the future; it exposes the present — and the present here is that good numbers against Zimbabwe will not prove the method changed.

The only remedy is to stop reading aggregate strike rate after the series and start reading dot percentage against spin between overs seven and fifteen. That number does not live in Sharjah. It lives in the batsman's head.

Ibrahim Zadran: a sample too small to hold an opinion

The interview contains one moment of authorial friction. The writer states plainly that Rahmat Shah impressed, and that Ibrahim Zadran did not impress with his batting returns. That is nobody's quote; it is the writer's own assessment, and it is the most analytically useful line in the piece.

Because what follows is a full defensive block from the coach, built on the baptism-of-fire trope. The trope is elegant. The trope does not measure.

In T20, innings-to-innings variance for a batter is so high that across fifteen or twenty innings, a swing of ten to twelve strike-rate points sits inside the noise band rather than the signal. Captaincy does affect batting — I do not deny the mechanism. Extra tactical load, a shift in batting position, a change in the responsibility of an innings, and sometimes a reduced appetite for risk. But proving that mechanism requires a different dataset than total runs and overall strike rate.

What should be measured: balls faced per innings (has it dropped?), stability of batting position (has he been shuffled?), phase-wise strike rate (powerplay, middle, death), and modes of dismissal (is he rushing under new responsibility?). Not one of those numbers appears.

So the link between captaincy and form is not established here. What is established is that the coach reached for sentiment where an argument was available, and the interviewer did not press. Correlation is not causation, and a metaphor is not data.

Rahmat Shah: the exact profile the team says it is worried about

Here is a contradiction nobody raised. The stated goal is fewer dots and a higher strike rate. The most praised batsman was Rahmat Shah, whose game is built on slow starts, high dot tolerance and the art of leaving the ball.

That is not an error. It is a selection, and selections have logic: hold one end so the other can attack. But if the structure rests on an anchor, then a large share of that 43 percent is structural, not defective. In which case the coach's line about developing "the nuances of batting" actually means either changing the philosophy or changing the anchor — and neither was named.

The selection philosophy and the declared metric are in conflict. That conflict can be hidden; it cannot be erased. Until it is clear which role may absorb dots and which may not, any dot-ball improvement programme runs half-finished.

Rashid Khan: praise inflation

The most delicate passage in the interview. The talk of Rashid's discontent arrives with no source at all — recorded in the text as "there had been speculation," no name, no date, no basis. And then it is extinguished in the same breath: a model professional, one of Afghanistan's best across all three formats, a man who holds nothing back.

I recognise the form. When three superlatives about a player land inside one paragraph, that is not praise; it is a statement issued on behalf of an institution. It is positive, so it offends nobody. But it conceals a fact: Rashid Khan was never asked directly. The central figure of the most discussed transition in Afghan cricket has not been given a sentence.

I have a measure for spinners that I apply without exception: which phase the overs came in, against which batsman, and how many overs were left. If the captaincy change altered the distribution of Rashid's overs — fewer in the powerplay, more at the death, or the reverse — that is the hardest available evidence that the handover touched the cricket itself. That data exists and is public. It went unasked and unanswered.

A captaincy change shows up first in the role of the man who lost it. Measuring that is cheaper than investigating a rumour. Nobody did either.

Contrarian: three places the interview escaped the real question

First, the word benchmarking. It is a beautiful word because defeat hides inside it as process. But benchmarking means you measured something and now hold a list. Where is the list? Which phase came out weakest? Against which bowling type was the dot rate worst? What was the powerplay strike rate against pace? None of it arrived. When a coach says "we learned a lot" and cannot say what, the sentence is not information; it is armour.

Second, the speculation created so it could be killed. In journalism this is the straw man: build a phantom opponent, knock it down, hand the protagonist a win. That is not a good interview; it is good hospitality. If there was a basis for the talk about Rashid, it belonged in front of the reader so the reader could weigh the denial. If there was no basis, it did not need raising.

Third, and largest, the numbers arrive unsourced. Forty-three percent and 136.4 — over what period, across how many innings, against which oppositions? Not stated. In 2026, building a ball-by-ball template for a Bengaluru digital desk, I made phase data a precondition of every match report. I built the template before the first ball was bowled, and it had one rule: a claim that cannot be tied to a phase or a rate gets cut. There is no phase expansion of 43 and 136.4 here. That does not make them wrong. It makes them uncheckable, and an uncheckable number is not an argument; it is an assertion of good faith.

This is my old quarrel, now with a new front. The data desk won the tactical argument years ago; television was the last holdout. What has changed is that analysts now walk into dressing rooms, and their conclusions detach from the actual rhythm of the match. Dot-ball percentage is a good measure. Is it as good on Sharjah's short square boundaries? Probably not. A side with Rashid and that class of spin can win at 155 rather than 165 if it bowls 38 percent dots instead of 43. We have fallen into evaluating bowling through a batting metric, and that habit is most expensive for teams like Afghanistan.

Takeaway: what to watch in the Zimbabwe series

Afghanistan will likely post big totals in Sharjah. The scoreboard will be read as evidence that the problem is solved. I will not be reading the scoreboard. I will watch one number — dot percentage against spin between overs seven and fifteen. If that number does not drop below 40 on Sharjah's short boundaries, then even 180 is not improvement. It is weather.

The ledger never lies, but the stadium tells a different story — and right now Sharjah's stadium is in a position to tell the sweetest lie of all. The question is whether the coach believes it, or puts that 43 percent on the table the way he did this time.