Finding Tenths Nobody Sees

Walk through any karting paddock on a race weekend and you'll see dozens of identical karts. Same chassis manufacturer. Same engine homologation. Same tyres, from the same batch, all at the same pressures. To the untrained eye, there is nothing to separate one machine from the next.

And yet, when the lights go out, some karts are simply faster. Not because of the engine. Not because of the tyres. Because of how the chassis has been set up — and the engineer who understood what the track, the conditions and the driver needed before anyone else.

The Myth of the "Fast Kart"

There's a persistent belief in grassroots motorsport that some karts are just faster. That a factory chassis off the line will be inherently quicker than its shelf neighbour. This is, to put it bluntly, nonsense. What makes a kart fast is how it's prepared, how the geometry is set, how the driver's weight interacts with the chassis flex characteristics, and how all of those variables are tuned to suit the specific conditions of that day, on that track, in that session.

A kart chassis is a living, breathing thing. It flexes. It loads and unloads. It transfers weight in ways that are invisible at speed but absolutely critical to how the rear axle drives out of a corner. Get it right and you have a kart that rotates beautifully, puts its power down cleanly, and feels alive in the driver's hands. Get it wrong and you have an understeering, tyre-eating liability that no amount of driver talent can compensate for.

What a Setup Engineer Actually Does

My job begins long before the driver arrives at the track. It starts with understanding the circuit layout, the surface type, the expected weather conditions, and the specific characteristics of the driver I'm working with — their weight, their driving style, their experience level, and what they're trying to achieve that weekend.

From there, I'll build a baseline setup. Ride height, caster, camber, toe, axle stiffness, seat position, front bar configuration — every parameter is a lever that affects how the chassis behaves. Change one and you change everything. A 2mm shift in seat position can transform the balance of the kart. A different front bar can be the difference between a podium and P15.

The real skill isn't knowing what each parameter does in isolation — you can learn that from a textbook. The skill is understanding how they interact, how they compound, and how to adjust them in real time based on feedback from the driver and the data system. That's where experience, instinct, and thousands of hours at the trackside become irreplaceable.

The Language of Feel

One of the most undervalued skills in motorsport engineering is the ability to translate driver feedback into setup changes. A driver will tell you "it's pushing in the middle of the corner" or "I'm losing the rear on turn-in." Those are feelings, not instructions. It's the engineer's job to decode that language, cross-reference it with the data, and make a change that solves the problem without creating a new one.

This is where the gap between a good engineer and a great one becomes a chasm. A good engineer knows the theory. A great engineer has felt it — in their own hands, in their own racing career — and can connect a driver's description of a problem to a mechanical solution in seconds. That's not something you learn in a classroom. It takes years. Sometimes decades.

Two karts can be mechanically identical and separated by a second a lap. The only difference is the engineer standing behind them.

Why This Matters Beyond Karting

The principles I apply in karting are the same principles that govern setup in Formula 1, Le Mans Prototypes, GT racing, and every category in between. Chassis setup is chassis setup. The variables scale — from caster angles on a kart to spring rates on a GT car — but the engineering philosophy is universal: understand the platform, read the data, listen to the driver, and make the chassis work with the conditions, not against them.

This is why the best F1 teams in the world employ hundreds of engineers. Not because the technology is complex — although it is — but because the art of setup, of finding the perfect balance between mechanical grip and aerodynamic load, between driver confidence and raw lap time, is one of the most nuanced disciplines in all of sport.

In karting, you get one engineer. Maybe two. And the margins are just as fine.

Every modern racing kart generates thousands of data points per second. GPS position, speed, RPM, lateral G-force, longitudinal acceleration, steering angle, throttle position, temperature — the black box sees everything. And most of it goes completely unread.

Data acquisition has become one of the most powerful tools in motorsport. But it's also one of the most misunderstood. Having a data system doesn't make you faster any more than owning a piano makes you a musician. The value isn't in the data itself — it's in what you do with it.

Numbers Don't Lie. But They Don't Speak Either.

The first thing I tell any driver or parent investing in a data system is this: data is not a shortcut. It's a mirror. It shows you exactly what happened — every braking point, every apex, every throttle application — with zero emotion and zero ego. It doesn't care if the driver "felt fast." It tells you whether they were fast. And that honesty is uncomfortable.

