I Went Looking for the Data and Found an Eight-Layer Empty Framework

I went looking for the data.

Last month a document landed on my desk — an eight-layer "deep professional analysis, cricket domain." Every layer had tables, risk flags, confidence tags, source grading, even a separate column called "hidden information." At first I thought someone had finally broken a match down with real depth. But as I turned the pages, almost every cell said the same thing — "insufficient information, assessment not possible." Twenty-eight tables. Zero facts.

That was the moment the real face of cricket's data revolution opened up in front of me. We live in an age where the structure of analysis is so polished that its emptiness goes unnoticed. A table does not make an analysis. A layer does not make depth. And we commit this error every day in cricket — from broadcast graphics to franchise dugouts.

Context: What Runs Under the Name of Data

From the mid-2010s, a flood of data hit cricket. First wagon wheels, pitch maps, line-and-length charts in Test cricket. Then, with the rise of T20 leagues, match-ups, expected runs, win probability, strike-zone maps, phase-based bowling analysis. Today every franchise has a team of analysts behind it, and every broadcast screen carries a percentage that updates after each ball.

But here is the first crack. Much of this modelling came from football and baseball — worlds where data sets are far larger, seasons far longer, and the sample behind a single event far bigger. In cricket the picture inverts. In a T20 match a batter might face ten to thirty balls. Using that sample to speak of "form," "trend," and "pitch map" is like writing an entire film script from one photograph.

Take a simple case. A bowler keeps a superb economy across four matches in a season. The graphic says — "new sensation." But two of those four were on easy pitches, one was rain-affected, and in one the opposition fielded an experimental side. Calling four matches a "sensation" is fraud in the name of statistics.

My Experience: The Size of the Sample

In 2026, when I was thirty, I went looking for the A-League — and found a data revolution that was never really there. The headline was — "The A-League's Data Revolution Is a Myth: Brisbane Roar's Fourth-Place Finish Was Luck." I showed that behind their 42 points sat an expected-points figure of just 36.8, and that Jamie Maclaren's 19 goals came from only 14.7 expected goals. The piece drew 180,000 reads and 2,300 comments.

That article built a habit in me — hunting the gap between a team's "story" and its "numbers." I later carried that habit into cricket. And every time I see the same thing: the bigger the story, the smaller the number — or the bigger the number, the more absent the context.

When I started the social-media cricket page BDCricTeam in 2026, the goal was already the same — to show the distance between story and reality. In 2026 I left the newspaper desk to cover Bangladesh home and away and looked for the same thing. My 2026 call on Germany came from the same belief — the bigger the headline, the weaker the foundation.

Core Analysis: When Numbers Lie

What is the most deceptive statistic in football? Possession. A team can hold 60 percent of the ball and still create not a single goal-scoring chance. Sideways passes, safe passes, pointless passes — the percentage looks lovely, the match is lost.

Cricket has an exact mirror image. Batting strike rate. A batter makes thirty off twenty at a strike rate of 150 and becomes the hero — yet look at how much of that came from a deliberate attempt to break the field, and how much came in an over where a fielder stood in the wrong place, or a bowler had lost his length. Strike rate does not say how hard each ball was, does not say what the pitch was like, does not say what the scoreboard pressure was.

I have watched matches from the ground for years — home venues, away venues, control-room screens. From that experience I will say: strike rate, dot-ball percentage, economy rate — these are "effort metrics" packaged without match context. Just as football's "distance covered" or "high-intensity sprints" turn pointless running into a pretty number, cricket's dot balls and economy turn pointless thrift into something called "control." A bowler can concede just fifteen in five overs — because batters were settling in, or the match situation made risk unnecessary. The number is superb. The bowling may have been ordinary.

The Format-Mixing Trap

Then comes the biggest trap — mixing formats. A batter's T20 strike rate is not his ODI strike rate. A Test average is not a T20 average. Yet both analytical reports and TV graphics cross this line. The phrase "in form" blends three different meanings across three formats into one sentence. And fans believe it, because the number has a decimal place.

We have seen this phrase applied even to a batter like Virat Kohli — brilliant in one format, struggling in another, yet merged into a single headline. If an analysis does not separate formats, it is not analysis, it is a slogan.

Home Ground and the Luck Ledger

And one thing we routinely forget — luck. The toss, dew, Duckworth-Lewis, rain, a dropped catch, an LBW review. A large share of cricket results comes from these uncontrollable elements. Analytical models either skip them or shelve them in a corner under "luck factor."

Say a team chases 180 in a T20 and wins in the last over. Next day the writing reads — "brilliant finishing, batting depth, nerves of steel." The truth might be: two dropped catches, a no-ball the umpire missed