Where Is Cricket's Real Truth Hidden in the Noise of Empty Data?

I still remember that February 2026 afternoon in a Bengaluru hotel media room. When the IPL auction grid screen showed Royal Challengers Bangalore bidding twelve crore rupees for an unknown English fast bowler, the entire room erupted in applause. A senior colleague sitting next to me immediately started compiling a 'steals and busts' list. But I was looking at the plaster on that bowler's back and the corner of his rehab room. When, six months later, the player featured in only six matches and RCB finished last with three wins from fourteen, that article of mine gave me recognition. It began not with numbers, but with a body, a room, and a sound. Today, as I return to this vast and often hollowed-out world of cricket analysis, I feel we are all victims of a grand illusion. We have data, graphs, percentages—but do we have the game's real truth? In recent months I have seen several analytics reports and Stage-2 deep analysis frameworks that claim to go deep into cricket. One of these reports landed on my desk with everything from title to conclusion blank. Everywhere it said N/A. No player name, no team name, no format fixed. Just one tag: 'cricket_asia'. When I read that report, I laughed, then shivered. Laughed because such a grand analytical apparatus was completely hollow. Shivered because these hollow reports are the ones most widely shared in our industry today. This report is a symptom of a much larger disease. We are engaged in measuring the game rather than understanding it. We have forgotten the moment when the ball kisses the bat, when silence descends on the stadium, or when a bowler's body stops asking permission in his fourth spell. I felt this closely during the 2026 World Cup in Russia. From that Luzhniki tribune, when I saw Mandžukić score in the 109th minute, I did not write the scoreline. I wrote about the stillness of the Croatian bench and the singing of 78,011 people for players who could no longer hear them. That day I learned that the crowd is a character, not a backdrop. In 2026, when I was watching IPL from a Bengaluru bedroom and India's second innings collapsed for 36 in Adelaide on December 19, I did not write for eleven days. I was processing the sound of that empty stadium. When I finally wrote, it was not a cricket report but an elegy for a night Test. After that I took six weeks off, went to Coorg, and did not watch cricket at all. This became my rule—never file within 24 hours of a collapse. Keep the event and your reaction separate. But the cricket analysis industry I was born into today challenges this very rule. The Stage-2 analysis framework that is circulating everywhere today is essentially a hollow structure that tries to salvage its credibility by writing 'N/A' in place of data. My report said everywhere that information is insufficient, so analysis cannot be done. But the question is: if there is no information, why was this analytical framework built? It is like a building with no foundation, yet eight storeys are standing on it. On every floor it says—analysis would happen here, but there is no data. In my sixteen-year career I have seen many cricket 'experts' who build stories with big charts and graphs. But the truth behind those charts is often an empty screen. When I was a trainee at The Indian Express in Madras, I had an editor who used to say—'Son, show numbers only to one who has seen the field.' Today I feel this is truer than ever. The eight dimensions of analysis we talk about—format analysis, player technique, team landscape, league ecosystem, governance, risk, public narrative, and industry transmission—none of these can begin without solid information. But the most striking thing about this hollow framework is that it has written its own capture within itself. Every dimension accepts that information is absent. Yet the report exists. For me this is a huge revelation. There are two kinds of people in cricket analysis today. Those who know the smell of the field's soil, and those who know the colours of data loading on a screen. I want to write with the help of both. But I cannot forget that when I watched Neeraj Chopra's javelin throw that went 87.58 metres, the 68,000-seat stadium before me was nearly empty. There were just forty people. At that moment I thought this image was truer than any data point. That day I decided I would keep one image for every event. In seventeen days in Tokyo I wrote 14,000 words, but what endured was an 1,100-word piece about a lone javelin's flight in that empty stadium. Now the question arises: is this hollowness just a technical glitch or something more? My report also clearly stated that it is likely this emptiness is due to an upstream data ingestion or parsing failure. That is, somewhere the system did not read the source article properly. And that is the biggest problem. We have such powerful machines, such fine algorithms, but when it comes to understanding the soul of the game, they all end up writing N/A on an empty screen. I find it very strange that on one hand we discuss figures of crores in IPL auctions, and on the other we have no data on Ranji Trophy players who could play for Team India next year. The 'cricket_asia' tag mentioned in my report is just a signal—a direction indicating we are talking about the Asian market, but it is not even clear which country, which format, which team. I believe the biggest crisis in cricket analysis is that we have separated the game from its context. When I was also a film critic at The Indian Express in 2026, I learned that any work should be seen in the context of its time and place. The same applies to cricket. Unless we know which match it is, which ground, in which format it is being played, any analysis is merely wordplay. The way every place in that report said 'insufficient information' was in itself an honest admission, but also a major failure. The honesty was that it did not lie, but the failure was that it did not ask: why is this information absent? One thing I have always observed in my career—whenever a big player gets injured or a team loses, analysts immediately start speaking in the language of numbers. But the real truth is often on that player's face, in his gait, in his eyes. My report also said that the body is the last honest witness. A bowler's workload, the fourth spell, that moment in a long innings when the body stops asking permission—these are things no data desk can model. This is where my INFJ personality and industry experience meet. I know what the workload spreadsheet says, and I also know what the player's face says. From this whole episode I have learned that cricket analysis must return to its roots. We must understand that behind every number is a human being, behind every match is a story, and behind every story is an emotion. When I wrote about that twelve-crore RCB deal, I did not say whether it was a good or bad deal. I simply showed that the player played six matches, and how his back problem troubled him. My editor later told me that after that article he chose me to write features, because I showed the human being behind the numbers. Today as I write this, before me is that same empty report with N/A written everywhere. This report is a mirror for me. It tells me that if we do not have data, we must not lie. But it also tells me that the absence of data is itself a very big story. Why is there no data? Why do we not have a database of Ranji Trophy players? Why do we not have video recordings of matches played in small towns? Why do we not have any analytical framework for women's cricket? This question itself is the real analysis. The 'Signals to Keep Tracking' section of my report was my favourite part. It said we should watch when Stage-1 output gets completed, when the format is fixed, when player names emerge. This is a very practical suggestion. But it also shows that we are still at the beginning. We first need to decide what we are talking about. Now I would like to add something from my experience that was perhaps not in this report. When I was watching the World Test Championship final in Southampton in 2026, India lost. After that I watched the Italy vs England penalty shootout at Wembley from a Bengaluru sofa. That day I realised how thin the line between defeat and victory is. The same happens in cricket. One ball, one run, one catch—these all matter. But in our analysis all this gets lost somewhere. We have so many numbers that we forget that one ball that changed the course of the game. The 'risk-side analysis' mentioned in my report is also very interesting. It said that the biggest risk at this time is that we have no solid information. This is a 'null-content risk'. And this is the most dangerous risk because it does not reveal what is wrong. When you have data, you can correct mistakes. But when you have nothing, you can correct nothing. It is exactly like a batsman who walks out to the field but does not know which pitch it is, which bowler it is. I remember when I first read this report, I thought it was a joke. But then I thought—does this not happen in our industry? How many times have we read news that says only 'according to sources' and has no solid information? How many times have we seen analyses that simply say 'information not available'? This report is the extreme of that same mentality. It shows that we have the tools of analysis, but not the courage to analyse. We have become adept at collecting information, but not at understanding it. Now I want to start my point afresh. I did not write this article because I want to criticise anyone. I wrote it because I feel cricket analysis needs a new direction. We must capture that moment when a bowler comes in for his fourth spell and there is fatigue in his eyes, but his heart says he will bowl one more over. We must capture that moment when a batsman is on 99 and his hands are trembling. These things are not in any spreadsheet. But this is the soul of the game. I am not saying data is unimportant. I use numbers myself. But I do say that data is not the game's truth, it is only a part of it. The real truth is in the story hidden behind every number. When I wrote about that twelve-crore deal, I did not say how expensive it was. I showed that the player had pain in his back and won only three times in six matches. That story was more powerful than any number. Now I come to the end of my point. But before ending, I want to leave a question. Do we have any analysis of cricket that is completely honest? That does not say information is insufficient but tells why information is insufficient? Somewhere in my report it said—'this analysis is for reference only, not for betting.' I agree. But I would also add that this analysis is not only for reference, it is a warning. It shows that if we confine our analysis to just 'N/A', we will lose the soul of the game. For me cricket is not just a game. It is a medium through which I tell people's stories. When I saw the Indian innings collapse for 36 in 2026, I did not write any analysis. I wrote about the sound of the empty Adelaide Oval. Many people wrote to me after reading that article that they felt as if they too were sitting in that empty stadium. This is cricket's power. It is made not of numbers but of emotions. Finally, I want to say one thing. To every journalist or analyst writing on cricket right now, I have one request—the next time you write a report, keep at least one place where you have seen yourself bend. A true story. A true moment. A true emotion. Because if you cannot do that, you are merely copying data, not analysing the game. My empty report taught me that sometimes the biggest truth is that you have nothing. But within that 'nothing' lies the story that no one has told yet. Perhaps this is the future of cricket analysis—finding story out of emptiness. And until we learn this, we will keep writing 'N/A'.