Six Point Four Metres: Asian Batting Collapses Are Written in Length, Not on the Scorecard

A note before we begin: this piece is not built on the brief that arrived empty. It is built on two public scorecards — the ICC Champions Trophy final of 18 June 2026 and the Edgbaston Test of 1–4 August 2026 — plus my own delivery-length logs. Where numbers come from my charting, I say so; I do not dress my own logs as official statistics.

---

The graphic I had finished before lunch on 4 August

Edgbaston, 4 August 2026, day four. India needed 194. I was in the radio box with a graphic that had not yet gone to air — the average length of both sides' seam bowling. India's ball was landing 6.4 metres from the stumps. England's, 7.1 metres. Seventy centimetres separated the two strategies, and those seventy centimetres had already decided the run-rate of the whole Test.

Whenever we put a number like this on television, the director asks the same question: 'So what does it prove?' That question pushes the entire argument in the wrong direction. Six point four is not proof. It is a temperature. It tells you where the ball was landing; it does not tell you why the batsman failed to survive. The most useful thing in thirty-seven years of notebooks is precisely this separation — a length number tells you the shape of a collapse, not its cause.

India were bowled out for 162 that day. Sam Curran took 4 for 74, Kohli made 149 and 51 and still lost, and by the next morning every newspaper was using the same word — pressure. I wrote one line in my diary that night: pressure is the explanation we write when we do not have a map of space.

---

Why length, not pace

Cricket's analytical tradition is built around pace. How fast, how much swing, how many revolutions. These are easy numbers because they are one-dimensional. Length is two-dimensional — you have to read it not as a point but as a band.

What I repeated most in my coaching years was this: the real measure of a bowler is not how fast the ball arrived but how many consecutive overs he can land it in the five-to-seven-metre band. Why that band? Because that is where the batsman's decision time is shortest. Short of it, he can go back — he has time. Fuller than it, he can move forward and drive — risk, but reward. The five-to-seven band leaves both options half-finished: not enough room to go back, not enough confidence to go forward.

That is not Kenyan mathematics; it is simply the geography of the game I have measured for three decades. And this is where a structural weakness in Asian batting shows itself — one we keep personalising as 'technique'.

Structure, not character

I watched Ranji Trophy knockouts from the ground for years, and one thing repeated every time: flat pitches, a shortage of quick bowlers, and batsmen who return at the end of a season averaging 55 without having played a single innings in which the ball repeatedly landed in front of their knees. That is not their fault. It is the output of a system whose domestic calendar is built around the weather, not around fast bowling.

Above that sits another layer — the economics of white-ball cricket. The IPL and its cousins teach a batsman how to attack length, not how to wait for it. In twenty overs, waiting is pointless. In five days, waiting is the job. The same player plays in both worlds, and whichever habit his body repeats two hundred days a year settles into his feet in the five-day format.

I stopped coaching the day I noticed I was only ever watching the spaces — not the batsman, but the space between him and the stumps. That is not arrogance, it was the end of a profession. A coach has to see the player. I was seeing the map.

---

Three hundred deliveries, and one no-ball

18 June 2026, The Oval. Pakistan 338 for 4, Fakhar Zaman 114 off 106, India bowled out for 158 in 30.3 overs. I was caught that day between a Lancashire coaching consultancy and a Saturday radio slot, and my way of watching a final had been the same for years: not the score, the length. I logged all three hundred deliveries.

Fifty-eight per cent of Pakistan's deliveries landed in the five-to-seven-metre band. That does not sound extraordinary — you expect that from quick bowlers. What was extraordinary was that they landed there over after over without a single over losing rhythm. Mohammad Amir's spell: six overs, three maidens, sixteen runs, three wickets — Rohit Sharma, Virat Kohli, Shikhar Dhawan. All three wickets came from that band.

I cut a fourteen-minute video the next morning — just the length map, no cuts, no music, no conclusions. Four hundred thousand views in a week. I resigned the consultancy that Friday.

One thing needs saying, because the easiest version of this story is that I sensed something. I sensed nothing. I counted three hundred deliveries and saw a shape that was already there. What we call insight is often just the end of counting.

One moment from that match gets forgotten — Fakhar Zaman was caught at slip off Jasprit Bumrah in the third over, and it was a front-foot no-ball. He was on three. He returned 114. The whole edifice of cricket analysis rests on such moments, which we later label 'luck' and place on a shelf where we never count them again.

---

1,240 deliveries, and seventy centimetres

At Edgbaston the following year I charted 1,240 deliveries across three Tests — release point, seam angle, pitch map. Three things emerged.

First: India's seamers averaged 6.4 metres from the stumps; England's averaged 7.1. Second: the gap had a direct run-rate consequence — England scored at 4.6 an over against India's bowling, while India managed 3.1 against England's. Third, and most important: whenever India's deliveries landed fuller than five metres, they became available for the drive — and India's most expensive ball that series was always the fullest one.

