McLaren's Baku upgrade: what can be measured, and what the circuit hides

The first practice session in Baku had ended, and in McLaren's garage area, some bodywork panels had to be removed for repair. That was the only detail that made me pause longer than necessary that weekend. A large upgrade package had been brought to Azerbaijan, but its introduction did not go as smoothly as previous packages. In my trade, the launch day of an upgrade is the easiest day to lie, because anything can be labelled an encouraging sign if the writer does not force themselves to point at something measurable. The team said it was satisfied. It said the upgrade brought the improvements it was looking for. I believe them, but not in the way a supporter believes. I believe them because it is a claim that can be verified — it simply cannot be verified right now. Baku City Circuit has a feature every engineer knows by heart. The main straight runs along the Caspian shore, among the longest on the calendar. The rest of the lap consists almost entirely of slow, short, right-angled corners between walls. This kind of circuit demands two contradictory things: low aerodynamic drag to achieve straight-line speed, and enough downforce to rotate the car through ninety-degree corners. A car designed to be strong in long, fast corners — where downforce works continuously and stably — will find no environment to express itself in Baku. In the other direction, a car constrained by short gearing, meaning each gear reaches its rev limit at a lower road speed, will be exposed on the longest straight of the season. These two characteristics are not the fault of a single weekend. They are the fingerprint of a design philosophy. I have followed many upgrade cycles at midfield teams across nineteen years in this trade. What I learned is fairly simple: an upgrade is never judged where it debuts, but where it is allowed to express itself. Baku, with the circuit structure just described, is the worst possible place to run the test. The problem in Baku belongs to measurement, not to performance. Separate two questions that are usually merged into one. The first: did the upgrade work? The second: can we see it working? In Baku, the answer to the second is almost certainly no, whatever the answer to the first may be. The mechanism of this masking becomes clear once it is broken apart. The long straight rewards top speed; short gearing punishes top speed. The slow, short corners do not exploit high-speed downforce — precisely what this car is said to do well. In other words, the circuit removes exactly the two things the upgrade was meant to improve, and leaves the observer with the part the upgrade was not aimed at. too clean. An update without numbers is a too-clean update, and I always read those by counting the gaps rather than the sentences. There are three notable gaps here. The first: no anchoring numbers. No lap times, no top speed, no tyre degradation figures were offered for comparison before and after. An upgrade of this size should have at least one quantitative anchor for outsiders to hold onto. The second: the published content itself concedes that outsiders cannot judge the magnitude of the improvement. That is an honest sentence, and it is also the most important sentence in the entire story. A team willing to say that is placing a limit on its own claim. The third, and the one I care about most: nothing states clearly whether the repairs after the first day of practice were crash damage or a component fault. Those two possibilities lead to entirely different conclusions about the team's production capability. If it was a crash, it is a weekend matter. If it was a component or fitment fault, it is a supply-chain and process-maturity problem — one that will return at a far worse moment. An injury file does not lie — only the person reading it knows how to hide the truth. The same principle applies exactly to an upgrade file. Technically, the most valuable information in the whole story is not in the upgrade. It is in the short gearing. This is an architectural decision, not a weekend-specific choice. It says the team accepted a top-speed trade-off in order to optimise for the majority of the remaining circuits in the season. That is a portfolio-level bet, and it will be exposed at every Monza, Spa or Baku-type venue — places where top speed decides track position down a straight. This leads to a consequence that upgrade reporting usually ignores. Even if the upgrade works exactly as designed, the car will still be weak at high-speed circuits for the rest of the season. The two issues are independent. Merging them is the most common mistake when reading upgrade news. When the dressing-room door closes, I understand that tactics are not on the whiteboard. The same applies here: the true performance of an upgrade is not in the press release, but in how engineers talk to each other at eleven at night, with the car still in the garage and the engine cover off. There is one more layer to address, though it is far less attractive than the aerodynamic story. A team repeatedly bringing upgrades — and here, the latest in a series — implies a functioning development loop. It has a wind tunnel, simulation, a manufacturing process, logistics that deliver parts to the circuit on time — until that chain breaks at some link on the first day of practice. A large upgrade also consumes both cost-cap budget and aerodynamic testing allowance. Development cadence is not free, and a package arriving late is a signal worth recording. The counter-intuitive point lies here. The team says it is satisfied, and the conventional reading is that the upgrade worked. There is another reading, more plausible on technical grounds. A team's satisfaction in Baku most likely comes from internal data — the correlation between aerodynamic simulation, wind tunnel and driver feedback — rather than from a step in real lap time. Simply because Baku does not produce that step. A technical team saying it is satisfied at a circuit that masks the benefit is usually talking about the upgrade correlating with prediction, not about the weekend result. Read that way, the conclusion inverts. The real encouraging signal is not that the car became better in Baku, but that the team's design process is still accurate. That is a far better piece of news, and also one far more easily lost when packaged into a short headline. The biggest risk here is the upgrade being misread, not the upgrade failing. Baku hides the benefit, so the team could credit a package that did not work, or discard one that did. Both are decision errors, and both affect the development rhythm of later packages. In a season where both budget and testing time are restricted, a single misreading does not cost only one weekend. Data has no gender. Only the person reading the data carries bias. With an update that has no data, both halves of that sentence become awkward. The thing to watch is not in Baku. It is in the next two rounds with contrasting circuit characteristics — where high downforce and long, fast corners dominate. That is where the upgrade must prove itself, and where we will learn whether the satisfaction in Azerbaijan was a data point or merely a turn of phrase. And there is one detail I keep to myself, as a small test. If at the next round another upgrade arrives late and again needs repairs in the first practice session, then it is no longer a small matter. At that point, the story stops being about the upgrade, and becomes about how a team evaluates itself.