Separate decision errors from execution errors

Generated from content/lms/coaching-science/04-coach-perception-and-decision-quality/04-separate-decision-errors-from-execution-errors.md; edit the source file, not this page.

Source path: content/lms/coaching-science/04-coach-perception-and-decision-quality/04-separate-decision-errors-from-execution-errors.md

Course: Coach drivers with evidence, not instinct

Module: Coach perception and decision quality

Estimated duration: 45 minutes

A coach can only fix the mistake that actually happened. That sounds obvious until you are standing by the car after a session, the driver is frustrated, the data trace shows a lost exit, and everyone wants a quick answer. The easy answer is usually an execution answer: brake harder, turn in earlier, squeeze the throttle, be smoother. Sometimes that is right. But sometimes the driver made a good physical input from a bad decision. Sometimes the hands, feet, and release were not the real problem. The driver chose the wrong reference, committed to the wrong speed, copied another car's turn-in point without adapting it, or gave too much attention to learning the track and not enough to feeling what the car was telling them.

This lesson teaches you to separate those two categories before you coach. A decision error is a wrong choice about what to do, where to do it, or what information to trust. An execution error is a failure to carry out the right choice with the needed timing, rate, pressure, or smoothness. The two can look identical from the outside. Both can produce a late apex, a missed exit, a hesitant throttle trace, or a driver who says the car would not take it. Your job is to slow the debrief down enough to ask: did the driver choose the wrong plan, or did the driver have the right plan and fail to deliver it?

The reason this matters is that every driver makes errors, and the useful driver is not the one who pretends otherwise. The useful driver is the one who can recognize the error, analyze it, and learn from it. That is also the useful coach. You are not trying to dwell on mistakes or turn every session into a courtroom. You are trying to find the correction with the shortest path back to better driving. If the mistake was a decision problem, drilling smoother hands may make the driver better at repeating the wrong choice. If it was an execution problem, giving a longer lecture about strategy may leave the real motor skill untouched.

The core rule is simple: before prescribing a fix, identify the driver's intent, the information they used, and the physical input they made. Intent tells you the plan. Information tells you what cue or reference drove the plan. Input tells you whether the plan was carried out. If intent and information were wrong, treat it as a decision error first. If intent and information were sound but the physical action missed the target, treat it as an execution error first. If both were wrong, fix the earliest wrong thing, because later corrections are built on top of it.

Start with intent. Ask what the driver was trying to accomplish in that corner on that lap. Keep the question concrete. Were you trying to protect exit speed, carry more entry speed, get to throttle earlier, make the apex, follow the car ahead, pass, defend, or just survive a new section of track? The answer matters because the same trace can have different meanings. A late minimum speed can be a deliberate patience choice in one car and a sign of entry overload in another. A lift at the exit can be a throttle execution problem, but it can also be the result of deciding to go to throttle before the car was able to accept it.

Then ask what information the driver used. This is where many coaching errors start. Drivers often borrow reference points from video, instructors, friends, or faster cars. That is useful preparation, but it is not a commandment. A reference point is a reference point. The driver may use the same object and still need to turn before it, after it, or adjust how much the car is loaded when they arrive there. If a driver copied a turn-in point from a different car and then missed the exit, the bad outcome may not come from poor hands. It may come from treating another driver's reference as a fixed instruction.

Finally, ask what physical input actually happened. Did the brake pressure match the plan? Did the release come at the intended rate? Did the steering build cleanly? Did the throttle application match the available grip, or did the driver breathe the throttle, add too soon, then lift at exit? Execution is the delivery layer. It is the part you can often see in video, feel in the passenger seat, hear in the engine note, or read in data. But execution only has meaning after you know the decision it was trying to serve.

A useful coaching diagnosis has three columns. Column one is choice: the driver's intended line, speed, timing, and objective. Column two is cue: the reference or sensation the driver used to choose that action. Column three is delivery: what the driver did with the controls. When the choice is wrong, coach the plan. When the cue is wrong, coach the driver's attention. When the delivery is wrong, coach the input. This keeps you from spending coaching attention on the wrong layer.

