Hadjar's Empty Seat: When Red Bull Loses a Sense No Stopwatch Can Measure

On Sunday morning in Monaco, I stood in the cabin above the Massenet corner, and the thing that lingered in my ears was a dry, sharp "tick" — the sound of a tyre brushing lightly against the barrier at a speed only a driver willing to gamble would dare attempt. Across many years of reporting on Formula 1, I learned that this sound is the signature of a driver who knows exactly where he is on the track, down to the centimetre. This year, I no longer hear it coming from Isack Hadjar's car. The seat in the Red Bull garage is still there, but the man who sat in it to score a podium in Monaco is absent with an injury. What troubles me is not the absence itself, but how the world reads it through familiar numbers: Verstappen still took two podiums, and Lawson still finished in the points in two of his three substitute races. Reading the timing sheets, someone could conclude that Red Bull lost nothing. And precisely the gap between that "lost nothing" and the technical truth is where I want to linger longest.

Before going deeper, let me rebuild the context for those who follow Red Bull from a distance. This team is entering what I believe is the biggest turning point in more than a decade: the RB22, tied to a new generation of technical regulations, changes almost everything — from how aerodynamics generate downforce, to how the power unit distributes electrical energy, to how tyres degrade stint by stint. When regulations change, a driver's value lies not in how fast he drives, but in how well he can translate feel on the car into clear technical signals for engineers groping for a development direction under a tight budget cap.

That is why Hadjar's story is not merely a story about an injury. Before he stopped, he did something very few drivers can do alongside Max Verstappen: eight top-10 finishes, one podium in Monaco, and three times out-qualifying Verstappen himself. Three times. Let that number settle for a beat. People say a lot about beating Verstappen in a single lap being nearly impossible for a young driver new to the team. Hadjar did it three times. When a driver strikes that balance with a completely new car, it means he and the car have found each other — what I call car-driver character match.

Then the injury came, and the garage door closed on him. This is where the story departs from the part most readers care about.

When a driver is absent, the first loss everyone sees is points. The second, rarely noticed, is seat time. And the third — which I consider the most serious under a cost cap — is the ability to provide real-time feedback about the car. A driver does not merely drive; he is a living sensor. When he runs on track, every vibration through the steering wheel, every moment of tyre losing grip in a high-speed corner, every time the engine switches energy deployment modes, becomes data engineers cannot obtain from any wind tunnel. A driver sitting out loses the ability to update that feel map.

I have spoken with no small number of race engineers in my career, and what they repeat is this: in the cost-cap era, the greatest value of a driver with good feedback is not scoring a few extra points, but helping the team avoid going the wrong way in development loops — each wrong step burns millions and costs months that cannot be recovered. A new car is born not from a blueprint on paper, but from thousands of laps the driver turns into words for engineers.

Lawson came in as substitute. And Lawson did his part as well as possible: two points finishes in three races is no poor number for someone stepping into a car mid-season with very little preparation. But here is the subtlety most analysis skips. A substitute driver brings different data — not wrong, just different. Different driving style, different braking points, different way of feeling the tyres. If the car is being developed around Hadjar's feel, Lawson's data can muddy the correlation the team has carefully built for him.

Picture it with a simple comparison. If you are tailoring a suit for a person, you measure that person. If he is absent and you measure someone else with similar measurements, you can still make a suit that fits — but it never fits exactly along every seam. The RB22 is being "tailored" to a particular set of feel signals, and when the man who contracted for those signals sits out, the team is forced to temporarily use someone else's measurements.

I once heard a line somewhere in the technical world: Tactics are not a mummy, do not wrap them behind museum glass. The same goes for the car. A race car is a breathing organism, changing race by race, and the driver is its lungs. When you pull out the lungs, the organism still lives — but its breathing changes rhythm.

This is where I offer my central technical hypothesis: Red Bull may be paying not in points, but in the speed of the RB22's development direction, and that price only shows up at the end of the regulatory cycle, when the gap in car understanding accumulates into a gap in results.

To test this hypothesis, I want to dissect three layers of signal.

