Vietnamese Esports Analysis: Step Zero and the Discipline of Data

One evening I had seven browser tabs open at once. A domestic league standings page, a match statistics site, a note about the latest patch, and four "analyses" circulating in Vietnamese esports community groups. Those four pieces were long, eloquent, drenched in emotion. They talked about form, about nerve, about the shining moment of a single play. But by the last line, I realized none of them said which patch the match was played on. None identified which game was being discussed, which metrics are standard for that game, or where the data came from. I closed them all and wrote a line in my notebook: four more unverifiable articles today. An analysis without a data foundation is not analysis — it is an opinion dressed up in terminology. That is why I want to talk about something rarely mentioned in Vietnamese esports analysis: process. Before debating which team is strong, before arguing over who will be champion, an analyst must answer six foundational questions. Which game? Which patch? Which tournament, at what tier, with what format? Which entities are involved — teams, players, coaches, organizations? What is the time anchor? And is the source trustworthy? Skip these six, and every conclusion that follows stands on air. In esports, these six questions matter even more because they differ sharply across titles. Tournament systems, metric sets, and even business logic vary enormously. KDA, Rating, pick-ban rate — each game defines them differently. You cannot take one game's yardstick, apply it to another, and call that analysis. Vietnamese esports is at a stage where the volume of content grows faster than its quality. Domestic tournaments draw hundreds of thousands of viewers, teams have passionate fan bases, but the public data infrastructure remains thin. That is fertile ground for emotional takes. The worrying part is that public data at many domestic tournaments is still not standardized. Each statistics platform defines a metric its own way, each record differs. When sources don't align, the analyst must keep manual records — time-consuming work that cannot be skipped. I once spent four hours on a single match just to normalize the metrics. That is the price of honesty. People call me a "number nut"; I take it as a compliment — because correctly classifying numbers has saved me from many wrong conclusions. Picture a nine-layer analytical framework I use for every major tournament. Layer one is patch and meta. Every time a publisher ships a patch, some gain and some lose. The question is not "is this patch strong or weak" but "which playstyle does this patch favor, and which team owns that playstyle". Without win-rate and pick-ban data, any claim about the meta is just a guess. Layer two is tournament format. BO1 differs from BO3 differs from BO5; round robin differs from a knockout bracket; schedule density decides both fatigue risk and preparation advantage. A team strong in short series can collapse in long ones, and vice versa. Ignore format, and you will misread the cause of a defeat. Layer three is teams and players — paper strength, role fit, roster chemistry, and bench depth. A headline signing can break the locker-room balance if it doesn't fit the role. Layer four is the regional landscape: which scene sits on top, which is closing the gap, which way the flow of imported players is heading. Layer five is club finance: sponsorship revenue, publisher distributions, salary budgets, and risk signals such as unpaid wages or dissolution. Layer six is rules and governance: competitive integrity, transfer regulations, protection of underage players. The last three layers are the most neglected. Layer seven is the risk profile — and I rank input-quality risk above all. If the underlying data is wrong, every conclusion is wrong, no matter how elegant the reasoning. Layer eight is public narrative and expectation: what the crowd expects, and whether that expectation is backed by fundamentals. Layer nine is industry transmission: from publisher, through clubs and streaming platforms, down to sponsorship and derivative markets. It sounds like a lot, but the operating principle is compact. For each layer, I ask three questions: what data supports this claim, what other hypothesis could explain the same data, and if I am wrong, where am I wrong. Those three questions turn a commentary into an experiment. They force me to separate fan emotion from the variable to be explained, rather than treating emotion as something to judge. A fervent crowd is not the enemy of analysis; it is an indicator to read. Take an illustrative example. Suppose a Vietnamese team wins three matches in a row after a patch goes live. The emotional reading says: "this team adapts to the meta fast". The disciplined reading asks: were those three opponents strong or weak, was the schedule congested, did the team change its playstyle or just exploit the opponent's mistakes? If the pick-ban rate shows the team still uses the same old champion pool, then the run likely comes from opponent quality, not the meta. The same winning streak, two opposite conclusions — and only data can adjudicate. On the regional landscape, I always ask where Vietnamese esports stands on the map. The gap with leading scenes lies not only in skill but in infrastructure: youth development systems, the quality of opponent analysis, and the ability to retain players. Those signals don't show up on the scoreboard, but they decide results two to three seasons out. A strong esports scene is not measured by one championship, but by its ability to keep producing competitive teams. On finance and governance, this is the zone fans rarely see yet it directly affects on-stage results. A team paid late plays differently from one paid in full; a changed transfer rule can upend an entire roster plan. I treat these factors as part of the analysis, not backstage gossip. Here I must say something not everyone wants to hear. Most popular "esports analysis" in Vietnam today fails not for lack of inspiration — it fails for lack of step zero. Writers jump straight from observation to conclusion, skipping the identification of game, patch, format and source. The result is claims that sound certain but cannot be verified, and worse, cannot be reused for the next round. But I also don't want to fall into the opposite trap: believing that numbers equal truth. Correlation is not causation. A team that wins after changing coaches did not necessarily win because of the change — it could be an easier schedule, a rival losing a key player, or simple luck in a small sample. The only way to tell is to state an alternative hypothesis and interrogate yourself before publishing. The match ends, but the data remains — and data is only worth something when we read it honestly. I wrote a blog from a rented room in Nha Trang; now probability takes me everywhere. But precisely because I have gone far, I must hold even firmer to the discipline of step zero. An analysis that cannot name the game and patch is not a poor analysis — it is not yet an analysis. And when an entire community skips that step, the danger is not a few wrong articles, but that the correct standard is gradually lowered. The next round will come again, and again someone will open with a conclusion instead of data. An empty arena doesn't need spectators; it needs an analyst willing to look. I don't expect every esports article to be nine layers deep. But I do expect that before speaking, a writer pauses for a second to ask: which game am I talking about, which patch, and based on what data. If the answer is "I'm not sure", then staying silent for one more round is an honest choice. Because in analysis, the worst thing is not being wrong — it is being certain about something you have never verified. The question I leave is not "which team will win the title", but "are you establishing the right data foundation before you speak".