For an intermediate driver, the hardest part is that the categories overlap. A driver who turns in late may have decided too late, may have looked too late, may have chosen the wrong reference, or may have chosen correctly and moved the wheel too slowly. A driver who is slow out may have carried too much entry speed, may have been hesitant with throttle, may have breathed the throttle in a kink, or may have gone to throttle early enough to create a later lift. The lost time is visible. The reason is not automatically visible. The coach has to identify why, and that is not easy.

Use this sequence in the debrief. First, describe only what happened. Avoid diagnosis language at the start. Say that the throttle came in, then came out near exit. Say that minimum speed occurred later than the comparison lap. Say that the car reached the apex with extra steering still in it. Say that the driver was still adding brake after the intended marker. Those are observations. They keep the conversation open.

Second, ask for the driver's model of the lap. What were you trying to do there? What did you look at? What did you feel? What did you expect the car to do? The driver's answer often reveals whether you are dealing with a decision problem. If the driver says they were trying to be early to throttle because earlier throttle is always faster, and then the data shows an exit lift, the first coaching point is not foot smoothness. The first coaching point is that early throttle is not the same as useful full throttle. If the driver says they turned at the cone because the instructor in an earlier session told them to, but the car is now faster and the line no longer works, the problem is reference rigidity.

Third, compare the driver's intention to the outcome. If the driver wanted a later apex to protect exit and actually placed the car late but still hesitated to throttle, you may be looking at execution or confidence. If the driver wanted more entry speed and achieved it, but the data shows delayed full throttle and a slow exit, you may be looking at a decision tradeoff that cost more than it gained. If the driver wanted to copy a fast video line and the car never settled, the mistake may be preparation becoming over-programming.

Fourth, prescribe one correction at the earliest useful layer. Do not stack five fixes. If the decision was wrong, give the driver a new objective for the next session. If the cue was wrong, give one earlier or more reliable cue. If the execution was wrong, give one control target. The lesson is not to create a full theory of the driver in every debrief. It is to pick the one cause that, if improved next lap, makes the biggest difference.

Decision errors usually have a verbal signature. The driver describes a belief, rule, or plan that does not fit the situation. They say they were trying to learn the track rather than drive the car near its limit. They say they used a video reference as if it were fixed. They say they got to throttle early because early throttle sounded faster. They say they turned where another driver turned. They say they added speed because the previous corner felt easy, even though the exit was the important part. These are not clumsy hands. These are choices.

Execution errors usually have a different signature. The driver can explain the correct plan and the correct cue, but the delivery did not match. They knew they needed to wait for rotation before adding throttle, but their foot moved early. They knew the release needed to be smooth, but the brake came off abruptly. They knew the apex target, but the steering rate was too slow. They knew they should keep the car balanced in the kink, but they breathed the throttle. In that case, another lecture about the plan may not help. The driver needs a smaller action, a rhythm, a sensation, or a repeatable drill.

Do not let the driver hide behind one category. Some drivers call every problem execution because that feels less threatening: I know what to do, I just did not do it. Other drivers call every problem decision because it sounds analytical: I chose the wrong line. You need evidence. The evidence may come from data, video, seat feel, driver self-report, and written notes. Writing matters because it forces honesty. A driver who records how close they drove to the limit in each section, then answers debrief questions after each session, becomes more aware of exactly what they are doing. Awareness is the gateway skill for both decision and execution improvement.

A productive self-debrief for this lesson has five questions. What was I trying to make happen in that corner? What cue made me start that action? What did I actually do with the controls? What did the car do as a result? If I repeat that corner next session, which one layer will I change first? The order is important. If you start with what to fix, you will often pick the most obvious symptom. If you start with intent, cue, action, and result, you will usually find the cause.

You can also use sensory channels to separate the categories. Visual information often exposes decision and cue errors. Did the driver look for the right reference? Did they collect enough information about the corner? Did they focus too hard on the map of the track and not enough on the car at the limit? Kinesthetic information often exposes execution and balance errors. Did the car take a set? Did the driver feel the weight transfer? Did the driver sense g-force building or bleeding away? Auditory information can expose throttle mistakes: a breath, a lift, a too-early squeeze, or an engine note that rises before the chassis is ready. A driver learning a new track can deliberately spend sessions soaking up visual, kinesthetic, and auditory information. As a coach, you can use the same idea in diagnosis.

