Week 13 — Training Design I: From Trends to Target Performance

Outcome

Use longitudinal evidence, athlete context, and uncertainty to create a reasonable target-performance analysis, sample week, and race or competition plan.

Required preparation

Bring rslts development or workout history and/or an APOPT Watch Analysis export for at least one runner. Bring equivalent result, timing, workload, or movement evidence for a non-runner when available.

Part 1 — 5–7 minute instructional script

A training plan is not a collection of impressive workouts. It is an organized sequence of stress, learning, and recovery directed toward an athlete’s goal. Good design rests on familiar principles: consistency, progressive overload, specificity, individualization, recovery, and variation. Data does not replace those principles. It helps coaches apply them to the person in front of them.

Consistency creates enough repeated exposure for adaptation and skill. Progressive overload increases challenge gradually enough that the athlete can absorb it. Specificity connects training to the demands of the event without making every day event-like. Individualization accounts for current fitness, development, history, response, and life constraints. Recovery allows adaptation and protects the quality of priority work. Variation changes emphasis across days and phases so stress is useful rather than monotonous.

Begin with current fitness, not ambition. A target can be motivating, but training prescribed from the desired identity rather than the current athlete often becomes too fast or too much. Review recent performances, stable training, comparable efforts, race history, and athlete experience. Ask what is supported, what is estimated, and what is missing.

rslts Development Metrics may show aerobic pace, cardiac cost, durability, training base, critical speed, and race validation. These are athlete-specific field estimates. Their greatest value is comparison with the athlete’s own earlier information under supported conditions. Check confidence, run selection, sample coverage, uncertainty intervals, and extrapolation markers. A trend is not a laboratory measurement and correlation is not proof of cause.

APOPT Watch Analysis can assemble weekly mileage, training load, efficiency, heart-rate patterns, pace curves, predictions, training targets, and a target-race timeline from activity files. Predicted times should be presented as ranges or planning anchors with assumptions. A prediction based on sparse, misclassified, or non-representative efforts deserves less confidence. The athlete’s current health, event conditions, course, tactics, and training response remain important.

For a runner, build the target analysis in five steps. First, state the athlete’s goal event and date. Second, summarize current evidence and data quality. Third, identify the implied current performance range and the main limiter or uncertainty. Fourth, choose the next training emphasis and a sample week. Fifth, write a race plan with controllable execution cues and adjustment points.

Every day in the sample week needs a purpose. Label aerobic development, quality, long duration, recovery, strength, skill, or competition. Then audit where stress accumulates. A hard interval day followed by heavy strength, poor sleep, and another organized sport may create more total stress than the running plan shows. Increase load by changing one major variable at a time where possible, and protect easy days from becoming accidental moderate days.

Prescribe intensity from current evidence and purpose. Athletes at different levels may complete the same type of session with different volume, pace, recovery, or technical complexity. Equal effort does not require identical numbers. The plan should show which feature is essential and which can be adjusted without losing the intended adaptation.

Performance plans for other sports use the same logic. A swimmer may use repeat splits, stroke count, and turn consistency. A basketball player may use decision quality, movement demands, and shot patterns. A thrower may use competition results, implement speed where available, and video consistency. State the benchmark, current evidence, priority adaptation or skill, practice design, and competition cues.

The plan needs a reassessment rule. What observation means continue? What response means hold or reduce? What result challenges the target? Avoid automatic changes from one bad session. Prefer multi-week direction, relevant athlete feedback, and repeated observations. When the evidence is inconclusive, the correct next step may be a conservative plan and better information.

Communicate prediction responsibly. Say, “This evidence supports a current range, assuming normal conditions and continued training. The next block will test whether pace stability and durability improve.” Do not say, “The app proves you will run this time.” The first statement creates a shared experiment. The second creates false certainty and can damage trust.

Your challenge is to produce a plan where every element can answer “why?” Why this target, why this session, why this load, why this cue, and why this reassessment date? If the answer is only tradition or dashboard suggestion, the plan needs more thought.

Three takeaways

• Apply foundational training principles to current fitness and the athlete’s total context.

• Read field estimates, predictions, and trends with their confidence and assumptions.

• Treat the plan as a testable hypothesis with explicit continue, adjust, and reassess rules.

Part 2 — 30–45 minute application lab

1. Athlete and event — 4 minutes: State the goal, date, current training, and life constraints.

2. Evidence review — 10 minutes: Use rslts and/or APOPT to summarize relevant trends, quality, confidence, and missing context.

3. Target range — 6 minutes: Create a current estimate and goal range without guaranteeing an outcome.

4. Sample week — 10 minutes: Label each day’s purpose and audit accumulated stress.

5. Race/competition plan — 7 minutes: Write execution cues, decision points, and a fallback.

6. Reassessment — 5 minutes: Define what will confirm, challenge, or change the plan.

Data-driven participation assignment

Prepare one runner target-performance analysis with a sample week and race plan. If the assigned group includes a non-runner, prepare an equivalent benchmark and competition plan. If all athletes are runners, compare two runners at different developmental levels.

Literature + Generative-AI discussion preparation

Search periodization, progressive overload, load monitoring, critical speed, durability, or performance-prediction validity. Use and verify the standard AI summary. Bring a sample week and identify where too much stress may accumulate.

Multi-sport adaptation

Replace race time with the sport’s meaningful performance benchmark. Preserve the five steps: goal, current evidence, priority, training or practice plan, and competition execution with reassessment.

Protect athlete data and interpret cautiously

De-identify exported summaries before external AI. Present predicted performance as a range with assumptions. Do not use training data to make medical decisions or public comparisons between athletes.

Resources and next week

• rslts Development Metrics: https://rslts.run/docs/performance/data-analysis/development-metrics/

• APOPT Watch Analysis: https://apopt.com/watch/

• Next: Week 14 — Training Design II: The IRSRI Model in Practice