When a 14-Page Analysis Cites Nothing

On 12 March 2026, at a cafe in Mapo-gu, Seoul, a data analyst for an LCK team I had followed for six years slid a 14-page document across the table. Page three was packed with 60 columns of metrics: gold difference at 15 minutes, major objective control rate, wards placed per minute, recovery time after teamfights, win rate after taking the Rift Herald. It was laid out so cleanly that I almost nodded. Then I flipped to the bottom row of the table. The source column was empty. No match ID, no match date, no patch version, no tournament name. Sixty columns of data and not one line of provenance. He looked at me: "I know. But my boss needs this before tomorrow morning's strategy meeting." I took the document home and read it four times over two days. Every metric in it could be correct. I had no way to prove it and no way to disprove it. That is the worst state a writer can be in: holding something that looks perfect and being unable to verify a thousandth of it. Korean esports analysis left the manual era long ago. In the LCK, almost every team has its own data department, people reviewing VODs, people running numbers after each round. The annual season, with its two-matches-a-week rhythm, produces a continuous stream of data, and that stream creates a paradox: the more numbers there are, the fewer people stop to ask where they came from. I once sat in another team's meeting room and heard a coach say something I wrote straight into my notebook: "I don't need to know where it came from. I just need to know it's right." The trouble is that in this profession those two things cannot be separated. Everything began with a promise made in 2026. In March 2026, when I was a young reporter covering a football club in Seoul, I mispronounced a young player's name three times in a single live broadcast. He scored the only goal of the match in the 78th minute. Afterwards, I apologised to him in the stadium corridor. He smiled: "Just write what you saw on the pitch, hyung." I spent the entire following month rewatching every touch he took, noting down his shirt number, his movement habits, even how he celebrated. That 2026 promise is the root of every rule I keep: no provenance, no data. What I cannot source, I do not write. That 14-page document was not the work of one weak individual. It came from three layers of failure stacked on top of each other. The first layer is lost provenance. A metric separated from its source lives on forever in collective memory and, worse, it replicates itself. I have seen identical tables, cell for cell, appear at three different teams in the same season, because all three copied from the same unsourced compilation. One bad copy is enough, and that error outlives a playing career. The second layer is template pressure. A report with nine sections requires a conclusion in every section. Nobody accepts a section that says only "insufficient data to assess." But in this line of work, that is often the most honest answer. When a template forces a writer to speak in every box, it quietly teaches the writer how to fabricate. Fabrication here is not blatant lying; fabrication is filling a plausible-sounding judgement into a space where a blank should be. The third layer is the most dangerous: mistaking silence for safety. In a risk table, an empty box does not mean "no problem." An empty box means "nobody has checked yet." In the LCK and its sibling leagues, three lethal risk categories — unpaid wages, match-fixing, unhealed injuries — share one trait: they do not emit their own signals. If the people handling data do not go looking, they stay in the empty box and look exactly like safety. The locker room is where I learned to be silent. But silence is for hearing the whole thing, not for avoiding a verdict. When I sat in an arena corridor at 23:40, waiting for a player to emerge from a three-hour meeting, I was not silent out of fear. I was silent because I was waiting for the last fact to fall into place. When it does, I write, even when the conclusion offends someone who trusted me. There is an occupational trap I have to remind myself of every week: do not mould esports into the shape of another sport. I come from football, and the biggest temptation is to explain a digital match as if it were football played on a keyboard. That approach erases esports' own rhythm. Where does that rhythm live? It lives in the fact that esports analysis only means anything when it is anchored to a specific title. The tournament system, the metrics, the business logic and even the governance structure of League of Legends differ completely from Dota 2, from CS2, from Valorant. A judgement about regional strength in one title cannot be carried into another. A writer who skips that anchoring step produces prose that sounds very confident and cannot be verified anywhere. It also lives in the concept of version lock. Professional tournaments play on a pre-locked patch, while the public server fans play on has already moved several weeks ahead. Any conclusion about champion strength, pick-ban rate or composition efficiency has to be tied to a version. Remove that line and the table still looks good — except it is describing a different game. And it lives in sample size. An LCK round produces far fewer matches than a football round. When someone makes a claim about a team based on four games, I always want to ask: who were those four games against, on which patch, and was any of them played at an unusual hour? Four games can be the start of a trend, or they can be four coin flips. I once followed a team's run in 2026, from the play-in stage to a world championship. The biggest lesson was not the fairy tale. The lesson was that before every round, the crowd's predictions and the actual results diverged enormously, and most of that divergence came not from tactical mystery but from people evaluating that team with data from an older patch. There is a class of composite metric I trust less and less: metrics invented to replace judgement. In football it is expected goals. In esports it is the composite that folds dozens of variables into a single score and is then cited as if it explained why a match was won or lost. Such metrics can describe outcomes; they cannot explain decisions. A fight at 28 minutes is decided by whether the shot-caller says back off or go in, and no composite metric records that moment. I do not write about what the audience sees; I write about what they never get to see in time. The problem is that the market rewards confidence, not provenance. A piece opening with "according to data I collected from 42 games on patch 14.5, 17 of them featuring Team X" will get fewer readers than a piece opening with a tidy, unsourced assertion. The readers are not wrong. They are simply reacting to the signal this industry has emitted for years: whoever speaks with certainty is believed. In Korea, I saw that mechanism most clearly in 2026, when the LCK had to move online and the stands were completely empty. No cheering, no crowd, no atmosphere. During that period, some of the media pressure disappeared, and problems that had been drowned out by cheering began to surface: psychological strain, family pressure, quiet partings. I kept one team captain's story confidential through that whole pandemic season and instead wrote about players' mental health. I still believe that was the right call. But I also ask myself: without that season of empty stands, would those problems ever have been looked at directly? In November 2026, I held information about a closed meeting between a player's agent and a European club, mid-tournament. I waited. I waited until that national team won its decisive match, until the fans had their full share of joy, and only then published. The piece reached more than a million reads in 24 hours. The agent called me and said something I still keep: "You are the only person in this business who keeps his word." In Vietnam, where the LCK audience is enormous, the problem gains an extra layer. Most analysis reaches Vietnamese readers through translation. Every time it crosses a language layer, a source line falls away. I once read a translated version of a team's metrics in which the line "data from 12 games on patch 13.19" had vanished entirely. What remained was a single assertion. Six months later, that assertion was being cited as historical fact. If an analysis cannot cite its sources, it should be sent back — out of respect for the reader, not suspicion of the writer. If a section of a report lacks enough data for a conclusion, leave the box empty and write it plainly: insufficient data. Those two words are worth more than any judgement filled in to complete a template. If someone makes a claim about a team's strength, ask three questions: which title, which patch, how many games. I keep these rules for a very personal reason. At 36, I no longer chase daily breaking news. I write to preserve what will still be true after the season ends. A contract has its own pulse, and I simply stand and listen before it touches the ground. If the next generation of writers in Korean esports learns only one thing from us, I hope it is this: curiosity is unlimited, but credibility is finite, and it can only be spent once.