The most common decision error in this lesson is reference overcommitment. Preparation is valuable. Track maps, video, simulation, and written descriptions can reduce the mental load of a new track. But the driver must not set every detail in stone before driving. If they copy the exact turn-in from a video without accounting for car, speed, tires, or confidence, they may make a rational-looking error. The fix is to keep the reference but loosen the rule. Use the object as a reference, then adjust whether the action begins before it, at it, or after it based on the car's response.

Another common decision error is objective confusion. The driver does not know what the corner is for. They say they are working on entry speed, but the corner rewards exit speed. They say they are learning the track, but they are using so much attention on corner direction and line that they are not sensing the car. They say they are trying to be smooth, but the actual target is to identify the limit earlier. In these cases, the next-lap instruction should define the objective. For this corner, protect the exit. For this lap, soak up visual references. For this session, rate how close each section is to the limit. A clear objective makes good decisions possible.

The most common execution error is timing mismatch. The driver chooses the right thing but begins it at the wrong time or the wrong rate. They decide to go to throttle on exit, but the throttle begins before the car is pointed enough, so they lift later. They decide to carry speed through a kink, but their foot breathes out of habit. They decide to get the car slowed before turn-in, but the brake release trails longer than intended. The correction is not a new philosophy. It is a smaller, measurable action: delay the first throttle squeeze until the steering is unwinding, hold maintenance throttle through the kink, or finish the main brake work earlier.

A second execution error is pressure mismatch. The plan is right, but the input magnitude is wrong. The driver brakes at the right marker but not hard enough, then carries unwanted speed into the corner. Or the driver adds throttle at the right location but too quickly for the grip available. Or the driver turns at the right point but adds too much steering too soon and asks the front tires to do work they cannot do. In the debrief, this sounds like the driver knew exactly where they wanted to act. In the car, the action was not calibrated.

A third execution error is attention leak under load. The driver may make the right decision in the paddock and lose it at speed. That is not a moral failure. It is normal that the more attention spent on remembering which way the track goes, the less attention remains for limit sensing, references, and control precision. The solution is to reduce cognitive load. Preparation helps, but so does not over-programming. On track, assign one sense or one section at a time. After the session, write down what happened. This creates awareness without demanding that the driver solve the whole circuit at once.

As a coach, listen for the recovery path. A driver who has learned from enough errors begins to recognize when the car is beyond the limit and how to survive it. That experience is not built by pretending errors are rare. It is built by analyzing them without panic. If the driver went beyond the limit because of a wrong decision, the recovery discussion should include the earlier cue or choice that would have prevented it. If the driver went beyond the limit because of execution, the recovery discussion should include the input that needs to be changed next time. In both cases, the driver is building a library of patterns.

The best debriefs are specific enough to change the next lap. Avoid broad verdicts like be smoother, be more committed, be less aggressive, or trust the car. Those may be emotionally satisfying, but they do not separate decision from execution. Instead, say that the driver chose a turn-in point from a different speed range. Say that they decided on throttle before confirming the car was pointed. Say that they had the right exit plan but their foot moved faster than the chassis could accept. Say that they used the right brake marker but did not deliver enough initial pressure. These statements tell the driver what category the error belongs to and what to do next.

Use data carefully. Data can show that the driver was in fast and out slow. It can show a later minimum speed. It can show hesitant throttle, a breath in the kink, early throttle followed by a lift, or delayed full throttle after too much entry speed. But data by itself does not automatically explain the cause. A trace is evidence, not the whole diagnosis. Combine the trace with the driver's stated intent and the cue they used. That is how you avoid turning every data difference into an execution scolding.

Video has the same limitation. It can show placement, timing, steering motion, traffic, and whether the driver appears rushed. It may reveal that the driver was following another car, adapting to traffic, or reacting to an unexpectedly fast approach. But you still need intent. A late turn-in on video might be a chosen later apex, a missed reference, or slow hands. Ask before you label it.

