Nine Sections, Not a Single Line of Data

The document ran nearly four thousand words. Nine large sections. Each one had its own table, its own risk matrix, its own one-to-five-star rating field, its own source line at the bottom. And in every answer cell, the same sentence repeated verbatim: insufficient information, cannot assess.

I read it on a January morning, with snow still unmelted against the window in Chicago. It came from a young editor, with a short question attached: “Can you check whether this is deep enough?”

It was deep in form. It had nine parts, exactly matching the professional analysis framework the big esports outlets are running. It touched on patches, tournament formats, rosters and players, regional landscape, club finance, rules and governance, risk profiles, public narrative, and the industry transmission chain. Not one topic a serious analysis must reach was missing.

And it contained no fact at all. No specific match. No name. No timestamp. No win rate, no pick-ban figure, no disciplinary record.

A blank page does not chill me. What chills me is that it looked exactly like a real analysis. If it had been published, most readers would have scrolled past, seen the tables, seen the star ratings, seen the words risk matrix, and believed it.

Ten years ago, a decent esports analysis cost me three days. Rewatching footage, scrubbing back and forth through every teamfight, logging timestamps, calling people inside the scene, then cross-checking at least two independent data sources. Now a regional split lasting a few weeks can generate hundreds of articles. Distribution platforms reward frequency. Search algorithms reward structure. Structure is far easier to clone than understanding.

The nine-section framework was born from a legitimate need: make sure no analytical dimension is skipped. But when a framework is detailed enough to become a form, it is also detailed enough to become an excuse. Writers stop asking what they actually know about the story in front of them, and start asking what this section needs filled in. The second question always has an answer. The first one does not.

I once sat in a newsroom like that. In 2026, when I was twenty-three and working as a production assistant at WSCR Chicago, the sports world stopped rolling. The summer of 2026 had no crowds, but sport had never been so honest — with no stands to perform for, people had only one option left: tell the truth. A transfer market in a pandemic is a place where people trade panic, not players. An assistant coach at Chicago Fire called me about a loan move for Robert Berić from Saint-Étienne. I checked his record in Ligue 1 — seven goals in twenty-two appearances — then called an agent to verify. The desk looked at me the way people look at a young woman guessing. On 12 August 2026, the club confirmed the deal.

The lesson sat somewhere else: a claim only deserves to be printed when a fact stands behind it, and that fact needs someone accountable for it.

In 2026, when I was twenty, I wrote the opening post of a blog called “Hiệp Ba” about the team I watched every week. Chicago Fire then had the lowest pass accuracy in the league, around seventy-eight percent, yet scored fourteen goals from counterattacks, the most in MLS. The whole city called it crudeness. I pulled the numbers from Opta, built charts, and argued that direct play was a tactical statement. A male commentator messaged me on Twitter: women like peering into tactics, huh. I did not delete the post. I wrote a response, charts attached. Chicago Fire taught me that football always knows how to trample the script.

A year later, after the 2026 World Cup semi-final between Croatia and England, I wrote about Luka Modrić. One line from that piece I still keep: Modrić ran without stopping, as if fleeing something called memory. A former England international scolded me for mixing emotion into expertise. But that line did not stand alone. It stood beside the distance he covered in extra time, beside the number of recoveries in his own half, beside a specific match that ended with a specific score. Emotion earns its credibility only when anchored to a fact. Remove the fact and the line is just a line.

I wrote “Hiệp Ba” to tell stories about football, and it turned out I was telling stories about myself.

A text with no data belongs to an entirely different genre, and calling it “analysis” is precisely how we fool ourselves.

There is an emptiness that hides behind tables. The writer builds a matrix, splits risk into six categories, assigns each a level and a probability, yet never says what the risk is, whose it is, when it occurs, ahead of which event. Here the table serves as a shield rather than a tool. When a writer knows nothing, a table always looks more credible than a sentence.