But raw data is meaningless without interpretation. A speed trace on its own is just a squiggly line. The engineer's job is to look at that line and understand the story it tells: where time is being lost, why it's being lost, whether the problem is driver technique, chassis setup, or both — and what to do about it.

Pattern Recognition: The Engineer's Superpower

What separates an experienced data engineer from someone who just learned the software is pattern recognition. When I look at a dataset from a session, I'm not reading every number sequentially. I'm scanning for signatures — patterns I've seen hundreds of times before that immediately tell me what's happening.

A dip in minimum speed through a particular corner type tells me the rear is stepping out and the driver is scrubbing speed to compensate. A spike in lateral G on corner entry followed by a plateau tells me the front is loading too aggressively and the kart isn't rotating. A gradual loss of sector time over a stint tells me tyre degradation is outpacing the setup window.

These patterns are invisible to most people. They're obvious to me because I've spent nearly two decades watching them repeat across different drivers, different chassis, different circuits, and different conditions. That library of patterns is what makes an experienced engineer worth their weight in gold — and it's exactly what I was hired to translate into AI algorithms at a motorsport-tech startup.

Data as a Coaching Tool

One of the most powerful applications of data in karting isn't setup — it's coaching. When you overlay two drivers' data on the same circuit, the differences become undeniable. You can show a driver exactly where they're losing time, exactly how their braking compares to the benchmark, and exactly what they need to change. It removes the subjectivity from coaching conversations.

But there's a subtlety here that most people miss. Data tells you what happened. It doesn't always tell you what to do. A driver might be braking 5 metres later than the benchmark, but that doesn't mean they should brake earlier — maybe they can carry more speed if they change their line. Maybe the chassis needs adjusting so they can trust the front end more. The engineer's role is to use data as a diagnostic tool, not a prescription pad.

Data doesn't make you faster. Understanding it does. And that takes an engineer who's read a thousand datasets before yours.

The Future: AI and the Democratisation of Data

At a motorsport-tech startup, I spent months translating my pattern-recognition instincts into structured data that a machine learning team could use to build algorithms. The goal was ambitious: create an AI that could do what I do — read data, recognise problems, and suggest solutions — but make it accessible to every racer, not just those who can afford a professional engineer.

It was fascinating work, and it forced me to examine my own thought process in ways I'd never done before. When you have to explain to a data scientist why a 0.3G difference in lateral load at a particular point in a corner matters, you start to realise just how much of elite engineering is built on accumulated intuition. Can AI replicate that? Eventually, probably. But we're not there yet — and the human engineer who can feel the data, not just read it, still has a role that no algorithm can replace.

When people think about driver development, they think about coaching. They picture someone standing at the side of the track with a stopwatch, shouting "brake later" or "carry more speed." And yes, that's part of it. But the most impactful driver development work I've done in 18 years hasn't happened trackside with a clipboard. It's happened in the engineering bay, at the data screen, and in the quiet conversations between sessions where the real learning takes place.

The Engineer as a Silent Coach

A driver's development isn't just about their technique on track. It's about their ability to communicate feedback, manage pressure, understand their own machinery, and make smart decisions when the race is live and emotions are high. These are skills that a race engineer influences every single day — often without either party realising it.

When I work with a young driver, I'm not just setting up their kart. I'm teaching them how to describe what the kart is doing. I'm training them to differentiate between "the rear feels loose" and "the rear is stepping out on initial turn-in under braking" — because the precision of their feedback directly determines the quality of the setup changes I can make. Over time, that process sharpens their awareness, deepens their understanding of vehicle dynamics, and makes them fundamentally better racing drivers.

The Development Pathway

I've worked with drivers at every stage of the journey — from complete beginners who've never worn a helmet, through to international-level competitors racing at FIA World Championship events. The engineering approach changes at each stage, but the philosophy doesn't.

At club level, the priority is building confidence and consistency. The chassis setup needs to be forgiving, predictable, and confidence-inspiring. I'll typically run a softer setup that sacrifices peak lap time for drivability, because a driver who trusts their kart will learn faster than one who's fighting it.