Passenger-seat feel is useful because it captures balance and timing. You may feel the car still loaded when the throttle arrives. You may feel the driver ask for steering after the front tires are already busy. You may hear the engine note rise, fall, and rise again. But seat feel can tempt you into immediate execution coaching. Pair it with one question after the run: what were you trying to do there? If the driver answers with a flawed rule, coach the rule before the foot.

This lesson sits between several related coaching skills. Spending attention on the decisive cue comes before this when the main problem is where the driver's eyes and attention go. Building next-lap patterns comes after this when you have identified the correct category and need to turn it into a repeatable plan. Protecting cognitive bandwidth matters throughout because a driver who is overloaded will make both bad decisions and poor inputs. Your job here is narrower: classify the error well enough that the next coaching instruction lands in the right place.

A practical classification test is the one-lap replay. Ask the driver to replay the corner in words before you show the data. A decision error often appears as a wrong or vague script: I was just trying to get through, I used the cone because that is what we said earlier, I wanted more entry speed, I tried to get on throttle as soon as possible. An execution error often appears as a correct script with a missed physical step: I wanted to wait, but I squeezed early, I wanted to hold throttle, but I breathed it, I wanted to release slowly, but I came off too fast. The script is not perfect evidence, but it tells you where to look.

The second test is the repeatability test. If the driver repeats the same wrong outcome while giving the same wrong explanation, suspect decision. If the driver gives the right explanation and the outcome varies depending on pressure, fatigue, or speed, suspect execution. If the driver improves immediately after one clearer objective, it was probably decision or cue. If the driver improves only after several repetitions of a smaller control action, it was probably execution.

The third test is the transfer test. Change the context slightly. If the driver can execute the input in an easier corner but not in the problem corner, the decision or cue environment may be the issue. If the driver chooses the correct plan in the classroom but cannot deliver the timing anywhere on track, the motor execution needs work. This test keeps you from blaming a driver for a skill they actually have, or giving a theory lecture for a control movement they have not yet built.

When you have both kinds of error, prioritize the upstream one. Suppose the driver chooses too much entry speed and then has a messy throttle trace. The throttle problem is real, but it may be caused by the entry decision. Fix entry objective first. Suppose the driver chooses the correct patient entry but has a foot that snaps to throttle early. Fix the execution. Suppose the driver uses the wrong reference, turns late, then rushes the steering. Fix the cue first. The later symptoms may clean up after the earlier cause changes.

Your language should protect learning. Instead of telling the driver they made a bad decision, say the decision did not match what the corner rewarded. Instead of saying they cannot execute, say the plan was right and the delivery needs calibration. This is not softening the truth. It is making the truth usable. Drivers learn faster when the error is specific, observable, and correctable.

You should also protect against false certainty. Sometimes you will not know. In that case, say so and design the next run to find out. Have the driver keep the same entry decision but change throttle timing. Or keep the same reference and change steering rate. Or keep the same physical input and change the objective for the corner. A good diagnostic drill produces evidence. It is better to run one clean test than to invent confidence in the paddock.

The final standard is next-lap usefulness. After your debrief, the driver should be able to say one sentence before going back out: I am changing the decision, the cue, or the execution. If they cannot say which one, your coaching is still too vague. If they can say it and the next session gives you evidence, the lesson is working.

Worked example: early throttle that creates a later lift

The data example gives a classic trap: the driver appears to get to throttle early, then has to lift at exit, and the result is delayed full throttle. A shallow diagnosis says the driver needs better throttle execution. That may be true, but it is not the first thing to assume. Start with intent. If the driver believed early throttle was the goal, the error begins as a decision error. They chose a rule that did not fit the corner. The correction is to redefine the goal as useful throttle that can continue, not merely first throttle application.

Now inspect execution. If the driver understood that the car needed to be pointed before full commitment, but the foot still moved early and caused the exit lift, the decision was sound and the execution was poor. The correction becomes a physical timing drill: wait for the steering to begin unwinding before adding meaningful throttle, then make the first application small enough that it can stay in. The same squiggle in the throttle trace can therefore produce two different coaching instructions. One fixes the driver's rule. The other fixes the driver's foot.

