Recently, there were significant pushes for leveraging general AI/LLM approaches to support or “replace” coaches and they have clearly provided interesting are aspects into training and coaches. However, they typically try to build a complete new training/coaching ecosystem (atheltica.ai, AI endurance, …) or update their existing ones to leverage AI (TrainerRoad, etc.).
To me, this is the wrong approach. The GUIs and visuals of these training platforms always fly short of i.icu in terms of data visualization, analysis, and even showing prescribed plans – and thus we always need to use two or more platforms. Moreover, people developing and implementing AI coaches should rally spend their time on that, which is (hopefully:-o) what they are good at instead of “wasting” time on developing a new UI, which is often not their strength;-) We should merge this into one, and i.icu has all provisions for that.
In the spirit of good-old Unix, we should create tools for a, one, purpose and do that very well. And allow them to interact.
Proposal
To this end, I propose to have intervals.icu (or even TrainingPeaks, etc.) as our favorite visualization point. Here we (already) aggregate our data, visualize the data, wellness, and derived analyses.
Here, in i.icu, we would/do interact with real coaches – besides minimal communication outside. We should do no different with the AI coaches.
Setup
In short, AI coaches should be selected the same way as real human coaches – through the i.icu interface.
There should be a list of AI coaches available/selectable in the same way as human coaches, e.g., through a button “AI coaches” in the top row of activities and fitness pages.
Interaction
You could then chat with these in the i.icu chat/message functionality (instead of having to go to a different, different-looking and -working, website) to understand capabilities, exchange wishes and offers, find common ground (or not), and even arrange for payments/subscription if we wish to go forward.
The AI coach should look at incoming workouts, including athlete manual info and the workout chats and provide feedback to athlete’s comments in the workout chats.
More general or broader discussions should be performed in the general chat(s) between the athlete and AI coach.
Analysis
The AI coach should offer advanced analysis, the reasoning behind, and explanations thereof in the general chat.
For advanced analysis, the AI coach should offer to and do implement new charts/tabs, custom streams, etc. in i.icu and show the analysis to the user in the standard i.icu system. (Explanations in the general chat.)
Training prescription
The AI coach should simply put prescribed workouts and plans into the athlete’s calendar – using clean, uncluttered, and descriptive workout names, clear prescriptions, and detailed written explanation of workout details, hard and soft goals of the workout, etc.
I.e., no “MIT by I-am-the-best-coaching-system-in-the-world and you-should-not-forget” but “HIIT: 4 x 6’ VO2max power” or “Z2: 3 x 1 h VT1 heart rate”…
One important point is that the AI coach can also remove it’s own planned workouts on the athlete’s request.
Training concepts
Besides the technical/communication details, the actual training concepts are, of course, to utmost importance for the coach we want. I will write a bit more about this as my time permits, but in general this is exactly where multiple AI coaches should and will differ and which is the point for distinguishing yourself, the AI coach, from others.
General comments
Dear coaches, please don’t be afraid. I think this, AI coaching, is not there (yet?) to replace you. We are far away from LLMs being truly intelligent and creative systems. Both highest performance and beginners/juniors/etc. will need real coaches to guide them. A system like the one I am trying to describer here would serve for improving the training and performance of people not using a real coach anyway – age groupers, eventually maybe also the average joe’s and jane’s
Unfortunately, I am short on time these days and would have written a lot more. But I also wanted to get this discussion, which is pondering in my mind for many weeks, out here and see it discussed and hopefully implemented (with a number of different AI coaches all using the same interface, namely i.icu:-). I will continue to refine this idea/post, also based on feedback I get – which will surely shape and sharpen my thinking.
What do you think? Please leave your comments and feedback on the AI coach you think we want ![]()