RB22 and the Data Gap: When Red Bull Lost the Man Who Reads the Car

Three times. That is how often Isack Hadjar beat Max Verstappen in a qualifying session before injury forced him out of the Red Bull seat. For a young driver sharing a garage with a four-time champion, that number is far from small. Add eight top-10 finishes and a podium at Monaco, and Hadjar proved he was more than a placeholder in the RB22. But when I went back through the data after his absence, what caught my attention was the stretch of time in which Red Bull had to keep developing the car without the man who felt it on track. Three numbers — three, eight, one — paint the portrait of a driver finding his harmony. It is the gap behind them that deserves the discussion. At 60, I no longer believe in luck, only in the numbers that have yet to speak. RB22 belongs to a new regulation cycle. This is a phase in which every race brings a fresh batch of baseline data, and every upgrade must be validated by driver feedback before engineers decide the next direction. Under cost-cap pressure, teams cannot test every option. Each new part fitted to the car must answer one question: which weakness does it fix, and can the driver feel that fix? When Hadjar was injured, Red Bull lost a feedback source that had been calibrated. Liam Lawson stepped in and scored points twice in his first three races. Looking at results, the team had no reason to worry. But results and data are two different things. Points tell you Lawson did well in the specific conditions of a race. They do not tell you what kind of data Lawson is feeding into RB22's development. This is what many outsiders overlook. A race car is not refined on the timing sheets. It is refined in conversations between driver and engineer, when the driver describes the car going unbalanced on corner entry, or the rear sliding on exit, or brakes that are inconsistent lap to lap. Those descriptions cannot be replaced by telemetry charts. They are inputs to a process in which every week's upgrade depends on whether the driver feels the change correctly. I once spent three months analyzing 1,247 players from 15 European leagues to build an evaluation framework of 12 metrics. That experience taught me one thing about cost limits: the scarcest resource has shifted away from money, toward the ability to read signals. In F1, the driver is the most expensive sensor, and every week he does not drive is a week of data never collected. The transfer market is a game in which whoever prices correctly wins — and here, what is being priced is Hadjar's seat time. Hadjar left behind three important data trails before his injury. First, eight top-10 finishes — a steady frequency showing he was not merely fast in a few lucky moments. Second, the podium at Monaco — a track demanding absolute precision and low-speed car control, where small errors are magnified into large time losses. Third, and most telling, three qualifying wins over Verstappen. The third number matters because it measures pure one-lap speed. Verstappen is the reference standard of the entire F1 grid. Beating him once can be conditions — track temperature, timing of the run, or simply a rare perfect lap. Beating him three times in a season shows Hadjar had found harmony with the RB22. And that harmony is precisely what a team needs to understand its own car. When a new driver joins a team, he goes through what is called car-character match — the fit between driving style and car characteristics. This process cannot be rushed by reading data sheets. It is built lap by lap, tyre set by tyre set, setup change by setup change. Hadjar was at the stage where that fit had formed and was beginning to pay off. The injury came at exactly that moment. This is where the comparison with Lawson becomes complicated. Lawson scored twice in three races. On paper, that is acceptable performance. But when you factor in RB22's development process, the real issue is not how many points Lawson scored. It is how Lawson is feeding back on the car. Every driver has a personal sensing language. Some are sensitive to changes at the front of the car, others feel rear instability more clearly. Engineers calibrate setups based on that language. When Hadjar was injured, the team had to switch to Lawson's language — or whoever sits in that seat. This transition creates a bias in the data correlation. More concretely, suppose the team develops a new aerodynamic part for the front of the car. Hadjar, with his calibrated sensing language, can report precisely how that part changes the feel at high speed. Lawson, with a different style and sensitivity, may report a different feel. Both reports are true to the person giving them. But they cannot substitute for each other within the same data series. The team cannot compare Lawson's feedback today with Hadjar's feedback last week and draw a conclusion about the part's effectiveness. That is the blind spot the numbers on the standings do not reflect. Lawson can score, but the data he gives the team does not connect to the data Hadjar had built. This is the kind of noise that must be separated from real signal. Red Bull, according to what the team has disclosed, uses simulator sessions to keep Hadjar's reflexes and sensory map current. In theory, this keeps him from losing full connection with the car. But the correlation between simulator and track has never been perfect. The simulator does not reproduce tyre degradation over a long stint, the effect of changing track temperatures, or the feeling of losing grip once a tyre is past half-life. Those things are only available on the real track. And they are exactly what a driver needs to understand a car in a new regulation cycle, where every old assumption must be re-tested from scratch. I have a different way of looking at the value of this absence. In the transfer consulting industry, we evaluate players with time-series data — the change in metrics across many games. A young driver like Hadjar is at the stage where his learning curve is steepest. Every lap he completes adds to the team's model of what he needs from the car. When that time series breaks, the team loses not only the data from the missed period. It loses the slope of that curve. This is why I do not underestimate the impact of this injury. Data is never in a hurry, but people always are. Red Bull's leadership may be looking at Lawson's two points finishes and feeling reassured. But that number measures short-term results, not long-term developmental capability. Viewed through the lens of data series, Hadjar's injury creates three kinds of loss. The first is missing data — laps he did not run and feedback he could not give. The second is noisy data — feedback from the substitute that does not match the calibrated sensing language. The third, and hardest to measure, is biased baseline data — when the team compares new parts based on a different driver, they may draw conclusions that are right for Lawson but wrong for Hadjar. A more concrete example. In the new regulation cycle, teams must rebuild their understanding of tyre management. With new tyres and different aero loads, the operating temperature window changes. The driver is the only one who can feel whether that window is opening or closing in real time. If Hadjar, who has spent thousands of kilometers building a sensory map of the tyres on the RB22, misses several consecutive races, then upon return he must rebuild part of that map. Meanwhile, the car has changed through upgrades he knows only through data, not through feel. This is a process that cannot be replaced by attending the track. Sitting in the garage looking at a data screen is different from driving the car and feeling it. The team can show Hadjar thousands of telemetry traces, but he cannot feel how the suspension changed through a specific corner unless he drives through that corner himself. There is one more detail that public data does not clearly show: opportunity cost. Every cost-cap hour spent on one development direction is an hour not spent on another. When a team loses the feedback of a driver who had bonded with the car, it tends to be more cautious in upgrade decisions. That caution, in a regulation cycle where every team is racing to understand new rules, can become a cumulative disadvantage week by week. The comparison with Lawson is fairer if we separate two kinds of value. Racing value — points, finishing positions, the ability to keep the car on track — Lawson delivers. Development value — the ability to translate feel into continuous technical data — is something else. A team can survive with substitute racing value for a few races. But development value cannot be patched by a new arrival, no matter how talented. This is why I watch the team's technical briefings rather than just the standings. The tone of the chief engineer when speaking about upgrade progress reveals more than a substitute's points. When they say the team needs more data, that is a signal the feedback channel is blocked. The crowd celebrates every time a substitute scores. We love stories of stand-ins outperforming expectations. But that story is told through results, not process. In a sport dominated by cost caps, the most valuable thing reaches beyond the points from a Sunday afternoon. It is the accumulated data that helps the team make upgrade decisions the following Tuesday. There is an implicit assumption most commentary is making: that any driver in the seat provides equivalent data. That assumption is wrong. Driver data is the translation of personal sensation into technical language, and each person translates differently. When a team changes interpreters, it does not just change the reading voice. It changes the vocabulary. I have seen this in the transfer industry many times. When a football team changes strikers, it does not just change the source of goals. It changes a data series about how the team creates chances. A striker who runs into space one way cannot continue the data of one who runs another way. F1 is the same. Lawson is good, but he is not Hadjar. And in a regulation cycle where every correlation is new, that difference is worth more than a point. Every regulation cycle has a group of drivers who lose momentum at the most critical moment. Teams still treat drivers as replaceable labor, when in reality they are a data channel that cannot be replicated. What I leave behind to reflect on comes down to one question: when Hadjar returns, how much value will the data series he built still hold. The RB22 Hadjar returns to will not be the car he left. And in the new regulation cycle, every week of absence is a week the team's learning curve runs backward. Next weekend, I will be watching not Lawson's track position, but the direction of new parts on the RB22 — and whether the team still has the confidence to read the car through the eyes of someone who is not driving it.