Needs analysis, program design, and context-specific adaptation
Needs analysis, program design, and context-specific adaptation
This domain tests a systematic path from sport demands to an individualized, periodized plan that survives real-world constraints.
Core rules
- Needs analysis has three parts: sport/task demands, athlete profile, and gap analysis. Use competition analysis, testing, and coach input.
- Program design applies overload, specificity, individualization, and recovery; periodize across the competition calendar.
- Context adaptation considers travel, facility access, squad size, sport culture, and rule changes.
- Testing should answer a decision, not fill a spreadsheet; choose valid field tests and retest at consistent times.
Worked example
A soccer team has a congested preseason with limited field access. Needs analysis shows high intermittent running and repeated-sprint demands. Rather than copying a generic strength block, you prioritize high-speed running exposure on available days, use small-sided games for conditioning, and schedule lower-body strength away from the highest load days. You monitor with session RPE and GPS high-speed distance, adjusting volume if soreness or load spikes. This is context-specific adaptation: the principles remain, the delivery changes.
Traps
- Copying another team's program without a gap analysis.
- Over-testing and leaving no time to train.
- Ignoring the competition schedule when prescribing load.