Read the driver before prescribing the fix

Generated from content/lms/coaching-science/02-diagnose-performance-before-prescribing/01-read-the-driver-not-just-the-mistake.md; edit the source file, not this page.

Source path: content/lms/coaching-science/02-diagnose-performance-before-prescribing/01-read-the-driver-not-just-the-mistake.md

Course: Coach drivers with evidence, not instinct

Module: Diagnose performance before you prescribe

Estimated duration: 60 minutes

Principle: a mistake is evidence, not the diagnosis

When you coach an intermediate driver, the visible error is rarely the whole problem. An early throttle lift, a missed brake release, a line that pinches the exit, or a vague complaint about the car can all look simple from the pit wall. The trap is to prescribe the visible correction too quickly. If you do that, you may fix the shape of one corner while leaving the driver unchanged. The same driver will then produce the same kind of error somewhere else, under a different name.

The skill in this lesson is to read the driver before you prescribe the fix. That means you treat the mistake as the first clue in a diagnostic chain. You ask what the driver intended, what the driver noticed, what the driver trusted, what habit the driver fell back on, how prepared the driver was, and whether the evidence from data agrees with the driver's own feedback. Ross Bentley describes the driver engineer as needing to be good at reading the driver in the same way a car engineer reads data acquisition, driver feedback, and tire appearance. That is the model here. You are not only analyzing a corner. You are analyzing the human system that produced the corner.

This matters because the same on-track symptom can come from very different causes. A driver who lifts in a fast sweeper may be at the limit of confidence, may not know that the lift happened, may be using a poor reference point, may be chasing a lap-time target instead of executing a performance task, or may be reacting to a car setup that has not earned trust. If you prescribe the same fix to all of those drivers, you are guessing. One driver may need better sensory honesty. Another may need a track-map download and a sharper mental image. Another may need a confidence-building setup change even if that setup is not the fastest final configuration. Another may need to stop thinking about the result and return attention to controllable performance.

The core rule is simple: diagnose the driver state that made the mistake reasonable to the driver at that moment. Drivers usually do not choose the slower action because they prefer being slow. They choose it because, in that instant, it appears safer, clearer, more familiar, or more likely to produce the outcome they want. Your job is to discover that inner logic. Once you find it, the fix becomes smaller and more durable.

Why reading the driver works

Driving is not only a sequence of control inputs. It is perception, interpretation, trust, preparation, habit, and execution under pressure. Bentley's coaching perspective comes from many viewpoints: behind the wheel, trackside, passenger seat, video, data acquisition, television, engineering, vehicle dynamics, sports psychology, learning, and performance. That range matters because no single viewpoint owns the truth. A corner worker view may show the car's path. Data may show throttle, braking, speed, rpm, and g force. The driver may report what they felt and what they believed they did. The tires and car balance may reveal whether the car supported the request. Coaching starts when you combine those views instead of worshiping one of them.

Data is especially useful, but it is not the whole coach. A data system can show where the driver began braking, throttle position, g forces, speed, rpm, and engine functions. It can reveal something the driver did not notice, or confirm what the driver already suspected. Bentley gives the example of a driver believing a fast sweeper was flat while the computer showed a small throttle ease. That is a powerful coaching witness. But he also makes the boundary clear: no matter how sophisticated the system is, it cannot replace driver feedback. The most successful engineers know that the driver's feedback is more important. So your method is not data versus driver. It is data with driver.

Reading the driver also works because confidence can be a legitimate performance limiter. Bentley notes that a driver engineer may sometimes suggest a car change that ultimately makes the car slower, but builds the driver's confidence. Once the driver is confident, the car can be changed back to the faster setup. That is not lazy tuning. It is human-aware sequencing. The fastest theoretical setup is not useful if the driver cannot commit to it. A coach who reads only the mistake may keep demanding more commitment. A coach who reads the driver may first create the conditions in which commitment becomes possible.

