Since there has been a lot of talk about developer communication style, and a sort of tongue-in-cheek poll, I thought I would do a poll about how people prefer to receive developer communication.
Let me give some details to define what these options mean.
Share concrete information when it’s done
In this style, the developers would be effectively radio silent on what they are working on until it is in final polish stages. They would then make a big update announcement with all details and release date all at once.
This could mean there would be weeks or months between completion of the update and it’s release, since they will have to have nearly 100% certainty that they would hit the release data.
If they need to do testing, it would be done similar to the current method, with testing happening as needed with patch notes, and then once major testing is done, the developers would go radio silent about the update up until they are done and can announce a release date.
This is the “We’re all adults here” option. Many work-in-progress items are shown/teased, with explanations of where they are in the dev process. Estimated release dates are announced, and when issues arise that cause delays, the reason and expected delay time are explained very briefly.
This method will mean that the community will see a lot of features that never come, or take a very long time to come, but should expect explanations of why things were dropped or delayed. It is important to understand that the most common reason for delay is likely to be “We determined that feature B is higher priority than feature A”.
This could be implemented with weekly, bi-weekly, or monthly dev streams or dev blog posts.
Share concrete information when it’s done, but teasers are good too
Same as “Share concrete information when it’s done”, but twitter teases of prototypes & concept art (with context of how far along the process is) are a good thing that makes you happy.
Keep it the same
The devs keep doing what they are doing now, which is somewhere between “open communication” and “Share concrete information when it’s done”
- Share concrete information when it’s done
- Open communication
- Share concrete information when it’s done, but teasers are good too
- Keep it the same