Nine Layers of Esports Data: When a Perfect Framework Stands on Nothing

Nine Layers of Esports Data: When a Perfect Framework Stands on Nothing

A report more than a dozen pages long sat on my desk one midweek afternoon. It had all nine major sections, each with tables, an assessment column, and a bolded conclusion line. But as I scrolled down row by row, every cell repeated the same phrase: insufficient information to assess. No tournament name. No team name. No player name. No patch number. A framework designed so carefully it approached perfection, standing upright on a completely empty base.

I have read more than a few poor analyses in thirteen years on the job. Most of them are poor because they lack a framework. This one was poor for the opposite reason: the framework was too good, while the input data was zero. The writers did not fabricate. They followed the profession's principle exactly, which is not to speculate without grounds, so in every cell they wrote three words: insufficient information. That behavior deserves praise. But it also exposed a larger problem: if an analytical process can run through all nine layers without needing a single number, then the problem lies in the process, not in the data.

Context: two layers, and every layer needs numbers

In the trade of esports analysis, the process is usually split into two layers. Layer one is extraction: turning a raw article into structured information points, including tournament name, team name, player name, timestamps, and source. Layer two is deep analysis: taking those information points and examining them across multiple dimensions, including meta, format, roster, region, finance, rules, risk, public sentiment, and the transmission of the whole industry.

The key point is that layer two does not generate data on its own. It only reorganizes the data layer one has gathered. If layer one returns an empty result, layer two has nothing to organize. The nine-dimension framework stays intact, but it resembles a building with all its beams and columns and not a single brick to build with.

In Vietnam, most esports content still stops at the level of narration: recounting the action, copying statements, reporting transfers by headline. Readers are used to "team A beat team B," rarely shown why. That gap is precisely why a nine-layer framework was born. But that gap is also a trap: without numbers, a writer easily slides from analysis into description, and from description into speculation.

I once witnessed the opposite. In 2026, while a second-year student in Binh Duong, I collected the data of a football club across the first twenty rounds of the season. They generated an average of 2.1 expected goals per match but scored only 0.8. I wrote a piece concluding that if they kept their coaching staff, they would survive relegation. The club's leadership sacked the head coach right before the second half of the season. The team was relegated. The article was shared two thousand times. From that day I understood one thing: data does not lie, only the listener is not patient enough. And without data, a writer has nothing left to say but feelings.

Nine layers, and the price of an empty cell

To see why an empty framework is dangerous, one must walk through each layer and ask two questions: what data does this layer need, and if it is missing, what collapses.

Layer one is patch and meta. This is the foundation layer, because everything after it depends on it. To speak of meta, one must first know which game is being played. League of Legends, Dota 2, CS2, Valorant, or Arena of Valor, each title has a different patch cadence and metric convention. Without identifying the title, there is no anchor point. Then one needs the patch number, a description of mechanic changes, and metrics such as win rate, pick-ban rate, and match duration. Missing all of it, the question "where is the meta shifting" has no answer. In that report, even the game-title cell read "insufficient information." When the foundation layer is empty, all nine layers above it wobble.

Layer two is tournament system and format. Format determines the probability of upsets. A single-elimination, one-match format is very different from a best-of-three or best-of-five series. One needs the qualification path, the draw method, the seeding, and the schedule density. Without a format, one cannot judge whether a strong team is stable or prone to crashing out. In Vietnamese esports, where many domestic events still change format mid-season, this is the most easily overlooked layer, and also the one that makes many predictions go wrong.

Layer three is teams and players. This is the densest data layer. One needs the roster, roles, form, and a metric set specific to each title, including kill counts, opening-fight rates, and resource-conversion efficiency. One also needs information on the head coach and the coaching staff. If not a single player name exists, every judgment about roster strength is mere guesswork. This is where I always slow down. A single number is an accident. A cluster of numbers is a confession. But before there is a cluster, there must be a name.

Layer four is the regional picture. Regional strength depends on the title, so it cannot be generalized. One needs international results, the talent pool, academy output, and the flow of imported players. A region strong in one title can be weak in another. Skip this layer, and a writer easily imposes regional rankings by gut feeling.

