When Data Lies: Lessons from a Football-Less Summer

When Data Lies: Lessons from a Football-Less Summer In the summer of 2026, when the pandemic halted every league worldwide, I sat in my small room in Hanoi, rewatching all of Liverpool's matches from the 2026-20 Premier League season. It was a strange summer, with no opening whistle, no wild celebrations. Just me and hundreds of gigabytes of tracking data. I remember the 0-3 loss to Watford in February of that year. Liverpool pressed high, pushing the opponent back into their own half, but then got torn apart by long over-the-top passes. I measured the average distance between defender and goalkeeper: 28 meters. In winning matches, that number was just 15 meters. Numbers only tell the story; tactics begin with mistakes. This story isn't just about Liverpool. It's about how we read the game, about how data can lead us in the right direction or completely astray. And it starts with a mistake of my own, in 2026, at the World Cup. I was invited by an online newspaper to write a column for the 2026 World Cup. For the Belgium vs. Brazil quarterfinal, I analyzed Roberto Martínez's 3-4-3 formation. I wrote that Kevin De Bruyne dropped deep to create a numerical advantage in midfield, while Nacer Chadli covered the entire left flank. I was so confident that I mistakenly wrote 'Belgium pressed successfully 21 times' when the actual data was 14. A Twitter reader pointed it out that very night. I had to correct it and realized I had been too confident in my memory. My 2026 mistake reminded me that data is a mirror, not a lamp. A mirror reflects reality; a lamp illuminates the path but can shine in the wrong direction. Since then, I never write numbers from memory. I set up a checklist of two independent data sources before publishing, always noting the source at the end of the article. This made my writing more cautious and credible, but each article took an extra three hours to verify. A football-less summer is when high pressing reveals its skeleton. When there were no new matches, I rewatched old ones and realized something: high pressing isn't about winning the ball; it's about forcing the opponent to lie. When Liverpool pressed, they didn't necessarily need to win the ball immediately. They wanted to force the opponent to make decisions under pressure, and those decisions were often wrong passes, rushed executions. But the Watford loss exposed a blind spot. When pressing high, Liverpool left space behind their defensive line. Watford didn't try to pass short to escape the press. They passed long, over the lines, putting the ball directly into the space Liverpool's center-backs had vacated. It was a lesson in balance. A successful pressing performance begins with recognizing how the opponent doesn't want to be broken down. I remember the first match I dissected, in 2026, when new sports media was booming in Vietnam. I was 39, starting a tactics blog. The Hanoi FC vs. Thanh Hoa match in Round 18 of the V-League. I used FIFA tracking data: Hanoi FC had 612 passes, 58% possession, but only 3 shots on target. I found the problem lay in the high defensive line; center-back Quoc Long was often 30 meters from the goalkeeper, making it easy for opponents to escape the press. That 2,000-word article got 10,000 views on Facebook in three days, three times the readership of local print newspapers. I learned that Vietnamese readers weren't familiar with terminology, so I started annotating every concept like 'high line,' 'third-man pass.' But I also realized something more important: data isn't absolute truth. It's one perspective. In the Liverpool vs. Watford match, tracking data showed Liverpool had 68% possession, completed 587 passes with 87% accuracy. These numbers tell a story of dominance. But if you only look at those numbers, you'll never understand why Liverpool lost 0-3. You have to look at the movement map, at the distance between lines, at each player's position in each moment. A player's movement map is like a chess game: read the intention, predict the next move. When I rewatched that match, I saw clearly: Virgil van Dijk pushed up so high that he was often in the opponent's half. When Watford won the ball, they just needed one long pass into the space behind Van Dijk. Ismaila Sarr, Watford's winger, exploited that perfectly. Numbers only tell the story; tactics begin with mistakes. If I only looked at possession, I'd conclude Liverpool played well but were unlucky. But when I looked at the distance between lines, I saw a structural problem. Liverpool didn't lose because of luck. They lost because their system had a flaw, and Watford exploited it deliberately. This leads me to a bigger question: how do we read data intelligently? I don't believe in intuition. I believe in how many variables that intuition has been fed. When I see an unusual number, I don't jump to conclusions. I investigate how that number was created, in what context. In the Liverpool vs. Watford match, the 28-meter distance between defender and goalkeeper wasn't a random number. It was the result of a high-pressing system where the whole team pushed up to apply pressure. But when the opponent broke the press with a long pass, that distance became a dead zone. The defender couldn't get back in time, the goalkeeper didn't dare come out. That's why I always emphasize that data must be read in context. A standalone number can lie. But when you place it next to other numbers, when you look at the movement map, when you understand both teams' tactical intentions, the story begins to unfold. In the summer of 2026, when I rewatched Liverpool's entire season, I didn't just watch the wins. I watched the losses, the draws, the seemingly meaningless moments. I realized that mistakes often say more than victories. A team can win 10 straight games on luck, but one tactical mistake will be exposed immediately when facing a strong enough opponent. This brings me to a counterintuitive perspective: sometimes, we should focus on what didn't happen rather than what did. When Liverpool pressed, they didn't just want to win the ball. They wanted to prevent the opponent from building up comfortably. But when Watford didn't try to build up short, when they passed long from the start, Liverpool didn't know how to respond. They had prepared for one scenario, but the opponent played another. In Vietnamese football, I see the same thing. Many teams adopt high pressing but have no Plan B. When opponents play long balls, they get confused, leave space, and concede. That's why I always advise young coaches: prepare for multiple scenarios, don't rely on a single system. I remember Euro 2026, when I paid special attention to Italy and left-back Leonardo Spinazzola. In the Round of 16 match against Austria, he had 12 crosses, 4 successful dribbles, and was always the target of long passes. I used software to map out 5 attacking phases, realizing Spinazzola started from position 30 on the left but actually played like a central midfielder. The article was shared by a young Vietnamese coach in the Facebook group 'Tactics Academy,' reaching 5,000 views. But what mattered wasn't the views. What mattered was that I learned how to dive deep into a specific individual. Every article since then has a 'player spotlight' with movement metrics and activity range. I also end with an open question to stimulate discussion. But I also learned another lesson: data can be abused. In an era where everything can be measured, we easily get caught up in numbers and forget the essence of the game. A team can have 70% possession but still lose 0-1. A player can run 12 km per match but have zero impact. What matters isn't the quantity of data, but how we read it. I don't believe in intuition. I believe in how many variables that intuition has been fed. When I see a number, I ask: how was this number created? What does it mean in the context of the match? How could it be misinterpreted? In the Liverpool vs. Watford match, if I only looked at possession, I'd conclude Liverpool played better. But when I looked at the movement map, I saw a structural problem. Liverpool controlled the ball, but they didn't control space. And in modern football, space matters more than the ball. That's why I always use spatial thinking in analysis. I measure distances between lines, between players, between the ball and the goal. I map out phases, marking each player's position in each moment. I look at the spaces, the zones that no one controls. In the Liverpool vs. Watford match, the space behind the defensive line was the fatal zone. Van Dijk pushed up, the full-backs pushed up, and behind them was a vast empty space. Watford didn't need to pass short to bypass the press. They just needed one long pass into that space, and Sarr would do the rest. This leads me to an important conclusion: high pressing isn't a universal tactic. It only works when you have the right players, when you control the space behind, when you have a Plan B when the opponent breaks the press. Liverpool learned this lesson, and they adjusted in subsequent seasons. But the story doesn't end there. It's also about how we read data, how we avoid the traps of overconfidence. I made a mistake in 2026, and I learned the lesson. Now, when I write any analysis, I always check two independent data sources before publishing. I never write numbers from memory. Stepping into the Vietnamese football data world, I learned to be silent before numbers. Not because I don't trust them, but because I know they can lie. A standalone number can lead you astray. But when you place it in context, when you look at the movement map, when you understand the tactical intention, the story begins to unfold. The transfer market is a massive map of errors. The wise look for blind spots, not treasure. I remember expensive transfers that failed and cheap ones that succeeded. Data can help you evaluate a player, but it can't predict the future. Football is a game of uncertainty. So, what did the football-less summer teach me? It taught me that high pressing isn't a formula for success. It taught me that data must be read in context. It taught me that mistakes are the gateway to tactics. And it taught me that sometimes, the most important thing isn't what happens on the pitch, but what doesn't happen. When I look back at the Liverpool vs. Watford match, I don't just see a defeat. I see a lesson in balance, in preparation, in reading the game intelligently. And I ask myself: are we too dependent on data, forgetting the essence of the game? Are we chasing numbers while ignoring the spaces on the pitch? The answer, I think, lies in how we ask questions. Instead of asking 'which team has more possession?', ask 'which team controls space better?'. Instead of asking 'which player runs the most?', ask 'which player moves most intelligently?'. And instead of blindly trusting numbers, trust your own ability to read the game. Numbers only tell the story; tactics begin with mistakes. And in that football-less summer, I learned to listen to what data doesn't say. That's the most valuable lesson I've gained in my entire analysis career.