Making the Complex Understandable Without Losing Meaning

“Simplicity is the ultimate sophistication.“

– Leonardo da Vinci

Last week, we explored a foundational idea: the body can’t access what it doesn’t know.

The nervous system won’t use what it doesn’t recognize as available, safe, or trustworthy. That principle sits at the heart of effective movement reconditioning, motor learning, and long-term performance.

This week, I want to build on that idea by talking about how we explain complex movement problems—without stripping them of their depth or value. Because understanding matters. And for many people, practitioners and clients alike, complexity can feel overwhelming, confusing, or even soul-crushing if it isn’t communicated well.

Vulgarization is not dumbing things down. Done well, it’s the art of making complexity digestible without losing its essence. The best teachers don’t remove depth—they translate it. Two of the most powerful translation tools we have are metaphor and analogy. They’re often mistaken for one another, but they serve slightly different purposes.

A metaphor directly equates two unlike things to highlight a shared quality. When we say a complex problem is a Rubik’s Cube, we’re not explaining every mechanism—we’re conveying interdependence, sequencing, and the reality that pulling on one piece affects the whole. An analogy goes a step further. It compares two different situations to clarify structure or process.

Using a story of Climbing Mount Everest as an analogy for the daily grind of work isn’t really about the summit—it’s about losing sight of meaning while becoming consumed by effort, discomfort, and logistics.

Someone who is skilled at vulgarization knows when to use each.

One of the most useful metaphors we use in Neuro Reconditioning is the distinction between Hardware and Software issues. It isn’t perfect—no metaphor is—but it gives us a shared language that helps clarify what kind of movement problem we’re actually dealing with.

When we talk about Hardware issues, we’re referring to true structural limitations. These are constraints that exist because of things like birth anomalies, surgery, joint replacement, scars, adhesions, bone calluses, or labral tears. There is usually a clear historical story attached—a mechanism, a moment, an event. These become real constraints to movement availability, and the system must organize around them in order to produce a desired movement response. From an ecological dynamics perspective, these are individual constraints that shape what movement solutions are even possible.

Software issues are different. They’re not about missing parts. They’re about how movement is organized, coordinated, and expressed. The hardware may be intact, but the system isn’t using it efficiently or effectively. These are neurologically driven problems—motor control, timing, coordination, and strategy selection—that can lead to overuse or misuse of other tissues as compensation.

These issues are often addressed by improving higher-order organizing systems. We sometimes refer to these as input satellites (another metaphor)—the visual, vestibular, and proprioceptive systems that inform the brain about where the body is in space. On the output side, this includes force production, soft-tissue availability, and the coordination of movement across regions. Software problems are rarely solved by simply adding more reps or more load. They’re solved by improving clarity of information and organization of movement.

Between these two categories sits a critically important outlier: the software-driven hardware issue.

This is where many people get stuck.

In these cases, movement restriction exists without a clear mechanical mechanism. What’s happening instead is often a form of sensory mismatch, poor communication between input systems, or an interpretation of information as threatening. When threat is present, the nervous system creates its own constraints. Range of motion disappears. Tissue tone increases. Force expression shuts down.

Not because the hardware is broken—but because the software has decided it isn’t safe.

This is why unexplained stiffness, tension, or “tightness” so often has a neurological origin. And it brings us right back to last week’s idea. The body still won’t use what it doesn’t recognize as available.

But recognition isn’t just awareness.

For software issues—and especially software-driven hardware issues—change requires three things: awareness, organizational capability, and real capacity. The nervous system needs to feel the option, organize around it, and prove to itself that it’s safe under load and variability.

Only then does self-organization become meaningful. Only then do new movement strategies show up when they matter.

Using Hardware and Software as metaphors gives us a way to distinguish true constraints from protective choices, avoid chasing symptoms, respect the intelligence of the nervous system, and design better reconditioning strategies. It helps practitioners think more clearly. It helps clients understand their bodies without fear. And it keeps us honest about what kind of problem we’re actually solving.

That’s the real value of good vulgarization—not simplification for its own sake, but clarity in service of better outcomes.

The Body Can’t Access What It Doesn’t Know

“We must perceive in order to move, but we must also move in order to perceive.“

– James J. Gibson

