Convert data into one next-session action

Generated from content/lms/data-interpretation-for-drivers/05-self-coaching-with-data/03-analysis-action-plan.md; edit the source file, not this page.

Source path: content/lms/data-interpretation-for-drivers/05-self-coaching-with-data/03-analysis-action-plan.md

Course: Data Interpretation for Drivers

Module: Self-Coaching with Data

Estimated duration: 65 minutes

Purpose

This lesson is about the last step in a data review: converting what you found into one action you can actually drive in the next session. The review is not finished when you find a slower corner, a lower minimum speed, a throttle lift, a brake trace with a long tail, or a lap that looks better than the others. The review is finished when you can name one situation, one driver behavior, one expected data signature, and one feel cue you will carry into the car.

That distinction matters because data by itself does not drive the car. You do. A data system can show where you began braking, what the throttle did, what speed you carried, what the steering angle looked like, and what the car generated in g-force. It can also reveal something you did not notice, or confirm something you already suspected. But until the information becomes a next-session objective, it is still only information.

The principle

The principle for this lesson is simple: data improves your driving only when it changes the next on-track behavior you are trying to perform. The data review should make you more aware of what you are doing, then help you choose a strategy for what to do next. If the review ends in a pile of interesting traces and no clear driving objective, it may have been entertaining, but it has not yet become coaching.

Think of the data system as an awareness amplifier. It records the car and the driver with less ego and less selective memory than you bring back from the session. You may be certain that you stayed flat through a high-speed turn, then the throttle trace shows a small lift. You may feel that you braked hard and short, then the brake pressure trace shows a light, long application with a long release tail. You may feel that your throttle pickup was confident, then the trace shows coasting, hesitation, or an early application followed by a lift. These are not personal attacks. They are opportunities to synchronize your perception with what happened.

The job is not to obey the data blindly. Bentley makes an important distinction: you need feedback from both sources, your feel and the data system. Sometimes the data suggests a change that would make the car quicker in theory but less comfortable or less confidence-inspiring for the driver. That matters because a driver who does not trust the car is unlikely to extract the performance the trace seems to promise. Your action plan should therefore respect both sides of the story: what the channels show and what you can execute cleanly in the car.

The one-action rule

For an intermediate driver, the strongest next-session plan is usually one action, not five. That is not because the data is simple. It is because the car is moving, the corner is coming at you, and your attention is finite. If you turn every trace observation into an instruction, you overload the next session. If you turn the most useful trace observation into a single behavior, you give yourself a chance to learn.

A good one-action objective has five properties. First, it is tied to an observed pattern in the data. Second, it is cross-checked with at least one other channel when possible. Third, it has a plausible cause, not just a symptom. Fourth, it includes a picture of what better would look like in the trace and in the car. Fifth, it is written before the next session so you can debrief against it afterward.

For example, do not write that you need to be faster in Turn 5. That is a wish. Do not write that you need to brake later everywhere. That is too broad and may be wrong. A better action says that in one named braking zone, the data showed a light, long brake application and delayed throttle pickup, so in the next session you will focus on making the initial brake application more decisive, then releasing with a cleaner shape so you can remove the coast before throttle. The expected trace is a shorter brake event, a cleaner release, less empty space between brake release and throttle, and no corrective lift after the first throttle application. The expected feel is that the car is settled enough that the first throttle request can stay on.

That is the level of specificity this lesson is teaching.

Start with the overview, then narrow

You are not replacing the broader review process taught elsewhere in this module. You are using it only long enough to choose the next action. Start with the overview: the lap, the segment or section report, the speed trace, and the obvious places where the car or driver did something different. Look for incongruencies. An incongruency is a mismatch between what you expected and what the data shows, or between two channels that should make sense together.

Then dig for details. If the speed trace drops earlier than expected, check brake pressure and throttle. If the throttle trace has a lift in a fast corner, check whether steering angle, speed, or line may explain it. If the brake pressure looks inconsistent, compare that with speed and throttle pickup. If the GPS line is available, see whether the path through the corner changed. If the steering channel is available, see whether extra steering angle appears at the same place as a throttle delay or a speed loss.

