Nine Analytical Dimensions and an Empty File: The Discipline of a Sports Data Writer

On the night of Russia, for the first time, I saw a number that could hurt. On 27 June 2026, I opened a Python file at 3 a.m. in a small apartment in Busan and pasted into it all 23 shots taken by Germany in their match against South Korea. The expected-goals model I had written myself returned 1.32 xG. The actual number of goals was 0. The score was 0-2, with Kim Young-gwon opening it in the 90th+2 minute, Son Heung-min sealing it in the 90th+6, and Manuel Neuer pushing up to the opposition half. Eighteen of the 23 shots, 78 percent, came from outside the penalty area. Watching the footage back, my eyes still saw a team laying siege. Pressure does not equal opportunity. Six years later, an analytics partner sent me an empty file. No tournament name, no team name, no patch, no publication date. The file held only a skeleton: nine analytical dimensions, pre-marked, waiting for content to be poured in. I sent it back. I entered this profession in 2026, first competing in esports and organising tournaments, then moving into esports media. What I carried over was not a record of results but a habit: check the source before saying anything at all. An empty space is not a conclusion. This profession holds a powerful temptation. With no data, we write from feeling. With no tournament name, we call it a major. With no patch, we talk about a shifting meta. With no metric, we talk about form. Those sentences read smoothly, and they are worthless. The nine dimensions I use daily are ordered for a reason. The first is patch and meta, and in esports it must be settled before anything else. Without knowing the game title, you cannot know which metric means anything. KDA in League of Legends, Rating in Counter-Strike 2, pick-and-ban rates under a specific patch — these cannot be converted into one another. Every meta update is a confession by the publisher, but to read that confession you must know which patch is running on the competition server. The second dimension is format. A best-of-one and a best-of-five are not the same probabilistic animal. A Swiss group stage differs entirely from a knockout bracket in how much surprise it permits. A dense or sparse schedule decides which team reaches the knockout rounds with its legs intact. The third dimension is team and player. Here I keep a rule learned from football: never compare metrics across positions. A defender with 92 percent pass accuracy and an attacking midfielder with the same figure are doing two different jobs. In esports the rule is stricter still, because roles shift with every patch. The fourth dimension is the regional picture. Regional strength is specific to each game title, so branding an entire region with a playstyle label is usually an operation with no foundation. The remaining five — club finance, rules and governance, risk profile, public narrative, and industry transmission — all stand on those first four. No foundation, no floors. Rules and governance is the most easily skipped dimension. The familiar risks are dual contracts, long-term deals that lock players in place, approaches to players still under contract, and allegations touching competitive integrity. When this dimension surfaces, it can invalidate the entire technical analysis that follows. When it does not surface, that is not a finding that it is absent. A missing signal is not a missing risk. Before arguing about wins and losses, I have to interrogate the numbers first. The 2026 season forced me to rebuild my entire foundation. K League 1 became the first football league in the world to resume play, and it did so in empty stadiums. The xG model built in 2026 began to drift systematically. I collected 152 matches: the home win rate fell from 46.2 percent in the 2026 season to 31.6 percent. A 40-page report concluded that every 10,000 spectators was worth roughly 0.08 expected goals added for the home side. The 0.08 coefficient does not measure the silence; it measures what we lost. Nobody commissioned that report. I did it for one reason: if the foundation is wrong, everything built on it is wrong too. That error does not show up in a single match. It shows up across an entire season, and it does so quietly. In December 2026 I was assigned Morocco, the first African side to reach a World Cup semi-final. Across three knockout matches, Morocco surrendered 71.6 percent of possession and conceded only one goal, while opponents generated 4.02 xG in total. The figure that stopped me was PPDA 25.1, nearly double the tournament average of 13.2. Yassine Bounou was in goal, Sofyan Amrabat in midfield, Achraf Hakimi on the right. What made the difference was not any individual, but where the whole team chose to defend. PPDA 25.1 — dropping deep is not a concession, it is stretching the pitch. Korean media at the time described Morocco as being pinned back. I wrote the opposite. A team that lets its opponent pass the ball in harmless areas is choosing the venue of the match, not enduring it. Correlation is not causation, and this is where a data writer is most likely to fall. A team winning four straight after changing head coach makes us want to write that the change saved the season. Four matches is a small sample. The opponents may have been far weaker. The schedule may have just opened up. A patch may have just neutralised a style that team never played anyway. In 2026, a sports data company in Lisbon shared the file of a Korean midfielder at a mid-table club. The previous season he played 564 minutes, far below the 1,200 minutes written into his contract. I sent his agent a six-page metrics report stating the sample size, the error margin, and what the data could not answer. On 8 June 2026, I was the first to report the loan deal with a 2.8 million euro buy option. A transfer fee does not measure talent; it measures the buyer's appetite. The 564 minutes do not say the player is poor. They say the observation window is too small to judge quality, and that a gap exists between what the contract promised and what the pitch recorded. An intelligent reader does not need a fabricated conclusion. The industry holds a mistaken belief: that a writer must always have an opinion, that silence is weak, that saying not enough information is a failure. I think the reverse. In the middle of a major tournament, when national-team emotion runs high and every feed is stuffed with metrics cut loose from context, the scarcest thing is restraint. A nine-dimension analysis with no data still has value, provided it declares itself empty: the patch section undetermined, the format section undetermined, the roster section undetermined, the finance section undetermined. That honesty is more useful than a fluent piece padded with speculation. What frightens me is an empty file passing through several hands and reaching readers as a tidy analysis with no trace left showing that it was hollow. When the next major season begins, I will check three things before writing a word: which patch the competition server is running and which playstyle that patch neutralises; whether the qualifying format lets a weak team survive a single match; and whether the starting roster is the same roster that generated the data I am citing. Those three questions are not glamorous. They merely keep the rest of the piece from collapsing. I do not write about esports. I write about the light that data illuminates — and about the regions it has not yet reached, where the only way to keep your integrity is to say that you do not know yet.