As the driver progresses, the setup evolves with them. We start chasing tenths. The kart becomes more aggressive, more responsive, more demanding. The data sessions become more detailed, the feedback conversations more technical. By the time a driver is competing at international level, the relationship between driver and engineer is a genuine partnership — each trusting the other to deliver their part of the performance equation.

What Makes a Great Engineer-Driver Partnership

The best results I've ever been part of came from partnerships where the driver and I had complete trust in each other. They trusted me to give them a kart that was competitive. I trusted them to give me honest, accurate feedback — even when it meant admitting a mistake or acknowledging that they weren't extracting the maximum.

That trust takes time to build. It takes consistency, honesty, and a willingness from both sides to be wrong sometimes. The engineer who blames the driver for every bad result will never develop a great driver. The driver who blames the kart for every bad result will never find the tenths that matter.

You don't develop a driver by telling them what to do. You develop them by giving them the tools to understand what's happening and the confidence to act on it.

From Track to Technology

My work at a motorsport-tech startup was the natural evolution of this philosophy. If the engineer's role is to translate complexity into clarity — to take a wall of data and distil it into "do this" — then an AI tool that does the same thing has the potential to accelerate driver development on a massive scale.

The drivers who rise to the top in karting are almost always the ones who had a great engineer behind them. Not because the engineer had some secret sauce, but because they had someone who could decode the data, optimise the setup, and guide the driver's learning in real time. Making that expertise more widely available isn't just a business opportunity — it's a genuine contribution to the sport.

Here's a question for anyone who follows motorsport: name the race engineer for any current Formula 1 driver. Not the team principal. Not the technical director. The race engineer — the person who talks to the driver every single lap, who makes the strategy calls under pressure, who translates the entire car's behaviour into actionable instructions in real time.

Most people can't. And that tells you everything you need to know about how motorsport values its engineers.

The Visibility Problem

In karting — the foundation of virtually every professional racing career — the engineer's invisibility is even more pronounced. The driver stands on the podium. The team name appears in the results. The chassis manufacturer takes credit for the package. But the person who spent Friday evening rebuilding the engine, who diagnosed a handling imbalance from a data trace at 7am on Saturday morning, who made the setup call that found three tenths before the final — that person is rarely mentioned. Sometimes not even in the team's own social media.

This isn't a complaint. It's a structural observation about how motorsport distributes credit, and it has real consequences — particularly for engineers who are building careers, seeking new opportunities, or trying to demonstrate their contribution to the sport.

What an Engineer Actually Contributes

Let me quantify it. In a typical weekend of international karting, the difference between pole position and 10th on the grid might be three or four tenths of a second. Of those four tenths, the setup engineer can influence at least half — through chassis geometry, weight distribution, axle selection, tyre management strategy, and session-by-session adaptation to changing track conditions.

Two tenths doesn't sound like much. But two tenths is the difference between starting on the front row and starting in the third row. It's the difference between being in the fight and watching it happen. And that contribution happens silently, systematically, and without any of the recognition that comes with the result.

The Compounding Effect

Over the course of a driver's career, the engineer's influence compounds in ways that are almost impossible to measure. The driver who had a great engineer from age 10 arrives at 16 with a deeper understanding of their kart, a more sophisticated approach to feedback, and thousands of data-informed decisions embedded in their driving style. The driver who didn't? They might be equally talented, but they're starting from a different foundation.

This is the unseen legacy of the kart engineer — not just the results, but the invisible architecture of a driver's development that was shaped, session by session, by someone who never gets interviewed, never gets profiled, and rarely gets credited.

The engineer doesn't lift the trophy. But without them, there's no trophy to lift.

Changing the Narrative

Part of the reason I'm writing this — and the other articles in this series — is to begin changing that narrative. Not for self-promotion (although, yes, I'm aware of the irony), but because the motorsport engineering community deserves recognition for the extraordinary skill, knowledge and dedication it brings to the sport.