Worked example: learning a new track without freezing the wrong reference

A driver studies video before a new track and arrives with several reference points. That preparation is useful because it reduces the brain power needed to know the track direction and basic references. The decision error appears when the driver treats the reference as fixed. They turn exactly where the video driver turned, even though their car, tire, speed, confidence, or line is different.

In the debrief, do not punish preparation. Redirect it. Keep the object as a reference, but teach the driver to adjust how it is used. The next session assignment might be to use the same turn-in object three ways across three laps: just before it, at it, and just after it, while rating which version lets the car reach the exit with less correction. If the driver can make those changes deliberately, the original problem was a decision and cue problem. If the driver chooses the right version but cannot turn the wheel at the intended rate, then execution becomes the next target.

Common mistakes

Mistake one is coaching the symptom. The car is slow out, so the coach says get to throttle earlier. But the data may show that the driver already got to throttle too early and then lifted at exit. Good coaching starts by asking why the exit was slow, not by prescribing the opposite of the symptom.

Mistake two is treating borrowed references as commandments. Video, maps, simulations, and other drivers can help a driver prepare, but the driver must still adapt the reference to the car and lap. Good looks like using the same reference object while changing exactly how and when the action begins.

Mistake three is calling every mistake a lack of smoothness. Smoothness is not the same as correctness. A driver can smoothly execute the wrong decision. Good looks like identifying whether the plan, cue, or input was the earliest cause.

Mistake four is accepting the driver's explanation without evidence. Drivers often describe what they meant to do, not what they did. Good looks like comparing the driver's replay with data, video, seat feel, and written notes.

Mistake five is overloading the next run. If the driver leaves the debrief with a new brake point, new apex, new throttle rule, and new vision target, the coach has created a cognitive load problem. Good looks like one next-lap correction at the earliest useful layer.

Drill: the three-column error sort

Run this drill for one full event day or at least three sessions. After each session, choose two corners: one that improved and one that cost time or confidence. For each corner, write three columns: choice, cue, and delivery. In choice, write what you were trying to make happen. In cue, write the reference, sensation, or information that triggered the action. In delivery, write what you actually did with brake, steering, throttle, or placement.

For the next session, change only one column in one corner. If you change the choice, keep the cue and delivery as stable as possible. If you change the cue, keep the objective and control input as stable as possible. If you change the delivery, keep the plan and reference stable. The success criterion is not immediate lap time. The success criterion is that you can name which layer changed and what the car did in response. By the third session, you should be able to classify at least one error as decision-led and one as execution-led with evidence rather than guesswork.

When the category is mixed

Many real mistakes are mixed. A driver carries too much entry speed, then hesitates on throttle, then misses the exit. The entry choice, the throttle execution, and the exit result are connected. Do not try to fix all of it in one sentence. Work upstream. If the excessive entry speed created the delayed full throttle, fix the entry objective first. If the entry was correct and the delay came from a hesitant foot, fix the throttle delivery first.

Mixed errors are also why written debriefs matter. A driver who writes down ratings and answers session questions becomes more honest about what actually happened. That record helps the coach see whether the same choice keeps creating the same result, or whether the driver has the right idea but inconsistent delivery.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Ultimate Speed Secrets - Ross Bentley	c4d9ecef-02de-0ceb-06e3-ddae82099f8e	404	1	uio_books_raw_v1
2	Ultimate Speed Secrets - Ross Bentley	3ac19536-3379-ed67-9a0f-ad94196e88d8	426	1	uio_books_raw_v1
3	Data-for-Drivers-PRINT	22c43975-be07-0a46-7288-6d34fd6842a6	13	1	uio_books_raw_v1
4	Ultimate Speed Secrets - Ross Bentley	0a61558b-5a10-1225-f51f-f058f81f3c61	209	1	uio_books_raw_v1
5	Ultimate Speed Secrets - Ross Bentley	0237a5bd-e2d4-724e-bc2e-ba13db924f66	11	1	uio_books_raw_v1
6	Ultimate Speed Secrets - Ross Bentley	7816dd86-ce80-1320-b6ed-b34e005cc98f	16	1	uio_books_raw_v1