Layer five is club finance and business. One needs sponsorship revenue, distributions from the league or publisher, salary costs, and capital backing. Without these numbers, one cannot know whether a team is losing money or being funded. This layer is often seen as secondary, but in reality it explains many roster decisions.

Layer six is rules and governance. One needs to know which rule system governs: the publisher, the tournament organizer, or national regulation. One must screen issues such as competitive integrity, transfers and registration, contract enforcement, and protection of underage players. This is the least discussed layer in mainstream media, yet it is the layer that can cost a team its tournament slot after a single administrative decision.

Layer seven is the risk profile. It synthesizes the six layers above into a matrix: competitive, financial, personnel, rules, public opinion, and systemic risk. Each risk needs a level, probability, impact, and mitigation. This is the layer most likely to become ritual, because if the layers below are empty, the risk matrix is just a grid of squares.

Layer eight is public narrative and expectation. One needs to identify where sentiment is hot, and how far market expectations diverge from reality. This layer explains why a team can be inflated and then burst. In Vietnam, where the esports community reacts very fast on social media, this layer is almost always on.

Layer nine is industry transmission. This is the most macro layer, linking three stages: upstream is the publisher and the licensing of patches and events; midstream is clubs, tournaments, and streaming platforms; downstream is sponsorship, derivatives, and the degree of mainstream integration. Without at least one named actor, the transmission path cannot be drawn.

Walking through all nine layers reveals one thing: each layer is an anchor to raw data. Without raw data, there is no anchor at all. A framework does not create understanding; it only keeps understanding standing upright. That is why a report with all nine layers but empty numbers is the clearest example that a framework cannot save the content.

The counterintuitive angle: the prettier the framework, the better it hides the emptiness

Most readers believe a structured analysis is a good analysis. Twelve pages, nine sections, neatly aligned tables, it looks professional. But structure is not evidence. A beautiful framework can conceal the fact that there is nothing to say, like a stage carefully built but with no actors.

Two traps come with it. The first trap is filling empty cells with speculation. When a cell lacks data, the instinct of an inexperienced writer is to fill it with a plausible-sounding guess. With a language model, that temptation is even stronger: it can invent team names, player names, and patch numbers to fill the table. Those fabricated data then contaminate every layer below, and the error spreads like an oil slick. This is the most serious risk, and the only way to block it is a hard rule: analyze only what is actually present.

The second trap is mistaking correlation for causation. A team that wins after changing its coach does not mean the coaching change caused the win. A player with a high metric in one match does not mean he is the cause of the victory. To separate correlation from causation, one needs a large enough sample and enough control variables. The nine-layer framework exists precisely to remind us of this: every conclusion must ask itself how many data points it rests on.

I do not write to be agreed with. I write to be verified. A conclusion that cannot be refuted by data is a worthless conclusion. And a framework that cannot be toppled for lack of data is an incomplete framework, it needs one more step: checking the input before analysis begins.

A crisis does not create a phenomenon. It only exposes data that was ignored. A process that returns an empty result is the same: it does not create a problem, it only exposes that the extraction layer has failed, or that the original article contained no substantive sports content. The source may be locked behind a paywall, it may be only an index page, it may be a short brief carrying no data. Whatever the case, the task is not to force layer two to keep running, but to go back and fix layer one.

An anchor point for the next cycle

The minimum list for a nine-layer analysis to begin is very short: one game title, at least one named actor, at least one information point with a source, patch information if the piece concerns meta, tournament name and format if the piece concerns an event, plus two assessments of source quality and time sensitivity. Six items, no more.

What is notable is that the very empty report became, unintentionally, a useful checklist. It shows that a good process must be able to say "no" to itself. In an industry where transfer rumors travel faster than data, the ability to say "insufficient information" is a skill, not a weakness.

The crowd watches the scoreline, while my job is to watch the rest of the bracket, and that rest exists only when someone is willing to count again from the beginning. Next time a nine-layer analysis is presented, the first question should be: what does layer one have. If the answer is nothing, then every layer above is just a beautiful building standing on sand.