When a publication profiles a rising karting star, the engineer should be part of the story. When a championship is won, the engineer's contribution should be acknowledged in the same breath as the driver's talent. And when an engineer builds a career spanning 18 years, three continents, and every level from club racing to the FIA World Championship, that career should be visible — not hidden behind the names of the drivers they helped get there.

This is a sport built on partnerships. It's time we started recognising both halves.

The kart is ready. The setup is locked. The data has been reviewed, the strategy agreed. Everything that can be engineered has been engineered. And then there's the bit that can't — the space between the driver's ears.

In 18 years of standing on grids, I've learned that the last 30 seconds before a race are some of the most important of the entire weekend. Not because of anything mechanical. Because of everything psychological. What you say to a driver in those final moments — and critically, what you choose not to say — can define the result more than any setup change.

The Rule of Three

A driver on the grid is already operating at an elevated heart rate. Adrenaline is flowing. Their senses are heightened, their focus is narrowing. In that state, the brain's capacity to process complex information drops dramatically. If you walk up to a driver and give them five things to remember, they'll forget all of them by turn two.

This is why I work with a strict rule of three. Three clear, simple reminders. That's it. Not five. Not "one more thing." Three.

Those three points will have been discussed in detail earlier — in the driver briefing, after the last practice session, in the data review. The grid is not the time to introduce new information. It's the time to anchor the most important messages that the driver already understands but needs to hear one final time.

Something like: "Smooth first lap — no heroes into turn one. Build your rhythm in the first three laps. And remember, the rear will come to you once the tyres are in." That's it. Clear, calm, actionable.

What Not to Say

This is where experience matters more than enthusiasm. I've seen well-meaning parents, coaches, even team managers walk up to a driver on the grid and unload everything — reminders about braking points, warnings about specific competitors, lap time targets, strategy variations, technical information about the kart. All of it delivered with urgency, energy, and good intentions.

And all of it counterproductive. An overloaded driver is a tense driver. A tense driver brakes early, grips the wheel too hard, and makes reactive decisions instead of instinctive ones. The engineer's job on the grid is to simplify, not complicate. To reduce anxiety, not amplify it.

I never discuss competitors on the grid. I never mention what could go wrong. I never introduce anything the driver hasn't already heard. The grid is a space for confidence, clarity and calm — not a last-minute classroom.

Reading the Driver

Every driver is different on a grid. Some go quiet. Some want to talk. Some want eye contact and reassurance. Some want to be left completely alone. Part of the engineer's skill — a skill that takes years to develop — is reading which state the driver is in and adapting accordingly.

A young driver in their first final at an international event needs a very different approach to an experienced competitor lining up for a championship decider. The words might even be the same, but the tone, the body language, the timing — all of it shifts.

I've had drivers who performed best when I said almost nothing. A hand on the shoulder, a nod, and walk away. I've had others who needed me talking calmly right up until the 15-second board, because the sound of a familiar voice kept their heart rate down. There's no formula for this. It's pattern recognition of a different kind — reading people instead of data.

The best thing an engineer can give a driver on the grid isn't information. It's confidence.

Frame of Mind

What I'm ultimately trying to achieve is a very specific mental state: focused but relaxed. Alert but not anxious. Present in the moment, not thinking three laps ahead.

The drivers who perform best under pressure are the ones who trust their preparation. They trust their engineer has given them a competitive kart. They trust their own ability. And they trust the three simple things they've been told to focus on. Everything else fades into background noise.

Getting a driver into that state isn't coaching in the traditional sense. It's engineering — engineering the conditions for performance. And like every other part of my job, it's invisible to everyone watching from the barrier.

If chassis setup is the invisible art of motorsport engineering, tyre management is the invisible science. Every decision an engineer makes — from caster angle to axle stiffness, from driving style coaching to race strategy — ultimately filters down to one thing: how much grip the tyres can generate and for how long.

Tyres are the single most important variable in any race. They're also the most perishable. Understanding how they work, how they degrade, and how to keep them in their optimal window is arguably the most valuable skill a race engineer can have.

The Tyre Window

Every tyre has an optimal operating window — a temperature range and load range where it generates maximum grip. Below that window, the tyre feels slippery and unpredictable. Above it, the surface starts to overheat, the rubber grains, and grip falls off a cliff.

