Yes! I totally appreciate the feedback.
You’re right, there’s always more to do.
When we release features, we make decisions on “will this add value”? The tough part about that is there is always more value to release.
For AT, we are 100% sure based on our metrics that there is a huge improvement for the vast majority of our athletes (even masters riders). We even had a 70+ year old rider who was stuck at an FTP for years raise it 20 watts and win a national championship and he credits AT.
When we look at what features to build, we think about how big of an impact it will make. For running, we know how many of our athletes do run activities based on Garmin/Strava sync. It’s about 20%. So a decent amount.
For AT, we know that 89% of our athletes are using some part of it.
For AT work, we had to decide how to prioritize features against other ones. We made the decision that AT was needed to have the foundation of the other features you’re talking about (different duration per day of week, different intensity per day of week, different rest/recovery periods, automatically changing intra-week intensity based on performance).
We could have waited to launch AT until we did all of those features. But if we did that, we’d have the same people on the forum complain that we didn’t get anything out (which was happening just before AT launched because it was such a big feature and took a while).
For the planning team, their current priority is to get AI FTP Detection out. We chose this because of the implementation lift (relatively easy, hard ML part was already done) and the number of athletes we see in our database has improper FTPs because they don’t assess. And we know that 75% of the athletes that do assess are very interested in using our AI FTP Detection.
Please PM these to me and I’ll ask more questions and/or we can do a call.