Reading the driver also protects against confusing result hunger with performance focus. Bentley describes a driver who went to race weekends with a lap time and finishing result in mind, such as reaching a certain time range to finish third or better. The coaching work was to shift focus away from results and onto performance. That distinction is central in diagnosis. A driver can sound serious and committed while actually using attention badly. If the driver is thinking about the result, the body may start protecting against loss instead of executing the next performance action. You will see that as hesitation, overdriving, impatience, or inconsistent commitment, but the visible mistake is downstream of attention.

Finally, reading the driver works because habits are sticky. Bentley describes coaching road racers who became strong oval racers partly because their coach corrected bad road-racing habits, and because the drivers had little oval experience, they had fewer bad habits in that environment. That is a useful diagnostic lesson. Some mistakes are not misunderstandings of today's corner. They are yesterday's solutions being reused in a place where they no longer fit. When you read the driver, you ask not only what happened now, but what old habit may have taken over.

The diagnostic sequence

Use a four-pass sequence before prescribing. The passes are short, but the order matters. First, let the driver download the session. Second, compare the download to evidence. Third, classify the driver limiter. Fourth, prescribe the narrowest change that targets that limiter.

Pass one is the driver download. After a session, Bentley recommends making notes on a track map with details such as shift points, where braking begins, where braking ends, where the driver returns to full throttle, and the reference points the driver has absorbed. For coaching diagnosis, that download is not busywork. It is a scan of the driver's mental model. If the driver cannot tell you where the braking began, where the brake release finished, where full throttle returned, or what visual reference controlled the decision, then the error may not be a courage problem or a technique problem. It may be a map problem. The driver is operating without enough usable information.

Do not begin by correcting the line. Begin by asking the driver to reconstruct the lap. Where did you decide to brake? What did you use as the cue? Where did the brake release end? Where were you first confident enough to add throttle? What did you expect the car to do at that moment? What did it actually do? You are listening for precision. A driver with a usable mental map can give location, timing, and cause. A driver without one gives impressions. Impressions can be honest, but they are not yet actionable.

Pass two is evidence comparison. Now you compare the driver's download to what the car and tools show. If data is available, use it to check brake points, throttle traces, speed, rpm, and g force. If another driver in a similar car is available, comparison can show where speed is possible. If there is no data, you still compare the driver's report to trackside observation, video, or the coach's passenger-seat view. The goal is not to catch the driver being wrong. The goal is to find where perception and behavior diverge.

The fast-sweeper example is the cleanest version of this pass. The driver believes they were flat. Data shows a throttle ease. A weak prescription is to say, keep it flat. A stronger diagnosis is to ask why the driver did not notice the ease, what sensation triggered it, and whether the driver has a reliable cue for full throttle commitment. The mistake is not simply the lift. The mistake is the driver-feedback gap that allowed the lift to remain invisible.

Pass three is limiter classification. Once you have the driver's story and the evidence, decide what kind of driver limiter you are dealing with. In this lesson, use six buckets: mental map, sensory feedback, confidence, habit, focus, and preparation. These buckets are not labels for the driver's personality. They are temporary explanations for the next intervention.

A mental-map limiter appears when the driver cannot name enough reference points or cannot place actions clearly on the track. The driver may brake at a different place each lap, return to throttle based on hope, or describe the corner only as fast, scary, slippery, or weird. The fix is not more bravery. The fix is a better download, sharper landmarks, and mental imagery based on actual track experience.

A sensory-feedback limiter appears when the driver reports one thing and the car record shows another. Data may reveal a throttle lift, a brake overlap, or a speed loss that the driver did not feel. The driver may honestly believe they are doing the target action. The fix is to build awareness of the exact sensation and connect it to a measurable trace or visible outcome.

A confidence limiter appears when the driver understands the task but cannot yet trust the car or themselves enough to commit. This is where the coach or driver engineer may temporarily prioritize confidence, even through a car change that is not the fastest final setup. The point is not to make the driver comfortable forever. The point is to help the driver reach a state where the faster method becomes executable.