The engineer's job is to get the tyre into its window as quickly as possible and keep it there for as long as possible. That sounds simple. It's anything but. The window moves depending on ambient temperature, track temperature, track rubbering, fuel load, and the cumulative effect of every setup parameter on how the tyre is being loaded.

A kart that's set up with too much front end will overwork the front tyres and understeer as they degrade. A kart with too much rear grip will slide the rear tyres until they overheat and the driver loses confidence. The balance needs to be set so that all four tyres are working proportionally — and that proportion changes as the race goes on.

Reading Degradation in Real Time

One of the skills that separates experienced engineers is the ability to predict tyre degradation before it becomes visible in the lap times. By the time a driver starts losing significant time, the tyre is already well past its peak.

I watch for earlier signals. A slight change in the driver's line through a particular corner — they're compensating for something they can feel but might not articulate. A tiny increase in minimum corner speed that actually means the kart isn't rotating as sharply as it was three laps ago. A barely perceptible drift in sector time that's consistent across two or three laps rather than one outlier.

These micro-patterns are invisible on a timing screen. They're obvious in the data — but only if you know what to look for and you've seen the same patterns play out across hundreds of races on different compounds, in different conditions, on different circuits.

Setup for Tyre Life

There's a fundamental tension in motorsport engineering between outright pace and tyre life. A setup that maximises single-lap speed will often burn the tyres faster. A setup optimised for tyre life might sacrifice peak grip for consistency.

The art is finding the point where both overlap — where the kart is fast enough to compete at the front but gentle enough on its rubber to maintain that pace over a full race distance. That crossover point changes with every variable: tyre compound, track surface, air temperature, session length, and the driver's style.

Anyone can set a kart up to be fast for one lap. Setting it up to be fast for every lap — that's where the real engineering happens.

The Compound Equation

Different tyre compounds behave in fundamentally different ways. A hard compound will take longer to come in but will hold its performance for longer once it does. A soft compound gives immediate grip but degrades more aggressively. The engineer needs to understand not just the compound's characteristics in isolation, but how those characteristics interact with the specific chassis platform, the specific driver, and the specific conditions of that day.

I've run the same compound on the same track on two consecutive days and had it behave completely differently because the ambient temperature changed by five degrees. That's the level of sensitivity we're dealing with. And it's why tyre management can't be reduced to a formula — it requires the accumulated instinct that comes from years of watching rubber behave in every conceivable condition.

Rain is the great equaliser in motorsport. It rewards adaptability, punishes rigidity, and exposes the gap between engineers who truly understand their machinery and those who are following a setup sheet. When the first drops fall, the setup sheet is worthless. What matters is how quickly you can think, how deeply you understand the chassis, and how decisively you can act.

I've won some of my best results in the wet — not because I have a magic setup, but because the wet demands exactly the kind of engineering that comes from 18 years of experience. You can't look up a wet setup on the internet. You have to feel it.

Why Everything Changes

In dry conditions, a kart generates grip primarily through mechanical load — pressing the tyres into the track surface. The chassis is designed to flex in specific ways to manage weight transfer and maximise this mechanical grip. When the track gets wet, the grip level drops by roughly 30-40%, and the entire dynamic changes.

The chassis needs to generate more mechanical grip to compensate for the reduced surface friction. This means softer setups, wider axles, more caster, lower ride heights — everything aimed at making the chassis work harder, flex more, and transfer weight more aggressively to help the tyres find whatever grip is available.

But here's the subtlety: "wet" isn't one condition. It's a spectrum. Light drizzle on a warm track behaves completely differently to heavy rain on a cold surface. A drying track requires different thinking to one that's getting wetter. And a track that's wet in some corners but dry in others — the mixed condition — is the hardest of all, because you're essentially trying to set the kart up for two different grip levels simultaneously.

The Speed of Decision-Making

In dry conditions, you might have three or four practice sessions to refine a setup. In the wet, conditions can change between sessions — or even during a session. The engineer who waits for perfect data before making a change will be overtaken by the one who reads the conditions, makes a decisive call, and adapts in real time.

