Data Only Tells Part of the Story: The F1 Signals Numbers Never Reflect

Every collapse has a premise; it's just that few people are willing to see it in advance. I've been saying this for 41 years of observing the paddock, from my days in the AC Milan coaching staff to standing behind the commentary screen for Sky Sport Italia. And this season, once again, I see cracks forming that no telemetry sheet can measure. Let's start with a small detail. Last weekend, at a race I won't name, I stood at the pit lane corner watching a chief engineer talking to his driver. Not through radio, not through data sheets — but through eye contact and breathing rhythm. That driver had just completed a lap 0.3 seconds faster than his teammate, but there was no satisfaction on his face. The chief engineer's face showed the same. They looked at each other, nodded, then turned away without a word. Nobody in the control room noticed that moment. But I did. That's what data never reflects. The numbers can tell you speed, tire wear, braking trajectories, but they cannot tell you when a driver is afraid, when an engineer is doubting, or when a team is deceiving itself. The context of this season is very special. We are in the middle of the current technical regulation cycle, where development advantages are being eroded by wind tunnel quotas and cost caps. The big teams can no longer spend unlimited money to find a tenth of a second. Everything must be calculated, prioritized, and sometimes sacrificed. In that context, the difference between a successful team and a mediocre one lies not in how much they spend, but in how they listen — listening to the data, listening to the car, and most importantly, listening to the people within the team. I remember 2026, when I was a member of the AC Milan coaching staff. The management tasked me with validating the movement data of 20 Serie A matches from the 2026-17 season. Milan's xG at home at San Siro was 1.85, much higher than the 1.02 away, but the actual goals scored were equal. If I had only looked at the numbers, I would have concluded the team had a finishing problem. But when I cross-referenced the video footage, I discovered that the sensor in the southwest corner had a 0.2-second delay, skewing every build-up from the goalkeeper. The data wasn't wrong — but it was lying. And if I hadn't been willing to listen to the noise from the measurement system itself, I would have delivered a completely wrong report. In F1, the same thing happens every weekend. Teams spend millions on sensors, telemetry, and simulations, but they often forget that those tools are only as good as the people operating them asking the right questions. I've seen too many young engineers look at an anomalous number and try to explain it with an alternative hypothesis, instead of questioning whether the number itself is trustworthy. That's a serious mistake. Let's talk about one of the biggest issues of this season: the homogenization of car design. When I started covering F1 in 2026, each car had its own personality. You could see a Williams and know it was a Williams, a McLaren and know it was a McLaren. Today, with tight technical regulations and reliance on CFD, all cars are starting to look alike. That not only strips away the beauty of this sport, but it creates a tactical problem: when all cars share the same design philosophy, the competitive advantage lies only in execution — and execution cannot be measured in a wind tunnel. I call this the "blockbuster" of homogeneity. Teams are racing to become the same, and the eventual winner will be the best executor, not the one with the boldest ideas. This goes against my instincts. In 41 years of observation, I have never seen a team win a championship by copying someone else. They win by finding their own path, a solution no one else sees. Look back at the 2026 World Cup, when I analyzed the collapse of the German national team. In the match against South Korea, at minute 70, I posted on Twitter: "Germany's defensive line is averaging 68 meters high, pressing has failed 17 times, South Korea has had 12 counterattacks. If they don't lower the block, the goal will come from a cross." At 90+3, Kim Young-gwon scored exactly as predicted. I was mocked by thousands of accounts for "turning emotion into calculation," but Gazzetta dello Sport republished my article with the distorted trapezoid diagram of the German defense. The Germans that year forgot that football never forgives the complacent. They looked at the standings, looked at their reputation, and believed everything would be fine. But football — and F1 alike — never operates that way. In F1, complacency often comes from pretty numbers. A team can have the best lap time for three consecutive races, but if they don't see the crack forming in the system — an exhausted engineer, a distracted driver, a process becoming loose — then collapse is only a matter of time. I've witnessed this too many times. Let's talk about empty grandstands. During the pandemic years, when races ran without spectators, I realized something: empty grandstands don't kill the race, but they take away something that numbers cannot measure. That is pressure. When you have 100,000 people watching you, when the roar of the crowd rises every time you brake a little later, when you feel expectation weighing on your shoulders — you drive differently. Not faster, but more precisely, more cautiously, and sometimes more boldly. Spectators are not just viewers; they are part of the system. And when they are absent, that system becomes distorted. Now, let's talk about what I call the "execution blind spot." In tactical analysis, we often focus on the big decisions: when to pit, which tires to choose, whether to gamble on a Safety Car. But those decisions are only good when executed perfectly. A perfect pit decision can be ruined by a wheel nut tightened 0.5 seconds slower. A perfect two-stop strategy can collapse because an engineer misreads tire temperature data. These small details never appear in the standings, but they decide results. I remember a race at Monza, a few years ago. A team had a perfect strategy on paper. They calculated everything: pit timing, tire windows, gap to opponents. But when the first car pitted, the tire crew was 0.7 seconds slower than expected because of a stuck wheel nut. 0.7 seconds. In a 90-minute race, 0.7 seconds sounds insignificant. But it was enough for that car to exit the pits right behind another car, lose position, and take 10 laps to overtake. They finished 5th instead of 2nd. Nobody remembers that stuck wheel nut. They only remember that the team "didn't have the pace" that day. That's why I always say: data only tells part of the story; the rest lies in knowing how to listen. And listening is not just hearing what is said, but also hearing what is not said. When a chief engineer stays silent too long in a strategy meeting, when a driver answers interviews with unusually short sentences, when a tire crew suddenly changes procedure without clear reason — those are signals. And they are usually more reliable than any number. Let's talk about the driver market. Every season, we hear about blockbuster contracts, shocking transfers, drivers paid tens of millions. But I've learned that a contract only looks good on paper until someone tries to fit it into a running system. A driver can be world champion at one team, but when moving to another team, with a different car, a different engineer, a different culture — everything can collapse. I've seen too many such cases. And that's why I believe that, this season, the team that wins will not be the one with the fastest car, but the one with the most stable system. The team that listens best, adapts fastest, and — most importantly — stays humblest. Because F1, like football, never forgives the complacent. I will watch the next race with one question in mind: which team is listening, and which team is only hearing itself? The answer will not be in the telemetry sheets. It will be in the eyes of the engineers, in the breathing of the drivers, in the silence of the control room. And I will be there, watching, listening, and recording what the data never says.