Progression–Regression vs. Agile Programming Model

For decades, strength and conditioning has leaned on a structured, linear mindset: identify an exercise, build a progression, and scale it up or down through regressions. It’s clean, organized, and easy to coach across large groups. But as our understanding of movement, learning, and individual variability evolves, so too must the way we design training.
 
The question is no longer just what’s the next step?
It’s what does this athlete need, right now?
 
The Traditional Model: Progression–Regression
 
The progression–regression framework is built on predictability. Coaches map out a sequence:

• Start with a simplified version of a movement (regression)
• Gradually increase complexity, load, or intensity (progression)
• Apply that pathway broadly across athletes

 
On paper, it works. It creates structure, ensures exposure to foundational patterns, and provides a clear roadmap for long-term development.
 
But in practice, it assumes something that rarely exists in real environments:
 
Uniformity.
 
Athletes don’t arrive as blank slates. They come with:

• Different structural considerations
• Unique movement solutions
• Varying coordination strategies
• Individual histories of training and injury

 
When everyone is pushed through the same pathway, even with regressions available, training can become less about solving problems and more about fitting into a system.
 
The Limitation: One Path, Many Athletes
 
The issue isn’t that progressions and regressions are wrong, it’s that they’re often too rigid. They tend to:

• Prescribe instead of respond
• Prioritize the exercise over the athlete
• Limit exploration & adaptability
• Reduce the athlete’s role in the learning process

 
In a dynamic system like the human body, fixed pathways can create bottlenecks. Two athletes might perform the same “progression,” but arrive there through entirely different needs, or be held back by entirely different constraints.
 
The Agile Programming Model
 
An agile approach shifts the focus from pre-planned pathways to real-time decision making.
 
Instead of asking: “What’s the next progression?”
 
We ask: “What is this athlete showing me today?”
 
Agile programming is built on four key considerations:
1. Structure
Anthropometrics, joint architecture, and physical makeup influence how an athlete organizes movement. Not every position or pattern will look the same or should.
 
2. Action Capabilities
What can the athlete currently produce, manage, and control? Force, velocity, coordination, timing, these qualities fluctuate daily and evolve over time.
 
3. Rate Limiters
What’s holding them back right now?
It could be speed, strength, perception, or even confidence.
 
4. Enhancers
What gives them an advantage?
Leveraging “strengths” is just as important as addressing the limiters.
 
From Pre-Planned to Adaptive
 
In an agile system, training is not locked into a rigid sequence. It becomes fluid and responsive, allowing for:

• Session-to-session adjustments
• Exercise selection based on readiness, not just program week
• Variability in how movements are explored & expressed
• Multiple solutions within the same training environment

 
The goal isn’t to eliminate structure, it’s to make structure adaptable.
 
Built-In Autonomy: The Missing Link
 
One of the most powerful aspects of the agile model is training autonomy. Athletes aren’t just following instructions, they’re:

• Interpreting tasks
• Making movement decisions
• Adjusting effort & strategy
• Learning through interaction, not imitation

 
This creates a different type of engagement:

• Less passive compliance
• More active problem-solving
• Greater ownership of the training process

 
And ultimately, that leads to more “sticky” learning, skills and qualities that transfer beyond the weight room.
 
The Weight Room as a Dynamic Environment
 
In an agile system, the weight room becomes less about executing perfect reps and more about navigating constraints.
 
Instead of: “Everyone moves from A > B > C”
 
It becomes: “Here’s the task. Find a solution that works.”
 
This doesn’t mean chaos. It means guided variability:

• Constraints shape behavior
• The coach steers, rather than dictates
• Athletes explore within intentional boundaries

 
Bridging the Gap
 
This isn’t about choosing one model and abandoning the other. Progressions and regressions still have value, they provide reference points. But they shouldn’t become rails that limit movement.
 
Athletic development isn’t linear. It’s adaptive, nonlinear, and deeply individual.
 
When we move beyond rigid pathways and start designing for the athlete in front of us, not the template on paper, we unlock something far more powerful: Training that evolves as the athlete does.