The important move is to narrow. Data review can expand forever. The source process lists steering, rpm, gear, segment times, fastest rolling laps, theoretical fastest, g-sum, GPS line, total steer angle, throttle histogram, brake pressure, and more. Those are useful tools, but the action plan must not become a catalog of every channel you opened. The purpose of the review is to find the one pattern that can become the next session objective.

The conversion chain

Use this chain every time: observation, question, cause, ideal, action, evidence.

Observation means the plain thing the data showed. Keep it factual. The throttle trace lifted in a fast corner. The brake pressure had a long tail. The throttle application was hesitant. The segment report says you lost time in one section. The speed trace says one lap carried more speed from entry to exit than another. At this stage, do not explain it yet.

Question means you ask why that observation happened. A lift in a fast corner might be a comfort issue, a line issue, a steering issue, a confidence issue, a car-balance issue, or a response to traffic or conditions. A long brake tail might be intentional trail braking, uncertainty during release, an entry-speed correction, or a habit of easing off the brake too slowly. The question step keeps you from turning the first visible symptom into the wrong fix.

Cause means the most likely driver-controllable reason you can test next session. The word test matters. You are not declaring permanent truth about yourself or the car. You are choosing a working explanation. If you cannot connect the cause to something you can feel and do in the car, it is not ready to become an action.

Ideal means the mental picture of what better looks like. This is not fantasy. It comes from your own best lap, a teammate or comparable driver if you have one, a previous session, a segment report, a theoretical fastest reference, or a clean mental program. The ideal should include both a trace picture and a feel picture. If your action is about throttle commitment, the trace picture might be a continuous application without an unintended dip. The feel picture might be a calmer steering hand, a car that does not need a midcorner correction, and a throttle request you do not immediately take back.

Action means the one thing you will do next session. It must be small enough to drive. It should name the corner or situation, the cue you will notice, the input you will change, and the expected result.

Evidence means how you will know after the session whether you improved. Evidence may be a cleaner trace, better lap-to-lap consistency, a faster section, a closer match between your predicted trace and the actual trace, or a more confidence-inspiring feel that allows the driver-car package to perform better. The evidence does not have to be a personal-best lap. In fact, if you are learning a new behavior, the first evidence may be consistency and awareness before outright speed.

Sub-skill: synchronize your feel with the data

Before you can turn data into action, you have to stop treating the data review as a trial where either you were right or the computer was right. The first skill is synchronization. That means you learn to read the track and car in a way that matches what the data system reports, and you learn to interpret the data in a way that matches what you are reporting from the cockpit.

This starts immediately after a session. Before you stare at the traces, write down what you think happened. Note the corners where you felt strong, the places you believe you were flat, the braking zones where you think you improved, and the sections where the car felt uncomfortable. This is not a diary exercise for its own sake. It creates a prediction that you can compare against the data.

Then open the data and check the match. If you predicted full throttle through a fast section and the throttle trace shows a small lift, do not defend yourself. Mark the mismatch. If you predicted that the car was under control because the lap felt calm, but the steering trace shows large corrections or the throttle trace shows a lift after early application, mark that too. If the data confirms what you felt, that matters as well. Confirmation means your sensory information is getting sharper.

The long-term goal is for your mental picture and the actual data to become increasingly similar. That does not happen by memorizing traces. It happens when you deliberately compare what you felt, saw, and heard with the recorded channels. The quality of your sensory information improves because the data keeps showing you where your perception is accurate and where it is not.

Sub-skill: describe the problem in driver channels first

A next-session action should begin with driver activity channels whenever possible: speed, throttle position, steering angle, and brake pedal position or pressure. Those channels answer the most practical question for a driver: what did I do with the controls, and what did the car do in response?

If the trace points to a balance issue, you may use more channels. Understeer and oversteer analysis can involve speed, throttle position, front lateral g-force, rear lateral g-force, steering angle, and understeer angle. But even then, your next-session action still has to come back to what you can do. If the car understeers because you are asking too much steering while adding throttle, the action is not a vague note that the car understeers. The action is to adjust the timing and size of the steering and throttle request in that corner, then check whether the channels move in the right direction.

