Too often we throw around the word “explosive” without any context.
In some instances we are talking about time to force application, or how long it takes to generate force in different tasks. And not all “explosive” outputs exist on the same timeline.
- Max Velocity Sprinting (~0.08–0.10s)
- Acceleration (~0.14–0.15s)
- Bounding (~0.15–0.16s)
- Depth Jumps (~0.25s)
- Trap Bar Jumps (~0.45s)
- Cleans (~0.70s)
None of this is meant to say certain exercises are wrong. It’s about having a framework for understanding where and
- Acceleration (~0.14–0.15s)
- Bounding (~0.15–0.16s)
- Depth Jumps (~0.25s)
- Trap Bar Jumps (~0.45s)
- Cleans (~0.70s)
None of this is meant to say certain exercises are wrong. It’s about having a framework for understanding where and
why each method fits in your program.
There are different schools of thought on what transfers, general vs. specific, direct vs. indirect. There’s no absolute. But you should be considering this kind of information in your planning.
There are different schools of thought on what transfers, general vs. specific, direct vs. indirect. There’s no absolute. But you should be considering this kind of information in your planning.
I’m getting close to releasing my most thorough resource on speed development, complete with an e-book and a full program
Generated by Thread Navigator
Press ⌘ + S to quick-export