Zero Information Points: The Silent Failure Inside Cricket's Data Pipeline

On a desk in Chattogram, at half past eleven at night, I opened a dashboard and saw something strange. Every column was standing in place — format, venue, player, team, ranking, commerce, governance, risk, public sentiment, industry flow. Beside each column sat the same answer, written in the same language: insufficient information, assessment not possible. The information-points cell was completely empty. Staring at that empty cell, my first question was plain — the match was played, so why is there nothing here? Two answers are possible, and the difference between them is the real subject. One possibility: nothing happened in that match worth analysing. The other: something happened, but the pipeline that pulls the data broke down. In cricket journalism, telling these two states apart matters more than writing any match report. Make the first mistake and we miss one match; make the second and we start misreading the system itself. I started the Chattogram xG blog in August 2026, after Burnley beat Chelsea 3-2. In that match Chelsea had 2.3 xG to Burnley's 0.9, yet the scoreboard read 3-2. My first post was about exactly this gap: the xG map said 2.7, but Burnley won. From that day a habit formed — every analysis begins with data and ends with a decision. In July 2026, during the Russia World Cup, I wrote my first paid column for The Daily Star dissecting France's 4-3 win over Argentina; the question there was how four goals emerged from inside France's 2.1 and Argentina's 1.9 xG. In May 2026, when the Bundesliga returned to empty stadiums, I started measuring distance covered and PPDA in Bayern's 5-0 win over Schalke, because with no crowd the other variables step forward. One lesson has become clear across this whole journey: analysis only means something when a verifiable information point sits behind it. Our work runs in two stages. In the first stage a source — a match report, a scorecard, a document — is broken into small information points. Who played, how many runs, which format, which venue, what result, who bowled, at what rate. These information points are the atoms; without them, everything else is just story. In the second stage those atoms become the foundation for deep analysis — tactics, trends, risk, prediction. The problem sits right here. If the first stage returns zero information points, the vast machinery of the second stage stands on empty ground. Then two paths open. One path: fill the cells with guesses, which is not analysis but invention. The other path: honestly write in every cell, insufficient information, assessment not possible. I chose the second path, and this article explains that choice. Seeing the structure shows why a single empty information point paralyses the whole analysis. Our analysis stands on eight pillars, and every decision on every pillar depends on some information point. Without information points the pillar does not stand; only an empty cage remains. The format-and-match pillar needs to know what kind of match this was — Test, ODI, T20 — where the venue was, how the pitch played, what weather or dew did. Without these facts the nature of the match is unknowable. If no format is stated, we cannot tell whether 350 was hard or easy, whether 50 in the powerplay was good or bad. A 200 on day four of a Test and a 200 in a T20 are two different universes, yet without information points there is no way to tell them apart. The player-technique-and-data pillar needs average, strike rate, economy, situational splits, recent trend. Suppose a batter strikes at 130 in the powerplay and 180 at the death — without those two numbers his role is invisible. But if the information-points cell is empty, where do those numbers come from? With no name given, inserting any player is fabrication. I say it repeatedly: a conclusion resting on a small sample carries the risk of collapse — but if there is no sample at all, the collapse has already happened. The team-and-ranking pillar needs ICC rankings, home-and-away profiles, batting depth, bowling combination, bench strength, age structure, match-up history. All of it is the child of information points. Without them we do not know whether a side is strong at home or weak away; we do not know how a given bowler has handled a given batter before. Match-up means history, and history means data. The league-and-commercial pillar covers broadcast rights, franchise valuation, player salaries, auction and trade activity. An IPL auction decision, a retention, a trade — analysing these demands the transaction date, the figure, the contract length. Without this data we are trying to read the market by groping in the dark. The rules-and-governance pillar holds power-sharing, playing-rule controversies, anti-corruption matters, eligibility and selection, political influence. Every big cricket decision — a DRS controversy, a quota, a points deduction — happens inside a rule. Not knowing the rule means not understanding the event. The risk pillar needs a probability and an impact for each of sporting, personnel, commercial, integrity, reputational and systemic risk. Without information points, no one can say how large any risk is. The public-narrative-and-expectation pillar needs what the market expects, what can actually happen, and the gap between the two. Measuring that gap demands surveys, sentiment, public data. With an empty input the gap cannot be measured, because neither of its two lines exists. The industry-transmission pillar looks from youth development to national teams, and from there to broadcast and commercial markets; every joint in that value chain needs a fact. Without facts the flow itself is invisible. Seen together, these eight pillars make one thing clear. Every conclusion, every forecast, ultimately rests on a small information point. The information point is the evidence of analysis. Without evidence a judge does not rule; he merely keeps the case pending. From years of watching matches I can say this: people prefer stories to numbers, because stories are comfortable. But a story cannot be verified. An information point can. In that 2026 Burnley-Chelsea post I showed that xG said Chelsea's attack was fine while their defence was collapsing. That was a conclusion with shot data behind it. Had the data been missing, I could only have written that Burnley stunned everyone — an emotion, not an analysis. Now suppose a cricket match's input is empty. We do not know who won, by how many runs, whose performance was good. In that state the greatest temptation is to invent a story that sounds credible. This is where our discipline is tested. Placing a player's name, a score, a team into a zero-information cell is not analysis but invention. And invention is the gravest sin in journalism, because once printed it travels like truth. This is why writing insufficient information is not weakness but strength. It admits that we do not have the answer — even though we have the question. The analyst who can hold the question, even without the answer, will give the right verdict later when the right data arrives. The analyst who fills the space with guesses loses the truth on day one. An empty input can also be read as the failure of one document, but something larger is at stake. It is a symptom of the whole data pipeline. If a source fails to load, if it is stuck behind a paywall, if the document is a scan rather than text, or if it was routed to the wrong domain — any one of these can zero out the information points. The empty cell is one face of many causes. Without knowing the cause, the remedy stays unknown. The real danger hides here, and it is not the empty input itself. The danger is that an empty input often looks like a successful one. When an analysis stands with its whole structure, every column filled, every heading correct, it looks complete from outside even if the information points inside are zero. In pipeline language this is silent failure. The system does not stop, sends no error, and instead delivers an empty result while saying everything is fine. Silent failure is more dangerous than loud failure. Loud failure we catch — if a pipeline crashes, nothing reaches downstream, and everyone knows there is a problem. In silent failure, what reaches downstream is a polished structure that makes traders, journalists, fantasy managers and selectors think there is no news today. But the truth may be that the news simply did not reach me. The distance between those two sentences is what ruins decisions. I recognise this error in cricket. When a team produces no statistics across several matches, people say the boys are out of form, when sometimes the real reason is that nobody is tracking the data. The player is not weak; the measuring instrument has gone quiet. The same holds for an empty input: there is nothing and it did not match are two things, and confusing them produces the wrong call. And here lies the biggest trap — the urge to invent. An empty structure makes the hand itch: put in a name, add a score, the story will sound so good. But this is where professional honesty is tested. I learned early that when the xG map and the scoreboard disagree, you can discard neither the map nor the scoreboard. The gap between them is the story. In an empty input that gap is the only true thing — there is no data. Accepting that, rather than covering it with guesses, is the whole job. There is something deeper still. This silent failure happens every day in cricket's data world, and we simply do not notice. Small leagues, women's cricket, associate-nation matches — their data is often not tracked at all. The story the media then builds is really a story covering the absence of information. An empty input is not an exception; it is a routine fact at the edges of our game. And where there is no information, the story wins — which is the greatest defeat for analysis. On Bangladesh specifically: if the data of a player like Shakib Al Hasan or Mushfiqur Rahim fails to enter our pipeline one day, we should say the data did not arrive — not that the player has lost form. The difference looks small, but its effect on decisions is enormous. One has truth behind it; the other has a guess. Our framework needs one new habit — an exception log. In every analysis we should record what did not fit the model. An empty input is itself an exception. If we do not log it, the same error returns, and we will not even realise where it went wrong. We also need a plain-language box, because our vocabulary is a fortress to many. xG means expected goals — a probability measure of how many goals a given shot usually produces. PPDA means passes per defensive action — an index of pressing intensity. DLS is the mathematical method for setting a rain-affected target. WTC is the Test Championship points structure. RTM is a team's right to match before retention. Read analysis without understanding these terms and a person only becomes anxious, never able to decide. A practical question arises about the empty input — is it good or bad? For me the answer is clear. An empty input is not bad, if it is honestly declared. What is bad is the moment an empty input is hidden behind a confident story. A dashboard that lights a red lamp when empty works. A dashboard that shows green when empty is the danger. Here a major weakness of our industry is exposed. We love building machines but forget to measure their failure. Tracking, analytics, models — everywhere we think about output, never about the health of the input. Yet if the input is bad, no matter how beautiful the output, it is groundless. So my proposal is plain. First, a hard gate should sit in any pipeline — if zero information points return, it should come back as an explicit error, not a successful result. Second, source diagnostics should be added — HTTP status, content-type, byte length. These reveal whether the source was genuinely empty or got lost on the way. Third, cells should never be filled with guesses. Every empty cell should tell the truth. I know this is not easy. A full dashboard feels good; an empty dashboard feels like failure. But an analyst's job is not to look good, it is to tell the truth. If an empty cell is the truth, then it is the most valuable cell of all. Coming from a football background, I have a habit — I turn the gap between model and reality into the story. In that August 2026 match where Burnley beat Chelsea, the gap was between xG and goals. In the empty stadiums of 2026, the gap was between the crowd and the distance covered. Today, at a desk in Chattogram, the gap is larger — between information and the absence of it. Every gap teaches us something, if we are willing to look. So the next time I open a dashboard and find it empty, I will stop and ask — was the source truly empty, or did my pipeline break? A system that forces a verdict the moment zero information points arrive cannot be trusted. A system that stops at zero information points, asks questions, and keeps its eye on the next batch of data — that is real analysis. The question remains: are we willing to give a verdict without numbers, or can we honestly say that, at this moment, we do not have the answer?