Use the rslts Data Analysis documentation and an authorized athlete dashboard to identify 2–3 defensible training insights and communicate them in a way the athlete can act on.
rslts organizes season training, workout summaries, development trends, race history, workload, and athlete-specific field estimates. Development measures compare an athlete with their own earlier data. They are not laboratory measurements or universal rankings.
Useful questions include:
Is training becoming more consistent?
Is aerobic cost improving under comparable conditions?
Is durability changing across longer or steadier efforts?
Does recent training match the purpose of the current phase?
Do race results support—or contradict—the training trend?
An insight is not simply “mileage increased” or “fitness went up.” Use this structure:
Observation → Context → Meaning → Action → Recheck
Example: “Your active days became more consistent across the last four weeks. You also reported normal recovery. That supports keeping the current schedule for two more weeks rather than adding another hard day. We will reassess after the next race.”
Before sharing an insight, check missing activities, terrain, weather, sensor coverage, illness, other sports, race tactics, and athlete-reported effort. If a measure is sparse or extrapolated, say so.
0–15 minutes — Athlete question. Ask the athlete what they want to understand. Record the goal and one decision the analysis may inform.
15–35 minutes — Coverage check. Review the relevant time window. Note missing periods, unusual weeks, recent races, and whether the available data can answer the question.
35–60 minutes — Candidate insights. Write five possible observations. For each, list supporting evidence, missing context, and an alternative explanation.
60–80 minutes — Select 2–3 insights. Choose the observations that are both defensible and useful. Convert each into one keep/change/watch recommendation.
80–105 minutes — Athlete conversation. Share the insights with the athlete. Ask what matches their experience, what does not, and what action feels realistic. Record the agreed next step and reassessment point.
What was the athlete’s question?
Which evidence directly supports each insight?
What does the dashboard not know?
How did the athlete respond?
What will you observe next?
Prompt 1: “Using this de-identified rslts summary, produce three candidate insights in Observation → Context → Meaning → Action → Recheck form. Label every inference and list the missing athlete questions. Do not rank the athlete against other athletes.”
Prompt 2: “Challenge my three coaching insights. For each, give the strongest alternative explanation and name the additional evidence needed to distinguish between explanations.”
Prompt 3: “Role-play the athlete. Ask me why this recommendation matters, what uncertainty remains, and what would cause us to change the plan. Score my answers for clarity, honesty, and athlete autonomy.”
Submit a de-identified coverage note, the 2–3 insight cards, the athlete’s response, and the next observation date. Do not paste identifiable athlete records into an external AI tool.
rslts dashboard: use development measures as athlete-specific field estimates, then pair 2–3 observations with context, action, and a reassessment date.