Empty Frameworks, Full Notebooks: Where Cricket Analysis Actually Stands

It was a quarter to three in the morning. The tea in my Manchester flat had gone cold long ago. I opened a file on the laptop, its title grand — "Deep Professional Analysis: Cricket Domain." Eight large sections, a tidy table beneath each one, and in every cell the same sentence coming back: insufficient information, nothing can be said. Eight chapters. Zero facts. Yet the file looked so orderly that at a glance one might believe the work was finished.

I pulled the notebook over from beside me. In 2026, when I first picked up a pen at the sports desk of The Daily Star in Dhaka, a simple rule was taught to me — do not write what you cannot prove. Thirty-five years on, that rule is still the foundation of my work. A sentence without evidence is, to me, like an empty room: it looks like space, but there is nothing in it to live in.

Cricket media today is a vast machine. On one side, Test, ODI, T20, The Hundred — a crowd of formats. On the other, the IPL auction, WTC points, the franchise calendar — something is always running all year. Within that crowd, the reader wants one thing: fast, deep, authoritative analysis. The pressure therefore lands on the analyst. Some choose to absorb that pressure with structure — a tidy table, a ready-made framework, eight sections. A framework is easy to build, and it even looks professional.

But the real work in cricket does not happen in a table; it happens at the edge of the field. I have seen it many times — the story of an innings is rarely written on the scorecard. It lives in the over after the powerplay, when the field spreads; in the internal arithmetic of the death overs; in the hesitation of a review.

The foundation of cricket analysis is data, and the foundation of data is presence. A conclusion you did not witness at the ground is one you are borrowing — from someone else, or from your own imagination. A bowler's economy rate may look good, but without knowing how much of it came in the powerplay and how much in the death overs, the number is not lying — it is telling a half-truth. And a half-truth is the most dangerous thing in cricket, because it looks exactly like the truth.

Take the DLS method. When rain falls, the target changes — some call it a lottery, some call it injustice. In fact it is a calculation in which wickets in hand and balls remaining both carry weight. An analyst who writes "injustice" without knowing the arithmetic loses the match and the reader's trust along with it.

Separating formats also matters. The first six overs of a T20 carry fielding restrictions; a Test does not. If someone explains a Test session using the logic of a T20 powerplay, they have forgotten the grammar of the whole format. An empty framework never catches this mistake, because a framework does not ask its own questions.

I often say that the notebook is my primary source. When I sit down to write after a match, I pick three points out of a dozen — the ones that can carry the whole argument. The rest stay in the book. Writing down everything means a crowd of data, and inside that crowd the reader loses the real point.

An empty stadium is my favourite place. In 2026, during Project Restart, when I entered the Etihad as one of six reporters allowed in, the stands were empty but my notebook was full. That day I learned that the true character of a place is not in its crowd but in its silence. Cricket is the same. The real story of a match is never in the highlights; it is found by talking to the ground staff, by talking to the stewards.

Now let me say the opposite. It is assumed that an empty framework is harmless, because it makes no claims. I think it is exactly the reverse. A wrong claim is easily caught. But a tidy empty framework is not caught, because it looks innocent, even honest. The reader sees the table and thinks the work is done. The editor sees the file and thinks the analysis has arrived. Yet inside there is no answer — only the structure of a question. That is why emptiness can sometimes be more dangerous than wrong information: wrong information can be corrected, but a framework that said nothing is never protested against.

The problem is not only the structure but the reward system. News media now treats speed and volume as virtues. Who wrote fastest, who wrote longest. Nobody asks how much was verified. As a result, building analysis with a machine has become easy, and it sometimes lands close to the truth and sometimes not. The only way to tell the difference is to go inside and ask: where did this claim come from?

My insistence on "role over star" in cricket comes from this same place. The real story of a team is often not in a famous name but in the fifth bowler's over, in the wicketkeeper's glovework, in a run-out saved by a fielder. Yet an empty framework always looks for a big name, because a name is easy to fill in. Filling in data takes labour; filling in a name does not.

That labour is the whole point. When I write about an auction price — who went for how much, what premium, and how the Right to Match rule changed the game — I do not merely write numbers. I ask: how many minutes will this player get in this side, in what situations will he bowl, and does that role fit his skill. The answers to these questions are not in the framework; they are in the reporter's notes.

I have a rule: one verdict per piece — clear, earned, and standing on what the notebook already shows. An analyst who describes forever and never concludes wastes the reader's time. An analyst who concludes without evidence destroys the reader's trust. The path between them is narrow, and it can only be walked with data in hand.

There is no use blaming the machine. A machine will do what it can — count numbers, arrange tables, align formats. But the machine was not at the ground. It does not know how the wind was that day, how slow the pitch was, which bowler was carrying an injury. These things must be seen with the eye and written by hand. So my fear is not the machine — my fear is the analyst who submits the machine's empty table as his own work.

Here is one concrete fact. At the 2026 Qatar World Cup, Julián Álvarez scored four goals for Argentina, and in the semifinal against Croatia he kept nearly 87 percent of his passes accurate. The number does not speak by itself — it speaks when you know how his pressing created space for Lionel Messi. That same night I stayed late to speak with Argentina's kit manager, who told me Álvarez always thanks the laundry staff too. That one sentence fits into no table, yet it is the proof of a player's character.

Cricket has its equivalent. The WTC points system places the weight of a single match inside a whole cycle — a draw can sometimes change a team's fate. An analyst who looks only at results cannot grasp that weight. One who watches the cycle knows which match was truly as important as a final. A framework cannot make this distinction, because a framework does not know which week is heaviest.

We are now inside a major tournament cycle. Tournament pressure compresses thought — flags and stories sweep everyone along, and analysis then often loses to emotion. What the reader needs most at such a time is a calm voice that speaks of the ground, not the story. And that calm voice is created only by verification.

Verification is nothing complicated. Three questions. One, where did the number come from — which source, which time. Two, in what context does it stand — format, venue, opponent. Three, whose story is the number serving — the truth's, or the opinion I had fixed in advance. If you hold the answers to these three, the analysis stands; if not, it collapses.

I have a weakness of my own, and I will name it. Because of empathy and service, it is easy for me to describe forever and never conclude. But description can never take the place of a decision. What the reader wants from me is to know what happened, and what it means. Without meaning, the notebook becomes only a data store; it never becomes analysis.

And one more trap — hanging between two audiences. Cricket is as much loved in Bangladesh as it is a blend of commerce and tradition in England. The two audiences do not read the same piece the same way. Caught in that hesitation, many pieces stand in the middle and go nowhere. What I have learned: name your audience at the top, then write once, confidently, for them. Translation is possible; compromise is not.

So I return to that empty file. Eight sections, zero facts — it is a failed analysis, but it is also a gift. Because an empty table reminds me that the real work is never done in a table. However good the machine becomes, the story of cricket is ultimately deposited in one person's notebook — the person who was at the ground, who saw, who wrote it down.

Next week another analysis may arrive, full of data. But no one recognises analysis by a full table. There is only one way to recognise it — by asking: how much of this did you see yourself? If the answer is "all of it," then perhaps it is time to sit down and write. And if the answer is "none of it," then it is better to keep the notebook closed.