They didn't waste their time. They got promotions and padded their resumes with "designed and implemented" sections. In the process they also justified their salaries. Imagine they are well paid designers getting nice 6 figure salaries. During review they say something like "we didn't do anything, all the stuff actually worked pretty well" vs "yeah, we identified these million things wrong then went and redesigned and modernized all the stuff". Which one will they go for. Which one does the management go for? Or future employees.
That's why I believe GMail was changing its UI every 6 months. You sneezed and you got a new UI in it, even though the old one was pretty decent.
Even if the new UI is crap nobody in the chain has the incentive to raise their hand and say it, because they've all been praising it and approving it for a year.
This highlights I think why it is very important to get impartial test users, who perhaps are paid to be brutally honest and just give their opinions whatever they are.
Better yet, link bonuses to actual feedback from real users. However, the best thing to do, is to implement a policy of strict continuity. Even radical architectural changes can be implemented under such a regime. Strict Continuity means being accountable to users. Relaxation of strict continuity generally means management/devs have their own agendas, and those stupid users be damned!
Yes there is - you call it what it is, a failed Epic. Pivot and see what you can salvage before moving on.
As for the why did this change / previous design wasn't broken - you're abstracting away the interface and systems from the careers which built them. We must endure constant change to allow new generations space to fail and grow. A cynical perspective would say that careers aren't made through maintenance work.
I call BS. I know for a fact that policies of strict continuity can be maintained, because I've done it -- that you can implement radical architectural change without rocking the boat and without throwing the users/UX under the bus. The fact that we, as a field, aren't aware of this just goes to show how "half a field" programming still is.
A big part is the blur between toy and product. We disregard end-users as "sheeple" while simultaneously receiving gratification from their auth count.
I call BS. If you're moving to a new UI framework, these are usually powerful enough to emulate the old UI. Getting the new framework to feel as snappy as the old UI is a very good benchmark for performance as well as for feature parity. (They usually have more features, but there might be some corner-case overlooked.)
The question is - will it be a heavily used multi-million dollar valuation site, or will it be a rarely-used development site?
Management sometimes will decide that it isn't worth the effort, and sometimes that will be the right call. But for a user-oriented site, high value should be placed on the user.
In their place, would you? How much money would it make for you to think about your users, and how much would it cost you?
That depends on the rate and cost of user acquisition, as well as the ROI of user retention.
There's no easy back peddling from a year of development. It may be crap, but they put so much time & effort into it they can't turn back now - even if a lot of users hate it. They're also working more on becoming an Advertising platform, and this redesign allows for more flexibility there, like linkedin's auto-play videos when scrolling into view.