The Lesson of the Empty Spreadsheet: The Discipline of Saying 'No Data' in Cricket Analysis

It is 2:40 a.m. in Barishal. The laptop screen glows alone. I open a coded match file I had been tagging ball by ball for three straight hours. What comes back are empty rows. No entry, no zone code, no delivery angle, no defensive-line height. The analysis engine answers in three words: 'insufficient information.' That blank screen gave me the most honest lesson of my fifty years of watching matches. The real test of an analyst begins when there is nothing in his hands.

Two roads were open. One, fill the empty space with story — 'the match turned on momentum,' 'the pressure was too much,' 'the lack of experience was obvious.' Those sentences sound good, please the reader, please the editor. Two, admit that I have no answer, and then write down, item by item, exactly what data is required. I chose the second road. Because I know that a confident verdict standing on an empty table is no different from a lie.

Cricket analysis is a pipeline. In the first stage the raw material arrives — scorecard, ball-by-ball log, field placement, video timestamps, release angle of the delivery. In the second stage meaning is extracted from that raw material — who stood where, who triggered the press and when, in which over the defensive line dropped, how wide the gap between midfield and defence was. But if the first stage returns empty, no analysis is possible in the second. With only a regional label — 'Asian cricket' — you know the market, but not the format, the team, the player, the match.

A regional tag shows a direction, it does not create an entity. 'Asian cricket' could mean a Test, a T20, The Hundred. It could be a franchise in Cumilla, a Test innings in Mirpur, an Under-19 game. The label points at the door; it does not identify the room. Write analysis without grasping that difference and you will build the room out of your own imagination — and that is the biggest trap of all.

In the regular season the reader's hunger is different. They watch almost every match. They need to see the undercurrent beneath the table before it becomes a headline — title pressure, relegation stress, fitness swings, umpiring tendencies, a changed death-over plan. That hunger pushes the analyst beyond the data. The reader wants a name, a number, a story, fast. And that is precisely where the honest analyst's job becomes hardest.

Saying 'there is no data' is a skill, not a weakness. I call it null-handling. It does not mean conceding defeat; it means refusing to walk in the wrong direction. Any cricket claim needs four pillars: sample size, venue, opposition quality, and time. If any one is missing, the verdict hangs loose. The analyst's job is to mark where it hangs, not to hide it.

Suppose someone calls a pacer 'flawless.' But over how many matches? Three? Five? In T20 an economy rate below seven is good — but it only becomes meaningful when the sample is at least two dozen innings. A finisher's strike rate of 180-plus sounds superb, but 180 built on six innings is not the same as 180 across thirty. A small sample first makes you a hero, then cheats you. A benchmark is necessary, but a benchmark that is not tied to a sample-size condition is mere decoration.

The most common error is mixing formats. You cannot judge T20 economy by Test rhythm. A bowler is king of line and length in Tests, yet helpless in the death overs without a stock of slower balls and yorkers. A middle-overs spinner in ODIs is a different animal in a T20 powerplay. Anyone who says 'he is in form' without naming the format has nothing behind the sentence. A format means a different game, different claims, different benchmarks.

Then the venue. At home, almost everyone looks better on average. The spinner turns it on a familiar pitch, the pacer swings it in familiar air, the batter plays quicker on familiar bounce. But whether those numbers survive away is the real question. Home data often conceals weakness. If an analyst looks only at home numbers, he is staring into a mirror — not at the ground. Pitch type, weather, humidity, outfield speed — without matching these, two matches' numbers cannot be pooled.

The toss and DLS — these two 'luck' factors must always be stripped out. With dew, the ball slips from the spinner's hand in the second innings. With rain, DLS changes a result mathematically, not through cricket skill. If someone reads 'form' or 'team strength' from that result without removing the luck, he is analysing the weather, not the game. Every regular-season week has at least two matches where the toss almost decides the outcome — yet that never reaches the headline.

And DRS. This is my biggest objection. 'Clear and obvious error' — the phrase itself is a vague clause. Ball-tracking, pitch line, wicket height, stump projection — all are projections, all model estimates. How much of a third umpire's 'final' decision rests on model estimation, on camera frame rate, nobody measures. The space for subjective judgement is far larger than we admit. It feeds directly into the fairness of the result, yet it almost never enters the discussion.

A player's age curve and injury history cannot be dropped either. A 33-year-old batter's hands may no longer move as fast, but he covers it with experience — and that rarely shows up easily in the data. Others stay in the shade for two months after returning from injury, then erupt. If someone delivers a permanent verdict off one snapshot, he has misread time. Without knowing which way the age curve is turning, saying 'it is over' is judging without seeing the future.

This is why I keep my coded data like an open ledger — every entry timestamped, every decision traceable. If someone asks 'where did you get this from,' I can turn and show it. Analysis that cannot be re-verified is not analysis; it is only a claim. I coded the BPL before I trusted the eye test — because the eye is deceived, while a coded notebook is not. A ledger that does not change, only grows, is where trust lives.

Here lies the real argument. The industry rewards confidence, not caution. An analyst who admits doubt is seen as weak. The one who is clear, decisive, certain — he is rewarded, shared, invited for interviews. That pressure is what puts a story on top of an empty table. And when automated systems begin to fill empty space, those stories spread even more silently — no one notices, no one verifies. A human error can be corrected; a system's error gets replicated.

The same logic holds in football. Modern inverted wingers have made football homogeneous; the old touchline-hugging winger is being forgotten. Everyone copies the same template, so no one looks sideways. Cricket analysis carries the same risk — everyone writes the same decisive narrative, so no one says 'I don't know' anymore. The left half-space is not a fashion; it is a door — but before you recognise the door you must recognise the room. And the only way to recognise the room is to honestly know which corner lacks your data.

So what do you do next match? Here is a simple method. First, write down which piece of data you do not have. Second, write beside it the sample size, the venue, the format. Third, keep the luck share (toss, dew, rain) separate. Then see whether the verdict holds. Takeaway: never fill the empty cell with imaginary numbers. The empty cell is itself information — it says more coding is needed.

2026's empty stadiums, full notebooks — that habit still pays. When some analysis tells me 'insufficient information,' I am not annoyed; I ask which variable exactly is missing, and who will fill it — a human, or a machine that does not know its own gaps? Next over, when you read a 'certain' verdict, ask one question: is this coded data, or the story of an empty cell? Evidence over reputation.