This is why the phrase driver-controllable is so useful. Driver-controllable does not mean the car setup never matters. It means that the next session objective should be something you can attempt without a setup meeting, a new part, or an engineer translating the trace for you. Brake shape, throttle timing, throttle commitment, steering smoothness, line choice, and consistency lap to lap are all places where the data can point to a driver action.

Sub-skill: use incongruencies, not curiosity, to choose the action

There is nothing wrong with curiosity. The source advice even encourages getting your hands dirty and playing around with the data. But the action plan should not be selected because a channel was interesting. It should be selected because the data reveals an incongruency that matters.

A strong incongruency has tension in it. You thought you were flat; the throttle says you lifted. You thought you were braking short and hard; the brake trace says light and long. You thought earlier throttle was helping; the trace says early throttle led to a lift. You thought the car was consistent; lap-to-lap traces show a different brake point or a different throttle pickup. You thought the lost time was in the corner; the segment report says the bigger loss was the exit or the following straight.

When you find one of these, resist the urge to solve it instantly. Cross-check. Use other channels if available. If the throttle lift occurs with a steering correction, the action may be about the line or steering input, not just courage with the throttle. If the brake release is long and the throttle is delayed, the action may be about the transition from brake release to throttle, not simply braking later. If the fastest rolling or theoretical fastest view shows that your best sectors are spread across laps, the next action may be consistency in one section rather than a new peak-speed attempt.

Sub-skill: ask why until the action is small enough

Asking why is not an academic exercise. It is how you keep the next action from being a slogan. If your observation is that the throttle trace shows coasting, ask why you coasted. Were you waiting for the car to finish rotating? Were you unsure where the track-out would be? Did you add throttle too early and have to remove it? Did the brake release leave the car unsettled? Did the steering angle stay in the car longer than expected?

If your observation is that the brake trace shows a long tail, ask why the release stayed long. Were you using the brake to finish rotation, or were you slowly bleeding pressure because you were not confident the car would make the apex? Did the long tail help the car, or did it delay the throttle and hurt the exit? The answer changes the action. A useful trail-brake release and an indecisive release can look superficially similar until you compare speed, throttle pickup, steering, and the result through the section.

Stop asking why when you reach a testable next-session behavior. If you keep going until the answer becomes vague, you have gone too far. The useful endpoint is not that you need to be smoother, more committed, or more aggressive. The useful endpoint is that in one corner you will release the brake with a cleaner shape, wait until the car accepts the first throttle request, and avoid the early throttle followed by a lift that the trace showed last session.

Sub-skill: compare, but do not worship the comparison

Comparison is powerful. You can compare your laps against each other, compare sessions, compare with a teammate, compare with another driver in a similar car, or compare against what you mentally programmed. Data becomes especially valuable when you can see what a faster driver or a better lap did differently in the same section.

But a comparison is not automatically an instruction. A faster trace may show a later brake point, more minimum speed, earlier throttle, or less steering. That does not mean your next action is to copy all of it immediately. Your job is to identify the difference that is both important and executable. If the faster lap gained time because throttle pickup was earlier and stayed on, but your own trace shows early throttle followed by a lift, your action is probably not simply earlier throttle. It may be a better entry, a cleaner brake release, or a more settled first throttle request.

Your own best laps are often the most useful comparison because they show something you have already done in the same car. If one lap carried speed better through a section, ask what the driver channels did differently. If your best sector appears in a lap that was not your best full lap, that can become a focused consistency objective. You are looking for the smallest repeatable behavior that moves you toward the better pattern.

Sub-skill: imagine the ideal before you drive it

The data process explicitly includes imagining what ideal would look like. This is where the review becomes a rehearsal. You are not just looking backward. You are creating a forward picture of the next attempt.

Build the ideal in two forms. First, build the data picture. What should the throttle trace do? What should the brake pressure shape look like? What should be different in the speed trace? Should the steering angle be smaller, slower, or more consistent? Should the section time improve, or should the lap-to-lap spread shrink? Second, build the cockpit picture. What will you see, feel, and hear when you are doing it correctly? What will tell you that the car is accepting the input rather than making you take it back?

