Time feedback around the rep

Generated from content/lms/coaching-science/03-build-deliberate-practice-loops/03-time-feedback-around-the-rep.md; edit the source file, not this page.

Source path: content/lms/coaching-science/03-build-deliberate-practice-loops/03-time-feedback-around-the-rep.md

Course: Coach drivers with evidence, not instinct

Module: Build deliberate practice loops

Estimated duration: 55 minutes

Principle: feedback belongs around the rep

Time is not the lesson. Time is the witness you bring in after the driver has made a rep, felt the car, and stated what they think happened. The core skill is to bracket each practice rep with the right feedback at the right moment: a clear pre-rep question, an immediate driver self-report, then timed or logged evidence, then one decision for the next rep. If you let the lap time arrive first, especially as a comparison to other drivers, the driver starts protecting an ego or chasing a scoreboard instead of noticing the car. Bentley makes the same sequence plain in his coaching material: awareness and feedback accuracy suffer when comparison arrives before the driver has gone through the awareness process. For an intermediate driver, this is the difference between using timing as a teacher and using timing as a distraction.

This lesson is not about choosing the one change. That belongs to the sibling lesson on defining one change for one run. It is not about every data tool you could use. That belongs to the sibling lesson on using review tools without drowning the driver. Your job here is narrower and more powerful: decide when the driver gets each kind of feedback around the rep. The timing of feedback shapes what the driver learns from the run.

The mechanism is simple. Driving improves through hands-on experience, but the experience becomes more useful when the driver can picture the theory, perform the rep, then connect the felt result to evidence. Reading and theory can prepare sensitivity, but the learning still has to be put into practice. A feedback loop therefore has to protect the practice moment. Before the rep, the driver needs a concrete intention. During the rep, the driver needs attention on the cue. Immediately after the rep, before seeing the number, the driver needs to write down or say what the car did and what they did. Only then should the coach or data system reveal elapsed time, split time, speed trace, braking deceleration, corner speed, or straight speed.

Think of timing feedback as four gates.

Gate one is the question gate. Before the run, name the segment and the evidence you will accept. If the rep is about a braking zone, the useful evidence might be braking deceleration derived from the speed change, plus the driver report on how the release felt. If the rep is about a corner, the useful evidence might be minimum corner speed, exit speed, and the driver report on whether steering input became calmer. If the rep is about a setup or aero change, the useful evidence might be corner speed, straight speed, sector time, and total elapsed time so you can see whether a gain in one place was paid back somewhere else. The bonded corpus supports this kind of timing because even a speed or rpm trace versus time can give corner and straight speeds, elapsed time, split times, and braking deceleration rates.

Gate two is the rep gate. During the lap or run, the driver does not need a lecture. The driver needs to execute the agreed cue. This preserves the distinction between practice and review. If you keep adding information during the rep, you change the task from driving to mental juggling. The driver should know what to notice: the first point the car asks for steering, the smoothness of the brake release, the point at which throttle can be committed, the way the car accepts a line, or the segment speed they are trying to carry. The rep is narrow on purpose.

Gate three is the self-report gate. As soon as the rep is over, ask for the driver account before numbers. This is not soft coaching. It is calibration. The driver is learning whether their awareness matches what the car and trace later show. Ask for sequence, not drama. What was the first thing you noticed. Where did the car change attitude. Did you ask for more steering or less. Did the exit feel delayed or free. Did the car feel better in the corner but slower afterward. The driver writes it down because the act of writing improves awareness and creates a record that can be checked later. This step also prevents the common habit of inventing a story after seeing the lap time.

Gate four is the evidence gate. Now you reveal the time and trace. Keep the reveal matched to the original question. A full data review can be valuable, but not after every small rep. If the rep was about the braking zone, reveal only the braking-zone evidence first. If the rep was about an aero or setup change, compare the segment speeds and total elapsed time. If the rep was about a habit, compare what the driver felt with what the coach observed. Then decide whether to repeat, keep, revert, or change the next question. The point is not to make every run faster immediately. The point is to make every run answer something.

What counts as feedback

Feedback is not only the stopwatch. The corpus gives you a practical hierarchy. First is driver awareness: what the driver felt and can describe before outside comparison. Second is the written note: a stable record of that awareness. Third is objective timing: elapsed time, sector or split time, corner speed, straight speed, and braking deceleration derived from speed change. Fourth is interpreted review: coach, engineer, or teammate discussion that turns the evidence into the next action. Fifth is long-term record keeping: permanent traces and notes that let you compare one run with another after the emotion of the session has cooled.