One of the most important things to understand when you’re trying to improve someone’s movement—whether the goal is pain relief or better performance—is this:

The body can’t access what it doesn’t know.

Just like in life, you can’t change what you don’t acknowledge.
And the nervous system can’t use what it doesn’t recognize as available.

We often talk about movement in terms of strength, mobility, or technique. But underneath all of that sits something more fundamental: recognition. If the brain doesn’t recognize an option as existing—let alone safe—it will never choose it.

Self-Organization Isn’t Magic — It’s Conditional

In the world of motor learning, we often lean on ideas like self-organization, ecological dynamics, and constraints-based learning. And rightly so.

Movement solutions don’t need to be prescribed.
They emerge.

Given the right task, environment, and individual constraints, the system will self-organize into something efficient and functional.

But here’s the part that often gets glossed over:

Self-organization can only occur within the options the nervous system believes it has.

The system doesn’t explore what it doesn’t perceive.
It doesn’t organize around what it doesn’t recognize.

If prior injury, pain, fear, threat, or background noise has narrowed the menu of available strategies, the body won’t magically rediscover them just because we “let it move.”

The Nervous System Chooses Safety, Not Efficiency

There’s a common phrase that gets thrown around: “The body takes the path of least resistance.”

I don’t think that’s true.

The body takes the path of greatest safety.

Efficiency only matters once safety is established.

If a joint, range, or movement strategy has been associated with pain, instability, or uncertainty—even years ago—the nervous system may quietly remove it from consideration. Not because it’s weak. Not because it’s immobile. But because it doesn’t feel trustworthy.

So when we ask the system to self-organize, it will…
Just not in the way we hoped.

It will self-organize around protection.

Constraints Don’t Create Options — They Reveal Them

This is where a constraints-led approach becomes incredibly powerful—but only when used intentionally.

Constraints shape behavior by highlighting affordances: opportunities for action relative to the individual.

But affordances are only perceived if the system can detect them.

If a movement option has been neurologically “blurred out,” no amount of clever constraint manipulation will bring it back online. The system simply won’t see it as an option.

So before we ask for variability, adaptability, and emergent solutions, we have to ask a more basic question:

Does the nervous system even know this option exists?

That’s why every effective reconditioning process starts the same way:

By teaching the body what it’s missing.

We call this the parts phase.

This isn’t about isolating muscles or joints for the sake of isolation.
It’s about restoring recognition.

If someone has lived with back pain, for example, their spine may not be “stiff” in the traditional sense—it may simply be absent from the system’s map. Pain, disuse, or misuse can quietly erase certain movements from the brain’s available options. Or it may have self-costrained this option in order to protect.

So first, we create a good postural setup of the spine and trunk.
Then we teach the system how to actually use it equitably and effectively.

That’s capability.

Capability comes before capacity.

Capability is about access.

It’s about:

• Interoception: Can you feel where you are?
• Exteroception: Can external feedback help clarify position and movement?

Touch, props, slow exposure, intentional positioning—all of these help the nervous system re-establish a clear signal.

But capability alone isn’t enough.

Because the nervous system doesn’t trust novelty.
It trusts repetition without consequence.

That’s where capacity comes in.

From Access to Ownership

Capacity is what turns an option into a strategy.

It’s not just “can you get there?”
It’s “can you stay there, load it, breathe through it, and return from it?”

This is the difference between:

• Accessing a movement once

and

• Owning it under varying constraints

Only when a movement has demonstrated itself to be safe, repeatable, and resilient will the nervous system begin to use it automatically.

And that’s the moment when true self-organization becomes possible.

Self-Organization Requires Recognition

Ecological dynamics teaches us that movement emerges from the interaction of the individual, the task, and the environment.

What I’d add is this:

Emergence is limited by recognition.

The nervous system cannot self-organize around options it doesn’t believe it has.
It cannot adapt with tools it doesn’t trust.
And it will not choose strategies that feel unsafe—no matter how biomechanically sound they look on paper.

So our job, as practitioners, isn’t to force new patterns.

It’s to expand the menu.

Teach the system what’s available.
Prove to it that those options are safe.
And then—step back and let it organize itself.

That’s not anti-technique.
That’s not anti-structure.

That’s honoring the intelligence of the system.

Well orchestrated movement is a beautiful thing.