The Courage of the Empty Cell: What a Cricket Analyst Does When There Is No Data

Late last year, after a completed series, a one-page analysis report landed on my desk. Eight columns, and in every single cell a single phrase — not applicable. No player named, no format, no pitch, no dew reading. At the bottom of the email, the young analyst who sent it had written one uncomfortable question: Sir, what do I write now?

That question, I think, is the most honest question in cricket analysis today. For twenty-five years I have watched the cricket world do the easiest thing available to it — fill the empty cell. The hardest thing is to fold your hands and wait. In my notebook there is a page that reads: on the day the data does not arrive, the verdict does not arrive either. The pressure runs the other way. Editors want conclusions, audiences want opinions, platforms want something new every day. Nobody wants an empty cell.

That tension sits at the centre of Asian cricket analysis. A typical pipeline has two stages. The first strips the source into information points; the second runs dimensional analysis over those points. A match, an innings, a player's form — all of it travels through both stages. When the first stage returns empty, the second stage has nothing but a question.

Cricket differs from most news here. It is a statistic-dense game. Every ball produces an outcome — runs, a wicket, a dot, a wide. The stream is so thick that an analyst is rarely truly empty-handed. So when someone writes 'no conclusion available', that is not laziness. It is a deliberate choice. And the Asian stage makes that choice harder. Dew in Dhaka, the sea breeze in Chattogram, the damp Colombo afternoon, the dry heat of Dubai — every venue walks onto the field with its own character. The pattern is already there before the first ball moves.

Sample size: three innings cannot write anyone's future

The first rule in my notebook is simple: beside every conclusion I write how many balls stand behind it. One innings is twenty-four legal deliveries; one T20 spell is the same. At that size the variation in strike rate is so wide the number is close to meaningless. Yet every series I see someone declare, after one good innings, that this is the future. Two matches later the same player is written up as not yet ready.

I remember an old story. On 10 November 2026, Bangladesh played their first Test, against India at the Bangabandhu Stadium in Dhaka. That single match could not write Bangladesh's Test future. Five years later, in January 2026 in Chattogram, the first Test win arrived against Zimbabwe. Between those two events lie dozens of innings and disappointments. That is the real data, not the scorecard of one match.

There is a second trap in sample size — format mixing. A batter's patience in Tests and their aggression in T20 are different skills. Carry a small sample from one format into another and the analysis collapses. When I build a model I never merge formats into one column; each gets its own cell. If a player's last six innings are spread across three formats, the effective sample is not six. It is two per format.

With a player like Shakib Al Hasan the split is obvious. His bowling economy shifts by format, and so does his batting role. No single-format number measures his total value. So when someone writes that he is out of form, my first question is: in which format, over how many balls, in what role?

For long-career batters such as Tamim Iqbal or Mushfiqur Rahim the reading is different again. A poor series is not proof of decline, just as a good one is not proof of genius. For me, the length of the career is the sample. A five-year average is far heavier evidence than a flash of one series. There is a hidden trap too: home-ground bias. In many Asian venues home averages inflate, because those batters know the pitch and the dew. That number cannot predict away success. So beside every figure I note whether it is home or away. The away sample is smaller but far more honest.

Before filling the empty cell I ask myself: if this number had come out the other way, would my conclusion change? If not, the number is not the cause of my conclusion — it is decoration. A great deal of false certainty in cricket analysis is built in the name of that decoration.

Weather: when dew changes sides

The second variable arrives from outside the boundary. In Asian cricket the weather is never mere backdrop — it is a selected player. In a Dhaka night match, once dew settles, the grip changes, the spinners lose the ball, and winning the toss to bat second becomes almost automatic. For that single reason, many matches are decided before the first ball.

I like to call this the player outside the notebook. An analyst who reads only the scorecard never sees the dew. But anyone who has sat in Mirpur for a night match knows the pitch becomes a different surface between eight and nine o'clock. The same spinner who found no turn in the first ten overs is suddenly stopping the ball in the last ten. Here a gap opens between statistics and the eye. The scorecard will say the second-innings bowling average was poor. The scorecard does not mention the dew. So in every match report I keep a separate column — conditions. Wind direction, humidity, when the dew arrived. If that column is empty, the rest of the analysis is incomplete.

Rain and the Duckworth-Lewis-Stern method complicate the account further. Introduced in 2026, the method sets a revised target after interruption, but it is never perfect. Had a side known how many overs it would bat, it would have batted differently. What never happened can be calculated, but it cannot be compared with what did. This is where I open my second notebook — the one kept for the matches that never happened.