That order matters. Stopwatch-only feedback is too blunt. It tells you whether the lap was quicker, not why. A speed trace or rpm trace versus time is already more useful because it lets you inspect where the time appeared or disappeared. You may see that a driver improved the corner speed but gave away the straight. You may see that the braking deceleration improved but the exit suffered. You may see that the lap time went nowhere because two effects canceled each other. That is why the lesson title says around the rep, not after the session. Useful feedback is placed close enough to the rep that the driver still remembers the sensations, but late enough that the sensation is recorded before the number edits the memory.

The driver also needs protection from comparison too early. Comparing to other drivers has its place, but not before the driver has developed an accurate account of their own rep. If the first feedback is that someone else was quicker, the driver starts searching for a global answer. They may overdrive, copy a line without understanding it, or abandon a useful experiment because it did not beat someone on the first attempt. The self-report gate keeps the driver inside their own learning loop long enough to build accurate awareness.

How to run the loop as a coach

Start with the smallest segment that can answer the question. A full lap is usually too large for a first feedback loop. A braking zone, one corner, the straight after that corner, or one linked sector is better. The corpus supports segment thinking because split times and section-by-section speed can be extracted even from simple traces. This lets you avoid giving global feedback for a local problem.

Before the driver goes out, write the rep card in plain language. Segment: Turn-in through exit of the target corner. Driver cue: release brake so steering can be reduced. Driver prediction: exit should feel freer, but entry may feel less heroic. Evidence after the rep: minimum speed, exit speed, split to the next marker, and driver self-report before numbers. This is not bureaucracy. It is how you prevent the driver from coming in with ten impressions and no decision.

After the rep, take the driver report first. Do not ask whether it was faster. Ask what happened. If the driver says the car felt better, ask where. If the driver says it felt worse, ask at what event in the sequence it started. If the driver can only say it was good or bad, narrow the next rep. Intermediate drivers often have enough pace to create rich sensations but not enough discipline to sort them. Your feedback timing teaches that sorting.

Then reveal evidence in the same order as the original question. If minimum speed improved but exit speed fell, say so. If braking deceleration improved but elapsed time through the sector did not, ask what happened at release or rotation. If the driver felt slower but the trace says the segment was faster, that is an important calibration event. If the driver felt faster but the trace says the gain was only on entry and was lost on exit, that is also important. Either way, the timing number becomes a witness to a specific question, not a verdict on the driver.

Finally, choose one next action. Repeat the rep if the driver report and data disagree and you need another sample. Keep the change if the driver report and evidence point the same direction and the total segment or lap result improved. Revert if the change solved one local sensation but lost more time elsewhere. Try something else if the evidence shows the question was wrong or the car responded differently than expected. Motorsport development includes trial and error, and the corpus is clear that what works on one car may not work on another. A good feedback loop does not pretend every idea will work. It makes failure cheap and informative.

Sub-skill: protect awareness before score

The most important sub-skill is delaying the score until the driver has made an honest observation. This is especially important for intermediate drivers because they are fast enough to care about lap time, but still building the internal sensors that make lap time repeatable. Ask for the report before the display, before the coach verdict, before the comparison to a friend, and before the paddock story. The goal is not to hide time. The goal is to keep the driver from rewriting the rep after the number appears.

Good awareness reports are sensory and sequential. The car took a set earlier than before. I added steering after apex. I was late getting back to throttle. I felt more confidence but less speed on the straight. Poor awareness reports are judgment words with no location. It was fine. I blew it. The car was bad. I was fast. Your feedback timing should pull the driver from judgment into evidence.

Sub-skill: make timing local enough to matter

A lap time can be correct and still useless for coaching the rep. If the lesson was the brake release into one corner, a whole-lap time may be polluted by traffic, a missed shift, a different exit elsewhere, or a better start to the lap. Use splits when you can. Use speed at a marker when you can. Use braking deceleration when the question is braking. Use corner speed and straight speed when the question is aero or balance. The McBeath data chunk is useful here because it shows how much can be learned from speed or rpm versus time: corner speed, straight speed, elapsed run time, split time, and braking deceleration are all available from relatively simple evidence.

