Read moreI will try to address both challenges in my way of thinking, of course I don't know how internally the company works so I will not have assumptions and just to think the most simple way about it:
I think that the first problem would be a little more troublesome to address, but at same time I think that you forwarding to the team is already the right direction and maybe the solution would be a compromise from the whole team, and the company, of a couple hours per week to read said feedback forwarded by you and give their thoughts/opinions on the matter back, so someone (I don't know if could also be you) could make a compilation and come back with the feedback that the team provided.
Thus It would also address the second point, like Lyefyre already talked, knowing what feedback was take, be it in "We will look towards it and try to implement in the future" or "This is not be possible because of X or Y" without being something that is defined only internally and the c...
Hi! Sorry about the delay, got busier. I like the first idea, but as I said in some other post, it's not my time alone to compromise so I can't say if it'll happen. Feedback ends up having to go through many teams to see if it's doable.
As for devlogs, I really like the idea, but I know in practice some of them would be very boring, like "we're still developing the 3rd Mythical, we're still working on a secret feature that we want to keep a secret from you until release". The old roadmaps still work in terms of features, and with Seasons there's a lot more info on dates, themes, and all that. I'm also, personally, worried about spoiling too much about upcoming features before the right time. I've seen it happen and didn't like the result.
But the one, true, actual issue I see with this is that I fear the community won't feel heard unless their feedback has been implemented, not acknowledged or discarded.