- RNP
- Motor Learning
- Learning in real conditions: fatigue, stress and programming
- Strength, power and speed: why they do not kill motor learning (and when they sabotage it)
SeriesLearning in real conditions: fatigue, stress and programming5 of 11
Strength, power and speed: why they do not kill motor learning (and when they sabotage it)
Strength and speed are not the enemies of motor learning. Depending on timing and intention, they either reveal it or block it. An RNP reading.
In short. The compatibility of strength, power and speed describes how motor learning work coexists with physical qualities. These qualities are not opposed to learning. Depending on timing and intention, they either reveal it or block it.
Picture the scene. A strength and conditioning coach watches you set up a slow perceptual task on the floor, almost silent, just before their power session. They frown. You can feel the question coming before they say it: "Isn't your thing going to wreck my session?" Their hand is already on the bar. For them, the choice is binary. Either you load, or you tinker with coordination. Not both.
This fear shows up everywhere. On the field, in the gym, in people's heads. Motor learning will hold back the development of strength or power. The LabO RNP Level 2 manual names this fear so it can defuse it: it is a false dilemma. And until you see why, you keep picking a side that doesn't exist.
The false dilemma: picking a side that doesn't exist
The resistance comes from a simple belief. The coach thinks they have to choose. Strength or learning. Power or coordination. As if every minute given to one were stolen from the other.
The manual is clear on this point. The idea that motor learning undermines strength only holds in two specific cases: when learning is poorly placed, or poorly understood. In other words, coexistence itself is never the problem. The problem is placement and intention.
Once you accept this, everything changes: you can work on strength and on learning. But not in the same way, not at the same time, and not with the same intention. The dilemma doesn't pit two goals against each other. It pits two uses of the same body against each other.
Learning doesn't oppose strength, it changes the intention
Let's state it plainly. Motor learning is not opposed to strength. It is not incompatible with speed. What it changes is the intention and the context in which the physical quality is called upon.
So what matters is not the type of quality you train. It's when you call on it, and how. The same load, the same sprint, the same jump can serve learning or trample it. It all depends on the state of the system and on what you are trying to produce.
You feel the difference in your hands when you handle a heavy bar and when you guide a new movement. The weight is not the enemy. The problem is being blind to what that weight does to the system.
The RNP training space, free for life
Get access to RNP training, no strings attached.
Strength: it stabilizes fast, so it freezes early
Strength has two faces. It can support learning. It can also mask it.
Here is the mechanism. A heavy load quickly stabilizes an attractor. It reduces exploration. In practice, your system finds a solution, locks it in, and stops searching. That is exactly what you want when you are consolidating. And exactly what you don't want when you are trying to let something new emerge.
Hence the manual's rule: load is useful for stabilizing, less so for emergence. If you load heavy from the start, you freeze things. You stiffen. You reinforce what already exists, compensations included. A heavy bar doesn't create new coordination. It sets the existing one in concrete.
Power and speed: revealers, not learning tools
Fast actions have a formidable property. They reveal the quality of calibration. And in the very same movement, they amplify perceptual errors.
Speed amplifies everything. If calibration is good, the fast movement brings it to light, clean and readable. If calibration is poor, the same fast movement magnifies the flaw instead of correcting it. You learn nothing under speed. You see what's already there, only bigger.
The manual draws a distinction from this that should shape all your programming. Fast actions are good tests, but poor tools for primary learning. You use them to check, not to build. To probe, not to lay foundations.
The RNP reading: calibrate before you intensify
This is where RNP becomes decisive. In explosive qualities, sensory imbalances are amplified and compensations show up quickly. The higher you push intensity, the more a fragile system falls back on its old defensive strategies.
What RNP brings, the manual puts this way.
RNP makes it possible to identify when learning is being blocked by the nervous system, and when you need to recalibrate before intensifying.
The consequence is direct. If you layer power or speed onto a poorly calibrated system, all you do is reveal and reinforce the imbalances. So order matters. Calibrate first. Intensify after. On the field, that means placing perceptual learning before the power session, so explosiveness is built on clean calibration, never on compensation. In rehab, the same logic applies: speed introduced too early reinforces avoidance, because the person you're working with compensates and you've just set their escape strategy in concrete.
The principle to remember
Hold on to the manual's formula, because it turns the initial intuition upside down: physical qualities don't prevent learning, they reveal it or block it. Everything depends on what you decide to do with them, and on the state of the system when you call on them.
In one sentence: strength, power and speed are never the enemy of motor learning. They reveal it when the system is calibrated, and sabotage it when it isn't.
Field test. Before your next intense session, set up a slow perceptual task on the same movement pattern. Watch what happens when you speed up afterwards: if the quality holds, your calibration is clean. If it collapses as soon as speed comes in, you've just found what needed recalibrating before you intensify.
Smart programming isn't about stacking qualities. It's about reading the system to know which one reveals and which one blocks. If you want to learn to apply this filter yourself, with your athletes or the people you work with, I'll guide you through it in our training programs.
To place this work within a complete programming logic, connect this article to Placement within the session: why 'early, when you're fresh' misleads you and to Placement within the cycle: why trying to do everything at once stops you from progressing, two decisions that determine what a task actually produces. Also keep in mind the distinction between learning versus performance: loading heavy improves today's performance without necessarily advancing deep motor learning. That nuance is precisely what conditions transfer of learning to the real task, and it is the sensorimotor loop, in the background, that decides whether speed reveals clean calibration or amplifies a compensation.
Scope: a functional, non-medical approach. It complements healthcare follow-up and does not replace it.