When the Box Score Is Empty: The Trap of Reports That Look Complete

On Saturday night, after a VBA group-stage game, I opened the log file as I do every week. The table came up clean: the right columns, the right formatting, headings printed clearly. Except that under each heading was a blank space. Not a single shot. Not a single timeout. Not a single number. In all my years reading basketball data, this is the kind of error that keeps me up the most. Not because it is hard to fix, but because it is so easy to overlook. A corrupted file makes everyone shout. But an empty file, neatly presented, slips quietly past the reader, then gets filled in with things that never happened on the court. That night I stared at the empty table for a full fifteen minutes. Then I did something my colleagues considered pointless: I did not write the report. I went to find where the data pipeline had died. VBA, Vietnam's professional basketball league, tipped off in 2026. Each game produces no small amount of data: minutes for each player, shooting percentages, assists, personal fouls, pace. To a data consultant like me, that is the raw material for answering a question few coaches bother to put into words: why is the winning team not necessarily the better team? People are used to looking at the scoreboard. Points are tangible; everyone sees them, everyone remembers them. But points are only the final result of a chain of decisions — choosing a position, passing or shooting, holding or releasing your man. That chain lives in the data, not on the scoreboard. That is why a game with lost data matters more than a loss. A loss still leaves footage to learn from. Losing data loses the very ability to separate luck from real strength — the thing I have chased for years. When people talk about a data system failing, they think of broken machines, deleted files, hard drives smoking. But the most dangerous errors always take the shape of a correct result. It returns the right number of columns. Writes the right field names. Prints a table that no one would doubt at a glance. Only when you read every single number do you realize there is nothing inside. A model never says "I am missing data." It stays silent and waits for you to understand. If you do not, it lets you do the worst part of the work: imagine the answer. People are very good at imagining. Hand a coach an empty table and he will fill it with his memory of the game. That memory is not wrong emotionally, but it is skewed statistically. People remember the game-winning shot in the final second, not the eighteen misses before it. In basketball there is a kind of data I call soft-lying data. Take shooting percentage. A player who goes 8-for-10 gets praised as a marksman. But if all ten of those shots were wide open, with no one guarding, then 8-for-10 only says he stood in the right spot, not that he is good. Conversely, a player who goes 3-for-10, with most of those attempts heavily contested, may create far more value. Shooting percentage lies if you do not know the context of each shot. I have seen this many times. A team loses three in a row and the coaching staff concludes the defense is weak. But when I rebuilt the opponents' shooting data, the problem was elsewhere: the opponents hit threes at a rate well above their season average across those three games. That was the opponents' luck, not the defense's weakness. Overhauling the defense because of three superhuman shooting nights is shooting yourself in the foot. But to say that, I need data. Without data, I only have a story — and every story sounds plausible. Every coach talks about feel. I do not have feel. I have standard deviation. Standard deviation does something feel cannot: it tells you whether an outlier is a signal or just noise. Three games above average may be a signal, if the opponent repeats it all season. It may just be noise, if they fall back to their old level right after. Feel cannot tell the two apart. Standard deviation can. But I have to say something hard to hear. Data is not truth. It is a mirror, and that mirror can crack without anyone knowing. Numbers do not lie, but they do not tell stories either. If the person reading the mirror is careless, he will see in it exactly what he wants to see. That is why I spend almost all of the first part of each week not analyzing, but checking whether my data actually exists. It sounds trivial. But most mistakes in sports analysis do not come from bad math — they come from doing math on an empty foundation. Here is the paradox. Everyone thinks the enemy of analysis is a lack of data. It is not. The real enemy is data that looks complete. A table with dozens of metrics, formatted beautifully, exported to standard, that no one reads. On many teams I have seen reports as thick as a book, and the coaching staff still looks at exactly three numbers: points, fouls, and shooting percentage. The rest exists to prove that people are "doing data." That is silent failure at a second level. Not empty data, but data that is full yet meaningless. Both are equally dangerous, because both make the decision-maker believe he is fully informed, when in truth he is guessing — just guessing with charts attached. The counterintuitive point I want to stress: in Vietnamese basketball today, the problem is not that we lack data. The problem is that we have too much data and too little discipline in reading it. A team that collects ten metrics and uses none is worse than a team that collects three and uses all three. Quantity is not quality. Charts are not understanding. I once received a twenty-page report analyzing every possession of a single game in detail. By the end, I could not find one conclusion usable for the next game. It described the past perfectly but said nothing about the future. To me, that was an empty table presented at greater length. People look at the score to remember a game. I look at the metrics behind the score to understand how the game almost happened differently. But if those metrics do not exist, or exist without anyone reading them, then I am left with only the score, and the score always tells the winner's story. On the night of the empty log file, I drew no conclusions. I told the coaching staff plainly that there was no data for this game, not to use it. They were a little annoyed, because everyone wants something to say. But I would rather say nothing than say something I made up. A week later, I found the bug: a processing step in the middle layer received empty data but still returned a properly formatted table. It never raised an error. It simply did its job with an empty input. If I had not read carefully, cell by cell, I could have filled it with numbers born of imagination, then presented them as though they were fact. Years in this job have taught me a lesson I have to relearn every season: the greatest enemy of a data consultant is not bad data, but confidence. The confidence that you already understand, when in truth you are only filling the gaps with a story that sounds plausible. The season is long, and the numbers will keep pouring in every week. The question I keep for myself is not which team is stronger this week. The question is: how much of what I am about to say is real data, and how much is the echo of empty cells I quietly filled in?