Nine Data Dimensions and a Blank Page: The Discipline of Verification in Esports Analysis

At three in the morning in Penang, I reopened the analysis file I had been building for two weeks. Nine pages, each page a dimension of data: patch, tournament format, roster, regional landscape, club finances, rules and governance, risk profile, media narrative, and the industry's transmission chain. All nine pages were blank. The only cell with text was the one labelling the domain: esports.

Six years in this trade, and I had never seen a sheet like that. The daily work is pouring numbers into a sheet: win rate by patch, pick-ban rate, gold per minute, teamfight count, win rate after taking a major objective. This time there was nothing to pour. My first reaction was not "what do I write" but "why". An empty dataset is not neutrality — it is a warning signal, and how an analyst reacts to it decides the entire value of the report.

This nine-dimension framework is not my own invention. It grew out of a habit that started in 2026, when I was fourteen and sat counting Luka Modric's running distance by hand in the World Cup semi-final between Croatia and England. Modric ran 11.7 kilometres and made only one tackle. I rewatched that match 47 times, and each time the data told a different story. When I moved into esports, that question followed me intact: a high number does not necessarily say anything, and a low number is not necessarily a bad sign.

The esports analysis industry runs on a fairly stable nine-dimension framework, and I use it for every report. Each dimension answers its own question, and no dimension is allowed to substitute for another.

The first dimension is the patch. League of Legends ships an update every two weeks; Dota 2 ships updates less often but with far larger swings. That cadence shapes how a team prepares: on a two-week cycle, the team that learns the meta fastest gains in the group stage; on a slow cycle, one big update can wipe out a champion pool a team spent months building. That is why I always note the tournament server version beside every win-loss figure. A 62% win rate on the old version does not carry over to the new one.

The second dimension is format. Single elimination produces a far higher upset probability than a double-elimination bracket, while a Swiss group stage rewards teams with a wide tactical pool. When I assess title chances, I split the question in two: how strong is this team, and what kind of strength does this format reward? The third dimension is the roster. The performance curve by career age in esports is far steeper than in football, yet Lee Sang-hyeok debuted in 2026 and still competes at the highest level more than a decade later — a case strong enough to break any model built on birth year alone. Form lives in the number of high-quality practice hours and in whether a player is allowed to play to their strengths.

The fourth dimension is the regional landscape. Strength in one title says nothing about another, because the talent pipeline, the number of domestic events and the import policy differ by game. The import quota is the biggest variable almost nobody factors in when predicting regional results. The fifth dimension is club finance, with four lines that must be kept separate: sponsorship revenue, publisher distributions, salary spend, and owner capital. A club that looks healthy because its wage bill is low can still collapse if its revenue depends on a single sponsor.

The remaining four dimensions close the loop. The sixth is rules and governance: competitive integrity, transfers and registration, contract compliance, protection of minors. The seventh is the risk profile, split into competitive, financial, personnel, legal, reputational and systemic risk. The eighth is the media narrative, measuring the gap between community expectation and measurable strength. The ninth is the transmission chain, from publisher down to clubs, streaming platforms, sponsors, and finally the degree of penetration into the mainstream sports current.

Those nine dimensions need a minimum of three data points to start running: the game title, the tournament, and a time marker. This time we had exactly one: the domain label. No game title, no tournament, no team, no player. When I cross-checked two sources as usual, both returned identical blanks. On a sheet like that, every conclusion I could write would be fabricated — and a fabricated conclusion in this industry can become the basis for a transfer decision.

This is the most dangerous place, and it is counter-intuitive. An empty compliance checklist is not a clean bill of health. When the transfer-rule compliance cell has no data, the correct status is undetermined. Many reports in the industry write "no violation detected", and readers translate it into "no violation exists". A lack of information is never evidence of compliance.

The second mistake is more common: reading a champion's post-patch win rate as causation. A champion's win rate can rise because the champion was buffed, because its counters were nerfed, because a strong team suddenly added it to its pool, or simply because the sample size is still too small. There are two things that never lie: data and time. But data is only honest when we ask it the right question. The numbers never panic — panicking is what turns a person into a variable.

I spend most of my writing time cross-checking sources, ever since I pushed back on a European analytics company during Euro 2026. They concluded that Germany had lost its high pressing. Rebuilding the raw data, I found they had missed six acceleration runs by Jamal Musiala because those runs did not end in a pass. Those six runs were not inside their definition, but they were inside the match. Before you trust your eyes, check what your eyes already decided to believe.

What I take into the next analysis cycle sits at step zero: before pouring data into any framework, check whether the framework has anything to hold. A good pipeline should reject empty inputs at the door instead of letting them flow downstream and turn into conclusions that look complete. In esports, where a patch can decide a championship and a transfer slot can decide a team's fate, caution at the first step is far cheaper than correcting a wrong conclusion later. If your analysis framework returns a blank page, will you keep writing, or will you stop and go find a source?