A habit limiter appears when the driver imports an old solution into a new situation. The oval example is useful because it shows how fast drivers can improve when bad habits are corrected early, and how clean habits in a new domain can accelerate learning. If the driver's error repeats across different corners with the same flavor, suspect habit. The fix is not a lecture about the one corner. The fix is a replacement pattern practiced deliberately.

A focus limiter appears when the driver is attached to lap time or finishing result instead of performance. Bentley's result-focused driver had expectations going into the weekend and a target time tied to a finishing outcome. The coaching change was to move attention toward performance, because the driver can control performance more directly than results. If your driver is talking more about the number than the action, diagnose focus before technique.

A preparation limiter appears when the driver wants improvement but has not committed time to prepare. Bentley describes a driver who used mental imagery once or twice a day and improved dramatically, and then points out that the preparation amounted to no more than about 30 minutes a day. The lesson for coaching is direct: if the driver is underprepared, the in-car fix may not hold. The prescription may need to include off-track imagery and track-map rehearsal, not just another instruction for the next session.

Pass four is the narrow prescription. Once you classify the limiter, choose the smallest intervention that fits. If the limiter is mental map, assign a track-map download and reference-point plan. If it is sensory feedback, pair the driver's feel with data or video and set one awareness target. If it is confidence, reduce the perceived risk enough to let the driver execute, then return toward the faster configuration. If it is habit, create a replacement cue and practice it in a lower-load section first. If it is focus, change the objective from result to controllable performance. If it is preparation, assign imagery repetitions built from the driver's real session download.

The phrase narrow prescription is important. Intermediate drivers already have enough to think about. A broad fix such as be smoother, brake later, trust the car, or use more track often sounds useful but does not tell the driver what to do next. The prescription should name the behavior, the location, and the success evidence. For example: in the next session, at the sweeper, hold the throttle trace steady from turn-in to exit and report the exact sensation that makes you want to ease. Or: after the session, mark the first full-throttle point and compare it to the previous session. Or: before the next run, do five mental laps where the only objective is the brake release and throttle return sequence.

How to listen during the download

The driver's first words after a session are diagnostic. Do not rush past them. You are listening for what the driver values, what the driver noticed, and what the driver cannot yet see.

A driver who speaks only in outcomes may say the lap time is still not where it should be, that another driver is quicker, or that the car should have been better. This may be a focus problem. Bring the conversation back to controllable performance. What action did you execute better? Where did you lose the planned action? What one performance behavior will define the next session?

A driver who speaks only in feelings may say the car was loose, pushy, nervous, good, bad, or not confidence inspiring, without locations or inputs. This may be a feedback precision problem. Do not dismiss the feeling. Bentley's boundary around data and feedback means the driver's feedback matters deeply. But the feedback must be made usable. Ask where, when, on which input, and compared to what. A feeling becomes coachable when it has a place and a trigger.

A driver who speaks only in mechanics may immediately ask for setup changes. This may be correct, but it may also be a confidence or execution issue wearing a setup costume. Bentley's confidence-first setup example allows for car changes that help the driver, but it also implies the coach must know why the change is being made. If you soften the car, change balance, or alter something to help confidence, say so plainly in your own diagnosis. You are not declaring the faster setup wrong. You are staging the driver's learning.

A driver who has no details may simply lack a download habit. This is where the track map matters. The act of writing shift points, brake start, brake end, full throttle, and reference points forces the driver to encode the lap. If the driver cannot yet provide details, do not prescribe a complex technique. Assign observation. The next session's job may be to return with three exact references and one place where full throttle began.

A driver who contradicts the evidence may have a sensory blind spot. The data system may show a throttle ease, a different brake point, or a speed change the driver did not notice. Treat that as a learning opportunity, not a character issue. The coach's language should keep the driver curious. The question is what sensation caused the unplanned action and how to make that sensation visible next time.

Reading confidence without patronizing the driver