The first layer is quantitative. Hadjar has eight top-10 finishes and one podium in Monaco. Verstappen, in Hadjar's absence, has two podiums. Reading only this, people will say Verstappen carries the team better. That is true, and unsurprising — Verstappen is one of the greatest drivers in history, and his carrying the team at the highest level is a default. But the question is not how good Verstappen is. The question is what kind of signal the team loses when Hadjar leaves the seat. And here, Hadjar's three times out-qualifying Verstappen become more important data than the podium itself. Because it shows he could not only exploit the car at its peak, but also understood how to extract it at the limit even Verstappen does not always reach.

The second layer is the translation of feel. This is what the team calls "car mapping." A new driver needs thousands of real kilometres for his body to react automatically to the car's variations. When injury cuts across that process, what is interrupted is not speed, but the synchronisation between hands and car. Mekies, who runs the team, mentioned simulator sessions to keep Hadjar tracking the car's development. The simulator is a good tool — but imperfect. Sim-to-track correlation always carries error, and under cost-cap pressure, every simulator hour is expensive. When a driver does not race for real, his simulator signals gradually lose accuracy — not because the simulator worsens, but because the human body forgets the real feel of tyres on hot asphalt.

This is something I draw from watching races for many years: tyre feel is the easiest to lose and the hardest to regain. You can relearn a corner in a few laps. But you need many real stints to regain intuition about when the tyre starts to drop and how the car reacts when downforce changes with fuel load. No simulator session perfectly recreates that feeling.

The third layer, which I consider most important yet rarely discussed, is data correlation. When Lawson replaces Hadjar, the team gains a new dataset. That dataset has its own value — it can confirm or refute certain assumptions about the car. But it cannot replace Hadjar's data. Because each driver is a different reference frame. When you mix two reference frames into one development model, you create noise. And noise, in a game where one wrong development direction costs the whole next season, is the most expensive thing.

I want to dig into this point because I believe it is the core of the story.

Football and F1 differ in that a football match can be won by a moment, while an F1 season is won by accumulation. You cannot win a championship with one divine lap; you win it by understanding your car a little more deeply than rivals, race by race. That understanding comes from the driver, and the driver can only convey it while sitting in the car. This is why I hold that Hadjar's injury is not an individual event but a system event.

Let me attempt a calculation no one wants to make. In a season, a top team introduces dozens of upgrade packages. Each upgrade needs on-track confirmation by the driver to know whether it truly works or is an aerodynamic illusion. If the main development driver races only part of the time, the confirmation laps fall, and the team must decide on less data. Deciding on less data means raising the probability of choosing the wrong direction. The cost cap means each wrong choice cannot be fixed with money — it can only be fixed with time, and time is what no one has more of.

And this is where I admit I may be missing something.

The sweetest mistake is the one that makes me feel I can still listen. I have been wrong in the past in a very similar way. When Haaland left Dortmund for Man City, I loudly declared that a classic centre-forward would break Guardiola's pressing structure. I was wrong, and I do not hesitate to call it a sweet mistake — because being wrong taught me to see differently. In Red Bull's case, there is a scenario where I may be wrong. It is the scenario where the team actually benefits from the change. Lawson brings a new perspective, a different driving style, and perhaps that difference reveals problems with the RB22 that Hadjar, already too familiar with the car, no longer sees.

This is not unreasonable. There are times when the too-familiar go blind to flaws. A new driver with unshaped feel may discover a weakness in how the car enters corners that the man who spent a year taming it has unconsciously ignored. If so, then Lawson running as substitute is not data noise, but a precious independent information source. And if I am wrong, I am wrong in a way I am ready to accept — a sweet mistake, as I always call it.

But I still lean toward my original hypothesis, for a simple reason: blindness to flaws only holds when a driver has bonded with a car for years. Hadjar and the RB22 are too new to each other for familiarity to become a blind spot. He is in a learning phase, where every lap brings new information. Cutting that phase with an injury is not handing the team an independent perspective; it is withdrawing a man midway through learning to read the car. This is the difference between temporarily losing an expert and interrupting a talented apprentice.

At 54, I have learned that emotion is also a rare form of data. And my emotion looking at that empty seat is a regret hard to name. Not regret for lost points — Red Bull remains in a good position. But regret for the continuity of a forming process. A young driver learning to understand a car is a fragile, breakable process, extremely hard to restart from scratch.

