Your team is worried about backlash from an update. How do you address their concerns effectively?

Use Cognitive 3D or other data tools inside your games/simulations to understand UX barriers and other challenges your users are having without them needing to think about what they are.

Listening to your team’s concerns is key to effectively addressing them. Each member has a unique perspective shaped by their role, so encourage open dialogue in a safe environment. By understanding and acknowledging their fears and reservations, you can identify the root causes of any anxiety and work together to find solutions. This approach not only helps resolve issues but also fosters team unity and shows that their voices are heard and valued.

Ask open ended questions. Encourage deeper discussion by asking questions that more than a Yes/No answer. By so doing you get to understand in detail the perspective and concerns of team members

Listen to your team's ideas first to make everyone feel valued. Then, deal with their worries head-on so they can take action instead of worrying. Next, check out what players are saying on forums and social media to see what they think of the game. This way, everyone works together, the game gets better, and everyone loves it in the end. If you don't do this, people will get upset, things won't get fixed, and the game won't be as good as it could be. Also, if you're too bossy, your team won't feel good about themselves and will feel undervalued. Things will get worse, and they won't come up with new ideas because they feel they're not heard. But if you work together, everyone will trust each other. It's about Respect and Loyalty.

Before taking any action, make sure to listen to your team. Understand their concerns and acknowledge their worries. Create an open environment where everyone feels comfortable sharing their thoughts. Sometimes, just being heard can alleviate a lot of anxiety.

Collect feedback from various sources, including internal team members and external users. Use data analytics to identify potential pain points and areas of improvement. This comprehensive understanding helps in addressing issues more effectively. Remember, feedback is a gift that helps you improve.

If you fear your team will face backlash after an update, why not ask the players before publishing the update. Gather feedback from the players and try to incorporate it in your decision. The goal is to satisfy the players, and the best way is to make them feel listened. If you do have to go against their feedback, communicate with them. Be transparent and let them know why this decision was necessary.

Analyzing feedback from players before an update is crucial. Review forums, social media, and in-game data to understand what players like and dislike about the game. This helps you make informed decisions and anticipate reactions to changes. Be mindful of the difference between the vocal minority and the silent majority, as a small but loud group can sometimes overshadow the broader player base.

For Unity developers, Unity Gaming Services (UGS) provide a suite of tools particular Unity Analytics which can help you analyze how players are interacting with your game, where the get stuck, and much more.

Transparency is key. Keep your team informed about the update process, the reasons behind it, and the steps being taken to mitigate risks. Clear communication can alleviate fears and build trust. Make sure everyone knows that their concerns are being taken seriously and that there is a plan in place.

A base de um jogo é estruturada em sua maioria por pessoas bem diferentes, idades diferentes, gostos, personalidades, níveis de conhecimento, cren?as e expectativas... Um dos maiores desafios ao lan?ar um game, é tentar abra?ar todo mundo, o famoso "agradar à gregos e troianos", o que às vezes pode ser a solu??o, ou um tiro no pé, e realmente é uma etapa cautelosa e requer um planejamento executado sem pressa.

Your playerbase is essential. Be clear and transparent when announcing updates, add changelists to every release and update. If you're fearing backlash from the community, it's important to consider if you could share more about the motivation and the purpose of the update.

Before releasing the update, ensure it is thoroughly tested. Utilize beta testing with a small group of users to gather insights and identify any issues that need to be addressed. This reduces the risk of major problems upon full release. Testing helps to catch potential issues early, making the final product more robust.

Never skip on QA. Make sure that everything that you launch is polished and bug-free in order to prevent negative reception from the players. If the update you're releasing might be controversial, you could host a closed beta and get all the feedback you can from your players.

Prepare a contingency plan for any potential backlash. Have a dedicated support team ready to address user concerns promptly and effectively. Being prepared shows your team that you take their worries seriously and are ready to handle any situation. It's always better to be safe than sorry.

Always keep a backup of previously working code including all database, settings necessary to reproduce the previous product in case the current one fails on launch. Github for version control backups. Now people are keeping docker images of the entire setup needed to reproduce the code/database/ etc all in one place needed to reproduce each version of in code running format. This kind of backup could be restored in future and your previous code could be up and running in no time. Always have in app code to check current version and latest version from playstore/etc. So Whenever you have a faulty version of app it will check there is newer version and disable current app from loading until your user updates it from playstore etc.

Use the feedback and data collected to evolve your update strategy. Continuous improvement and adaptation ensure that each subsequent update is better received. Show your team that learning and evolving from each experience is part of the process. It's about making progress, not perfection.

Steve Jobs well said "Don't let the noise of others' opinions drown out your own inner voice". As Most of Them dont know what they really want. Building a Killer App Should be about Changing The Rules of The Industry You Are in. How Angrybirds and CandyCrush Got Rich With Simple Mechanics but Great Addictive Driven Development Strategy. Build it and People will come... distribution could be bought in the online space by Ads. So Focus on Building Great Stuff not on pleasing everyone all the time. You Should Improve Your App only 20% By Feedback and 80% by Strategy.