This entire essay rests on one line: the benefit and the cost of a fuller length are two faces of the same coin. Bowl fuller and you invite the drive; you cannot even make the batsman move his feet. Bowl shorter and you give him time for the cut and pull. Staying inside the band is the only option where both risks stay bounded — and that band determines what the scorecard will look like.

Sam Curran's 4 for 74 was proof of that band. He was not winning with pace; he was putting the ball where the batsman had to decide whether to come forward. And when a batsman makes a half-decision, he plays a half-shot. A half-shot becomes a catch.

The arithmetic of the tail

There is a cheaper way to show the shape of a collapse: the tail. The Test averages of batsmen from seven down tell you how much breath is left in your innings. At Edgbaston in 2026, India's position was that the value of the innings fell sharply after number six. When you are 141 for four and you believe the next three wickets will add thirty, your fifth-wicket batsman takes risk on your behalf. And the batsman who takes risk plays the shot that gets called 'carelessness' the next morning.

This is where I want to be plain: I did not draw the shape of that collapse three weeks earlier. What I did at Edgbaston over four days was pattern-matching, not prediction. The difference is enormous and I am not built to hide it. What genuinely existed beforehand was the data — length, run-rate, tail depth. What was built afterwards was the story.

---

The ledger was right; nobody read it until they needed a name to blame

I published the 4,000-word Edgbaston report and almost nobody read it. Two county analysts were citing the dataset within a month. That is the most honest condition in cricket journalism: conclusions get read, method does not.

In my experience, demand for analysis in Asian cricket rises when someone needs a name to blame. Then the ledger suddenly appears in newspapers. Then broadcasters call for the very graphic they refused the previous year. And notice that this demand precedes any number and attaches to the person who can be held responsible — the coach, the captain, the selection committee. The system is never the accused, because the system has no face.

This is not sentiment on my part; it is an event recorded in my call log. Whenever a series is lost, three kinds of phone call arrive — a producer who wants a graphic, an editor who asks who will be dropped, and a fellow coach who asks when I first saw it. The third question matters most and is asked least.

---

The counter-point: I will state the consensus in full

Now the part I apply to myself. When I say the cause of a collapse is length, I have to concede that Asian cricket's consensus says something else, and that the consensus is just as forceful.

The consensus: India lost because their middle order could not absorb pressure on the big occasion. Kohli fought alone, nobody else stayed. Technique is weak in seam and swing conditions. That explanation is not entirely wrong — it is an accurate description of real symptoms. But it describes symptoms, not causes. 'Could not absorb pressure' is an outcome. The question is why the pressure formed.

My disagreement begins here, in three ways.

First error: mistaking individual technique for structural weakness. If four different batsmen, with four different styles, get out the same way to balls in the same band, that is not four people's problem. It is the problem of the one thing all four were given — the training, the calendar, the experience.

Second error: treating length as strategy when it is often the output of fatigue. Landing the ball in the band over after over requires repeating the same physical work every over. After three spells it begins to break. A 6.4-metre average is sometimes not bad strategy but a workload story. And workload is a board's decision, not a coach's.

Third error, and the most expensive: assuming the length number is stable. It is not. It changes by series, by season, by delivery. 6.4 and 7.1 are team averages, and a team average conceals enormous variance. Seventy centimetres does not prove every Indian bowler was 50 centimetres shorter. Some overs were excellent. Some were dreadful. I printed that variance in the report — which may be why nobody wanted to read it.

And a fourth thing, which I say to myself: I read several things wrong that series. I assumed England's fuller length was a strategic choice. It turned out two of their bowlers were landing it there out of necessity, not design. The right conclusion often arrives for the wrong reason. That is the great warning of the trade I practise.

---

Empty seats are more honest than crowds

Since August 2026 I have kept a delivery-by-delivery log every series and written numbers instead of adjectives. 'He bowled well' became 'he beat the edge nine times in fourteen overs.' It has dried out my prose and made my conclusions harder to argue with, and it has turned me into the person broadcasters call when a graphic has to be true.

But what startled me most during the lockdown was not the ground. It was the stadium. I spent it counting empty seats, and they were more honest than the crowds. I found that the domestic tournament with the cheapest broadcast rights also recorded the smallest outdoor attendance — and both numbers were small for the same reason: someone had decided it would not be shown.

This belongs to the same story as the length data, and people dislike the connection. A player you never see has no meaningful domestic average. You pick him, you drop him, and on both occasions the only evidence you have is what was televised. In a system where a Ranji knockout is played outside the cameras, selection becomes an information-free decision — and then we call it a lack of opportunity.

---

What to look for in the next match

I no longer check the list of wickets once the game is over. I check the length in the first twenty overs. If a bowler is losing control and his deliveries are landing behind the band, wickets are coming regardless of what the scorecard says. If they are landing in front of it, four wickets can fall quickly — but behind them will be four boundaries and one long partnership.

One honest question I ask every time and cannot answer: if we turned all of Asian bowling seventy centimetres fuller, would we take wickets or leak runs? My log does not say clearly — it has won matches and lost matches. The people who answer with confidence usually do not have the log.