The Discipline of the Void: When an Esports Analyst Has to Say 'Insufficient Data'

One October night in Boston, I opened a spreadsheet a colleague had sent over and found all 47 rows carrying the same value: insufficient information to assess. The framework spanned nine blocks — game patch and meta, tournament format, roster and players, regional landscape, club finance, governance compliance, risk profile, public narrative, and industry transmission. All nine were blank. The only label left on the input was a single word: esports.

The editor sitting opposite me asked the most ordinary question in the trade: "So what goes into the conclusion?" I remember my fingers stopping on the keyboard. In this line of work a blank table always offers two exits: fill it with language that sounds reasonable, or close it and say plainly that there is nothing to say. The first exit pays faster. The second one keeps the craft.

Vietnam is one of the most-watched esports markets in Southeast Asia. VCS, the country's top League of Legends competition, has sent GAM Esports to the World Championship several times. Mobile titles such as Arena of Valor draw crowds large enough to fill an indoor arena, and organisations like Saigon Phantom and Team Flash have built loyal followings across multiple seasons. At recent SEA Games, esports featured as an official medal event, with Vietnam regularly in the medal-contention group.

Audience density, however, does not produce data density on its own. Most information about Vietnamese teams comes from three sources: organiser announcements, player interviews, and community speculation. Match-level metrics — objective control rates, teamfight efficiency by game phase, the ability to convert an early lead into a result — are rarely published as a systematic series. An analyst working inside the country who wants to do the job properly usually has to build the database by hand, and most working hours disappear into patching those holes rather than answering the professional question.

On the revenue side, most of a domestic esports team's budget comes from sponsors and commercial activity, with a smaller share from prize money and redistributed media-rights income. Cash flow depends on media presence, and media presence depends on publishing rhythm. That pressure lands directly on the analyst's desk: every day without a piece opens a gap, and a gap is always filled with the easiest thing to produce — a prediction.

Discipline lives there, not in the tooling. An analysis is only credible when every conclusion can be traced back to a specific data source; when that source does not exist, the only correct conclusion is a declaration that no assessment is possible. It sounds obvious, yet in practice it is the hardest sentence to write. It forces the writer to separate two entirely different things: an absence of data and an absence of signal.

The case in front of me belonged to the first kind. No tournament name, no team name, no player, no patch number, no financial figure. Nothing from which to reason about the direction of the meta, the fit between a roster and a new patch, format or schedule density, club financial health, compliance risk, or the cycle of a public narrative. Any judgement produced under those conditions would be a product of imagination, not of analysis.

Walking mechanically through each block produces the same result. Without a specific patch you cannot describe where the meta is heading, who benefits and who suffers. Without a tournament name you cannot assess format, series length, schedule density, or the qualification path. Without a roster you cannot compare paper strength, role fit, or bench depth. Without a region you cannot map the relative standing of different scenes. Without contracts or salary figures you cannot say anything about an organisation's financial health. Each empty cell is a closed door, and counting how many doors are shut is itself the job.

What matters is that the emptiness was itself a signal. When an extraction process returns a domain label with no data points attached, the problem sits in the process, not in the market. Missing data is not useless; it is a map pointing to the places nobody has measured. A blank table told me the collection system was broken, that someone had assigned the work but forgotten to supply the raw material, and that a gap exists between where data is generated and where it is used. Those three facts are worth far more than a long commentary on a tournament I never watched.

Based on my experience tracking matches and transfer windows, most mistakes in this industry do not come from misreading numbers. They come from reading an incomplete table as though it were full. In 2026 I built a database myself, tracking under-21 midfielders with fewer than 500 league minutes but high pressing indicators. The output was a 47-page report on Morten Hjulmand, then 21 and playing for a small club in Austria. I sent it to three clubs; one replied. Two years later the player moved to Serie A.

Reading that report again today, the most valuable section was not the praise. It was the pages listing what I could not measure: the quality of the teammates around him, the effect of a change in tactical system, his capacity to handle media pressure in a larger market. I did not know those things. Writing down that I did not know them is precisely what let the report hold up under questioning.

The second lesson cost more. In the 2026-23 season, running transfer strategy for a club in Boston, I chased a Brazilian full-back across three transfer windows with a budget of 2.4 million dollars. I built an almost complete analytical frame: technical metrics, physical profile, even family circumstances. Another club signed him within 48 hours. The board told me plainly that a perfect model does not exist and that timing is itself a variable. That is when I understood that the true value of a deal only becomes visible once the market stops making noise — but the market will not wait for anyone to finish their model.

All of this is to say that declaring "insufficient data" is not a virtue in itself. It is a tool, and any tool can be abused. In many organisations, "not enough data yet" has become a shield for delay: nobody is punished for failing to decide, while whoever decides badly carries the blame. The result is analytical departments full of methodologically sound reports that are useless at the moment they are needed. We do not need more data. We need better questions, so the data we already have can speak.

The counter-intuitive part is this: esports does not lack data the way people assume. It lacks the discipline to accept empty results. A single tournament can generate thousands of hours of footage, yet if nobody publishes the failed analyses — the cases where data was too thin to conclude, the deals missed because of delay, the models that predicted wrong — then every new generation of analysts starts from the starting line again. We archive victories and delete the gaps. Then we wonder why the same category of error returns a few seasons later.

There is one more point that few young operators want to hear. A strong team is not created by owning a handful of exceptional individuals. A system does not create genius; it only creates the room for genius not to be suffocated. At the analytical level the same rule holds: good conclusions come not from having a great deal of data, but from having a process clean enough that the data is not bent toward what the client wants to hear. A blank table published honestly serves the system better than a full table produced by inference.

That leaves a question for the people running Vietnamese esports: if domestic organisations started publishing the times they did not have enough data to conclude — scouting reports with no result, failed transfers, metrics they cannot measure — what would happen to the learning speed of the whole scene? There would probably be fewer articles. Probably fewer views in the short term. But a gap named honestly is always where the next piece of valuable data begins.