This is especially important because data review happens while you are parked, but driving happens through sensory information. If your next action lives only on a laptop, it will disappear when the corner arrives. If the action includes a sensory cue, it has a chance to survive at speed.

Sub-skill: write the objective before the next session

A driver log is not just history. It is part of the action loop. Before each session, write the objective and the technique or plan you will use to achieve it. After the session, record the conditions, what changed, and what the result was. That turns the session into a test instead of a blur of impressions.

The objective should be short, but not vague. Use this format: In this situation, I will change this input or timing, using this cue, expecting this data signature and this feel.

Here is the shape, without relying on any specific track from outside the corpus. In the fast corner where the throttle trace showed a small lift, I will enter with the same safety margin, notice whether my steering input is still asking the front tires for too much, and aim for a throttle trace that stays continuous through the section. The feel I want is a car that does not require me to take back the throttle after I have asked for it.

Here is another shape. In the braking zone where the pressure trace was light and long with a long release tail, I will make the initial brake application more decisive, release with a clearer shape, and reduce the coast before throttle. The feel I want is that the car is settled enough at release that the first throttle application does not become hesitant.

These are not magic words. They are a way to turn data into a behavior you can remember.

Calibration cues: how you know the action worked

The first calibration cue is reduced surprise. If you get out of the car, write what you believe happened, and the data mostly agrees, your awareness is improving. This may sound less exciting than a lap-time gain, but it is foundational. A driver whose perception matches the data can coach themselves more accurately.

The second cue is a cleaner target channel. If the objective was about throttle, the throttle trace should show less coasting, less hesitation, fewer unintended lifts in fast corners, or less early application followed by a lift. If the objective was about braking, the brake pressure trace should show the intended shape: a more appropriate initial application, a cleaner trail, less inconsistency, or less light-and-long braking if that was the issue. If the objective was about steering, the steering trace or total steer angle should move toward the intended pattern.

The third cue is section evidence. Segment reports, section times, fastest rolling laps, and theoretical fastest views help you avoid overreacting to total lap time. A session can be messy because of traffic, weather, tires, or learning load, but a section can still show whether the target behavior helped. If the section improves or becomes more consistent while the target channel also improves, the action is probably useful.

The fourth cue is repeatability. One lap can be luck or circumstance. A tighter lap-to-lap pattern suggests the behavior is becoming yours. Consistency matters because the purpose of driver development is not merely to produce a single trace that looks nice. It is to build a skill you can access repeatedly.

The fifth cue is comfort that helps performance. If the data-only version of the change makes you tense, late, or distrustful, the driver-car package may not improve. A good action often improves both the trace and your confidence. When those two move together, the next-session objective is doing its job.

Failure mode: the data review never becomes a plan

The most common failure is stopping at discovery. You find the throttle lift, admire the overlay, talk about the brake trace, and then go back out with no objective. This is how data becomes entertainment. The recovery is to force the conversion chain: observation, question, cause, ideal, action, evidence. Do not close the laptop until the action is written.

Failure mode: the action is too broad

A broad action feels productive because it sounds ambitious. Be smoother. Carry more speed. Brake later. Get on throttle earlier. The problem is that none of those tells you what to do at the moment the car asks for a decision. The recovery is to attach the action to one situation and one input. If the data issue is a hesitant throttle application, the action should name the corner or type of corner, the cue for first throttle, and what the trace should show afterward.

Failure mode: you argue with the data

Another failure is defensiveness. The data shows a lift and you insist you were flat. The data shows a long brake tail and you insist you braked hard and short. The recovery is to treat the mismatch as synchronization work. You are not trying to prove that your memory was bad. You are training your perception so the next report from the car is more accurate.

Failure mode: you obey the data without respecting feel

The opposite failure is treating the trace as the only truth. If the data suggests a change that makes the car less confidence-inspiring, you may not be able to execute it well. The recovery is to include feel in the action plan. You can still pursue the faster pattern, but the first step may be the version that lets you trust the car enough to repeat it.

Failure mode: you chase symptoms instead of causes

