Developing speed is simple, but it’s not easy.
One of the biggest mistakes I see? Poor planning. Speed work is often tossed into a program with zero thought to structure.
No progression. No consideration for residual effects. The result? You sprint, but you don’t actually
get faster.
Programming for speed means answering real questions
How many times a week should you sprint
What’s the right volume for the sport or event?
Where do resisted and overspeed runs fit?
How does weight training fit? Plyometrics? Aerobic work?
Programming for speed means answering real questions
How many times a week should you sprint
What’s the right volume for the sport or event?
Where do resisted and overspeed runs fit?
How does weight training fit? Plyometrics? Aerobic work?
This is why I wrote Speed Kills. It’s the most thorough resource I’ve made, built from reading the greats, learning from mentors, and working with athletes daily since 2008.
Inside, I cover how to
Organize sprint work for the highest return.
Inside, I cover how to
Organize sprint work for the highest return.
Integrate strength, plyos, and conditioning without interfering with speed.
Avoid the recovery mistakes that keep athletes stuck.
It finishes with a complete 8-week program so you can see the plan in action.
fredduncantraining.com/product/speed-…
Avoid the recovery mistakes that keep athletes stuck.
It finishes with a complete 8-week program so you can see the plan in action.
fredduncantraining.com/product/speed-…
Generated by Thread Navigator
Press ⌘ + S to quick-export