Spend coaching attention on the decisive cue
Generated from
content/lms/coaching-science/04-coach-perception-and-decision-quality/01-coach-attention-as-a-limited-resource.md; edit the source file, not this page.
Source path: content/lms/coaching-science/04-coach-perception-and-decision-quality/01-coach-attention-as-a-limited-resource.md
Course: Coach drivers with evidence, not instinct
Module: Coach perception and decision quality
Estimated duration: 55 minutes
Attention is a tool, not a mood.
When you coach a driver, your first job is not to notice everything. You cannot. Your driver cannot either. Motorsport attention is limited, and only a small part of the environment can be processed deeply at one time. That limitation is not a weakness to be beaten with more intensity. It is the operating condition of the job. The coach who accepts it becomes selective. The coach who ignores it becomes noisy.
The lesson rule is simple: spend coaching attention on the cue that can change the next lap. Not the cue that annoys you most. Not the cue that is easiest to describe. Not the cue that proves you know a lot. The cue that matters is the one that is task-relevant, close enough to the cause of the performance problem, visible or feelable by the driver, and small enough to act on during the next driving cycle.
This is why good coaching feels calmer than average coaching. If the driver is late to full throttle, missing the apex, breathing the throttle in a fast kink, and reporting tension in the hands, you do not throw all four observations into the helmet at once. You ask which one explains the others. If excess entry speed is forcing a late minimum speed, the slow exit and delayed full throttle may be symptoms. If the driver is simply not aware of where the car is relative to the apex, a precise awareness cue may solve more than a command to turn earlier. If fatigue is causing attention to wander, another line correction may be the wrong use of both your bandwidth and theirs.
Limited attention also changes what you do with data. Data does not make attention unlimited. It gives you witnesses. Speed, throttle, brake pressure, and time-loss traces can show you where the meaningful difference lives, but you still have to choose the coaching cue. A trace that shows a driver carrying too much entry speed, reaching minimum speed late, and delaying full throttle points you toward an entry-speed-to-exit-speed relationship. It does not give you permission to deliver a ten-point debrief. The useful data question is still why this trace matters for the next lap.
For an intermediate coach, the hard part is not finding something wrong. You can usually find plenty. The hard part is refusing nine correct observations so one useful observation can land.
Principle: attention has a cost
Every coaching cue taxes two people. It uses your attention while you observe, interpret, and decide. It uses the driver's attention while they listen, translate, remember, and attempt the change under speed. If you spend that attention on an irrelevant cue, you may cause the driver to miss the information they needed to drive safely and quickly.
That is the core mechanism. Drivers must differentiate task-relevant information from irrelevant information while driving. They also have to shift frames from one cue to another: their own line, the actions of other drivers, mechanical signals from the car, and internal physiological states such as fatigue or hydration. Your coaching either helps that frame shifting or overloads it. A useful cue narrows the driver's field to the information that matters now. A weak cue widens the field until the driver has too much to process.
This is why coaching attention is different from general observation. Observation asks what happened. Coaching attention asks what deserves the next unit of limited bandwidth. In the paddock, on video, at trackside, or in the passenger seat, you are not merely collecting errors. You are budgeting attention.
The cost shows up in familiar ways. The driver nods during the debrief, then changes nothing on track. The driver fixes the apex but loses the exit because the real issue was entry speed. The driver becomes more forceful with the wheel or pedals because they heard the cue as an effort command. The driver asks whether they should brake later, apex later, unwind sooner, and pick up throttle earlier, all in the same corner. That is not a motivated student problem. It is usually a cue-selection problem.
Doing the wrong thing with more effort rarely improves performance. In coaching terms, saying the wrong cue more loudly, with more urgency, or more often does not make it more useful. Great performance is often produced with less visible effort, not more. Good coaching should move the driver toward that same economy: cleaner attention, cleaner input, cleaner result.
What makes a cue decisive
A decisive cue has four properties.
First, it is connected to the cause rather than only the symptom. A late throttle trace matters, but the cue might not be get to throttle sooner. If the driver is entering too fast and using too much road midcorner, earlier throttle may only make them lift at exit. The decisive cue may be to adjust entry speed so the car can be pointed and committed earlier. This is the difference between coaching the trace and coaching the cause behind the trace.
Second, it is task-relevant for the current situation. The useful cue changes with the context. In open track, the key cue might be line placement or apex awareness. In traffic, it might be the other car's behavior. In a long session, the key cue might be the driver's wandering focus or rising fatigue. In a car with a possible issue, it might be a mechanical signal. You are not loyal to your favorite cue. You are loyal to the cue the situation needs.
Third, it is available to the driver while driving. A cue the driver cannot see, feel, or check at speed is usually a debrief topic, not a next-lap command. If the driver can note how close the car is to the apex, feel whether they had to lift at exit, or recognize whether the throttle breathed in the Kink, the cue can guide action. If the cue requires a spreadsheet, it belongs after the session.
Fourth, it is small enough to practice. A cue such as improve corner entry is too broad. A cue such as notice whether minimum speed happens before or after the apex is more coachable. A cue such as check how much road is left when throttle reaches full is even more actionable. The smaller cue helps the driver gather quality input, and quality input is what improves output.
Use a three-pass scan
A practical way to spend coaching attention is to use a three-pass scan: pre-run hypothesis, live observation, post-run cue selection.
Before the run, decide what you are looking for. This is not a rigid prediction. It is an attention filter. Maybe the driver's last debrief and data suggest an entry-speed problem. Maybe the driver reports that the car will not rotate. Maybe a previous session showed late full throttle after a fast corner. Enter the session with a candidate cue so your attention has a job.
During the run, watch for evidence rather than entertainment. You are cycling between frames: line and visual placement, control inputs, traffic, car behavior, and driver state. The skill is not to stare at one frame forever. The skill is to know when to stay and when to switch. If the line cue keeps explaining the result, stay there. If a mechanical signal or traffic decision starts controlling the lap, shift. If the driver is clearly overloaded, the cue may need to become simpler, not more technical.
After the run, choose one cue for the next attempt. The cue should answer the practical question: what should the driver attend to next time to produce a better outcome? You can store other observations for later. You can write them down. You can tell the driver there are other things you will come back to. But the actual coaching instruction should preserve attention for the thing with the highest leverage.
This three-pass scan also protects you from hindsight clutter. After a session, everything looks connected. A coach can sound smart by explaining all of it. But the driver needs a usable next action. Ross Bentley repeatedly points toward usable instruction: language the driver can understand and apply, reminders that can be brought to the track, and practice that changes behavior. If the debrief cannot become action, it is not yet coaching.
Rank cues by leverage
When several observations compete, rank them in this order.
Safety and control come first. If the driver is missing flags, losing awareness of nearby cars, repeatedly creating unstable car behavior, or showing signs of fatigue that affect focus, that cue overrides lap time. Attention that preserves safety is always relevant.
Cause comes before symptom. A symptom cue tells the driver what the result looked like. A cause cue tells them what to attend to so the result changes. Slow exit speed is a symptom until you know why it happened. Delayed full throttle is a symptom until you know whether the driver entered too fast, turned too late, apexed too early, lacked confidence, or had to respond to traffic. The cue that matters is the one closest to the driver-controllable cause.
Earlier usable information usually beats later correction, but do not turn this into a slogan. The sibling lesson on earlier cues teaches that skill directly. Here, the point is narrower: if a late corner problem was created by an earlier cue, coach the earlier cue. If the driver can only discover the issue at exit, then the exit sensation may be the right awareness cue for now. You are choosing the earliest useful cue, not the earliest possible word.
Basics beat magic. Consistent winners refine fundamentals and preparation instead of searching for quick tricks. In coaching, that means line awareness, speed placement, throttle commitment, brake release, visual information, and relaxed execution usually deserve attention before clever setup theories or exotic explanations. The more overwhelmed the driver is, the more valuable the basics become.
Driver availability matters. The perfect technical cue is weak if the driver cannot hold it in working memory at speed. A useful cue fits the driver's current state. Sometimes the right coaching move is to simplify from a technique command to an awareness question. Instead of telling the driver to force a tighter apex, you ask them to notice the car's actual distance from the apex. Awareness often lets the driver self-correct without adding effort.
Technique: convert observation into a one-lap cue
A strong coaching cue has a sequence behind it.
Name the observed result to yourself first. Do not immediately speak. For example: the driver is late to full throttle. Then ask what could be causing it. The trace might show too much entry speed. The in-car view might show late vision. The driver's hands might show tension. The exit track-out might show that the car was not pointed. Only after that do you choose the cue.
Phrase the cue as an attention target. The driver needs to know what to notice or do during the next lap. Notice whether the car reaches minimum speed before the apex. Check whether throttle can stay down after pickup. Feel whether the hands get lighter as the car unwinds. Look for how much road is left when the throttle is full. These are not motivational statements. They direct attention to evidence.
Keep the cue inside one corner or one linked problem. If the driver is learning a fast kink, do not attach every braking zone in the lap to the same debrief. If the problem is exit speed from one corner, coach that corner until the result changes or evidence disproves the hypothesis. The driver should return to the track knowing exactly where the experiment happens.
Set a success criterion. A cue without a success criterion can turn into vague trying. The criterion can be felt, visual, or data-backed. The driver can report that the car was closer to the apex without extra steering. The driver can keep throttle down after pickup instead of breathing it. The data can show minimum speed earlier and full throttle not delayed. The instructor can hear less correction needed in the same place. The point is not perfect measurement. The point is knowing whether attention was well spent.
After the next run, compare evidence to the criterion. If the cue worked, decide whether to repeat, deepen, or move. If it did not work, do not assume the driver ignored you. Re-check whether the cue was the right one, whether it was too broad, whether the driver could perceive it, and whether another frame has become more relevant.
Sub-skills inside cue selection
The first sub-skill is filtering. Filtering is the discipline of separating useful information from distracting information. The driver may mention lap time, a missed shift, a scary moment in traffic, a car ahead, tire feel, and frustration all at once. You do not discard those details, but you filter for the cue that changes performance or safety now.
The second sub-skill is frame shifting. A coach must move attention between line, car, traffic, mechanical performance, and driver state without becoming scattered. Frame shifting is not random scanning. It is purposeful switching. If a visual cue explains the lap, stay with vision. If traffic changes the problem, switch to racecraft. If the driver is getting tired and missing information, switch to refocus strategy. If the car shows a possible issue, stop treating it as a driver technique problem.
The third sub-skill is causal questioning. Data-for-drivers material keeps returning to the need to ask why. That is the coach's filter. Why was full throttle delayed? Why did minimum speed happen late? Why did the driver lift after early throttle? Why did the same corner look different on two laps? Asking why keeps you from coaching the visible symptom as if it were the root.
The fourth sub-skill is cue compression. You may understand a complicated chain, but you have to compress it into something the driver can use. The explanation can be longer in the paddock. The on-track cue must be short and specific. A simple sketch can help when words are too much; a picture can carry the line, apex, and exit relationship faster than a long lecture.
The fifth sub-skill is awareness building. Some drivers do not need a command. They need a sharper sense of what is already happening. When a driver is told to be aware of the car's placement relative to the apex, they may unconsciously correct toward their ideal line. That is different from ordering them to turn more. You are improving sensory input so the driver can produce better output.
The sixth sub-skill is attention recovery. Over a long session or race, attention wanders. Fatigue, pressure, and internal noise pull attention away from task-relevant cues. A coach has to notice when the driver no longer needs another technique instruction but instead needs a reset cue: breathe, simplify, return to the next brake marker, or focus on the next usable reference. This connects directly to cognitive bandwidth, but the cue-selection skill is deciding when refocus is the decisive cue.
Calibration: how you know your cue was right
A good cue changes behavior without creating three new problems. On track, the driver may sound calmer. Inputs may look less forced. The car may arrive at the exit with more road available. The driver may stop needing repeated reminders in the same corner. The next debrief may become more precise because the driver can describe what they saw or felt.
Data can confirm the same thing. In the coaching example with the Blue trace, the relevant signatures include late minimum speed, slow exit speed, throttle hesitation, a throttle breath in the Kink, early throttle followed by a lift, and delayed full throttle after carrying too much entry speed. If your cue was entry-speed discipline for exit commitment, the trace should move in that direction: minimum speed no longer pushed late, pickup no longer followed by a lift, and full throttle no longer delayed by the earlier mistake.
A good cue also reduces the need for effort. The driver should not need to wrestle the car into compliance. The performance literature in the corpus points repeatedly toward relaxed, disciplined, prepared execution and toward practicing the right skills. When the driver fixes the cue with less strain, you are probably working near the cause. When they fix the apparent symptom with more strain, you may be treating the wrong layer.
The debrief quality improves too. Early in the process, the driver may say the corner felt bad. After a useful awareness cue, the driver may say they were a car-width wide at the apex, or they picked up throttle before the car was pointed, or they saw the exit late. That is progress. Better sensory input gives the next coaching decision better material.
Failure modes
The first failure mode is cue stacking. You give the driver several correct instructions at once, and none of them becomes a practiced skill. Cue stacking often comes from fear that you will forget something or from wanting the driver to see how much you noticed. Write the extra observations down. Coach one.
The second failure mode is symptom chasing. You see slow exit and tell the driver to accelerate sooner. Then the driver picks up throttle early, runs out of road, and lifts. The original symptom remains because the cause was earlier in the corner. Symptom chasing is common because the symptom is visible. The cure is to ask why before speaking.
The third failure mode is data flooding. You bring speed, throttle, brake, time loss, and GPS into the debrief, then make the driver responsible for all of it. Data should focus attention, not multiply commands. If the data points to one cause, present the one cause and the one cue.
The fourth failure mode is effort escalation. You tell the driver to attack, commit, push, or be more aggressive when the actual need is cleaner input and better awareness. More effort applied to the wrong action makes the session worse. Use less-force language when the issue is awareness, relaxation, or precision.
The fifth failure mode is staying in the wrong frame. You keep coaching line while the driver is actually managing traffic. You keep coaching throttle while the car may have a mechanical issue. You keep coaching technique while fatigue is degrading attention. Frame shifting is the antidote.
The sixth failure mode is cleverness before basics. A coach can become tempted by advanced explanations before the driver has stable fundamentals. The corpus points away from magic solutions and toward refining basics, preparation, and disciplined practice. If the driver is not yet aware of apex distance, throttle commitment, or entry-speed effect, start there.
How this lesson fits the module
This lesson is the attention-budget lesson. Use Train drivers to look for earlier cues when the decisive cue is specifically about visual timing and earlier information. Use Build patterns the driver can use next lap when the driver needs a repeatable recognition pattern across corners or sessions. Use Separate decision errors from execution errors after you have isolated the cue but need to know whether the driver chose the wrong action or failed to execute the right one. Use Protect cognitive bandwidth under pressure when stress, fatigue, or competition load becomes the central constraint.
Here, your job is narrower and more fundamental: choose where coaching attention goes. If you choose well, every other coaching tool gets cleaner. If you choose poorly, even correct information becomes clutter.
Worked example: the Kink throttle breath
In the bonded data example, the Blue driver breathes the throttle in the Kink. That is the visible event, but it is not automatically the coaching cue. A weak debrief would tell the driver to be braver or to keep the throttle down. That might sound decisive, but it skips the attention problem: why did the driver breathe the throttle there?
Start by spending your own attention on the evidence around the lift. Did the driver arrive with too much speed from the previous segment? Was the car placed poorly before the Kink? Did the driver see the exit late? Did the throttle trace show hesitation before the breath, or was it a single correction? The corpus example reminds you that identifying why is not easy. That is exactly why you should not spend the driver's attention on the first visible symptom.
The useful next-lap cue should be the smallest cue that tests the cause. If the evidence suggests confidence and visual timing, the cue might be to notice the exit earlier and report whether the car had room when throttle stayed down. If the evidence suggests entry placement, the cue might be to set the car a half-step earlier before turn-in and check whether the throttle breath disappears. If the evidence suggests the driver is overloaded, the cue might be to make the Kink the only assignment for the next session. The success criterion is simple: no throttle breath in the Kink without adding a new exit problem.
This example is also a reminder that fast corners punish vague courage coaching. The driver does not need a speech. The driver needs the cue that gives them task-relevant information soon enough to act safely.
Worked example: late minimum speed and slow exit
The same data packet describes a Blue driver whose minimum speed happens later and whose exit speed is slow. It also notes that the driver gets to throttle too early, then has to lift at exit, and that too much entry speed hurts exit speed and delays full throttle. This is a classic attention-selection trap.
If you coach only the slow exit, you may tell the driver to get to throttle sooner. But the trace already shows early throttle followed by a lift. The driver is not missing the throttle pedal. The driver is arriving in a way that makes full commitment unavailable. Spending attention on earlier throttle would likely amplify the mistake.
The decisive cue is closer to the cause: enter at a speed and shape that lets the car accept throttle without a later lift. For the next lap, you might ask the driver to notice where minimum speed happens relative to the apex, then judge whether throttle pickup can stay down. You are not asking for a perfect corner. You are asking for a proof: can a slightly more disciplined entry create an earlier usable exit?
The data signature should change in a specific way. Minimum speed should stop drifting later. Throttle pickup should not be followed by a corrective lift. Full throttle should arrive sooner because the car is ready, not because the driver forced it. Lap time may improve, but the first evidence is cleaner shape and cleaner commitment. That is attention well spent.
Drill: one-cue evidence loop
Use this drill at the next HPDE, coaching session, test day, or simulator review. Run it for three sessions or three short run groups. The count matters because one repetition can be a coincidence and ten cues becomes clutter.
Before the first session, choose one corner or one linked corner problem. Write one hypothesis in plain language. For example: the driver is late to full throttle because entry speed is too high. Choose one observable cue for the driver. For example: notice whether minimum speed happens before or after the apex, then check whether throttle pickup can stay down.
During the session, protect the assignment. Do not add a second driving cue unless safety demands it. If you are in the car, watch and listen for the chosen evidence. If you are using video or data afterward, review only the channels that answer the hypothesis: speed, throttle, brake, line, or time loss. Ask why once before you change the assignment.
After the session, classify the result as confirmed, disproved, or unclear. Confirmed means the cue changed the behavior and the result improved without creating a new problem. Disproved means the cue was executed but the problem remained, so another cause is likely. Unclear means the cue was too broad, the driver could not perceive it, or the evidence was insufficient.
Repeat for two more sessions. Success is not measured by whether your first hypothesis was right. Success is measured by whether each session has one clear cue, one evidence standard, and one decision about the next coaching step. By the third session, the driver should be able to tell you what they were attending to and what changed.
Common mistakes
Symptom chasing: You coach the thing that looked bad instead of the thing that caused it. Slow exit, late full throttle, and a missed apex are often symptoms. Good coaching asks why first and chooses the cue that can change the chain.
Cue stacking: You give the driver several assignments because all of them are technically correct. The driver returns to the track with no single attention target. Good coaching stores the extra observations and protects one next-lap cue.
Data flooding: You show every trace because the software can display it. The driver leaves with more information but less clarity. Good coaching uses data as a filter. If speed, throttle, brake, and time loss point to one cause, the debrief becomes simpler, not larger.
Effort escalation: You ask for more attack when the driver needs better awareness or less tension. The result is often a harder version of the same mistake. Good coaching directs attention to a usable sensation or reference and lets the driver produce the correction with less force.
Wrong-frame loyalty: You keep watching the line because that was your plan, even after traffic, fatigue, or car behavior becomes the controlling issue. Good coaching frame-shifts when the relevant cue changes.
Cleverness before basics: You reach for sophisticated explanations before the driver can consistently report apex distance, throttle commitment, or entry-speed effect. Good coaching refines the basics until the driver's sensory input is good enough to support more advanced work.
When to switch cues
Switch cues when the evidence says your current cue is no longer the highest-value use of attention. That can happen for four reasons.
First, safety or control takes over. If the driver is missing information that keeps the session safe, that becomes the cue. Second, the cue is confirmed. Once the driver can execute it repeatedly and describe the relevant sensation, you can either deepen it or move to the next constraint. Third, the cue is disproved. If the driver does what you asked and the problem remains, do not simply repeat the same instruction louder. Ask why again and choose a better cause. Fourth, the driver's attention state changes. Fatigue, pressure, frustration, or overload can make a previously useful technical cue too expensive. In that case, the decisive cue may be a reset or simplification.
The important discipline is that cue switching is evidence-based. You are not wandering from topic to topic. You are reallocating limited attention to the cue that now matters most.
Debrief script: from evidence to cue
Use this script when you feel yourself preparing a long debrief.
Start with the result: what changed or failed to change? Then name the likely cause: what made that result happen? Then choose the attention target: what should the driver notice or do next lap? Then define the proof: what will show that the cue worked?
For example, the result is delayed full throttle and slow exit. The likely cause is too much entry speed making the car unavailable for committed throttle. The attention target is minimum-speed placement and whether throttle pickup can stay down. The proof is no pickup-and-lift sequence and a cleaner exit. That is enough for the driver to practice.
This script keeps you from turning a debrief into a lecture. It also keeps you honest. If you cannot name the proof, you may not have chosen a cue yet. You may only have chosen a complaint.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | the science of motorsport | 634258d2-d412-1ada-0ae7-f26dcee675c7 | 130 | 1 | uio_books_raw_v1 |
| 2 | Data-for-Drivers-PRINT | 9a14c339-f67f-0c81-5e92-d958f46f8150 | 13 | 1 | uio_books_raw_v1 |
| 3 | Inner Speed Secrets - Ross Bentley | eda21d60-302f-5a68-9152-a2833b724684 | 128 | 1 | uio_books_raw_v1 |
| 4 | Inner Speed Secrets - Ross Bentley | 42cd9797-25c1-9bbb-d1f4-7aa50b893094 | 189 | 1 | uio_books_raw_v1 |
| 5 | Inner Speed Secrets - Ross Bentley | 1f89d950-4532-a2f9-3f06-33a6a39f92d6 | 24 | 1 | uio_books_raw_v1 |
| 6 | Inner Speed Secrets - Ross Bentley | 12b38229-583d-d709-b629-b88b24921c14 | 164 | 1 | uio_books_raw_v1 |
| 7 | Inner Speed Secrets - Ross Bentley | f74de7b7-deb7-8b53-8851-548f3670c623 | 178 | 1 | uio_books_raw_v1 |
| 8 | Data-for-Drivers-PRINT | cb13d8c3-cc6b-28e9-246f-c3c64ae01efc | 1 | 1 | uio_books_raw_v1 |
| 9 | Ultimate Speed Secrets - Ross Bentley | 4400491c-451f-86fc-590c-1fa83983aef9 | 12 | 1 | uio_books_raw_v1 |
| 10 | Ultimate Speed Secrets - Ross Bentley | 7816dd86-ce80-1320-b6ed-b34e005cc98f | 16 | 1 | uio_books_raw_v1 |
| 11 | Performance-Driving-Illustrated-Ross-Bentley | 5cff603b-5e0f-da4a-41ef-f711fa235e6b | 4 | 1 | uio_books_raw_v1 |
| 12 | Performance-Driving-Illustrated-Ross-Bentley | d03d8129-9884-8385-fe77-b2af5835c3e6 | 1 | 1 | uio_books_raw_v1 |