The biggest issue I see with TrainerRoad compared to some its competitors right now, and the point of WLv2, is that it’s hyper-focused on the progression of individual workouts and doesn’t have any concept of training load. In the case of the LV plans with three workouts a week, for example, you’ve basically got three lanes on the board and Adaptive Training is trying to figure out the most efficient way to keep you moving each individual piece down its lane. It doesn’t know or care that you had 4-5 hour gravel races each of the past few weekends, it only cares about trying to make sure this Tuesday’s threshold workout is achievable, but incrementally more difficult than last Tuesday’s. You can have a lot of success with LV plans and adding Zone 2 rides, but I think it’s very easy to lose sight of your overall training load when you’re outdoors having fun while the same SSLV workouts are always waiting there for you.
The problem that I personally ran into last year after adhering very closely to an SSMV plan in the offseason was that I felt like I’d essentially become a data-producing machine rather than a human on a bike. I felt (not infrequently) like I had to ride indoors even when I could ride outside because maintaining the progression was the most important thing for my early season A race. My A race came in the spring, I hit a bunch of power PRs, then burned out and rode sporadically for about a month and a half before I started looking forward to my late August event.
This year, I focused more on volume, consistency, and getting outside whenever I could. Even after getting sick multiple times and losing several weeks between New Year’s and mid-April, I smashed those PRs. Even better, I finished my A race more excited to keep riding than I have been in years.
Based on my own experience and speaking as a middle-aged, (now slightly upper!) mid-pack Masters rider, I’d argue that an app’s ability to help manage volume and consistency is vastly more important than its ability to ensure progression along individual workstreams without being able to transparently maintain overall workload.
Nailing two threshold workouts a week is great, but what if it’s not sustainable combined with the Saturday group rides plus races every few weeks? A training app should be able to look at your weekend, see that planned long endurance ride that turned into a 350 TSS smashfest because it was a beautiful day and you felt great, and on Tuesday say “You know what? You don’t need a threshold workout today, here’s some nice, relaxing zone 2.” There are a number apps out now that can do that already: Athletica (which I’ve been tinkering with and finding very good), Join, Xert, Spoked, and I’m sure others I can’t think of.
From a software development perspective, I think what people are missing is that WLv2 is actually TR 2.0. It’s a fundamental redesign of the entire framework. This isn’t just adding a feature, it’s adding a whole host of interdependent features hampered by god-only-knows how much legacy code and tech debt. All of which is 100% normal and common, it just gets confusing and frustrating when we’ve been told for, what 18 months? that it’s just around the corner.