Confidence is one of the easiest driver states to misread. If you treat every confidence issue as fear, you will insult serious drivers and miss the mechanism. Confidence in this context means the driver's current trust is not sufficient for the requested commitment. That trust can be limited by car balance, inconsistent references, poor mental imagery, previous mistakes, unfamiliar track sections, or a lack of sensory proof that the car will accept the input.

The important coaching move is to separate confidence from identity. You are not telling the driver they are timid. You are identifying a performance condition. Bentley's example of making the car slower to build confidence is useful because it frames confidence as something you can engineer, not something you shame. The driver may need a setup, instruction, or session goal that lets them execute the movement with less threat. Once execution is stable, you can restore the faster demand.

This is especially important with intermediate drivers. They often know enough vocabulary to describe a problem, and enough speed to make the consequences real, but not enough repetitions to separate true car limits from nervous interpretation. If they are asked to leap straight to a high-commitment solution, they may comply for one lap and then regress. If you read confidence first, you can build a bridge: make the action smaller, prove the response, repeat it, then remove the support.

The confidence read also keeps you from wasting setup changes. If the driver cannot describe the corner, input, and sensation, do not let the setup change become a substitute for diagnosis. If the driver can describe those details and the car consistently blocks commitment, a confidence-building change may be the right coaching tool. The distinction is whether the change serves a diagnosed driver need or merely avoids a hard conversation.

Reading focus: performance before result

The result-focused driver in Bentley's example had a lap time in mind and tied that time to a finishing expectation. That sounds normal in racing, but it can be harmful in coaching if it dominates attention. The driver cannot directly control the field, conditions, or final placing. The driver can control preparation, attention, reference points, inputs, and the quality of each performance task.

When you diagnose a focus limiter, listen for future-result language before the session and disappointment language after the session. The driver may talk about needing a number, being behind another driver, or failing to get the expected result. The fix is not to pretend results do not matter. The fix is to convert the result goal into a controllable performance task.

For example, do not let the next-session plan be simply to find half a second. Convert it into a measurable action: brake at the chosen reference, release at the planned point, return to full throttle at the planned exit cue, and report whether the car accepted it. That is compatible with data review, but it is not the same as data worship. The data tells whether the action happened. The driver feedback tells why it did or did not happen.

Mental imagery is one bridge from result focus to performance focus. Bentley describes taking known track information and actual experience, then replaying it in the mind, with more repetitions making it more effective. For a result-focused driver, imagery should not be fantasy laps. It should be performance rehearsal. The driver rehearses where to brake, where to end braking, where to look, where to return to throttle, and what sensation to expect. That gives attention a job other than worrying about the result.

Reading preparation: the off-track limiter

Some drivers expect the next session to teach everything. Bentley's preparation example argues against that. The driver who craved learning used strategies including mental imagery once or twice a day and improved dramatically, with preparation taking no more than about 30 minutes a day. The coaching implication is that a driver who does not prepare should not be surprised when improvement is slower than drivers who do.

As a coach, you do not use this as a moral lecture. You use it diagnostically. If a driver cannot retain reference points, repeats the same uncertainty, or arrives at each session as if the previous session vanished, the limiter may be preparation. The next prescription may happen outside the car: write the download, build the mental lap, rehearse the sequence, then drive it.

The preparation read is especially useful between events. A driver may be limited in track time, budget, or weather. Mental imagery and track-map work allow useful repetitions without more laps. The driver takes the details from actual experience and rehearses them. When the next event begins, the driver is not starting from a blank page.

Reading habits: old solutions in new places

Habits are efficient. That is why they are powerful and why they are dangerous. A driver with road-course experience may bring assumptions to an oval. A driver with one car's balance may bring assumptions to another car. A driver who learned to protect entries may keep protecting entries after the car and skill level allow more commitment. Bentley's oval coaching story shows how valuable it is to correct bad habits early and how quickly drivers can learn when they do not have old habits in the way.

