Before I begin I wanted to link to this thread, which, outside of the minor cat-related tangent, makes a lot of good points and slices into the subject of transparency I’ve been wanting to make this post about for a while and have been drafting it in my head for a few weeks, but might as well just post it. I rewrote it a bit to get rid of a bunch of stuff that’s already been covered in that thread, but it was still too long to be a reply, so here it is;
We’re only a 3-4 months away from the first batch of Community Council members being removed after their 1 year term completes, so with that I wanted to reflect on it and why, in my outside opinion, it hasn’t been as succesful of a fix to “improve communication” as it was set out/hoped to be.
I wanted to reiterate that this is based on my opinion and having closely observed Blizzard, albeit from the outside, for over 10 years now. I might very well be extremely misintepreting things and being a terrible backseat commentator, however, here goes;
The problem (as I see it); Feedback acknowledgement
Quote by Ion in this interview from February this year.
“Coming out of a lot of our discussions leading to patch 9.1.5, and everything else last summer, we all realized we needed to do a better job of communicating,” he says. “We’ve always been listening. That’s never been the issue. But if it’s not obvious that we’re listening, it’s not enough to just say, well, we’re doing it… I think we have more to do, but I think the conversations we’ve had over the course of PTR are something that I would expect to be a standard going forward.”
One of the major issues that Ion points out is that while they’re listening, there’s not a lot of communication coming out of that.
This isn’t really something I feel like being a Blizzard specific issue but an issue for many games of WoWs size. There’s no magic fix for this that I know of, but more acknowledgement of feedback, even a “we’re looking at this”, “yeah this might not be great” or “something is planned for improving this in the future” would go a long way.
While I’m glad to see a recent uptake in this when it comes to the class design/talent trees in 10.0, that’s probably the only example I can think of where that’s currently being done to this extent (and I’m not saying feedback is being equally handled/acknowledged for all classes – which, even though we’re still in Alpha, isn’t the case). For other parts of the game, including some recent controversial changes, there has been very little of this.
More blue posts or even more tweets from @WarcraftDevs are an obvious way of increasing communication. Acknowledging feedback on the forums, for example this forum, for as many topics as possible, would also help. There are many threads here without a blue post, while most have probably been read by several devs at this point. The possible reasons/explanations for there not being a reply I’ll delve into later, but having SOME sort of feedback to threads would go a long way.
One thing that can help (on the forums) is Discourse’s built-in tag system (Discourse is the forum software used for these forums), this gives devs a chance to quickly tag something with a status (similar to issue trackers on open-source projects) preferably while they come up with a longer reply/reasoning as to why.
It could look like something along the lines of this (concept, tags are made up):
This is just an idea, and while it would be something, it alone wouldn’t give context as to why a thread would be tagged like that. That problem can only be fixed with an actual reply/explanation, which I feel are currently rare due to (what I think) are bigger underlying issues;
Lack of public roadmap/willingness to talk about future things
UPDATE: This now exists.
This feels like it has become an increasingly bigger issue as the game grows older. Outside of tidbits of information dropped in interview bursts around content announcements (e.g. a new expansion or patch) there’s very little long-term stuff known. And no, this doesn’t need to be spoilers of any kind or any exact dates, but more of a generic roadmap/set of plans for the future, even if it changes often.
We’ve sometimes seen the explanation for this not currently being a thing because “plans can change”, which, especially after these few years, is absolutely fine AND expected, but I don’t think that’s a reason to not talk about it at all until it’s set in stone with the stone already about to hit us in the face.
On the other hand, for example, at the end of Shadowlands we heard that the expansion was always planned to take that long and have that many raids – so unless that wasn’t accurate, why not say something like that from the start? Going “hey y’all, this is the amount of major patches we currently have planned for 10.0, this is what we’re aiming for in regards to season lengths, etc” doesn’t hurt much, even if the plans change. There’s a balance to be found there for sure, but right now it feels like everything we hear has already been the case for a while.
Note: An example of this that came up just now during writing is the post about the mobile AH coming back, which has been in development for “quite a while”. While this is great, this is something that could’ve been announced months ago, but instead was waited with until a week before 9.2.7 releases.
Walls of red tape…
The most logical reason for devs not communicating freely, is because they’re not allowed to for whatever reason, the most likely one is that the subject is something they’re addressing in the future, or thinking about addressing in the future, where “future” is anything longer than a week away, due to the above mentioned averseness of talking about things in the longer-term.
While some red tape when it comes to future content (especially to not spoil anything story-wise) is only logical, it being applied this widely seems to only create a feeling of not being acknowledged. That same issue extends obviously extends to beyond the community council as well, to the rest of the forums and beyond.
…but the walls have holes?
Then there’s places in the red tape that seem to be transparent cellotape instead, with the community often hearing stuff through third parties, for example through a content creator “teasing” or straight up relaying information they got from someone at Blizz. The fact some content creators/fansites have that kind of direct communication/access, but in a hush-hush manner also feels like a form of miscommunication as most of those things, outside of the obvious like exploits and such, could just as easily be made public through a @WarcraftDevs tweet or blue post/thread and are subject to an additional layer of miscommunication inbetween Blizz/the community.
In closing
If Blizzard wants to get better at communicating back to the community about their feedback, they need to come up with a better way of doing that. The current iteration of the WoW Community Council feels like it is not it, and I feel like most of that has to do with the incompatibility between the unregulated “just post stuff” feedback method and, primarily, their dislike of talking about stuff or taking stances on things that are further away than next week. In the original announcement of the WoW community council, it was mentioned that there would be regular live chats, “conversations” and separate discussions with devs about specific topics. That has yet to happen. Obviously changing any of that will require effort and probably putting more resources into actually having people reply to feedback and communicating more, but I digress.
I’m sure there’s varying opinions on this subject from other council/community members and I’m curious to see if there’s anyone who thinks I’m barking up the wrong tree/drawing the wrong conclusions, and why.