AI tool feedback
Posted: Mon Jan 04, 2021 3:26 pm
Hi,
I've been using the AI tool for about 3 months now, and in general I'm liking the tool and the sessions it produces. However I think there are some significant enhancements that could be made in order to progress from a good tool to an excellent tool.
1) Planned vs Actual Trimp - for me this is a big one. Since the Planned trimp doesn't include warm up, warm down or recoveries, the planned trimp is usually much lower than the actual. To make it closer to the planned trimp I would have to remember to continuously stop and start my garmin to include only the body of the session. That isn't very user friendly. I've mentioned this before and you claim that it doesn't matter as the AI will update to reflect, but....
2) the AI being over-sensitive to any adaption - the issue that I've seen when my actual trimp exceeds the planned trimp is that it drastically alters the future sessions, typically to shorter, less intense sessions, almost as a prevention to stop from over-training. In reality all the planned trimps should be higher anyway and therefore there will be no need to alter the future sessions.
3) No test periods - again this is a bit omission currently. You stress how important it is to keep the FTP / threshold paces etc up to date yet it seems like you do not factor in test sessions in the plan. For me this needs to sorted as soon as possible.
4) No API with zwift - Not a game changer but would definitely enhance the user experience.
It would be good to get some real feedback on this - and whether any of the above are within your development road-map. I think it has got so much potential to be an excellent tool with these adjustments!
Thanks, Nick
I've been using the AI tool for about 3 months now, and in general I'm liking the tool and the sessions it produces. However I think there are some significant enhancements that could be made in order to progress from a good tool to an excellent tool.
1) Planned vs Actual Trimp - for me this is a big one. Since the Planned trimp doesn't include warm up, warm down or recoveries, the planned trimp is usually much lower than the actual. To make it closer to the planned trimp I would have to remember to continuously stop and start my garmin to include only the body of the session. That isn't very user friendly. I've mentioned this before and you claim that it doesn't matter as the AI will update to reflect, but....
2) the AI being over-sensitive to any adaption - the issue that I've seen when my actual trimp exceeds the planned trimp is that it drastically alters the future sessions, typically to shorter, less intense sessions, almost as a prevention to stop from over-training. In reality all the planned trimps should be higher anyway and therefore there will be no need to alter the future sessions.
3) No test periods - again this is a bit omission currently. You stress how important it is to keep the FTP / threshold paces etc up to date yet it seems like you do not factor in test sessions in the plan. For me this needs to sorted as soon as possible.
4) No API with zwift - Not a game changer but would definitely enhance the user experience.
It would be good to get some real feedback on this - and whether any of the above are within your development road-map. I think it has got so much potential to be an excellent tool with these adjustments!
Thanks, Nick