To read a habit, look for repeat shape across different problems. The exact corner may change, but the driver's solution looks familiar. They always add a small protection lift. They always ask for setup before describing inputs. They always chase the lap time after two corners go wrong. They always overvalue the perfect line and undervalue driving the car to its limit. Bentley's track-learning sequence includes the point that, eventually, the driver must stop thinking only about the track and drive the car to its limit, because a car at the limit even off line may be faster than a perfect line below the limit. If the driver keeps treating line obedience as the whole job, that may be a habit of under-driving the car.

The fix for a habit is not more information. It is a replacement routine. Pick one place where the driver can practice the new behavior with low complexity. Name the cue, the input, and the review evidence. The habit changes when the new routine becomes easier to access than the old one.

Using data without letting it erase the person

The sibling lesson Use data as a coaching witness goes deeper into data practice. Here, keep the boundary simple. Data is a witness, not the driver. Use it to reveal hidden behavior, confirm suspicions, and compare drivers or laps. Do not use it to override the driver's experience without interpretation.

If data shows the driver lifted, ask what the driver felt. If data shows earlier braking than planned, ask what reference point triggered the pedal. If data shows slow throttle return, ask whether the driver was waiting for direction, waiting for grip, or waiting for confidence. If data confirms the driver's complaint, use that confirmation to build trust in the driver's feedback. In all cases, the data opens the question. It does not finish the diagnosis by itself.

This approach also makes data less threatening. Drivers can become defensive when a computer disproves their memory. But if you treat the mismatch as information about perception, the driver learns faster. The message is not that the driver lied. The message is that the driver's internal record missed something, and now you have a way to train that record.

What good diagnosis sounds like

Good diagnosis is specific, temporary, and testable. It does not declare the driver broken. It states the current limiter and the next experiment.

Instead of saying the driver is bad at fast corners, say the driver is not yet detecting the small throttle ease in the sweeper, so the next session will train throttle honesty and sensation matching. Instead of saying the driver needs to be braver, say the driver understands the exit task but does not yet trust the car enough to commit, so the next run will use a confidence-building support and then review whether commitment stabilizes. Instead of saying the driver needs to stop obsessing over lap time, say the next session will define success by a performance behavior rather than the final number.

Good diagnosis also preserves humility. Bentley's own writing emphasizes learning from many perspectives and making information usable. A coach who reads the driver stays in that spirit. You do not need to prove that your first guess was right. You need to find the lever that lets the driver improve.

The end state

A driver has been read well when the prescription fits the person, not just the corner. The driver leaves with one clear action, one reason for that action, and one way to know whether it worked. The next session produces better evidence, not just more opinion. The driver becomes more accurate in self-reporting. The data and feedback start to converge. Confidence becomes something you can build and then cash in for speed. Habits become visible enough to replace. Result pressure turns into performance attention. Preparation becomes part of the driving process rather than an optional extra.

That is the difference between correcting a mistake and developing a driver. Correcting the mistake may improve one lap. Reading the driver changes the system that creates the next lap.

Worked example: the fast sweeper that was not actually flat

The situation comes straight from the data-acquisition discussion. The driver believes the sweeper was taken flat. The data trace shows a slight throttle ease. A shallow coaching response is to tell the driver to keep the throttle down. That may be technically correct, but it skips the useful diagnosis.

Read the driver first. Ask what the driver felt at the exact moment the throttle eased. Did the car feel light, did the track edge arrive faster than expected, did the driver stop looking far enough ahead, or did the driver not know the lift happened at all? If the driver did not know, the limiter is sensory feedback. If the driver knew but did it anyway, the limiter may be confidence. If the driver lifted at a visual mark that moved lap to lap, the limiter may be mental map.

The prescription changes with the diagnosis. For a sensory-feedback limiter, the next session's task is to notice the first urge to ease and name the sensation after the lap. You compare that report to the throttle trace. Success is not only a flatter trace. Success is the driver's ability to predict the trace from feel. For a confidence limiter, you may reduce the demand, build repeated proof that the car accepts the load, and then return to the faster commitment. For a mental-map limiter, you assign a clearer reference and a post-session download of where the throttle first stayed fully open.