I remember a moment in my career, when the pandemic emptied stadiums and I first heard a coach's instructions clearly on the pitch. It was an experience that changed how I write — from sharp declarations to storytelling through sound. Hadjar's empty seat gives me a similar feeling: a silence that says more than any report. There are silences on the field that say more than any blockbuster signing. And in the Red Bull garage, that silence is crying out something the timing sheet cannot translate.

To reinforce the argument, I want to return to the number eight top-10 finishes. This is not merely a performance metric. It is a metric of repeatability. In F1, one good result can be luck — a chaotic race, a right strategy, an excellent safety car. But eight top-10 finishes with a car changing under your feet race after race is another signal. It says the driver knows how to exploit the car consistently, regardless of how surrounding variables shift. That consistency is what top teams need most in a new regulatory cycle, because a new cycle makes everything around you fluctuate.

Now place Hadjar's consistency beside Verstappen's two podiums during his absence. In results, Verstappen did better — of course. But in car development, those two podiums were built on a different reference frame. Verstappen is a driver who can carry an imperfect car to a high position. That ability is both a gift and a trap: it hides flaws that other drivers would expose. When you have a driver who carries the team too well, you risk losing the signal about where the car needs fixing. Hadjar, in his learning phase, does not hide flaws that way. Sometimes the cry of a young driver is the most accurate map of where the car still hurts.

This is a perspective I consider counterintuitive, and it is the part where I want to challenge readers.

What most people assume is: the stronger a team is with its number one driver, the better. But in the cost-cap and new-regulation era, that assumption has a hole. A team does not only need speed; it needs information. And high-quality information often comes from drivers right at the boundary of their ability to extract the car — not from those who have already passed that boundary. Hadjar, three times out-qualifying Verstappen, stands right at that boundary. He is fast enough to exploit the car, and not yet finished enough to sense every weakness. A driver like that is an information gold mine.

I have heard too much analysis that simply counts podiums. Counting podiums is the fan's job, not the technical analyst's. My job is to look at what does not appear on the scoreboard, and there, Hadjar's empty seat is a far greater loss than Verstappen's two podiums make people believe.

From pitch to esports, I seek only one moment that makes people forget they are breathing. In F1, that moment does not only come from a spectacular overtake. It comes from smaller things: a young driver realising how the car reacts when the tyre begins to lose grip in a medium-speed corner, and conveying that to his engineer. Those moments are the backbone of a championship team. And they are not happening, because the man who creates them sits out.

So what should Red Bull do, if I am right?

First, they need to protect the sim-to-track correlation for Hadjar more seriously than usual. That means designing simulator sessions not only to preserve feel, but to cross-check against real data from Lawson — turning the difference in driving style into a comparison tool rather than a noise source. If they manage this, they can turn a bad situation into a richer dataset.

Second, they need to prepare for Hadjar's return knowing his tyre feel will not be intact. Long runs will be needed to rebuild intuition about tyre degradation and car behaviour as fuel changes. This is not a speed problem, but a depth-of-understanding problem. And depth of understanding is what decides success in a new regulatory cycle.

Third, the team needs to admit to itself that still winning does not mean it lost nothing. That is the most dangerous trap in sport: results masking process. A team can win a few races while still accumulating a gap in car understanding that only surfaces late in the season. Verstappen can carry the team in the short term. But even Verstappen cannot carry a car developed in the wrong direction for months.

What I want readers to take away is a question. When you look at a timing sheet and see the numbers still fine, are you seeing the truth, or only the part of truth a timing sheet can hold? Hadjar's empty seat never appears on screen. But in the Red Bull garage, it is changing how the team listens to its car — and I do not think we will know until the new regulations enter their second season.

A prediction I am ready to bet on: if Hadjar returns this season and struggles in his first few races at race pace, that will not be a sign his talent is gone. It will be evidence for my hypothesis — that what was lost is not speed, but intuition. And in an era where every running hour is counted under a cost cap, intuition is the most expensive asset a driver can give a team.

As for Red Bull, as a championship team, it may be living in a temporary comfort granted by the timing sheet. But I have learned, through many years standing in commentary cabins at different circuits, that this comfort is what betrays the fastest teams. Because a team does not win by what it has at a moment, but by what it understands one step before its rivals. And understanding, in this game, is something that must be heard with a sense that is not on the stopwatch.