The Lesson of Zero Information Points: The Courage to Say “I Don’t Know” in Cricket Analysis

Last week an analysis pipeline sent me a result whose first page carried no score, no player’s name, no information point. There was only a label — cricket_asia. For forty-four years I have logged cricket’s field geometry in notebooks, and the most instructive pages were never the big-score stories; they were the blank pages, where a match has no name, a player has no name, only a date and a question. The software asked me exactly that: what will you analyse from this emptiness? My answer was flat — nothing. And that “nothing” is the subject of this piece. A zero dataset is like the most honest result in cricket analysis: nobody wants it, yet without it every other result is untrustworthy. Cricket analysis has turned from a craft into a factory. There is a metric for every ball, a dashboard for every metric, a report for every dashboard. Batting strike rate, bowling economy, powerplay run rate, death-over economy — numbers are produced so easily that nobody asks where the number came from, or what it proves. Asia’s cricket market — India, Pakistan, Sri Lanka, Bangladesh, Afghanistan — is the centre of this dashboard economy, because that is where the audience is largest, fantasy sport biggest, and the demand for headlines most intense. Under that demand, the distance between a number and an analysis shrinks. My hesitation sits right there. When the foundation of an analysis is zero, what emerges is not analysis but decoration. That is why a clean information point — a date, a score, a field change — is sacred to me. The information point is the atom on which every judgement stands; if it is absent, the analyst must stop, because the alternative is invention. And invented analysis is the most dangerous kind in cricket, because it sounds so credible that the reader stops checking. The first rule of analysis is not tactics but honesty. An empty input is not a failure; it is a result — often the most valuable one. When I see a report that makes a claim with not one verifiable fact behind it, I know someone has heard not the sound of bat on ball but the sound of their own imagination. My method in cricket is simple: shape first, then mechanism, then consequence. The scoreboard arrives last, as evidence — not as story. Take a rain-affected day. If someone writes “the match turned”, my question is: which mechanism turned? Did the field placement change? Did the bowler’s run-up shorten? Or did the spinner merely change his line for a wet ball? If there is no answer, “the match turned” is not analysis, it is syntax. Strip out the luck factors — the toss, Duckworth-Lewis-Stern, a dropped catch — and if nothing remains, then nothing remains. That is the null-result principle. In my notebook I keep the dismissals that began with a fielder looking the wrong way — because that moment never reaches a scoreboard, yet it is the most honest evidence. The lesson of an empty dataset is the same. When the pipeline says “no data”, it gives me a gift: there is nothing to arrange, so the work of verification stays perfect. Here the question of base-rate discipline arises. An international match contains 240 to 300 balls. From one delivery in one match, calling a bowler “consistent” is baseless. The question must be: how often does this recur, over how many matches, in how many conditions? One exception cannot be called a trend; the text itself must say — this is a one-off. Manufacturing baseless trends is the biggest product of today’s analysis economy. And the biggest consumer of that product is the viewer who watches every match — he genuinely wants to know, and someone hands him a story instead. What I learned in empty stadiums is tied to this emptiness. When you watch cricket in an empty ground, you understand that absence is also data — but only when you can name it. Some day, in rain, the ground is empty, a warm-up is under way, no camera, no one writing. What the players do that day never reaches a scoreboard — yet the team’s true method shows itself precisely then, when nobody is watching and nothing is at stake. That “archive of quiet” is my real source. Here is the uncomfortable truth. The analysis industry wants a take, not an “I don’t know”. Broadcasters want excitement, fantasy platforms want numbers, advertisers want confident predictions. So the analyst who truly says “the data is not enough” falls behind in the market; and the analyst who builds a story from every zero gets the headline. That is the wrong incentive. When I say “I will not draw a conclusion from this blank label”, some read it as weakness. Yet it is the hardest professional act: not to claim when there is no proof. My second caution is vocabulary import. Terms borrowed from football — “half-space”, “low block” — sound beautiful in cricket, but explain nothing unless they can be translated into field positions and ball-lines. If the translation is impossible, they are decoration, not analysis. My third caution is the confidence of memory. Long experience makes memory mistake itself for data; so every historical comparison must be tied to a date and a source before it becomes an argument, or it must be cut — there is no option of softening it. So at the next match, when a number floats up on your dashboard, ask: is there an information point behind it? Is there a date? Is there a mechanism — a field change, a shortened run-up, a changed trigger? If not, keep the number as decoration. And a request to analysts: returning a zero dataset is never a failure — it is the pipeline’s most honest signal. Because in turning zero information points into analysis, what you lose is your greatest asset: honesty.