Developers and artists clash on creative direction. How will you navigate feedback sessions effectively?

Yes, conflict will happen, but its also necessary to get things moving, no conflict might be a sign of lack of interest. Embrace and negotiate conflict as a leader and make decisions

Recognize that conflict between developers and artists can be a source of creativity and innovation. Embrace these differing perspectives as opportunities to explore new ideas and improve the project. Encourage an environment where constructive conflict is seen as beneficial rather than detrimental. By viewing conflict positively, you can foster a culture where team members feel comfortable expressing their ideas and concerns.

You should definitely embrace the conflict and listen to the other side carefully and give your best opinion. You'll either learn the good stuff or convince the other side. Either way the product will improve and healthy team culture wl flourish.

Focus on shared goals. Remind everyone that the ultimate aim is a fantastic game, not personal victory. Create a safe space for open dialogue. Encourage active listening and constructive criticism, without blame. Find common ground. Look for areas of agreement and build on them to find a compromise that satisfies both teams.

Before starting any feedback session, set clear goals for what you hope to achieve. This establishes a shared focus and direction. In my experience, when we were optimizing the performance of Scooby Doo Funfair Scare, our primary goals were to reduce WebGL loading times and avoid crashes on low-end devices. By having these clear objectives, discussions remained productive and aligned, ensuring that every piece of feedback contributed to these end goals.

First, turn off all computers. One of the reasons that prevent the development of creativity is that the computer is turned on while thinking. Let your mind relax. Take a pen and paper and start sketching and writing by yourself or with your group. Even if your design is very poor. Just think about the message and purpose of your work. Don't forget that the more limited your tools are, the higher your creativity will be.

Para complementar o comentário do Hassan, um exemplo prático de como definir metas para uma sess?o de feedback seria: Objetivo: Melhorar o sistema de progress?o do jogador em um RPG de a??o. Metas: ? Jogadores experientes devem identificar pelo menos 3 caminhos de progress?o viáveis. (Exemplo: Combate, Diplomacia, Furtividade) ? O sistema de recompensas precisa motivar os jogadores a experimentar diferentes estilos de jogo. (Exemplo: Habilidades e equipamentos únicos para cada caminho) ? A curva de progress?o deve ser gradual e recompensadora, evitando picos de dificuldade excessivos. (Exemplo: Analisar a curva de aprendizado de jogos similares e realizar testes de jogabilidade regulares).

Setting clear goals is key, but equally important is fostering mutual respect during feedback sessions. Involving both developers and artists early in the goal-setting process ensures alignment and reduces friction later on. Open communication and recognizing both successes and challenges will lead to more constructive and collaborative outcomes.

As a Project Manager & Senior Developer In a Game Studio. I can say we should setting clear, achievable goals before a feedback session is essential in bridging the gap between technical constraints and artistic vision. Goals serve as a guiding framework, ensuring that discussions remain focused and productive. They act as a common language, enabling developers and artists to better understand each other's challenges and collaborate effectively towards a shared objective. By aligning everyone on what needs to be accomplished, we can create a more streamlined process that leads to a cohesive and successful game development outcome.

Promote open and respectful dialogue during feedback sessions. Facilitate discussions where both can voice their opinions and listen to each other’s perspectives. Use techniques such as active listening, asking open-ended questions, and summarizing points to ensure everyone feels heard. Fostering dialogue helps to bridge gaps between different viewpoints and encourages collaborative problem-solving.

Por exemplo, após um teste de gameplay, ao invés de apenas dizer "o combate parece lento", um feedback construtivo seria: "Percebi que o tempo de resposta dos comandos durante o combate parecem lentos, o que impacta o ritmo do jogo. Podemos explorar anima??es mais rápidas ou comandos mais responsivos para tornar a experiência mais fluida?". Dessa forma, você abre espa?o para um diálogo produtivo e focado em solu??es.

Fostering open dialogue is indeed essential for productive feedback sessions. By creating a space where both developers and artists feel comfortable sharing their perspectives, you pave the way for genuine collaboration. Actively listening and asking clarifying questions not only validates their input but also encourages a deeper exploration of ideas. When everyone feels heard, the focus naturally shifts from winning arguments to working together on innovative solutions that enhance the game.

Well, Well, Well, When all voices are valued, the conversation becomes more constructive, often leading to innovative solutions. The aim isn't to win an argument but to work together towards creating the best possible game. Collaborative dialogue is key to achieving this. It's crucial to create an environment where both developers and artists feel comfortable expressing their ideas without fear of dismissal.

In the first phase of feedback we let everyone state their initial feedback without open discussion. One way communication. In the second phase we continue back to the first feedback and allow for all (each and self) to give perspectives and possible causes that may have led to that feedback. So to think with one other. We repeat for all other feedback. Third phase we return to all feedback one by one again and all (and self) take arguments against. Devil advocate. In the fourth stage we revise the second and third phases and all propose solutions and alternatives. Final phase is a round of judgment by each (and self) on how proposed solutions may affect the experience of the game. Share Feelings. In each phase we take notes.

When creating content, the priority should be the target audience; have those conversations about what goals align with what is best for them. You want to create a digestible product that's also an impactful story, and if the audience is flagging any issues, those needs come first.

Prioritizing feedback based on its impact on gameplay and artistic integrity ensures that critical issues are addressed first, creating a solid foundation for further refinements. This approach is key to efficient and effective game development.

