Skip to content
All posts

How To Approach Transparency The Right Way When Communicating With Your Community

In the games industry, players crave transparency. They want to know the why behind delays, the how of design choices, and the who of the team.

As a Community Management & Content Strategist who has worked on plenty of games, especially GaSS games, I've seen transparency build incredible loyalty. However, I've also seen uncontrolled "raw" transparency and rogue developers going it alone backfire, damaging trust and professional reputation.

The key is realising that transparency isn't about telling everything; it's about building a Strategic Transparency Framework. This provides the leadership insight needed to draw the line effectively:

1. Be Transparent on impact, Not on Internal Drama

  • Share: The impact of a delay ("We need two more weeks to ensure this feature meets our quality bar for you.")

  • Don't Share: Internal team disagreements, blame, or personnel changes. This is unprofessional and causes players to focus on internal politics instead of the game.

2. Prioritise WHY Over HOW (unless asked)

  • Share: The reason a highly-requested feature was deprioritised (e.g., "It clashed with our core network architecture," or "We prioritised fixing major stability issues first.")

  • Don't Share: Hour-by-hour details of the technical struggle, which can overwhelm and confuse non-technical audiences. However, also avoid falling into a defensive mode with justifications and emotions. Be ready to explain the how if pressed, but lead with the strategic why.

3. Maintain a 'Two-WayFilter'

  • Filter Out (Inbound): Do not let toxicity or abusive comments dictate the tone of your professional response. Address the substance of the feedback, not the delivery.

  • Filter In (Outbound): Before posting, ask: "Does this information serve the player base, or does it serve to make us feel better about a mistake?" If it's the latter, rework it. Professional transparency is service-oriented.

The ultimate balance is to be honest about the game's journey, but while being professional about the studio's operations. This maintains respect for the team while earning the trust of the community.

It's really easy to get dragged into defensive mode or for studios to feel like silence is safer; we've all seen it or been there. But avoidance is, in almost all cases, not a solution.