- RNP
- Motor Learning
- Designing practice situations
- Motor problem versus execution error: what you're correcting may not exist
SeriesDesigning practice situations5 of 7
Motor problem versus execution error: what you're correcting may not exist
Tell a recurring motor problem apart from a one-off execution error, so you stop overcorrecting and know what actually calls for intervention.
In short. A motor problem is the system's recurring inability to produce a functional solution, even when conditions are favorable. An execution error is a one-off gap between a correct intention and how it plays out. One persists and resists. The other fluctuates and fades on its own.
An athlete botches a start. You see the foot go off line, the shoulder drop, the posture collapse. Your hand is already up, the cue is already on your lips. Then the next rep comes, clean, without you saying a word. And the one after that too. You just corrected something that didn't exist.
The most expensive mix-up in coaching
In most practices, you see an ineffective action, a form judged incorrect, an awkward-looking coordination, and you rule on it instantly: there's a motor problem. In reality, what you're looking at is usually just an execution error.
That mix-up is costly. Treat a one-off deviation as a structural flaw and you overcorrect. You overload. You create frustration where the system was about to regulate itself. You can feel the tension build during the session: the more you step in, the more the learner tightens up, the more fluidity disappears. And you end up wasting time on something that needed nothing.
The hidden cost lies elsewhere. By correcting every deviation as a flaw to eliminate, you stop the system from learning to self-correct. You take away the very function you were trying to develop.
Telling one from the other
An execution error is transient. It fluctuates from one rep to the next, shows up then fades, and often resolves without any intervention at all. A motor problem, on the other hand, persists. It resists correction. It shows up across different contexts, with a regularity that has nothing to do with chance.
The mental test comes down to one question. Does what you're seeing come back despite favorable conditions, or does it dissolve on the very next rep? Listen to the rhythm of the reps, watch whether the deviation repeats when you change the context. A flaw that repeats across three distinct situations is telling you about structure. A flaw that vanishes on the second rep is telling you about a moment.
This reading isn't a matter of fussy vocabulary. Without it, you intervene on everything, and you turn every normal variation in movement into a pathology to treat.
The RNP training space, free for life
Get access to RNP training, no strings attached.
Correcting isn't teaching
Correcting an execution error can improve immediate performance, reassure the learner, and create the pleasant illusion of progress. But it guarantees no learning whatsoever.
Learning begins when the system has to change the way it perceives and acts, not when it adjusts an isolated execution. You can spend entire sessions polishing, cleaning up, smoothing out one-off deviations, and create nothing at all. Because you never put the system in a position where it had to transform something fundamental in its perception-action coupling.
That's where the difference lies between a learning intention and a mere surface-level cue. Polishing a form reassures your eye. Changing the way the system reads the situation is something else entirely.
The RNP reading as a filter
In RNP, an execution error can arise under fatigue, under stress, or during a momentary sensory overload. The movement degrades, not because the system doesn't know how, but because it's temporarily overwhelmed.
Intervening then as if it were a motor problem adds needless load, sometimes reinforces a compensation, and pulls attention away from the real dominant lever. This is exactly where the RNP reading becomes critical. It lets you know whether what you're observing is structural or contextual, whether it warrants intervention or whether the sensorimotor loop will regulate itself once the load drops.
The same caution applies when the problem is real: you still need to separate what comes down to capacity from what comes down to learning. A system can have the biomechanical capacity yet lack the perceptual capacity. You then see a body that could, and you wonder why it doesn't. The problem isn't motivation, nor willpower. It's in the sensory loop.
Three settings, one rule
A child falls once on an obstacle course. The adult reads it as a lack of coordination, wants to help, steps in. Yet the child nails the next attempts without any assistance. They didn't need help. They needed to try again. The hand offered too early whispered that they couldn't manage on their own.
A client shows a loss of control on an isolated movement, while overall function remains intact in ecological tasks. Correcting that execution would miss the point, because the problem you see on the table isn't the problem the client lives with throughout their day.
"Not everything you see is a problem. Not everything that fails needs correcting." Adapted from the LabO RNP manual, level 2.
In one sentence: a motor problem persists despite favorable conditions; an execution error fades on its own, and mistaking it for a structural flaw pushes you to overcorrect what was about to sort itself out.
Field test: before your next correction, wait three reps. If the deviation comes back identically across different contexts, you may be dealing with a motor problem. If it's already gone by the second rep, put your cue away: you were looking at an execution error.
Reading the system before acting means refusing to pay the price of overcorrection. When I'm torn between the two, I let the system answer before I speak.
Scope: a functional, non-medical approach. It complements healthcare follow-up; it does not replace it.