On the toss I remain sceptical, though it is hard to measure. If a venue produces ten straight matches won by the side batting second, the toss effect can be discussed. But on two or three matches, saying the toss decided the game is weak analysis. In my reading the toss is a tendency, not fate — and turning a tendency into proof demands a sample.

DRS and umpiring controversies add another layer. A single wrong decision can redirect an innings, and the scorecard never records it. If a catch is missed by the umpire, the effect ripples through the next ten overs. Miss these invisible variables and the analysis sees only the top image, never the structure beneath.

This is where the empty cell earns its value. If a match report carries no dew, wind or toss data, the honest act is to leave that cell empty — not to fill it with a guess. A cell filled with a guess breeds a larger error later, because the next analyst treats it as data.

Narrative pressure: the single-cause hero

The third variable is the strongest and the most invisible. It is narrative pressure. Once a match ends, a story is needed — who was the hero, who the villain, where the turn came. But in reality a match is never decided at one moment. It is the sum of many small decisions, conditions and luck.

In cricket I avoid single-cause explanation — the lone hero, the turning point. Say someone hits a six in the last over and the side wins. The report will say that one shot won the match. But the seven dot balls in the five overs before, the run-out chance missed — where did they go? When one variable explains everything, that is not analysis; it is a story.

The narrative pressure falls hardest on Asian cricket, where every match carries national emotion. A defeat becomes personal failure; a win becomes proof of character. The line 'he wanted it more' is, to me, the defeat of analysis. Character cannot be measured, but run rate, dropped catches and field settings can.

Another form of narrative is player bias. We forget the mistakes of favourite players and shrink the success of disliked ones. With bowlers such as Mehidy Hasan Miraz or Taskin Ahmed the bias is clear. A poor spell becomes evidence against them, while the same spell under a favourite name is excused as bad luck.

To avoid the trap I follow a simple rule. After every match I write down the name of the player about whom my conclusion is weakest. About the player I know least, I write least. Readers want opinion, but my job is not opinion — it is measurement, and where measurement is impossible, silence. The bias runs the other way with big names too. A large innings from Rohit Sharma or Virat Kohli quickly becomes a great player's return, when the number may simply be the product of a friendly pitch and a weak attack. The same applies to Babar Azam. I keep the weight of the name and the weight of the number in separate columns, then check whether they match.

This is where an old habit helps. I first draw a map of the field — which zone the ball is landing in, where the fielders stand, which area is empty. Then I place the player's name on that map. Put the name first and the analysis tilts toward narrative. Put it last and the analysis stays with structure.

The contrarian angle: the empty cell is itself data

Now to the argument that sounds odd at first. An empty cell is not only an absence of information — it is itself information. If a match report returns every cell empty, it tells you that somewhere in the data-collection pipeline there is a gap. That is a signal about process, not about play. Confusing the two is a serious error.

Many assume that no data means no news. It is the reverse. There may be news but no data — a completely different state. An interview, an announcement, an accident — these are news, but they cannot measure a bowling average. Lack of news and lack of data are not the same thing.

Understanding the difference changes the analyst's role. He is not only a machine for drawing conclusions; he is also a guard who spots gaps in the pipeline. If the first stage returns empty, the correct work of the second stage is to stop — not to start guessing. I trust the model, then I watch the player; but when the model is empty, the player cannot be watched either.

A philosophical question hides here. Is silence a failure? Not in my reading. Every silence has a shape; it just needs the right lens. Staying quiet about a match does not mean the match was not considered. It means it was understood that the data has not yet arrived. The honest analyst's greatest skill is not knowing what to say, but knowing what not to say.

This argument carries its own risk, and I should admit it. If an analyst always retreats to 'no data', no conclusion is ever drawn. So I keep a balance: every piece must carry at least one conclusion, however small, with a confidence level attached. That is not indecision — it is measured decision.

Takeaway: test the model next match

So to the young analyst whose report sat on my desk, I gave the answer — write nothing for now. Gather the data; the pitch, the dew, the toss, the sample size. When those are in hand, then write. He was disappointed at first. But three days later, when he returned with full data, the piece that came out was far heavier than a guess.

Cricket analysis is really a permanent exercise in verification. What I call a conclusion today, the next match may prove wrong. I do not fear that possibility; I treat it as part of the model. For those who love certainty, cricket is the wrong profession.

So my closing question is for the reader, and it is an invitation to verify. Can you write a confidence level beside your favourite conclusion? If you cannot, then perhaps the cell should still be left empty. Because the next match will always tell the truth — we only need the patience to hear it before we write the answer with a guess.