Local timing also protects the driver from overcorrecting. Suppose the driver improves the target corner but the lap is slower because they made an unrelated mistake later. If you feed back only lap time, you teach the wrong lesson. Suppose the lap is faster because of a tailwind or better traffic but the target segment got worse. If you feed back only lap time, you reinforce the wrong rep. The feedback window must match the practice window.

Sub-skill: separate possible from worthwhile

One of the useful ideas in the data-logging corpus is the distinction between what is possible and what is worthwhile. You can collect more information than a driver can absorb. You can display more channels than a coach can interpret between sessions. The skill is to choose the smallest evidence set that answers the rep question. For a driver habit, that may be driver report plus one speed trace. For a setup change, that may be split time, corner speed, straight speed, and total elapsed time. For a team debrief, it may be notes and traces saved for a longer review after the session.

If every run becomes a full data seminar, the driver stops practicing. If no run gets objective evidence, the driver keeps guessing. The middle path is a timed reveal: self-report first, then the evidence that answers the question, then one next decision.

Sub-skill: keep a permanent record without worshiping it

A permanent printed or stored record of runs has value because it lets you inspect patterns later. The record matters most when it is paired with the driver note from the same rep. Time alone is a thin record. A note alone is a memory. Together they let you see whether the driver is becoming more aware, whether a change repeats, and whether a result was local or global.

Do not turn the record into a museum. You are not collecting traces to feel professional. You are collecting enough evidence to decide what to repeat, what to abandon, and what to discuss. Discussion matters because motorsport learning is social as well as individual. Bentley points to the driver-engineer-team relationship as decisive because legendary teams communicated well. McBeath also reminds competitors that discussing ideas expands knowledge. That does not mean every opinion gets equal weight. It means the feedback loop should give the coach, driver, and data a shared object to talk about.

Calibration cues

You are improving at this skill when the driver can predict the evidence before seeing it more often than before. The driver comes in and says the segment probably improved but the straight might be down, and the speed trace confirms the shape. Or the driver says the entry felt fast but the exit felt pinned, and the split shows the loss after apex. The goal is not perfect prediction. The goal is a tightening relationship between sensation and evidence.

You are improving when the driver notes get shorter and more precise. Early notes are emotional and broad. Better notes name the event: brake release, first steering input, minimum speed, throttle commitment, exit straight, or confidence change. This is exactly the kind of awareness and performance-strategy work that the inner-speed material points toward: understand what causes performance, then build more consistent strategies.

You are improving when the timing discussion gets calmer. A driver who receives lap time too early often reacts as if the number is a verdict. A driver trained in rep feedback treats the number as information. Slower but cleaner can be useful if the goal was to learn the cue. Faster but unrepeatable can be a warning. Faster in one sector and slower overall can be a setup clue. The time becomes part of a deliberate practice loop, not the whole loop.

You are improving when the next action is obvious. After the evidence gate, you should be able to say repeat, keep, revert, or change question. If every debrief ends with a vague instruction to try harder or be smoother, your feedback arrived in the wrong shape or at the wrong time.

Failure modes and recoveries

The first failure mode is scoreboard-first feedback. The driver sees the lap time or comparison before speaking. The symptom is instant story-making. The driver explains the number instead of reporting the rep. The cost is distorted awareness. Recover by making a rule for the session: driver report first, number second. If the driver has a visible lap timer, cover it for that exercise or ask them not to look until the note is written.

The second failure mode is stopwatch-only coaching. The symptom is that every debrief starts with faster or slower but cannot explain where. The cost is wasted track time because the next rep is a guess. Recover by choosing one local measure that matches the cue: split time, speed at a marker, corner speed, straight speed, braking deceleration, or a coach observation.

The third failure mode is data flooding. The symptom is a driver sitting in the paddock while the coach scrolls traces, channels, overlays, and possibilities until the next session is almost here. The cost is attention. Recover by separating between-rep feedback from longer review. Between reps, reveal only what answers the question. Save the deep review for after the session or after the day.

The fourth failure mode is comparison poisoning. The symptom is a driver who asks how they compare before they can describe their own lap. The cost is copying, overdriving, or abandoning a useful learning sequence. Recover by delaying comparisons to other drivers until after the driver has written their own report and reviewed their own evidence.