This is where experience is worth its weight in gold. When I see rain starting to fall 10 minutes before a session, I'm already running through a mental checklist of changes. I know from hundreds of wet sessions what the baseline needs to be. I know which parameters need to change first and which can wait. I know what the driver is going to feel when they go out, and I know what they're going to tell me when they come back in.

That speed of decision-making can't be taught in a weekend. It takes years of getting it wrong, learning from it, and building an internal library of wet-weather patterns that you can access under pressure.

Dry weather rewards precision. Wet weather rewards instinct. And instinct is just experience that's been internalised so deeply it feels automatic.

Reading the Track

One of the most undervalued skills in wet-weather engineering is reading the track itself. Not the data — the actual physical track surface. Where is the water sitting? Where is the rubber line? Where are the rivers forming? Where is the grip going to come back first as it dries?

I'll walk a circuit in the rain before a session — something not every engineer does — because the information you get from physically seeing where the water is pooling and where the surface is draining fastest is information that no data system can give you. It tells me which corners the driver can push in and which ones they need to respect. It tells me whether the inside or outside line will have more grip. It tells me how long the wet tyres are going to last before the track dries enough to start overheating them.

That information, combined with the right setup and clear communication to the driver, is how you turn a wet race from chaos into opportunity.

There's a perception in motorsport that karting is where engineers start, and "real" racing is where they end up. Cars. Downforce. Dampers. Complicated systems with hundreds of adjustable parameters and a team of 50 specialists to manage them. That's the serious stuff. Karting is just the warm-up.

I disagree. Having worked across karting, GT racing, single-seaters, and everything in between, I believe karting is the most demanding engineering environment in motorsport — and therefore the best training ground any engineer could ask for.

Nowhere to Hide

In a modern racing car, there are layers of systems between the engineer and the result. Aerodynamics can compensate for a mediocre mechanical setup. A sophisticated damper package can mask chassis problems. A traction control system can cover for a rear end that's poorly balanced. Data engineers, performance engineers, strategy engineers — each person handles a slice of the puzzle.

In a kart, there is none of that. No aero. No dampers. No electronics. No team of 20 engineers splitting the workload. There is a chassis, an engine, four tyres, and one engineer who is responsible for all of it. If the setup is wrong, there is no system to compensate. If the data is misread, there's nobody else to catch the mistake. If the driver isn't performing, the engineer is also the coach.

That level of responsibility — owning the entire technical package from start to finish — is what makes kart engineering so demanding and so educational. You can't specialise your way out of a problem. You have to understand the whole system.

Sensitivity and Precision

A kart is the most setup-sensitive racing machine on the planet. At the top level, the difference between first and tenth might be two or three tenths of a second — across a lap that's only 45 seconds long. That's a margin of less than 1%. And within that margin, the engineer's setup choices account for a significant portion.

Moving a seat position by 3mm changes the weight distribution enough to transform the handling. Swapping from a 50mm axle to a 40mm axle changes the rear grip characteristic completely. Adding or removing a front bar alters the kart's willingness to rotate by a degree that the driver will feel in the first corner.

Working at those margins — where changes are measured in millimetres and their effects are measured in hundredths of a second — develops an engineering sensitivity that transfers directly to any category. An engineer who can find a tenth in a kart can find a tenth in anything.

Cars have systems that compensate for engineering mistakes. A kart doesn't. That's why the best engineers in the world started in karting — and why many of them still say it was the hardest racing they ever did.

The Complete Engineer

Karting produces a specific kind of engineer — one who can build an engine, set up a chassis, read data, coach a driver, manage a race weekend, and make strategic decisions under pressure, all as a single person. That breadth of capability is increasingly rare in professional motorsport, where specialisation has fragmented the engineering role into dozens of sub-disciplines.

But the best race engineers in Formula 1 — the ones who sit on the pit wall and talk to the driver every lap — are almost always the ones who started in karting. Because the job of a race engineer, at any level, is fundamentally the same: understand the whole picture, communicate clearly under pressure, and make the machinery faster. Karting teaches all of that, in the most unforgiving classroom motorsport has to offer.

That's why, after 18 years, I still believe karting is the most valuable engineering experience available in the sport. Not despite its simplicity — because of it.