The Nine Layers of Verification Behind an Esports Analysis

One in the morning in Busan, I rewound a recording of a post-match panel. On screen, three people discussed a team's defeat. None of them opened a stats sheet. The most-used phrase was "mentality". Nobody mentioned pick-ban rates, nobody mentioned the patch, nobody asked how many series that team had played that week. The panel ran forty minutes and closed with a confident verdict. I turned off the screen and opened my data file. That habit has followed me through eleven years in this trade. Before debating wins and losses, I question the numbers first. One thing troubles me more than hasty conclusions. It is how people handle gaps in data. When information is missing, most writers fill the gap with a story. I write down that I do not yet know. That sounds weak, but it is the line between analysis and speculation. I was born in Vietnam and work in South Korea, reporting esports for the local market. My job is to turn advanced metrics, patch history and tournament structure into readable stories. But the foundation of this craft, which I learned years ago, is not in the prose. In 2026, as a second-year student in Busan, I fed every shot of a major match into an xG model I had written in Python. The result showed that the eye is easily deceived. The team presumed to be attacking relentlessly had in fact taken most of its shots from outside the box. The losing side had created the better chances. That lesson shaped how I view every discipline, esports included: the feeling of a match and the substance of a match are two different things. Esports poses a harder problem than football in one respect. Here, the publisher itself changes the rules every few weeks. Each patch can overturn a power hierarchy that took a whole season to build. A champion loses damage, a map is adjusted, a mechanic is removed. Each meta update is a confession from the publisher. So I built myself a framework of nine layers. Each layer is a question that must be answered before I allow myself to write a judgement. This article lays out that framework, how it operates, and what happens when a layer is left empty. The first layer is patch and meta. Before discussing any team, I identify the game, the version number, and the specific element changed. The magnitude of change falls into three grades: a small numeric tweak, a mechanic adjustment, a full rework. I need at least one source: official patch notes, pick-ban rates, or a win-rate delta before and after. Without these, any meta conclusion is just a feeling. The second layer is tournament system and format. A BO1 is entirely different from a BO5 in terms of upset probability. Swiss differs from double elimination in how a team can correct mistakes. I need the event name, its nature, the series length, the qualification path and the schedule density. Density matters most. A team playing three series in four days shows different signals from one rested for a week. Attributing those differences to "form" is the most common misreading I have seen. The third layer is team and player. This is the layer the public cares about most and simplifies most. I assess a team along four axes: paper strength, role fit, chemistry, and bench depth. Chemistry needs tenure data, not a list of names. Bench depth needs a full roster, including those who rarely play. For each player I track the form curve and one crucial rule: metrics are not comparable across positions. A jungler and a mid laner bring different value; setting them side by side to judge who is better is a methodological error. The fourth layer is the regional landscape. A region's strength must be assessed title by title, because the same region can be strong in one game and weak in another. I compare regions by international results, talent pool, academy output and ecosystem health. Import flow is a more reliable signal than any statement. When teams in one region start importing from elsewhere, it marks a gap being filled with money. The fifth layer is club finance and business. I break revenue into sponsorship, league and publisher distributions, salary costs, and capital injection. For each deal I ask two questions: what is the real number, and how far does it sit from competitive value. A transfer fee does not measure talent; it measures the buyer's hunger. The same player can be valued very differently depending on whether the buyer is desperate for a role or racing for brand. Risk signals such as unpaid wages, dissolution, or slot sales must be raised when they exist, not when they are mentioned. The sixth layer is rules and governance. Each title has its own rule system, with authority resting in different hands. Conduct banned in one league can be valid in another. I check five points: competitive integrity, transfer and registration rules, contract compliance, minor protection, and publisher governance disputes. Here I am especially wary of one trap. Not seeing signs of violation does not mean everything is clean. The silence of data is not a verdict of innocence. The seventh layer is the risk profile. I split risk into six categories: competitive, financial, personnel, rules, public opinion, and systemic. For each I note level, probability, impact and mitigation. A systemic risk is far more frightening than any competitive risk, because it lies in no team's hands. A fault in the data-collection layer can collapse the entire downstream chain. The eighth layer is public narrative and expectation. Every period has its own storytelling motif: a new king crowned, a dynasty succeeded, a veteran's last dance. My job is to measure what foundation that story is fed by. I check sample size, check the durability of the claim, and compare market expectation with objective assessment. The gap between the two is where backlash risk is born. When a player like Faker sustains a peak for over a decade since his 2026 debut, the story about him has a real foundation. Most other stories do not. The ninth layer is industry transmission. I map the chain from upstream publishers, through midstream clubs, events and streaming platforms, down to downstream sponsorship, derivatives and mainstreaming. Every upstream change ripples downward with different lags. A publisher decision can take months to reach a team's payroll. Seeing that lag is the greatest advantage a data practitioner has. These nine layers sound long, but they were not written to show diligence. They exist to answer a single question: what ground is my article standing on. There is an uncomfortable truth about this craft. Most wrong conclusions do not come from misreading data. They come from leaving a layer empty and filling it with intuition. The writer sees team A lose, sees team B win, and connects the two events with a story about grit. Nobody checks whether team A was playing on an old patch while team B had trained three weeks on the new one. The contrarian point lies here. The public believes more data yields truer conclusions. In one important respect the opposite holds. More data without stratification creates an illusion of control. People start treating correlation as causation. A team wins more when a certain champion is in the lineup, and they conclude that champion is the key. But correlation is not causation; that champion may simply be favoured by the strong teams. I once saw this at scale. In 2026, when leagues returned before empty stands, I collected over a hundred matches and found home advantage had dropped sharply. I finished a long report and drew a conclusion about crowd contribution. But I also stated the error margin and sample size. Had I turned that figure into dogma and ignored its limits, I would have destroyed the very foundation I had built. That lesson applies directly to esports. Historical data can become meaningless after a major patch. A small sample of a few matches cannot judge a roster. A blowout win proves nothing if the opponent fielded a substitute lineup. The writer has a duty to say so, instead of collapsing everything into a neat label. The principle I most want to stress is how to handle gaps. When a layer has no information, the correct answer is "not enough data to assess". In my analytical table, gaps are flagged clearly, not filled with speculation. Failure to detect an integrity risk does not mean there is none. Failure to see negative financial signals does not mean the club is healthy. The silence of data is just silence. And this is what I want readers to carry away. A good analysis is not the one with the most conclusions. It is the one that knows exactly where it does not know. I do not write about football. I write about the light that data illuminates. Esports is the same. That light only reaches the places where I have built all nine layers of foundation. The next round of the season is coming, with a new patch. I have started loading the data. The question I ask myself now is simple: which of the nine layers will decide the hierarchy this time, and do I have enough evidence to speak about it yet. If the answer is no, I will write exactly that. Will you choose to read the conclusion, or to see the foundation it stands on?