The fifth failure mode is belief-confirming testing. The symptom is that a setup or technique change is declared good because it felt good in one place, even though the trace shows a loss elsewhere. The cost is slower development. Recover by using net-gain thinking. If corner speed improves while straight speed drops, total elapsed time and split structure decide whether the change was worthwhile.

The sixth failure mode is endless trial without record. The symptom is a paddock full of opinions and no traceable sequence. The cost is repeating blind alleys. Recover by writing the pre-rep question, the driver self-report, the evidence, and the next decision. Trial and error are part of motorsport, but disciplined trial and error is different from guessing.

Cross-references

Use this lesson after the driver understands the sibling lesson Define one change for one run. Feedback timing depends on a narrow practice question. If the run contains five experiments, no timing sequence will save the debrief.

Use it alongside Practice the cue, not the slogan. The self-report gate asks whether the driver practiced the cue, not whether they can repeat a phrase. The report should name an event in the car.

Use it before Use review tools without drowning the driver. This lesson teaches when to reveal evidence. The review-tools lesson can teach which evidence to choose when a deeper data review is needed.

Use it before Progress from clean reps to variation. Once the driver can bracket a clean rep with self-report and evidence, you can change conditions, traffic, pace, or line variation without losing the learning loop.

Worked example: aero change with faster corners and slower straights

A useful corpus-supported example is an aerodynamic change that increases downforce. The driver goes out expecting more corner grip. The timing loop should not ask only whether the lap was faster. It should ask where the gain appeared and what it cost.

Before the run, set the question: did the change improve corner speed enough to offset any loss in straight-line speed. Tell the driver to notice two sensations: whether the car accepts the corner with less correction, and whether the straight feels lazier. After the run, take the self-report first. The driver might say the car felt planted in the corner but seemed to run out of speed on the straight. Do not confirm or deny yet. Write that down.

Now reveal the evidence. Use speed versus time or rpm-derived speed if that is what you have. Look at corner speed, straight speed, split time through the affected section, and total elapsed time. If corner speed rises and straight speed falls, the result is not automatically good or bad. The net elapsed time decides whether the trade was worthwhile for that track and car. This is the exact discipline McBeath describes: corner-speed gains from downforce can be set against straight-line losses and overall elapsed time as a measure of net gain or loss.

The coaching point is not aero theory. The coaching point is feedback timing. If the driver saw the lap time first, they might call the change a success or failure too early. If the driver reported the sensation first and then compared it with segment evidence, they learn both the car and their own sensitivity. The next decision becomes clean: keep the change, revert it, or test again because the evidence was mixed.

Worked example: a road racer learning an oval habit loop

Bentley gives a useful coaching situation: road racers with little oval experience can learn quickly when a coach helps them build the right habits before bad habits form. Use that as a feedback-timing example rather than as an oval-driving lesson.

Before the run, the coach does not give the driver a full racing lecture. The coach chooses one habit question. For example, did the driver carry a road-course habit into the oval rep, or did they execute the new basic habit cleanly. The driver knows that the first feedback will not be lap-time comparison. It will be a self-report: what did the car do, where did the driver feel uncertain, and did the old habit show up.

After the run, the driver reports first. Because the driver has little oval history, the report may be rough. That is fine. The point is to start building awareness before the scoreboard speaks. The coach then adds observed evidence and only then uses timing if timing helps the specific habit question. If the driver was slower but the habit was cleaner, the next rep may be a repeat rather than a correction. If the driver was faster because they reverted to an old road-racing habit, the time is not the lesson you want reinforced.

This example matters for HPDE coaching because many drivers arrive with habits from sim racing, karting, autocross, street driving, or another track. Early feedback can install the right loop or cement the wrong one. Time belongs after the habit report, not before it.

Common mistakes

Mistake one is asking for lap time before asking what happened. Good looks like this: the driver speaks or writes a short sequence before seeing the number. The coach then uses the number to test the report.

Mistake two is making the feedback window larger than the practice window. If the rep was one braking zone, do not lead with whole-lap time. Good looks like a local measure that matches the local cue.

Mistake three is treating feel as truth or data as truth. Feel can be wrong. Data can be incomplete or interpreted badly. Good looks like a conversation among driver report, timed evidence, and coach observation.

Mistake four is collecting more data than the next decision needs. Good looks like the smallest evidence set that can answer the question. Save deeper trace study for the longer review.