Imagine um RPG onde o sistema de progress?o da história constantemente trava após o jogador completar uma quest principal. Este problema impacta diretamente a experiência central do jogo e precisa ser resolvido antes de polir o sistema de crafting, por exemplo. Priorizar o feedback crítico, como a progress?o da história, garante uma experiência mais sólida e agradável para os jogadores.

Prioritizing feedback is crucial for keeping sessions focused and productive. By addressing the most impactful issues first whether they relate to gameplay or artistic integrity you ensure that the core elements of the game are solid. This approach helps prevent the team from getting sidetracked by minor details and allows for more effective use of everyone's time. Starting with the big-picture items sets a strong foundation for refining the game further.

In feedback sessions, it's essential to prioritize the input that has the greatest impact on gameplay and artistic integrity. By addressing the most critical issues first, we ensure that the core elements of the game are solidified, providing a strong foundation for further refinement. This approach helps us stay focused on the big-picture goals and prevents us from getting sidetracked by less important details. Prioritizing feedback not only makes the most of our time but also drives the development process forward more effectively.

Exemplo prático: Em um jogo de plataforma, ajuste iterativo significa testar a sensa??o de salto do personagem em cada itera??o. Ajuste a altura, a velocidade e a resposta, coletando feedback dos jogadores para refinar a mecanica e encontrar o equilíbrio perfeito entre desafio e divers?o.

Implementing changes iteratively is a smart approach, allowing for continuous refinement without overwhelming the team. By making small adjustments and regularly reassessing their impact, you maintain flexibility and can course-correct as needed. This method not only conserves resources but also keeps both developers and artists engaged in the process, fostering ongoing collaboration and ensuring the game evolves in a well-considered way.

Implementing feedback iteratively is a smart approach that allows for flexibility and continuous improvement. By making small, incremental adjustments and regularly reassessing their impact, we can avoid overcommitting resources or making drastic changes that might not work as intended. This method fosters ongoing collaboration, providing developers and artists with regular opportunities to review progress and make necessary adjustments. Iterative implementation ensures that each step forward is thoughtful and aligns with the overall vision of the game.

Iterative workflow allows for better oversight on progress and comprehensible tasks. And a shorter feedback loop. There may be few elements that cannot always be split up into super small tasks. It's essentially to get these done early on if a lot depends on their success. (E.g. internal tools, or technical complicated mechanical systems) It's also advised to not start with any too heavy art or polished mechanics when still in a very dynamic stage of the project. Instead work with place holders and quick approaches. To prevent having to redo a lot of work with every change. Otherwise this can become very demotivating. In some cases you may want to branch out and pick a heavy art and a polished mechanic to validate the overall workflow.

In most cases, lack of communication causes continuous repetition of work, planning and continuous communication is too important, consistent workflows are needed in which both developers and artists are not conditioned or trapped In a loop of unforeseen events and incompatibilities, this can be very frustrating. It is very important to do this before starting production, even if production is on hold for a small period of time, it is something that cannot be done during production. You will get a united team, perfectly prepared for production and with good communication, something you will appreciate in the long term.

Documenting decisions made during feedback sessions is crucial for accountability and future reference. It ensures that everyone is on the same page and that the rationale behind decisions is transparent.

Documenting decisions, problems and solutions may seem useless. Maybe it is at first sight with tiny groups, still, get used to it anyway. If it doesn't directly prove useful in the beginning it can later. Like when a project grows larger. Or when outreach starts to become important. At the end It's simply crucial to create documents for people to be able to read back on meetings. Whether it is before the next or to refresh the mind on the previous meeting. Maybe someone had a break for a week or more or someone is new and enters later into the project. Maybe there is a collaboration or outsourcing. And for those that have to deal with anxious producers that want answers. Those that have to, they can now lookup decisions in a document.

Documenting decisions is key for future reference and conflict resolution within diverse teams like developers and artists. It helps uncover the root causes of misunderstandings, often stemming from communication misalignments. By articulating perspectives, we can bridge differing interpretations and address conflicts effectively. Beyond its role as a reference tool, documentation acts as a preventive measure against unnecessary changes. While post-decision modifications, provided they are rational improvements, are beneficial, the document serves as a shield against unwarranted alterations driven by mere shifts in individual tastes, vital for project success. Superfluous changes not only waste time but also impact budgets and team morale.

I use something I call "democratic design" 1. Avoid emotional attachment to the proposal: What I am proposing is a suggestion based on my experience and knowledge, not the final decision. 2. Become critical: Listening to all parties and subjecting the design to a technical evaluation leads to more structured decisions. 3. Guided design sessions: People who are involved disagree less and feel unity in the project. 4. (Development + Design + User Experience) x Business Strategy = Revenue. at the end, all of this is business. 5. Designers and developers can switch roles, the only thing that differentiates them is how bring ideas to live. Be nice with each other.

From my experience I know the conflict firsthand on both sides. It is always very important to maintain a constant exchange of opinions, looking for solutions and creating tools is a point of great importance, this helps to obtain a much more moldable and adaptable base on the developers' side. Artists obtain tools that facilitate work and boost production. A very important fact is that they also facilitate any type of unforeseen event. Sometimes it is not possible due to a technical impossibility, but alternatives are always available. I have always liked that the developers know the artists' workflow and vice versa, the result is a very united and versatile team capable of overcoming any obstacle.