How can you communicate creative ideas to team members unfamiliar with game development?

2 Simplify your language

Another tip is to simplify your language and avoid using jargon, acronyms, or technical terms that may be unfamiliar or confusing to your team members. Instead, use clear, concise, and plain language that everyone can understand. For example, instead of saying "We need to implement a procedurally generated level with a roguelike progression system and a permadeath mechanic", you can say "We need to create a random level that changes every time you play, with a difficulty that increases as you go, and a rule that you lose everything if you die". You can also use analogies, examples, or metaphors to help your team members relate to your ideas.

3 Listen and ask questions

Communication is a two-way street, so you also need to listen and ask questions to your team members. Listening can help you understand their perspectives, concerns, or suggestions, and show that you value their input. Asking questions can help you clarify any doubts, assumptions, or expectations, and ensure that you are on the same page. For example, you can ask "What do you think of this feature?", "How would you approach this problem?", or "Do you have any questions or comments about this idea?". You can also use open-ended questions to encourage more discussion and feedback.

4 Use common references

A fourth tip is to use common references that your team members can relate to or recognize. These can be examples from other games, movies, books, or genres that share some similarities or inspirations with your game idea. For example, you can say "Our game is like a mix of Zelda and Dark Souls, with a pixel art style and a retro soundtrack", or "Our game is a sci-fi adventure with a branching narrative and multiple endings, similar to Mass Effect or Detroit: Become Human". Using common references can help you establish a common ground and a shared vision with your team members.

5 Document and share

The last tip is to document and share your ideas and decisions with your team members. Documentation can help you organize, structure, and communicate your game design in a consistent and coherent way. It can also help you track your progress, goals, and feedback, and avoid conflicts or misunderstandings. You can use tools like Google Docs, Word, or online platforms like Notion or Trello to create and share your documentation. Some examples of documentation are game design documents, user stories, wireframes, flowcharts, or code comments.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?