Mistake five is comparing to other drivers too early. Good looks like a driver who first calibrates against their own rep, then later uses comparison after their awareness is stable.

Mistake six is failing to close the loop. A driver report and a trace are not enough. Good looks like one next action: repeat, keep, revert, or change the question.

Drill: four-rep feedback bracket

Use this drill at the next event when the driver has a clean session and enough space to repeat one segment. Pick one corner, braking zone, or sector. Do not use the whole track unless the driver is already disciplined with segment feedback.

Rep count: four reps in one session, or two pairs across two sessions if traffic interrupts. Before rep one, write the segment, cue, expected sensation, and evidence you will reveal. After rep one, the driver gives a self-report before seeing timing. Reveal only the chosen evidence. Decide repeat, keep, revert, or change question. Rep two repeats the same question unless the first evidence clearly shows the question was wrong.

For reps three and four, keep the same segment but ask the driver to predict the evidence before seeing it. The prediction can be simple: better, worse, or same in the target split, and where the time appeared or disappeared. The success criterion is not four faster reps. Success is that by the final rep the driver can give a specific self-report, predict the direction of the evidence, and name the next action without being handed a global lap-time verdict.

Debrief the drill after the session. Compare the written reports with the timing evidence. If the driver reports got more specific, the drill worked even if the fastest lap did not occur. If the driver only cared about the fastest lap, repeat the drill with the timer hidden until the self-report is complete.

When to widen or narrow the feedback window

Narrow the window when the driver cannot describe the rep. If the driver comes in with broad judgments, move from lap to sector, sector to corner, or corner to one event such as brake release or throttle commitment. Intermediate drivers often need this narrowing because they can feel many things but cannot yet order them.

Widen the window when the local improvement creates a global tradeoff. The aero example is the model: more corner speed may cost straight speed, so the feedback has to include total elapsed time or at least the next straight. A setup change can feel better in the corner and still lose time elsewhere. A habit change can slow the first clean rep but build a repeatable foundation. Widen only far enough to see the trade.

Delay the window when the driver is emotionally charged. If a number will cause defensiveness, take the self-report and basic notes first, then review evidence when attention is available. Discussing ideas expands knowledge, but only when the driver and team are actually able to communicate.

Move the window to a longer review when the question is no longer about the next rep. Permanent records are useful because they can be inspected later. Use the paddock or post-event review for patterns across runs. Use the immediate post-rep window for the next decision.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Ultimate Speed Secrets - Ross Bentley	1c0de301-8b35-9fab-3376-de66edf0d04d	535	1	uio_books_raw_v1
2	Competition Car Aerodynamics 3rd Edition McBeath Simon	ac2b13c4-51bb-bcb1-cbe4-e7f34da7f114	344	1	uio_books_raw_v1
3	Competition Car Aerodynamics 3rd Edition McBeath Simon	c7d0125c-8080-dbcc-df83-3b96d0b84bab	477	1	uio_books_raw_v1
4	Competition Car Aerodynamics 3rd Edition McBeath Simon	cd94958f-1042-ceff-8d99-06fa06ac633b	504	1	uio_books_raw_v1
5	Ultimate Speed Secrets - Ross Bentley	4400491c-451f-86fc-590c-1fa83983aef9	12	1	uio_books_raw_v1
6	Ultimate Speed Secrets - Ross Bentley	0237a5bd-e2d4-724e-bc2e-ba13db924f66	11	1	uio_books_raw_v1
7	Ultimate Speed Secrets - Ross Bentley	7816dd86-ce80-1320-b6ed-b34e005cc98f	16	1	uio_books_raw_v1
8	Inner Speed Secrets - Ross Bentley	1f89d950-4532-a2f9-3f06-33a6a39f92d6	24	1	uio_books_raw_v1
9	Ultimate Speed Secrets - Ross Bentley	c179b4ca-b1cd-bbae-16ca-d15b1ecdfc12	11	1	uio_books_raw_v1
10	Ultimate Speed Secrets - Ross Bentley	149c4d5c-d228-0358-acc0-8a92ac07ec7c	50	1	uio_books_raw_v1
11	Ultimate Speed Secrets - Ross Bentley	47f6de8d-9d56-5b6d-547a-f1e7bb92faaf	152	1	uio_books_raw_v1