A lost section time may be the symptom. A lower minimum speed may be the symptom. A late throttle may be the symptom. The cause may be earlier in the corner, in the brake release, in steering angle, in line, or in comfort. The recovery is to use other channels to check the story before choosing the action.

Failure mode: you use too many channels as equal voices

The source process lists many available channels and views. That is useful during analysis, but it can become noise during action planning. The recovery is to choose one primary channel for the action and one or two supporting channels for verification. If the action is throttle commitment, throttle is primary; speed and steering may support the story. If the action is brake release, brake pressure is primary; speed and throttle pickup may support the story.

Failure mode: you skip the written record

If you do not write the objective before the session, it is easy to rewrite history afterward. If you do not write the result after the session, you lose the thread when you return to the same track or face the same driving problem later. The recovery is simple: keep a record of the session objective, the plan, the conditions, the result, and the next decision. This lesson does not replace the learning journal lesson, but it depends on the same discipline.

The action-plan template

Use this template at the end of every data review.

Situation: name the corner, section, or repeated condition.

Observation: state what the data showed in one sentence.

Cross-check: name the supporting channel or comparison.

Likely cause: describe the driver-controllable reason you will test.

Ideal: describe what the trace and the cockpit feel should become.

Next-session action: write the one behavior you will perform.

Evidence: define what will count as progress after the session.

Here is the standard you should hold yourself to: if another instructor or driver read your action line, they should know exactly what you plan to attempt on track and exactly which trace to inspect afterward. If they only learn that you want to be faster, the plan is not finished.

How this connects to the rest of self-coaching

The sibling lessons in this module cover the broader structure of data review and the learning journal. This lesson is the bridge between them. The structured review finds the pattern. The journal preserves the objective and result. This lesson makes the pattern drivable.

That bridge is the difference between using data as reference material and using it as a coach. Reference material tells you what happened. Coaching tells you what to try next. Your goal after each session is to leave the review with one testable driving behavior, not with a larger pile of facts.

The final question

At the end of the review, ask one practical question: what can be done to go faster? Then make the answer smaller. Make it one corner or one situation. Make it one driver input or timing change. Make it visible in the data. Make it feelable in the car. Make it simple enough to remember before you reach the place where it matters. That is how data becomes the next lap instead of the last lap.

Worked example: the fast corner you thought was flat

This example comes directly from a common data-synchronization problem in the bonded corpus: a driver gets out of the car believing a high-speed turn was taken at full throttle, then the data shows a small lift.

Start with the observation. The throttle trace has a dip in the fast corner. Do not begin by calling yourself timid, and do not begin by blaming the data. The factual observation is simply that the pedal was not where your memory said it was.

Now cross-check. Look at speed to see where the lift occurred and what it cost. Look at steering angle if you have it. If a steering correction appears at the same time as the throttle dip, the issue may be that the car was not settled enough for the throttle you wanted to hold. If the GPS line is available, check whether the line changed on the laps where the lift appeared. If a comparable faster lap or teammate lap is available, compare only the relevant section first, not the whole lap.

Ask why. Maybe the line made the corner feel tighter than expected. Maybe you turned too much steering into the car and the throttle lift was your response to the front or rear not feeling trustworthy. Maybe you entered with more speed than your current reference points could support. Maybe the lift was tiny but repeated, which means your body has found a protective habit that your conscious report missed.

Now build the ideal. The ideal is not merely that the trace should be full throttle. The ideal is that your perception, the car, and the trace agree. You want to enter the corner with a clear enough plan that the throttle request can stay continuous. You also want to know what the car should feel like when that is possible: stable enough that you do not ask for a lift after turn-in, and clean enough in steering that you do not need to rescue the car with your right foot.

The next-session action might be: in that fast corner, keep the same responsible entry reference, notice whether steering angle is still being added after the car should be settled, and aim for one continuous throttle trace through the section. The evidence is not bravado. The evidence is a trace with no unintended dip, a speed trace that does not show an avoidable loss, and a post-session report that matches the data more closely than before.

If the next trace still shows a lift, that is useful. It means the action was either not executed or the cause was not the one you chose. Go back to the chain. The failure is not that you found the lift again. The failure would be ignoring it or turning it into a vague command to be braver.