The important move is that the data does not embarrass the driver. It reveals the coaching target. The lift is the symptom. The coachable driver limiter is the gap between what happened and what the driver could perceive, trust, or explain.

Worked example: the road racer learning an oval

Bentley's oval example is useful because it shows why reading history matters. He describes road racers he coached who became very strong oval racers because the coach corrected bad road-racing habits and because the drivers had little oval experience, so they did not arrive with as many bad habits in that environment.

Imagine an intermediate road-course driver entering a new oval session. The visible mistake might be an awkward line, a misplaced lift, or an input pattern that belongs to a road course. If you read only the mistake, you correct the corner shape. If you read the driver, you ask what old road-racing solution the driver is importing. The driver may be trying to solve the oval with a habit that was useful somewhere else.

The prescription is then built around clean basics and habit prevention. You do not overload the driver with advanced nuance. You establish the basic reference, the stable input rhythm, and the correct attention pattern before the old habit grows roots. That is why this example matters for coaches: sometimes the best diagnosis is not that the driver lacks talent or effort. It is that the driver has an existing skill pattern that is being used in the wrong place.

The success sign is not only a better oval lap. It is the driver's ability to identify when an old road-course habit tries to take over. Once the driver can notice the imported habit, you can replace it. Until then, the coach is only chasing symptoms.

Worked example: the driver chasing the mid-28s

Bentley describes a driver who arrived at a race weekend with a lap time and finishing expectation in mind. The driver believed that reaching a certain time range would put the result in reach. The coaching work was to move attention away from the result and toward performance.

This is a classic read-the-driver case because the visible mistakes may look technical. The driver may brake too late in one corner, rush throttle in another, or abandon a plan after seeing an unsatisfying lap. If you prescribe each mistake separately, the driver receives a pile of corrections. The deeper diagnosis is that attention is attached to the result. The driver is not fully executing the current task because part of the mind is already judging the scoreboard.

The fix is to translate the result into a performance plan. The driver can still care about speed. But the next session is defined by controllable actions: the braking reference, the release point, the full-throttle return, and the post-session download. Mental imagery supports the shift. The driver rehearses the performance sequence from actual track knowledge rather than rehearsing anxiety about the number.

The success sign is a change in language. Before the session, the driver talks about the action they will execute. After the session, the driver reports whether the action happened and what the car did. Lap time may improve, but the diagnostic win is that attention is now working on something the driver can control.

Drill: the driver-read loop

Use this drill at the next event with one driver, one recurring corner or section, and one review cycle after each session. Do it for three sessions if the schedule allows. If you only have two sessions, run the first two steps and assign the imagery step before the next event.

Session one is the uncorrected download. Before giving advice, ask the driver to mark a track map for the chosen section. They must identify where they began braking if braking applies, where braking ended if braking applies, where they first returned to full throttle, what reference point controlled the decision, and what they expected the car to do. Keep the count small: one section, five details, five minutes. The success criterion is not perfection. It is whether the driver can give location-based detail instead of general impressions.

Review one is evidence comparison. Use data if available, especially throttle, speed, braking, rpm, and g force. If data is not available, use video, passenger-seat memory, or trackside observation. Find one agreement and one mismatch between the driver's report and the evidence. The success criterion is a single classified limiter: mental map, sensory feedback, confidence, habit, focus, or preparation. Do not leave the review with a vague instruction.

Session two is the narrow prescription. Give the driver one action tied to the diagnosed limiter. For mental map, the action is to drive from the chosen reference and report whether it stayed stable. For sensory feedback, the action is to notice the sensation that precedes the unwanted input. For confidence, the action is to repeat a slightly reduced commitment until the car response becomes predictable. For habit, the action is to replace the old cue with a new one in that section. For focus, the action is to ignore lap time until after the review and judge only the performance behavior. For preparation, the action may be to run mental laps before getting in the car.

