Quote Originally Posted by Sjol View Post
I'm mostly trying to communicate the indecision that happens at the product level that leads to flip-flopping and unclear communication. I find that there's this impression that SE, internally, is mentally a monolith or that every decision is coming from Yoshi P. I would be amazed if he's even involved in half the decisions in any meaningful way. That's not typically the director's job. The director is there to set direction, but not necessarily get into every little decision.
While you have experience on the inside of development teams so you can understand the inner workings, you have to also understand that the customers can only see whats on the surface.

What we as customers see is a dev team that asked for feedback, did nothing about it, then never mentioned the topic again. While there might be heated debate inside the team itself, what we see outside is them totally ignoring the issue in its entirety. This would, of course, make it look like they're ignoring feedback.

And another thing. You say they're debating on things inside the team and that's probably why they're not committing. But if you look from the perspective of the customer, when people see the team flip-flopping and not committing, most will start thinking that they lack a vision on how to proceed, and the logical conclusion for most people is to blame the director.

Now, I'm not saying they should show us all the inside workings in the company. I'm just stating that what they're doing now looks really bad and they really should commit to one thing or another to show that they have an actual vision for the game, even if some on the dev team don't agree.