How to Stop Coaching Against Your Player’s Biology

In Part 1, we established the hidden divide in player development: how a player’s nervous system naturally organizes toward action. We introduced the Vertical Player (action-first) and the Horizontal Player (context-first).

Today, we look at the coaching paradox: why the exact same instruction, delivered by the same coach, works perfectly for one athlete and completely ruins the natural rhythm of another.

THE HOOK: THE UNIVERSAL CUE

Let’s look at a standard coaching cue used in every cage and on every mound across baseball:

“Stay back.”

The Vertical Translation

The Vertical player operates on a direct line. They need the shortest route to execution. When they hear this cue, their internal response isn’t a question, it’s an immediate action plan:

“Got it. Let’s do it.”

They don’t need the theory behind it. They identify the physical command—hold the weight back—and immediately initiate the physical adjustment to do exactly that. They jump straight to the solution.

The Horizontal Translation

The Horizontal player operates relationally. They need to establish conditions before moving. When they hear the exact same cue, their internal translation is:

“Why? What needs to be established to allow me to stay back?”

They cannot blindly force their body to freeze or hold a static position. Their brain needs to know how their posture, their back-hip connection, and their timing connect to make that outcome naturally possible. If they just “stay back” without context, they feel disconnected and stuck.

THE BILINGUAL EXAMPLES

If you want to reach both players, you cannot rely on a universal script. You need to adjust your vocabulary.

Hitting & Pitching:

• Vertical Focus: See → decide → attack. (Keep it direct and outcome-driven).
• Horizontal Focus: Read → organize → attack. (Establish the positional connection first).

COMMUNICATION & FRICTION

This is where player development stalls. Friction happens when we force a player to operate against their natural organization.

• When does a Vertical player block? When action is delayed by theory. If you give them a ten-minute bio-mechanical lecture, they shut down. What you think is “valuable context,” they experience as an unnecessary delay.
• When does a Horizontal player block? When action is demanded without context. If you just demand immediate execution without explaining the relational setup, they freeze. What you think is “keeping it simple,” they experience as a lack of necessary preparation.

THE FRONT-OFFICE TAKEAWAY

Imagine an elite prospect moving through your organization. The hitting coordinator uses Horizontal, contextual language. The S&C coach uses Vertical, action-first commands. The medical staff speaks in isolated anatomical terms.

Unified player development is not just about ensuring your data is accurate. It is about delivering that data in a language the athlete’s biology can actually organize. If your departments speak different motor languages, you are building friction into your own system.

THE REAL QUESTION

We spend millions of dollars and countless hours deciding what we should coach an athlete to do.

Perhaps it is time we start asking how that athlete naturally organizes information