Game Career Guide is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.


Get the latest Education e-news
 
  • Discord As A Tool For Community Led Design

    [04.11.19]
    - Becky Matthew

  • When a community is left unnurtured and uninspired, especially on a live chat platform such as Discord, players often use the platform as a way of expression - pushing the boundaries to test the consequences. This becomes especially true in larger communities when the Hawthorne effect (also commonly referred to as the observer effect) comes into play. Nurturing and encouraging a positive community of players will yield you and your team the best results when it comes to feedback; take the time to listen and acknowledge what your community is telling you as their suggestions may solve major issues within your game.

    Listening and acknowledging everyone's feedback doesn't mean that every feature idea and re-balance should or has to be implemented - though every idea should be considered. Acknowledgement is the stepping stone to one of the key principles of building a positive community - respect.

    Respect is one of the most important fundamentals of any community, respect between the player and developers, and respect between players. In order for a community to thrive in positivity, mutual respect is required to create a safe, friendly and approachable environment for everyone.

    Creating a channel solely for game feedback and desired features is a great way for new and existing users to know the best location to share their views with the team. Feedback left in general chat or similar are often lost in the masses resulting in players feeling neglected and ignored; a specified channel allows for players to chat away in the other channels whilst still retaining a single space where they know their views will be heard. Additionally, it limits the channels the development team need to filter through for feedback, which is always an added bonus!

    Aggregation and Consolidation

    Once a community is comfortable giving regular feedback, it then becomes time to filter through and aggregate the most relevant and usable designs into actionable game design documentation for the game. The role of your companies designer (or you, if that's your role!) is to speculate which suggestions are beneficial to not only the players but the game too.

    • Does this idea suit the game?
    • Is the feature beneficial, but maybe after some slight changes?
    • Do we have the resources and the tech to implement this feature? If not, what do we need?
    • How would we go about implementing this?

    Are all examples of questions you should be constantly asking yourself during this process.

    Listening to users can be an extremely valuable resource, but developers must also sort through the noise and have the guts to stick to their own vision and not try to satisfy everyone. The vocal community are often the minority; judge patiently and explore the possibilities of the ideas that come from the people who love the game as much as you do.

    Begin injecting your communities ideas into the sprint and spread them evenly like tasty salted butter on your morning toast, there will be times during development where usable community ideas will be few and far between but that doesn't mean that your community need to go without. People will often appreciate a steady flow of fun and enticing content rather than a big mashup of their ideas.

    One solution to this would be to create a backlog of fleshed out and documented community ideas for the development team to compile and discuss. Designing with the community in mind should not be a chore or a jar in the development process, it should instead be positioned seamlessly yet consciously into a workflow.

    It is important to note that these ideals and development concepts come from the mindset of working in a small, independent game studio and may not be relevant to that of a larger studio with a bigger and more persistent community. I imagine that in this instance, designers would work in conjunction with not only the producers, but social and community management as well, to help balance the workload and understand the communities persona clearly.

    Conclusion

    Sometimes what a community proposes might not be the best solution, but in the end if a player has taken the time to discuss an issue or an idea, solutions should be investigated and designs considered. Development teams can often get wrapped up during a long development process and forget to consolidate with their passive team. Stick true to the teams vision but consider the bigger picture and the key to your success - your games community.

Comments

comments powered by Disqus