Oh, it may very well be the immediate result of separate teams delivering similar features.
The thing is, though, I know Zwift comes to us from an “agile” team. That’s a popular, powerful way of rethinking how to deliver software. One sees signs of it in various places; if memory serves, the pace bots we have now were initially released as an “MVP” – which is a code word in agile for “minimum viable product.” The idea is to release a small feature and then guide its future development based on the feedback of users in places like this forum.
My simple attempt here is to remind the redoubtable Zwift team that sometimes new shiny features are not necessarily easy to take in for users who are still dealing with the rough-edged interfaces of ones that have already been released. Yeah, I want my Personal Best bot to ride ahead of (behind!) me the next time I ride, but if the interface for just knowing what the route I choose looks like is lacking, then some foundational work got overlooked.
I would suggest things like not showing the route for events in one place, though you have route info in nice detail elsewhere are gaps in continuity that could be as high on the priority list as other, perhaps shinier, bits of development. In the agile backlog of work, I’d bump that up a bit. That’s all.