A roadmap does not show what they are working on. A roadmap shows what they would like to work on, but it is not set in stone. It is merely a rough idea of what they would like to work on and in which order, based on info they have at the time. As I mentioned in my post - a roadmap changes very frequently as company priorities for the product change. The contents of a roadmap are not forever set in stone, nor are the rough deadlines attached to those goals.
Say you want to do A and B in January, then C and D in February, then E,F and G in March/April. You put that on a roadmap.
Then the teams start working, but as it turns out A is a lot more complex than initially estimated, so B can't even be started in January, so it's pushed to February. It also turns out that customer feedback suggested that E is much more important than C and D, so it's re-prioritized to be done right after B, which pushes it up to February, but pushes back C, D, F and G...
Hopefully you see where I'm going with this example and understand how a roadmap can and does change easily.
I never said or implied that they shouldn't communicate anything at all. I'm just saying making a public roadmap is not the way to go for reasons I already explained in this and in my previous post.
Sure, but a roadmap is still not the way to go, when it comes to communication with your customers. Again, for reasons already explained. As an additional FYI, I'm not pulling my roadmap explanation out of my ass - while I haven't worked in the gaming industry, I do have almost ten years of my own experience in working for software development companies, both as a dev and as a lead in multiple teams and on multiple projects. I am simply trying to explain what a roadmap is in this business and why it shouldn't be shared with people who don't understand what it is and what is its purpose.