Originally Posted by
FpicEail
The problem is that Blizzard seems to historically have a "don't knock it 'till you try it" attitude, which sounds positive until you realise that they take ideas that are CLEARLY bad on paper and figure that you don't know for sure that it will be bad until you actually spend a great deal trying to implement it. The stuff you mentioned, including Survival in Legion, are great examples of it. The legendary system in Legion is another great example, where pretty much everything people thought could have gone wrong with it has now gone wrong despite Blizzard's insistence to the contrary every single time.
Another good example is limited attempts in WotLK: remember how they kept trying out new limited attempt systems every tier and people hated them every time? Blizzard for some reason was obsessed with making this idea work despite absolutely EVERYONE involved despising the idea as soon as they heard it, thinking that people need to see it implemented before they could judge it properly. And what do you know, people hated it in practice, too. Sometimes you CAN knock it before you try it.
Or think back to the daily quests in MoP: they said that they felt they needed to test two parallel quest models where one had fewer quests with each giving higher rewards (August Celestials, Shado-Pan, Tillers, Order of the Cloud Serpent, Anglers) while the other gave a multitude of quests each having smaller rewards (Golden Lotus, Klaxxi); they had both of these at the same time to figure out which people liked more. So...you could either do 4 quests to get a certain reward, or you can do 12 quests and get roughly the same reward. More effort for the same reward. Why did this even need to be tested? Once again, "don't knock it 'till you try it".
This attitude stems from a larger issue where there just isn't enough internal criticism at Blizzard. There is just no real consequence for developer failure: it takes a massive, Tseric-level fuck-up to get you fired. I'm always reminded of how Square Enix handled the FF14 situation: when that game released it was an unmitigated disaster; a clusterfuck of incompetent game design so severe that it significantly harmed the company's financial position. When SE admitted fault (something that you RARELY see from Blizzard these days) they did not fuck around with rectifying the situation. Heads rolled over that: the director was sacked, and if I'm not mistaken a number of lead developers were let go as well. They got new talent and made damn sure they weren't going to fuck it up again and then they rebooted FF14 as an actual successful MMO and the only real competitor to WoW (even then, it's distant).
You just never see that at Blizzard. Remember how badly WoD damaged the game? A heap of the issues with those expansions were totally avoidable as well, yet absolutely no one at Blizzard saw any real consequence for that. Hell, at least one of the great minds behind several of that expansion's failings got PROMOTED: Hazzikostas, the architect of the whole no-flying fiasco, is now lead developer. When a company has no internal criticism, it's relying entirely on external criticism to point out decisions that will lead to inevitable failure. And it's a whole lot easier to ignore external criticism, which is Blizzard's MO at this point.