The Empty Cell on the Spreadsheet: The Best Sports Analysts Are the Ones Who Can Say 'Not Enough Data'

On a sweltering July night in Los Angeles, I sat in front of a screen with a spreadsheet already open, waiting for data to stream in from a match that had ended three hours earlier. The left column listed players. The right column held the metrics I needed to write the piece: sprint counts, distance covered, duel win rate, pressing index. Instead of the familiar numbers, every data cell displayed a single state: empty. The match data feed had failed, and I had no way to verify anything before my filing deadline.

In this profession, deadlines wait for no one. Editors need copy, audiences need commentary, algorithms need fresh content. In that moment, the easiest choice is to write by feel. "This team is pressing worse than last season," "that player seems to have lost form," "the tactical system appears to have a problem." Sentences like these read smoothly and sound convincing, and they cannot be verified at all. I once almost wrote that way. Then I remembered why I had started clinging to data so early.

In 2026, when I had just turned seventeen, I wrote my first piece about a World Cup final and was mocked by an online account saying a girl knows nothing about football to be analyzing it. My response back then was not to argue, but to attach statistical sources and keep the argument intact. From that point on, every conclusion of mine needed a piece of data standing behind it. Data became my shield. But precisely for that reason, I learned something harder: when there is no data, the shield disappears, and being honest about that gap is the real test of anyone in this trade.

That night, I decided not to write about the match. I wrote about the empty cell itself.

Why an empty cell matters more than a wrong number

In modern sports analysis, data exists in layers. The raw layer is what cameras capture: position, time, distance. The derived layer is the metrics calculated from the raw layer: distance covered, sprint counts, the PPDA index measuring pressing intensity. The interpretive layer is the conclusion: Team A played better than Team B. The most common mistake is jumping straight from the raw layer to the interpretive layer, skipping the derived layer, and turning feeling into conclusion.

When the raw layer fails, the whole structure above it collapses. A pressing metric calculated from inaccurate positional data will produce a false story. And a false story, once spread widely enough, becomes the default truth in the eyes of the audience. An analyst has a duty to distinguish clearly between "I know" and "I feel."

In esports, where I come from, this boundary is far sharper. Every match is recorded down to the frame, every champion pick, every gold and experience figure. But even there, when a publisher's API fails, the analytical community still has to wait. Nobody dares claim a team is "falling behind the meta" on feeling alone, because the community will immediately demand evidence. Football should require the same rigor, yet its commentary culture sometimes allows groundless judgments to survive far too long.

Three lessons from an empty spreadsheet

The first lesson came from my own work. While editing content for a sports channel, I once received a request to write an analysis of a big club's decline based on only its last three matches. Three matches is far too small a sample to conclude anything. I proposed expanding it to ten matches and adding possession metrics broken down by half. The result showed the problem was not form, but a congested schedule that left key players unable to recover. The conclusion "decline" became "overload." Two readings, two entirely different implications for the club.

That lesson taught me that schedule density is one of the biggest causes of swings wrongly attributed to form. Data does not speak for itself; an analyst must place it in the right context of schedule, opponent, and injury history. When one of those three pieces is missing, I write "not enough data" instead of guessing.

The second lesson concerns how metrics get packaged. Distance covered and sprint counts are usually presented as measures of effort. But a player who runs a lot has not necessarily run to the right places. I once watched a match in which a central midfielder topped the distance-covered table, but watching the footage back, most of those meters came from chasing the ghost of the ball rather than actively closing space. A pretty metric does not mean effectiveness. Readers need to know this so they are not seduced by flashy numbers. A striker like Kylian Mbappe can top a sprint table, but if you ignore whether those sprints actually created chances, you are only praising a number.

The third lesson is the hardest: distinguishing between a "bad decision" and a "bad outcome." A coach can pick the right tactical approach and still lose to a random moment. Conversely, a winning team may have played a flawed system. If you judge only by results, an analyst turns luck into merit and risk into guilt. When analyzing a team, the right question is not "did they win or lose," but "are they exploiting the opponent's weaknesses and the tournament context correctly."

Out of those three lessons, I built a fixed habit for myself. Before writing any conclusion, I list three columns: what I truly know, what I infer, and what I do not know. That three-column table usually makes an article longer but more honest. In many cases, it saved me from publishing a groundless judgment and having to delete the piece days later.

When you apply these three lessons to a situation where the data source is completely empty, the only conclusion available is: no conclusion can be drawn. In analytical terms, that is the state of "insufficient information, cannot assess." At first glance this looks like a poor answer, an admission of weakness. In truth, it is the most honest answer a professional can give. A spreadsheet stuffed with fake numbers is many times more dangerous than an honestly empty spreadsheet.

This is especially true in the middle of an annual season, when teams play at a density of two matches per week. In that phase, small swings in fitness and squad depth are often mistaken for a form crisis. Close followers will spot the tactical currents and refereeing controversies beneath the league table before they become headlines. But to spot those currents, you need data that is long enough and clean enough. When the data is insufficient, patiently waiting is a professional decision, not laziness.

The majority wants a story, not the truth

There is a paradox in the sports content industry. Audiences say they want deep analysis, but what makes them click is decisive conclusions, tidy provocative statements. "This team is finished." "That player has lost his motivation." Sentences like these spread faster than any spreadsheet. And because algorithms reward engagement, writers get pushed toward always having a conclusion, whether or not the data supports one.

I believe this is the biggest trap in the trade. When an analyst starts prioritizing decisiveness over accuracy, they are no longer analyzing; they are writing fiction. Fiction is entertaining, but it does not help anyone understand the match better. And eventually, when readers realize those decisive conclusions were often wrong, trust disappears, not in one individual, but in an entire way of working.

Curiously, in esports, where data is more transparent, the culture of "no data, no verdict" is respected far more. Professional analysts readily say "I need more data" in front of hundreds of thousands of viewers, and nobody treats that as weakness. Football can learn from that attitude. Honesty about the limits of one's understanding is a sign of expertise, not a lack of confidence. Just as defending was never cowardice, only a majority that had not read the survival meta correctly: admitting "not enough data" was never inferiority, only a majority unfamiliar with a higher standard of analysis.

What remains

The empty cell on that spreadsheet ultimately did not become a match report. It became a lesson I carried through the years that followed: the hardest part of the analytical craft is not finding an answer, but having the courage to say there is no answer yet. When a data platform builds its credibility by clearly stating sources, publication dates, and the points it cannot yet verify, it does not weaken; it becomes a place people can trust. In an industry where every judgment can be copied and spread, trust is the only asset that cannot be faked.