Name the Game Before You Name the Winner

At three in the morning, in a small studio down an alley on Nguyen Dinh Chieu Street, District 3, I sat in the last row, the seat I have kept for nine years in this trade. In front of me lay an open notebook, and that blank page had stayed blank for forty minutes. On the big screen, a match had just ended. The rapid clatter of mechanical keys, the drag of swivel chairs on the floor, then everything sank into silence. I waited. I did not write. The match was not dull. I simply had not yet worked out which game I was watching, which tournament, which patch, and which team was actually playing. For a sportswriter, a blank notebook has never been a sign of laziness. It is a reminder: the first beat is not made with the feet, but with the ears.

The esports news industry in Vietnam is moving faster than ever. Every evening there are dozens of matches across many different games, and each match has its own loyal audience, its own comment community, its own vocabulary. Writers are pushed into a spin cycle: file within hours of the final whistle, have a headline, have a conclusion, have numbers. And in that spin, the easiest way to fill the page is with vague lines: team A is tactically stronger, team B lost on mentality, player C is past his prime.

There is a paradox in how this industry works. The more games there are, the more writers tend to write the same way, because writing the same way is faster. A single match result gets repeated across dozens of articles, and gradually the name of the game is dropped, as if every reader already knew it. But not everyone knows. A newcomer who enters a community and reads an article with no game title will misunderstand from the start, and that misunderstanding follows them for a long time.

I understand why people write that way. I wrote that way myself in my early days with a pen. But then I realised something: esports is not a single sport. It is an umbrella over many different sports, and each one runs on its own logic. League of Legends has regional league systems, champion balance patches, the rhythm of mid lane and jungle. Counter-Strike has round economy, map control, the power of each weapon. Dota 2 has the complexity of items and power spikes. Valorant blends shooting skill with ability usage. PUBG and Free Fire tell their stories through the shrinking circle and survival. No single analytical framework works for all of them.

That is why I begin every article with a very simple question, one many people skip because they think it is obvious: which game is this?

An esports writer must name the game before naming the winner, because everything that follows — how to read the numbers, how to understand the tournament, how to judge a player — depends on that game. This lesson came to me from football, during the years I sat taking notes at FC St. Pauli's training ground, before I moved into writing about esports.

In football, you cannot judge a defender by goals scored. In esports, the same principle is even stricter. The KDA ratio — kills, deaths, assists — means very different things for a mid laner in League of Legends and a support in the same game, to say nothing of how nearly meaningless it becomes when compared with a Counter-Strike player. In Counter-Strike, people look at average damage per round and the rate of successful opening duels. In Dota 2, people look at gold per minute and the timing of key items. An analysis that mixes these measures will fail from its very first sentence.

The same holds for tournament systems. A double-elimination bracket is entirely different from a round-robin points league, and both differ from a Swiss format. The number of games in a series — one, three, or five — decides the probability of an upset. In a single-game series, one lucky play is enough to swing the whole thing. In a five-game series, true strength has time to show itself. If I do not know the game and the format, I have no basis to say whether a weaker team can beat a stronger one.

When I sit down before a match, I check three things before writing anything. The first is the game title and the version being played. The second is the format and the number of games in the series. The third is the timing, because a balance patch can completely change how a team plays within just a few days. Those three things are not glamorous, but without them every judgement that follows is shaky. I learned to check the origin of information — the official tournament page, the publisher's patch notes, a specific publication date — rather than trusting a reposted article of unclear origin.

In Vietnam, this becomes even clearer when you look at how diverse the communities are. Some fans follow a single game for years and understand it more deeply than any journalist. Others read esports news the way they read general sports news, and they are easily persuaded by grand conclusions. The writer stands between those two groups. Write vaguely, and the deep fans leave while newcomers are misled. The only way to serve both is to speak the correct language of the game you are writing about.

I remember once rewatching a match in which the underrated team won. Every comment called it a miracle. But when I rewatched it minute by minute, I saw that the weaker team had pressed very high, forcing their opponents to rotate and make mistakes. The so-called miracle was in fact the consequence of a specific plan, executed down to the last footstep. But to see that, I had to know which game I was watching, because pressing works differently in each one.

I do not analyse matches; I remember every face when the match ends. And to remember correctly which face did what, I have to name the arena they were standing in.

There is a small detail I always note down: the moment a player turns his head to check on a teammate before making a decision. In one game, that movement is mandatory. In another, it is nearly meaningless because the information is already on screen. The same behaviour, two entirely different meanings. Without telling them apart, I will praise the wrong thing, or blame the wrong thing.

In an analysis, I always leave a trace of the source. A specific date. A specific fact. A specific event. Readers need to be able to verify what I write, because if they trust me blindly, I have turned myself into a poor source.

Outsiders often think that an analyst who says "not enough information to conclude" is a failed analyst. They believe a good writer is one who always has an answer, always has a conclusion, always has a punchy closing line. That view sounds reasonable, but it places trust in the wrong place.

In my work, the hardest moment is not when I have to write a good conclusion. The hardest moment is when I have to stay silent while everyone around me has already begun assigning blame. After a loss, people want someone to be responsible. They want a player named, a coach blamed, a decision called a mistake. If I join in, I will immediately have an article that gets shared widely. If I wait, I will have an article fewer people read but a more accurate one.

The difference between a hot take and a useful analysis lies here: a hot take answers the question of who is at fault, while a useful analysis answers the question of what happened and why. The first question is easy, because it needs only a name. The second is hard, because it needs data, a game title, context, and time.

The beat keeper never stands in the middle of the pitch. I choose to stand at the edge, where I can see both the formation and the gaps between positions. Standing in the middle is noisy, but the view is narrow. Standing at the edge is quiet, but it reveals the whole flow. And sometimes the most correct thing a person at the edge can do is write one line in the notebook: not enough data.

We watch the match, but we live in the silence between matches. That silence is where data is checked, where the game title is confirmed, and where hasty conclusions are held back before they can wound a human being. When the stadium is empty, I understand who I am keeping the beat for. I keep it for the young players who will read my article again on some sleepless night, not for the algorithm or the share count. If I name their game correctly, I have respected them once. If I name it wrongly, I have failed them once. The first beat always begins with naming the right thing.