There is an emptiness that hides behind terminology. The meta is shifting. Roster depth. Industry transmission. Phrases with real meaning, placed in correct grammar, carrying no information at all. Terminology is a contract between writer and reader: I use expert words, you trust that I have expertise. A text made only of contracts with no delivery is no longer analysis; it is a promise.

There is an emptiness that hides behind prophecy. Predictions issued in the future tense, with no conditions, no checkpoints, and therefore incapable of ever being wrong. I once made a prediction like that, and I still remember how it felt when it landed. I was not happy to be right. A prediction that cannot be wrong cannot be right either; it is just a good line.

The patch section is where emptiness does the most damage, because it decides which teams the community believes hold the advantage. A patch only means something when tied to a specific change, a specific win rate before and after, and a sample window long enough to matter. Saying the meta is shifting toward earlier fights — with no version, no tournament, no pick-ban figure — is saying something true of every season since the game launched. A sentence true of everything says nothing about anything.

The regional section behaves the same way. Tier one and tier two labels get used as if they were natural facts, when they are only consequences of a traceable chain of international results. Remove that chain and the label stays on paper while meaning nothing in a reader’s head. I have seen reports place a region at the top simply because it sent many teams, while its knockout win rate sat below a region ranked under it.

The test is simple, and I have applied it to everything I have written since 2026: underline every declarative sentence, then write its source in the margin. Any sentence with nothing beside it must be deleted, or downgraded into a question. For a five-thousand-word piece, that takes about forty minutes. It is the cheapest forty minutes in the entire production process.

A null result is a legitimate answer. In most newsrooms, it is the only honest one.

The problem is that null results are not rewarded. Nobody shares a piece titled we do not have enough data to conclude. No algorithm pushes it to the top of the page. The young writer who sent me that document did exactly what the system taught her: keep the framework, keep the tables, and replace the conclusion with a polite apology. A better framework will not save her. What she needs is a newsroom that accepts some days produce a zero, and that a zero is not a verdict on the writer.

Since 2026, search algorithms have added another condition: every article must deliver something the reader did not already know. A fully completed form does not satisfy that condition. It only repeats what the reader already holds: that strong teams usually win, that patches change the game, that club finances matter. The safety of structure is exactly what renders it invisible.

Where I might be wrong.

There is another reading, and it is not foolish at all. That document may simply be a technical fault: one information-extraction step broke, not a symptom of a trend. A pipeline error says nothing about the editorial culture of an entire industry. If so, I am building a large argument out of a small incident, which is exactly the mistake I criticise in others.

It is also possible I am underestimating readers. They are not fooled by empty tables. They know what they are reading, and they only want something to pass the time between two matches. If that is truly the demand, then what I call empty analysis is just entertainment wearing the wrong label, and relabelling is cheaper than rebuilding an industry.

Then there is the possibility that bothers me most: my standard may be a privilege. I write for a small readership patient enough to finish an article. I am not racing thirty other outlets for pageviews. When you have a podcast with a few thousand loyal listeners, perfectionism is permitted. When you have a newsroom payroll to meet, perfectionism becomes a luxury. I do not dispute that reading. I just do not find it sufficient to excuse calling a text with no data an analysis.

Based on my experience watching matches, the failure order is always identical: the framework comes first, the data comes later, and when the data never arrives, the framework stands alone.

Someone will ask how to write instead. My answer is not a new framework. An honest analysis should end with a list of things to watch, plus concrete conditions for knowing you were wrong: if this team wins its group with that pick-ban rate, my conclusion collapses. The clearer the conditions, the more trustworthy the piece, even when it is wrong.

If you want to test me, do something that takes five minutes. Open the ten most recent esports analyses you have read. For each one, try to find at least one verifiable fact inside: a win rate, a timestamp, a sourced transfer fee, a disciplinary record. My guess is you will stop before finishing the list.

And if you can do that with this piece, then it has done its job.