The 0.2-Second Sensor Lag at San Siro and the Trap of Hasty Conclusions

At San Siro in the 2026-17 season, AC Milan's expected goals figure at home reached 1.85, nearly double the 1.02 recorded away. The actual number of goals the team scored at home and away, however, was identical. Nobody in the analysis room could explain the gap. The board handed me the job of re-verifying the motion dataset from 20 Serie A matches that season. I took it on with a principle that had followed me through 41 years in the trade: data only tells part of the story, and the rest lives with those who know how to listen. The 14-page internal report that followed pinpointed the fault. A sensor installed at the south-west corner of San Siro was running 0.2 seconds late across every goalkeeper build-up sequence. The error was small enough for the naked eye to miss, yet it distorted the entire build-up dataset and inflated Milan's xG whenever the team played at home. After the equipment was recalibrated, head coach Vincenzo Montella used the corrected output to increase ball circulation down the right flank. Milan won five of their last eight matches and secured a Europa League place. That story does not belong to one data room alone. The whole of football now runs on spreadsheets. PPDA, xG, passing progression, pressing distance, recoveries in the opposition third — every match generates hundreds of thousands of data points, and each point is packaged into a talking point on television minutes after the final whistle. That speed carries a price. When the volume of information outruns the capacity to verify it, people start reading data the way they read scripture, forgetting that every measurement comes with conditions attached. I set a rule for myself: every number needs a note on measurement conditions, and nothing gets quoted unless it has been cross-checked against at least two sources. Every tracking figure belongs on the operating table, not on the altar. A single metric is never enough. xG speaks to the quality of chances, not to finishing ability. PPDA speaks to pressing intensity, not to the quality of the block behind it. To read a match properly you must place the metric beside other variables: second-half fitness, minutes played across three weeks, pitch quality, and the fixture list ahead. A number torn from its context lies in a very confident voice. In the summer of 2026, at the World Cup in Russia, that rule paid me back. In the Germany versus South Korea match, on 70 minutes, I posted on Twitter that Germany's defensive line was sitting an average of 68 metres high, that pressing had failed 17 times, and that South Korea had already registered 12 counter-attacks. If the block did not drop, I wrote, the goal would come from an aerial situation. On 90+3, Kim Young-gwon scored exactly to that script. On 90+6, Son Heung-min sealed the win. Thousands of accounts piled in to mock me for turning emotion into arithmetic. Gazzetta dello Sport republished the piece alongside the distorted trapezoid diagram I had drawn of Germany's back line. The bigger lesson, though, sat elsewhere. Raw numbers do not stay with readers. I dropped the phrase "sitting 68 metres high" and replaced it with "the zip has burst open at the valve box". I dropped "the gap between centre-back and goalkeeper is 22 metres" and replaced it with "a vertical rectangle parked in front of the box". Spatial images enter memory far faster than tables. An analysis made only of numbers is a technical document. An analysis with numbers, images, radio audio and the breathing of the match is an analysis. At 57, I have sat in enough meeting rooms to notice something few will say out loud. The most dangerous document in football has never been the one with wrong numbers. The most dangerous document is the one that looks immaculate but is hollow inside: nine sections, neatly aligned tables, every cell filled with words, and no cell carrying information. That is the worst kind of blockbuster this industry produces. Such a report passes through three meetings, gets quoted in two bulletins, and by the time someone discovers it had nothing to say, the transfer has already been signed. A contract only looks good on paper until someone tries to fit it into a running system. Reports are no different. Before trusting a conclusion, ask where the data came from, what device measured it, under what conditions, and who checked it first. Without those four questions, any analysis is just emotion dressed in the language of numbers. Some variables never appear in any table. The tone of an engineer's voice over the radio. The length of the pause before a player answers a question. The sound of a stand breaking open and then falling silent after a goal conceded. Empty stands do not kill a match, but they take away something numbers cannot measure. I still log those things every match, because they are the remainder of the story that no sensor ever sees. Every collapse has its preconditions; few people bother to look beforehand. Next match, when a broadcast reads out a beautiful number, the first question should be: where is the sensor, and is it running 0.2 seconds late?