Worked example: the brake trace with a long tail and hesitant throttle

This example uses the brake and throttle questions in the bonded data-process chunks: brake pressure shape, initial application, trail, long tail, inconsistent pressure, light-and-long versus hard-and-short braking, coasting, hesitant throttle application, early application leading to lift, and fast-corner lifts.

The observation is that a braking zone shows a pressure trace that stays low or trails for a long time, and the throttle trace after it shows hesitation or coasting. The section report also suggests time is being lost in that part of the lap. A weak action would be to brake later next session. That skips too many steps.

First, ask what the brake trace is doing. Is the initial brake application strong enough for the speed you are carrying, or is it light and stretched out? Is the long tail a useful trail that helps the car rotate, or is it a sign that you are staying on the brake because you are not confident the car will make the corner? Is the pressure shape similar lap to lap, or does it move around?

Then check throttle. If the throttle trace shows coasting after brake release, your problem may be the transition, not the brake point. If it shows early application followed by a lift, your first throttle request may be arriving before the car is ready. If the trace shows hesitation, the car may not be giving you the confidence to commit, or your visual and feel references may not be clear enough.

Now compare. Use your own better lap if you have one. Use a similar driver or similar car if available. Look for the smaller difference that explains the section, not the largest-looking difference on the screen. A faster comparison may brake differently, but the useful action for you may be a cleaner release and a more trustworthy first throttle, not a later brake point.

The next-session action might be: in this braking zone, make the initial brake application more decisive, release with a cleaner shape, and delay the first throttle request until it can stay on rather than arrive early and require a lift. The expected data signature is a brake trace with the intended shape, less coast between brake release and throttle, and a throttle trace that does not show a false start. The expected feel is that the car is settled at the moment you ask for throttle.

This kind of action is useful because it connects multiple channels into one behavior. You are not chasing brake pressure in isolation. You are using the brake trace, throttle trace, speed trace, and section result to choose one transition to improve.

Common mistakes

Mistake 1: turning every finding into an objective. A data review can produce many useful observations, but you can only drive a small number of intentions at speed. Good looks like choosing the one observation that is visible, cross-checked, and likely to change the next session.

Mistake 2: choosing lap time as the action. Lap time is an outcome. It can tell you whether the driver-car package improved, but it does not tell you what to do with your hands and feet. Good looks like using section times, speed, throttle, brake, and steering to define the behavior that should produce the outcome.

Mistake 3: copying a faster trace too literally. A teammate or similar-car comparison can be extremely valuable, but the faster trace may contain several differences at once. Good looks like selecting one difference that is important and executable for your current skill level.

Mistake 4: arguing with a mismatch. If your feel says one thing and the data says another, the mismatch is not a reason to quit using data. Good looks like treating the mismatch as calibration work. Write what you thought happened, compare it to the trace, and use the gap to improve your awareness.

Mistake 5: ignoring the driver comfort side of the feedback. A data-only plan that makes you tense or distrustful may not improve the whole package. Good looks like choosing the version of the action that moves toward the better trace while still giving you a car you can drive with confidence.

Mistake 6: using channels without a question. Opening more channels can help, but only if each one is answering something. Good looks like using the primary driver channel for the action and one or two supporting channels to check the story.

Mistake 7: skipping the written pre-session objective. Without a written objective, the next session becomes hard to evaluate. Good looks like writing the plan before you drive and recording the result afterward so the next review has continuity.

Drill: one-session synchronization and action ladder

Use this drill at your next event. Count: one target situation, one on-track session, one 20-minute post-session review, and one written next-session action. Duration: the driving session plus the review block. Success criterion: your next-session action names the situation, observed trace, likely cause, intended behavior, expected data signature, and expected feel.

Step 1: before the session, choose one corner or repeated situation. Write what you expect your data will show there. Keep it concrete. Predict the throttle behavior, brake behavior, steering behavior, or speed behavior you believe is happening.

Step 2: drive the session normally, but keep that one situation in mind. Do not turn the entire session into a science project. Your job is to gather a clean comparison between what you thought you would do and what you actually did.

Step 3: after the session, write your memory before opening the data. Note whether you believe you executed the target behavior. This protects the calibration value of the exercise.

