The two problems McLaren must solve aren’t just about power; they reveal a deeper tension between machine capability and the craft of aerodynamics. If you’re looking for a take that goes beyond the post-race headlines, here’s the long view I’d offer about Melbourne and what it signals for McLaren’s season.
The power unit is not the entire story
Personally, I think the Mercedes power unit is a powerful enabler, but it’s not a magic wand. From my perspective, Andrea Stella’s admission that there’s a gap between the data on bendy straight-line speed and the car’s actual performance with the same PU signals an essential truth: performance is a system, not a single component. What this really suggests is that understanding how to extract the power—how to deploy battery energy, how to manage electrical modes, how to balance energy harvesting with a blistering pace in the late laps—matters as much as raw horsepower. This is a product of regulation changes and complexity that require very precise calibration, not just bravado about horsepower figures. What many people don’t realize is that the difference in pace can come from something as subtle as on-throttle mapping, or how the car stores and releases energy through corners versus straights. In practice, McLaren’s data challenge is a sign they’re at the edge of the frontier where engineering nuance trumps big-number bragging.
The aero question is equally acute
One thing that immediately stands out is how Brundle frames aerodynamics as the other half of the equation. The MCL40’s aero package is central because even with a competitive PU, a car still needs to slice through the air efficiently to translate that power into grip and speed through corners. In my opinion, the aero upgrade McLaren needs isn’t a single component but a broader refresh that rethinks airflow around the suspension, bargeboards, and the sidepods in the context of the 2026 rules. This is a trend you’re seeing across teams who rely on close collaboration with their power-unit suppliers: the real gains come from a harmonized chassis-PU packaging, not heroic tweaks to one subsystem. What makes this particularly fascinating is how much of this work is about predictive design—simulating thousands of corner sequences to anticipate how the car behaves in a race rhythm, not just in a single practice lap.
The Melbourne setback is a signal, not a verdict
From my vantage, Melbourne is a data point, not a verdict. Norris’s late-race pace shows the potential for pressure-release when conditions align—low fuel, fresh tires, and a clever energy strategy. The real question is whether McLaren can recreate that late-right cadence consistently, across tracks with different demands. What this reveals is that McLaren’s problem is not only how to use the power unit but how to adapt the aerodynamics to real-world race scenarios. If you take a step back and think about it, the team needs a cohesive development plan that treats PU understanding and aero upgrades as two strands of the same rope, pulled in sync.
A deeper pattern: learning under a new regime
This season’s context matters. The 2026 regulations heighten the complexity of extracting maximum performance from the engine and the car’s aerodynamic surfaces. The fact that Stella frames the collaboration with Mercedes HPP as critical underscores a broader industry trend: customer teams must win the “language” of the PU, not just the mechanical handshake. What this means in practice is that McLaren should push for more transparent data exchanges, and a joint development roadmap that aligns hardware and software in real time. What people often miss is how much a partnership can either accelerate learning or create friction points that slow down iteration when the feedback loop isn’t tight.
What this implies for McLaren’s strategy
Personally, I think the road ahead should center on two parallel streams: deepen PU comprehension and accelerate aero evolution. A strong interpretation is that McLaren’s engineers need to map every function of the Mercedes unit—how it responds to temperature, how it adapts over a race stint, how it interacts with various battery strategies—and then feed that into a reworked aerodynamic flow that capitalizes on the unit’s best characteristics. What makes this strategy compelling is that it aligns with a broader shift in formula racing: progress comes from disciplined cross-disciplinary optimization rather than chasing a single magic upgrade.
The broader takeaway: racing as a testbed for systems thinking
From my point of view, McLaren’s Melbourne experience demonstrates a larger pattern in high-performance engineering: the best teams don’t treat power units and aerodynamics as separate skill sets but as intertwined levers of a single system. If you’re assembling an elite car, the critical question becomes how well the team can predict, measure, and adjust this system under pressure—under race conditions, with evolving temperatures, tire wear, and strategy calls. That’s the real artistry here: turning data into decisive, real-world advantage through coherent engineering philosophy.
Conclusion: a moment of recalibration, not a permanent scorecard
What this episode ultimately invites is a patient, methodical recalibration. McLaren is not doomed by a single deficiency, but invited to prove that it can integrate deep PU knowledge with a forward-looking aero program. The takeaway is clear: the future of success lies in exporting a unified development doctrine—where software, engine behavior, and aerodynamics are not siloed but co-designed. If McLaren can align those strands, Melbourne becomes less a setback and more a blueprint for rapid, disciplined improvement.