Review two is convergence. Ask whether the driver's report moved closer to the evidence. If the driver now predicts the data more accurately, names the reference point more clearly, or explains the confidence limit more precisely, the drill is working even before lap time changes. Assign five mental imagery repetitions before the next session, using only the known details from the track map and the actual experience.

Session three is confirmation. Repeat the same section with the same success criterion. The goal is not to add three new fixes. The goal is to confirm that the driver can read themselves more accurately and execute the targeted action with less coaching. The drill is complete when the driver can state the plan before the run, execute or miss it, and then explain the evidence after the run in terms specific enough to choose the next prescription.

Common mistakes

Mistake one is treating the visible error as the whole truth. The driver lifts, so the coach says stay flat. The driver misses the exit, so the coach says use more track. The driver complains about balance, so the coach changes the car. Good coaching slows down long enough to ask why that action made sense to the driver in the moment.

Mistake two is using data as a verdict instead of a witness. Data can show that the driver eased throttle, braked earlier, or carried less speed. It can reveal or confirm. But Bentley's boundary is that data cannot replace driver feedback. Good coaching uses the trace to ask a better question and to train the driver's self-awareness.

Mistake three is dismissing confidence as weakness. Confidence is a performance condition. If the driver cannot commit because the car, reference, or sensation does not yet feel trustworthy, the coach may need to build confidence before demanding the faster final method. Good coaching can temporarily support confidence and then remove the support once the driver can execute.

Mistake four is letting result focus masquerade as seriousness. A driver who talks constantly about lap time may seem committed, but the attention may be pointed at something the driver cannot directly control. Good coaching converts the desired result into performance behaviors the driver can execute and review.

Mistake five is prescribing more information when the limiter is habit. A driver with a strong old pattern may already understand the explanation. The problem is that the old solution arrives first under load. Good coaching creates a replacement routine with a cue, an action, and review evidence.

Mistake six is allowing vague feedback to stand. A driver saying the car felt bad may be telling the truth, but the feedback is not yet usable. Good coaching asks where, when, on which input, and compared with what. The goal is not to turn the driver into an engineer. The goal is to make the driver's experience specific enough to act on.

Cross-references inside this module

This lesson sits before the sibling lessons. Turn fuzzy feedback into a testable hypothesis takes the usable driver read and turns it into an experiment. Use data as a coaching witness goes deeper on traces, comparisons, and evidence. Protect against your favorite fix guards against the coach's own pattern, which is especially important when a familiar mistake tempts you to prescribe before diagnosing.

The boundary is this: in this lesson, the central object is the driver state behind the mistake. You still use data, track maps, and session notes, but only to answer the coaching question. What did this driver need to perceive, trust, prepare, or focus on in order for the better input to become possible?

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Inner Speed Secrets - Ross Bentley	7a3d7866-53dd-4a5b-75a7-0463122fea1c	140	1	uio_books_raw_v1
2	Ultimate Speed Secrets - Ross Bentley	3d142f9f-7c75-7fdb-3c25-0edaa29d9600	554	1	uio_books_raw_v1
3	Ultimate Speed Secrets - Ross Bentley	7212e525-6587-a46d-1fab-5d027a6e940e	553	1	uio_books_raw_v1
4	Ultimate Speed Secrets - Ross Bentley	a9a648d9-5c51-dce8-aed0-7835e25db48e	211	1	uio_books_raw_v1
5	Ultimate Speed Secrets - Ross Bentley	533b69a9-6626-d899-c20e-acbaddcf44af	601	1	uio_books_raw_v1
6	Ultimate Speed Secrets - Ross Bentley	7816dd86-ce80-1320-b6ed-b34e005cc98f	16	1	uio_books_raw_v1
7	Ultimate Speed Secrets - Ross Bentley	4400491c-451f-86fc-590c-1fa83983aef9	12	1	uio_books_raw_v1