Decide at the next-action scale
Generated from
content/lms/mental-game-ii-perceptual-science/04-build-if-then-driving-decisions/03-choose-the-next-action-not-the-perfect-action.md; edit the source file, not this page.
Source path: content/lms/mental-game-ii-perceptual-science/04-build-if-then-driving-decisions/03-choose-the-next-action-not-the-perfect-action.md
Course: See sooner and decide faster at speed
Module: Preload decisions for fast-changing laps
Estimated duration: 55 minutes
Principle: the useful decision in the car is the smallest action you can execute now.
You are not trying to choose the perfect lap while the car is moving. You are choosing the next brake release, the next steering rate, the next throttle timing, the next reference point, or the next question to carry into the debrief. That scale matters because intermediate driving still includes conscious competence: you know what needs to be done, but part of you is still having to think through it. If the problem you ask yourself is too large, the answer arrives after the car has already crossed the part of the track where it mattered.
That does not mean you stop thinking. It means you place the thinking at the right size. Before the session, you choose an objective. During the corner, you choose one action that serves that objective. After the session, you debrief whether that action made the car faster, calmer, or more repeatable. This lesson is not replacing the sibling lessons on writing rules before the lap, adapting rules to the event, limiting the menu, or debriefing the rule. It sits between them. It teaches the moment where the written rule has to become one physical command.
Start with objective, not preference.
A next action is only good relative to an objective. The mental-game mistake is asking yourself what should I do here as if every answer has equal value. Before a quality decision, you need to know the primary objective for that activity, and that objective can change with the situation. In a qualifying lap the objective may be to extract the cleanest corner exit from the fastest corner onto the next straight. In a traffic session the objective may be to preserve track position and avoid forcing a low-percentage pass. In a learning session the objective may be to test whether a slower brake release gives you a cleaner entry platform. Same corner, same car, different objective, different next action.
The objective must be narrow enough to survive speed. A broad objective such as be faster is not usable at turn-in. It does not tell your right foot what pressure to carry, your hands how quickly to add steering, or your eyes which detail to use next. A usable objective sounds more like carry less brake past the first steering input and see whether the car rotates earlier, or delay throttle until the wheel is unwound enough to keep the exit open. You are not writing poetry. You are preloading a small decision so it is available when your attention is busy.
This is why the next-action scale is a mental skill, not just a tactical phrase. Your body does not operate separately from your brain. The car gets your mental organization through your hands and feet. If your mind is debating the perfect solution, your body sends mixed instructions. If your mind has chosen one next action tied to one objective, your inputs become more consistent. Consistency is what gives you evidence. Evidence is what lets you improve.
The mechanism: small choices protect execution.
Driving at speed is not learned only by reading, but theory matters because it lets you picture what should happen before the experience arrives. The useful picture is not the whole lap painted in heroic detail. The useful picture is the next cause-and-effect link. If you release the brake more gradually, the front tires may stay loaded longer into the entry. If you turn the wheel less abruptly, the car may take a calmer set. If you open the wheel before adding throttle, the exit may widen less. If the track surface or camber changes, the next action may need to change with it.
At intermediate pace, you often know the concept but still have to do it consciously. That is not a failure. It is a stage. The driver in conscious competence can perform the skill, but must think about the steps. The risk is trying to think about too many steps at once. You may enter a braking zone trying to remember line, brake pressure, downshift, release, turn-in, apex, throttle, unwinding, mirrors, traffic, and lap time. That is a menu, not a decision. Under load, the menu collapses into habit. The next-action method trims that menu to the one action that matters next.
A next action is not a vague intention. It has four parts: a trigger, an action, a constraint, and an evidence check. The trigger is what tells you the decision point has arrived. The action is what you will physically do. The constraint keeps the action from turning into overdriving. The evidence check tells you whether it helped. For example: when the car reaches the brake-release marker, release pressure one beat slower, keep steering rate calm, and check whether the car accepts the first steering input without pushing wide. That is small enough to execute and specific enough to debrief.
You can build these actions from track-reading details. Track reading is more than knowing whether the corner turns left or right. You read the surface, radius, camber, elevation, hillcrests, curbs, bumps, and straight length. Those details become triggers. A decreasing-radius corner asks for a different next action than a constant-radius corner. A downhill entry changes how confidently you can ask the front tires to combine braking and turning. A long straight after the corner changes the value of exit speed. A bump or curb changes whether your steering release must be more patient. The point is not to memorize labels. The point is to let track detail choose the next useful action.
Use the speed priority stack.
When you do not know what the next action should be, use the priority stack. First protect the line. Then protect the acceleration phase. Then work on corner-entry speed. Only after those are sound should you chase midcorner speed. This order matters because trying to carry more midcorner speed before you have the line and exit phase under control usually creates a false gain. The car feels fast for a moment, then you delay throttle, pinch the exit, or add steering that the tire cannot support.
The next-action version of that stack is simple. If your line is not repeatable, your next action is not more speed. It is a clearer reference, a calmer steering input, or a corrected turn-in. If your exit is weak, your next action is not heroic entry speed. It is an earlier unwind, a later throttle pickup, or a brake release that lets the car point sooner. If your line and exit are stable, your next action can move upstream into corner-entry speed. If all of that is stable and you are already carrying the car cleanly, then you can test midcorner speed. The great drivers may separate themselves through midcorner speed, but that comes after the fundamentals underneath it are strong.
This also protects you from the perfect-action trap. The perfect action is usually a fantasy built from all priorities at once: brake later, turn in perfectly, carry more speed, rotate cleanly, throttle earlier, and exit faster. The next action asks for one gain at a time. It respects the fact that driving improvement does not happen sequentially in a neat classroom order, yet the moment inside the car still needs a single command.
The five-step next-action loop.
Step one: name the session objective before you roll. Make it situational. Do not write faster lap. Write the part of the lap you are changing. A good objective might be to stop over-slowing the first half of a specific corner, to make the entry platform calmer, to improve the exit onto the longest straight, or to compare your braking point and corner shape against a quicker car. The source material emphasizes continuing to analyze how to go faster and making notes after sessions. A session objective gives that analysis something to test.
Step two: choose one track feature as the trigger. The trigger can be the brake marker, the release marker, the first steering input, a surface patch, a curb, a camber change, a hillcrest, or the moment a quicker car ahead begins braking. If you cannot say when the action begins, it is not yet a next action. It is still a wish.
Step three: state the physical action. Use verbs a driver can do: brake, release, wait, turn, unwind, squeeze, breathe, look, hold, compare. Avoid abstract verbs such as optimize or maximize. Your hands and feet cannot optimize in the middle of a corner. They can release one beat slower, add steering more slowly, hold the car one foot wider before turn-in, wait one breath before throttle, or unwind the wheel before asking for more drive.
Step four: add a constraint. The constraint prevents the action from becoming a new error. If the action is release the brake later, the constraint may be do not add steering faster. If the action is carry more entry speed, the constraint may be protect the exit and do not delay throttle. If the action is follow the quicker car as a reference, the constraint may be copy timing only after confirming your car can still make the line. Constraints matter because most intermediate mistakes are not made from doing nothing; they are made from doing one useful thing too much.
Step five: choose one evidence check. Use felt evidence during the lap and harder evidence after the session. Felt evidence includes whether the car takes a set, whether steering can be slowed without lowering corner speed, whether you turn the wheel less, and whether throttle arrives without a fight. Harder evidence includes lap time, segment time, straightaway speed, data traces, brake points, and speed comparison through the same section. One chunk describes a same-section comparison where the difference between drivers comes from one driver slowing too much in the first half of the corner. That is exactly the kind of evidence a next-action decision can test.
How to make the decision while the car is busy.
At speed, you do not have time to conduct a committee meeting with yourself. Use a three-word command. The words are not magic; they are a handle for the action. Examples: slower release now. Wait for unwind. Less wheel first. Protect exit speed. Compare brake point. Look through camber. Each command should connect to the objective you already chose. If you find yourself inventing the command after turn-in, you waited too long. The command should be loaded before the trigger appears.
Use your eyes to shorten the decision. If the track feature is part of the trigger, look for that feature early enough to act on it. If you only identify the camber change as the car is already loaded, the next action will be late. If you see the car ahead brake and you only react when your nose is already diving, you are copying without decision. Seeing earlier does not mean doing earlier. It means deciding earlier so the action can be measured and calm.
Use your body as the output monitor. The source material allows you to connect mental organization with physical skill. If your shoulders tighten, your hands make quick corrections, or your foot snaps from throttle to brake and back, you may be trying to solve too much at once. If your breathing stays steady and one input leads cleanly to the next, the decision is probably at the right size. This is not a substitute for data, but it is available in real time.
Do not let the next-action method become timidity. Smaller decision scale does not mean slower driving. One of the steering lessons in the corpus points toward slower steering inputs without slower corner entry, midcorner, or exit speeds. That is the feel you want. The action becomes more refined, not more cautious. You may brake later in a later session, carry more speed, or release pressure deeper, but you do it through one specific test rather than a general urge to be brave.
Calibration cues: what improvement looks like.
The first sign is repeatability. Your laps stop feeling like separate inventions. You can describe what you tried, where you tried it, and whether it worked. If you cannot describe the action, you cannot improve it. If you can describe the action but cannot repeat it, the action is probably too large or the trigger is too vague.
The second sign is quieter hands. The corpus supports the principle that less steering generally points toward more speed, and that steering inputs can be slowed without slowing the corner. When the next action is right, you often need less correction because the car is asked to do one thing at a time. This does not mean the steering wheel never moves. It means the extra movement caused by indecision starts to disappear.
The third sign is better exit timing. If your objective is corner exit, the evidence is not only how fast the middle of the corner felt. Look at when you could begin accelerating, how much steering was still in the car when you added throttle, and whether the straightaway speed improved. The source material places the acceleration phase early in the priority list. A next action that wins the center but delays the exit may not be a win.
The fourth sign is a cleaner debrief. Instead of saying the car felt bad or the lap felt messy, you can ask the real question: what can be done to go faster. You can make notes about your driving and the car, compare against a quicker car, and discuss one decision with an engineer, mechanic, instructor, or yourself. The debrief becomes a continuation of the action loop, not a separate storytelling exercise.
The fifth sign is better adaptation. Every track has its own personality, and success depends on how well you get to know and adapt to it. Next-action decisions help because they are local. You can adapt one corner phase without rewriting your entire mental model of the lap. If a surface patch, bump, or camber change changes the available grip, the next action changes with that detail.
Failure modes and recovery.
Failure mode one is perfect-lap paralysis. You enter the corner holding the entire lap in your head. The car asks for one input, but your mind is still comparing several possible strategies. The recovery is to return to the trigger. What is the next observable thing? When it arrives, what is the one action? What is the constraint? If you cannot answer before the corner, slow the test down and make the next lap a learning lap.
Failure mode two is action without objective. You decide to brake later because later sounds faster. But if the objective was a better exit, later braking may hurt the lap by delaying rotation or throttle. The recovery is to ask whether the action serves the session objective. If not, discard it even if it feels bold.
Failure mode three is chasing midcorner speed too soon. This feels exciting because the number at the center may rise. The cost is often hidden at exit. You add steering, wait on throttle, or run out of road. The recovery is to return to the priority stack: line, acceleration phase, entry, then midcorner.
Failure mode four is copying the quicker car without filtering. Watching a quicker car can be useful, especially when you note where it brakes and how it takes corners. But the next action is not to duplicate everything. Your car, tires, confidence, and objective may not match. The recovery is to copy one observable timing detail as a test, then check whether your car still makes the line and exit.
Failure mode five is debriefing the result instead of the decision. You say the lap was faster or slower, but you do not know why. A faster lap with a sloppy decision may teach the wrong habit. A slower lap with a controlled test may be useful if it reveals what not to do. The recovery is to debrief the rule and the action: trigger, action, constraint, evidence.
Failure mode six is making the action too tiny to matter. Not every next action is useful. If the change is so small that you cannot feel it, measure it, or debrief it, it may be comfort behavior rather than learning. The recovery is not to make a reckless leap. It is to make the smallest action that can produce evidence.
How this connects to the rest of the module.
When you write rules before the lap asks for them, you are building the material for this lesson. When you adapt the rule to what is happening now, you are changing the objective or the trigger. When you limit the menu before pressure rises, you are protecting the next-action scale. When you debrief the rule, you are closing the loop with evidence. The specific contribution here is execution size. The rule may be clever, but the driver still needs to turn it into one brake, steering, throttle, or vision action at the next decision point.
The practical standard is this: after any session, you should be able to name one objective, one trigger, one next action, one constraint, and one evidence check. If you cannot, you did not run a decision plan; you ran laps and hoped experience would organize itself. Experience matters, but organized experience teaches faster.
Worked example: using a quicker car without copying the whole lap
You are behind a quicker car for several corners. The tempting thought is to copy the lap. That is too large. The useful next-action version is to watch one observable detail: where the quicker car begins braking, how quickly it releases, or how it shapes the corner before throttle. The corpus specifically supports watching a quicker car, noticing when it brakes and how it takes corners, then debriefing afterward.
Set the objective before you use the reference. Suppose your objective is to stop giving away time before corner entry. Your trigger is the quicker car's brake light or initial deceleration point. Your action is not brake at exactly the same place no matter what. Your action is compare timing, then move your own brake decision only as far as your car can still make the line. Your constraint is protect the exit and do not add steering rate to save an over-ambitious entry. Your evidence check is whether you can still begin accelerating on time and whether the car accepts the turn without extra correction.
If the quicker car brakes much later, your next action may be only to delay your initial brake application a small amount, not to match it fully. If it releases more smoothly, your next action may be to copy release shape rather than braking point. If it turns in later but still exits better, your next action may be to test a later turn-in on the next lap while keeping entry speed unchanged. That is how you use another driver as data instead of as a dare.
The common failure here is ego transfer. You see a faster driver do something and treat it as permission. The better move is evidence transfer. Take one feature, test one action, and debrief whether your car and your current skill level could use it.
Worked example: the same-section trace that shows first-half over-slowing
The bonded corpus includes a data-acquisition example in which the difference between two drivers on the same section comes from one driver slowing too much in the first half of the corner. That is a perfect next-action case because the problem is not the entire lap. It is one corner phase.
Start with the objective: reduce unnecessary first-half slowing without damaging exit. The trigger is the beginning of the braking and entry phase for that corner. The next action could be release brake pressure one beat earlier while holding the same turn-in point. Or it could be keep the braking point unchanged but carry slightly less peak brake so the car arrives at turn-in with less excess speed loss. The constraint is that the car must still rotate and must not force a delayed throttle. The evidence check is the speed trace through the first half of the corner plus the exit speed or straightaway speed afterward.
Notice what you are not doing. You are not deciding to be faster everywhere in the corner. You are not adding midcorner speed because the graph says another driver was faster. You are choosing a single mechanism that could explain the gap: too much slowing before the car reaches the middle. Then you test a physical action that changes that mechanism. If the trace improves in the first half but exit speed drops, the next action was incomplete or the constraint failed. If the first-half speed improves and the exit stays open, the action probably served the objective.
This example also shows why debriefing matters. A lap-time improvement by itself cannot tell you whether the action worked. A same-section comparison can. If you make notes on what you changed and then compare the trace, you have a lesson. If you only remember that the lap was better, you have a result without a method.
Worked example: first laps at an unfamiliar track
On a new track, the perfect-action trap gets stronger because every corner is asking for attention. The corpus says track learning is more than knowing which direction each corner goes. You need to read surface, bumps, curbs, radius, camber, elevation, hillcrests, and straight length. That list can feel overwhelming, so turn it into next actions.
For the first session, make the objective learn usable triggers, not set a personal best. In each corner, choose one track detail to read. The action may be identify whether the radius opens, tightens, or stays constant. It may be notice whether the road is uphill, downhill, or cresting at the decision point. It may be mark whether a curb can be used or should be avoided. The constraint is no speed increase until the feature is repeatable in your mind. The evidence check is whether you can describe the corner after the session without guessing.
By the second session, the objective can shift from reading to testing. If a corner leads onto a long straight, the next action may be protect the acceleration phase. If a surface change unsettles the car, the next action may be slow the steering input rather than slow the whole corner. If a decreasing radius catches you late, the next action may be delay throttle until the car is pointed enough to keep the exit open. Each action is local, but the learning compounds.
The mistake is trying to solve the whole track by memory alone. The better method is to let each feature create one next action. Over time, those actions become a track model you can drive from, and then debrief.
Common mistakes: what wrong feels like and what good looks like
Perfect-action hunting feels busy and intelligent, but it produces late inputs. You think about line, entry speed, throttle, and lap time all at once. The car receives hesitation followed by correction. Good looks simpler: the objective is already chosen, the trigger is visible, and one input changes at the right moment.
Objective drift feels like a series of unrelated experiments. One lap you brake later, the next lap you try more apex speed, the next lap you chase a faster car, and after the session you cannot say what you were testing. Good looks like one session objective with several laps of related evidence.
Midcorner hero driving feels fast because the car carries a bigger number at the center. The cost appears when you wait on throttle, add steering, or run out of exit. Good looks like protecting line and acceleration before increasing entry or midcorner demand.
Copying the quicker car feels efficient because someone else has already solved the corner. The risk is that you copy a result without copying the supporting skill, car capability, or objective. Good looks like extracting one observable detail, testing it under your own constraint, and debriefing whether it worked.
Data worship feels precise but can still be vague. You see that another driver was faster in a section, but you do not turn that information into a physical action. Good looks like translating the trace into a hypothesis, then into one brake, steering, throttle, or vision change.
Feeling-only debriefs sound honest but often lack a learning handle. The car felt bad, the corner felt messy, or the lap felt better may all be true, but none is enough. Good looks like notes that connect feel to action: what you tried, where you tried it, what the car did, and what evidence supports the next test.
Drill: three-session next-action ladder
Run this drill at your next HPDE, test day, or practice session. Use one corner or one repeated corner type. Do not run it on every corner at once.
Session one is the trigger session. Count six laps after warmup if your run group allows it. For those laps, do not chase speed in the target corner. Your job is to name the trigger and make it repeatable. The trigger may be a brake marker, a surface patch, a curb, a camber change, a hillcrest, or the point where you begin brake release. Success criterion: after the session, you can write the trigger and the corner phase without hesitation.
Session two is the action session. Use the same corner and same trigger. Choose one physical action. Examples include release pressure slower, turn the wheel less abruptly, wait to throttle until the wheel is unwinding, or protect exit before entry speed. Hold the action for four to six laps. The constraint must be stated before you drive. Success criterion: you can report whether the action changed the car's behavior without relying only on lap time.
Session three is the evidence session. Keep the useful version of the action and gather proof. If you have data, compare the target section against your earlier laps, especially speed loss in the first half, throttle timing, and exit speed. If you do not have data, compare notes with an instructor, a coach, or your own written debrief. If you followed a quicker car, record only the one timing detail you tested. Success criterion: you can decide to keep, adjust, or discard the action based on evidence rather than emotion.
The drill is successful when the decision loop survives pressure. You should be able to say: objective, trigger, action, constraint, evidence. If any of those pieces is missing, repeat the same level before making the test harder.
When this principle breaks down
The next-action method is not permission to ignore the larger situation. If safety changes, traffic changes, or wheel-to-wheel racecraft takes precedence, the objective changes first. A driver who stays locked onto a prewritten next action while the situation changes is not being disciplined; they are being rigid.
The method also breaks down when the corpus is too thin for the decision you want. For example, these bonded chunks do not provide a formal taxonomy for every possible if-then rule, and they do not provide named-corner examples with detailed telemetry. In those cases, you should not invent a perfect example. Use the supported mechanisms: objective, track reading, priority stack, small physical action, and debrief evidence.
Finally, the method breaks down if you use it to avoid discomfort. The point is not to choose actions so small that you never challenge yourself. The point is to choose actions small enough to execute and large enough to teach. A useful next action creates information. A timid next action only preserves comfort.
Author Review
No quiz questions are attached to this lesson.
Sources
| # | Document | Chunk | Pages | Score | Collection |
|---|---|---|---|---|---|
| 1 | Inner Speed Secrets - Ross Bentley | 99f6bb64-a187-8d5d-eea4-a145add7b3f0 | 108 | 1 | uio_books_raw_v1 |
| 2 | Inner Speed Secrets - Ross Bentley | 4e60e810-69b5-28a6-2737-11b27f9dfcb8 | 126 | 1 | uio_books_raw_v1 |
| 3 | Inner Speed Secrets - Ross Bentley | 1f89d950-4532-a2f9-3f06-33a6a39f92d6 | 24 | 1 | uio_books_raw_v1 |
| 4 | Ultimate Speed Secrets - Ross Bentley | 0237a5bd-e2d4-724e-bc2e-ba13db924f66 | 11 | 1 | uio_books_raw_v1 |
| 5 | Ultimate Speed Secrets - Ross Bentley | c179b4ca-b1cd-bbae-16ca-d15b1ecdfc12 | 11 | 1 | uio_books_raw_v1 |
| 6 | Ultimate Speed Secrets - Ross Bentley | d64f3ac3-8ef8-0bfd-1ea5-ca5dc9d308c0 | 197 | 1 | uio_books_raw_v1 |
| 7 | Ultimate Speed Secrets - Ross Bentley | 47f6de8d-9d56-5b6d-547a-f1e7bb92faaf | 152 | 1 | uio_books_raw_v1 |
| 8 | Ultimate Speed Secrets - Ross Bentley | 7f32498f-d9fd-bd02-17d6-a1aa8be21a50 | 501 | 1 | uio_books_raw_v1 |
| 9 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 4285b990-c3e7-880e-5596-99af145b469c | 300 | 1 | uio_books_raw_v1 |
| 10 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 2cc8fb73-bf8b-6575-5167-9dbef050bdfe | 75 | 1 | uio_books_raw_v1 |
| 11 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 06a160fb-3b2a-e539-9ffc-8741bf0bd18d | 91 | 1 | uio_books_raw_v1 |
| 12 | Going Faster Mastering the Art of Race Driving - Carl Lopez | f8e3be74-968a-a046-4ad6-3509a8108cfe | 91 | 1 | uio_books_raw_v1 |
| 13 | Going Faster Mastering the Art of Race Driving - Carl Lopez | 132b7a24-40cb-abb1-5287-ba5b0971b786 | 120 | 1 | uio_books_raw_v1 |