The amateur spreadsheet taught me that data doesn't need to be flashy, it just needs to be right

In a small room on the second floor of an internet café in Da Nang, in 2026, I was 17 years old manually recording every pass of SHB Da Nang FC using a ballpoint pen and lined notebook. No Opta. No StatsBomb. Only a homemade Excel spreadsheet, a stopwatch, and the belief that if I was patient enough, the numbers would reveal truths that emotions overlook. Ten matches. For each match, I sat in the C stands, recording ball reception positions, failed pass counts, and dead ball conditions. Then I added everything up and discovered a pattern so simple I did not believe my own eyes: the team won only 2 out of 10 matches when their failed pass rate in the opponent's final third exceeded 15 percent. That was the day I understood that self-collected data could reveal tactical problems just as clearly as professional tools. Seven years later, I work as a transfer market administrator at a sports data company in Vietnam. My database has grown into a system tracking over 200 transfer deals from Southeast Asian clubs. I have watched clubs pay 100 million euros for players who have not played 50 top-level matches, and I have seen deals that major companies overlooked, picked up by lower-division clubs, and create surprises. What I learned is not that data beats emotion. What I learned is that data beats laziness in thinking. The 2026 World Cup was the biggest test of that belief. I was 18, a high school senior, spending all my spare time following Croatia's journey at the Russia tournament. Not because I idolized Luka Modric or admired their counter-attacking style. But because I wanted to prove that victory does not come from miracles. Croatia finished runners-up with 38 percent possession in the group stage. Denmark pressed hard in the Round of 16. I wrote a 2,000-word analysis pointing out that Croatia's midfield functioned most effectively when pressed high and transitioned quickly. I calculated Modric's distance covered across 7 matches, acceleration counts, and average distance between passes. A student's post on a forum was shared by 500 people, and many said I was lucky. I did not accept that. Croatia 2026 was not a miracle, but the sum of passes people overlooked. Those were short passes in their own half that fans do not remember, movements that did not create goals but created space for others to score, decisions to pass backward when everyone demanded attack. Like in table tennis, a victory does not lie in the decisive smash but in the 47 controlled pushes before it. In 2026, the pandemic suspended all tournaments. I was 20, a sophomore, and world football fell silent. Instead of doing nothing, I spent 6 months building a transfer database for Vietnamese clubs from 2026 to 2026. I collected contracts, transfer fees, player ages, positions, and post-transfer performance. Over 200 deals were coded, categorized, and analyzed by cycle. The first discovery that shocked me: Southeast Asian clubs often overpaid for Brazilian and Korean players over 28 because they only looked at goal-scoring records, ignoring injury history and workload metrics. A 30-year-old striker who scored 15 goals in Brazil's second division is not a good signing if he has already had two ligament injuries and his average match running distance has decreased 12 percent compared to three years prior. But nobody checked that. Nobody questioned a player's athletic longevity when he was scoring consistently. In 2026, when I was 24 and a new employee at a sports data company in Ho Chi Minh City, I brought the database built since 2026 and proposed finding potential players for a Thai first-division club. My database showed that a 23-year-old striker playing in Brazil's second division had an xG/90 of 0.68 but only played 45 percent of available minutes because the club preferred signing older stars. I negotiated with the agent, convincing them with performance comparison charts between this player and peers of the same age in equivalent leagues. Three weeks later, the deal was completed with a loan contract including a purchase option. The club rose from 6th to 2nd place thanks to 8 goals from this player in the remaining half season. That was when I understood that my data system had real-world value, not just academic exercise. But it was also when I recognized a dangerous trap: when data speaks, people tend to trust numbers absolutely and forget context. A player with high xG is not necessarily good for every team. A deal with high expected profit is not necessarily the right deal if the club culture does not fit. Every player is a notebook; only those who read carefully see the last line. That is the sentence I remind myself of whenever I want to rush to conclusions. In the transfer market, fans remember player names, while I remember contract expiration dates. But remembering expiration dates does not mean undervaluing human worth. It means I understand that football operates on two time dimensions: match time and contract time, and a good market administrator must read both. The Da Nang database taught me that patience is the algorithm easiest to write, hardest to run. Every coach and athlete knows what they need to do. Tactical analysis is readable by anyone. But executing correctly under pressure, when the opponent has thoroughly studied your system and pushes you into situations outside the original plan, that is the real test. Data tells you probability. Decisions under pressure, that is where skill and character separate. I do not believe in fate, I believe in correlation coefficients. But I also understand that correlation is not causation. Two variables moving together does not prove one causes the other. A player with high acceleration counts and high goal counts does not prove that speed creates goals. Both might be results of a third factor: the quality of space the team creates for him. A team's playing style does not lie in the formation diagram, but in the average ball reception position of each position. That is the lesson I learned from watching hundreds of matches and realizing that teams with average reception positions shifted toward opponents without creating passing pressure will struggle against well-organized defenses. Football tells stories through numbers; you just need to know how to ask the right questions. Readers easily notice that I never make definitive statements without contrasting data. Readers also notice that my writing has become less assertive after each time reality betrayed me. That is not weakness. That is methodology. A Vietnamese sports writer, from amateur spreadsheets and the Da Nang database, treating every match as a system that needs to be told through evidence, not flashy, just accurate. And when I recognize errors, I correct them directly like an algorithm that learns from mistakes. Not because I have no opinions. But because my opinions must emerge naturally through tactical analysis and storytelling, not through direct statements. I once made a serious mistake evaluating a transfer deal based on incomplete data. I concluded that a young midfielder would develop into a star because his xG/90 was above average. Six months later, he transferred to another club and seriously declined. I had not checked his passing rate under high pressure, a metric I knew was important but had skipped because it was not in the report I read. Lesson: data does not lie in available numbers, but in numbers nobody has collected yet. In a regular season, the story does not lie in beautiful goals on the front page, but in tactical signals below the standings. Which team is building a new playing style? Which coach is experimenting with an unfamiliar formation? Which player is changing position and why? Those are questions fans skip to jump straight to the standings, and that is why they are often surprised when their favorite team completely changes after a transfer window. I did not write this article to show off my database. I wrote it to say that in an age where everyone can access information, competitive advantage lies in how you read, how you ask questions, and how you accept that your model will be wrong. Always wrong. The problem is not avoiding mistakes. The problem is building a system flexible enough to update when wrong and continue moving in the right direction even knowing the path is never straight. My amateur spreadsheet from 2026 taught me that. And I am still learning.