Step 4: open the data and compare your memory with the trace. If they agree, mark that as improved awareness. If they disagree, mark the exact mismatch. Use speed, throttle, brake, steering, segment time, GPS line, or other available channels to cross-check the story.

Step 5: ask why until you reach one testable driver behavior. Do not leave the review with a general idea. Convert the mismatch into one action for the next session.

Step 6: write the action in the template from the lesson. Situation, observation, cross-check, likely cause, ideal, next-session action, evidence.

Step 7: after the next session, judge the action by the evidence you named, not by memory alone. The best result is that your feel and the data move closer together while the target trace or section result improves. If the trace does not improve, the drill still worked if it gave you a clearer cause for the next test.

Cross-references and scope boundaries

Use the lesson on structuring your data review when you need the broader scan: overview, incongruencies, details, cross-checks, comparison, and channel selection. Use this lesson when the review has produced a candidate finding and you need to turn it into one drivable objective.

Use the learning-journal lesson to preserve the objective and outcome across events. This lesson gives you the action line; the journal keeps that action from disappearing before the next time you return to the same track or the same driving problem.

Do not use this lesson as a setup-analysis substitute. The bonded corpus supports using data to understand both car and driver behavior, and it recognizes that data can help develop the car. But this lesson is specifically about driver self-coaching. If the conclusion is that the car needs a setup change, the driver action still needs to be clear: what you will drive, what you will feel, and what evidence will tell you whether the package improved.

Author Review

No quiz questions are attached to this lesson.

Sources

#	Document	Chunk	Pages	Score	Collection
1	Data-for-Drivers-PRINT	bbb02386-778f-20ec-ad16-b9c016921743	16	1	uio_books_raw_v1
2	Data for Drivers	cabda699642b26311b0a7ef998da2c71	15	1	uio_books_raw_v1
3	Inner Speed Secrets - Ross Bentley	02822a18-86f0-c082-0db4-b817146db0d9	153	1	uio_books_raw_v1
4	Ultimate Speed Secrets - Ross Bentley	7212e525-6587-a46d-1fab-5d027a6e940e	553	1	uio_books_raw_v1
5	Ultimate Speed Secrets - Ross Bentley	ffc0b430-cf01-f6b7-7a37-59982d3d8c06	557	1	uio_books_raw_v1
6	Speed Secrets Professional Race Driving Techniques Ross Bentley	a009c9a4-cb8d-b3b5-063d-33e44ea0b5cb	76	1	uio_books_raw_v1
7	Analysis Techniques for Racecar Data Acquisition	d0db9128-dc9a-aec3-14a8-5f101654753f	3	1	uio_books_raw_v1
8	Analysis Techniques for Racecar Data Acquisition	66088a66-7d06-8e55-03eb-967374239bec	6	1	uio_books_raw_v1
9	Analysis Techniques for Racecar Data Acquisition	52e7d5ab-412b-acc5-fb49-cb0e8d5511b1	6	1	uio_books_raw_v1
10	Analysis Techniques for Racecar Data Acquisition	41138569-fa56-a0a4-38c5-301475e4131a	21	1	uio_books_raw_v1
11	Analysis Techniques for Racecar Data Acquisition	5eeea298-6191-0fb2-1054-b10fe574a804	2	1	uio_books_raw_v1
12	Inner Speed Secrets - Ross Bentley	faf47214-2619-0395-43b8-f1f6523e5a80	32	1	uio_books_raw_v1
13	Inner Speed Secrets - Ross Bentley	1f89d950-4532-a2f9-3f06-33a6a39f92d6	24	1	uio_books_raw_v1
14	Ultimate Speed Secrets - Ross Bentley	0237a5bd-e2d4-724e-bc2e-ba13db924f66	11	1	uio_books_raw_v1
15	Ultimate Speed Secrets - Ross Bentley	7f32498f-d9fd-bd02-17d6-a1aa8be21a50	501	1	uio_books_raw_v1
16	Data-for-Drivers-PRINT	cb13d8c3-cc6b-28e9-246f-c3c64ae01efc	1	1	uio_books_raw_v1