If you're a leader in game dev who feels stuck, able to spot problems but struggling to make a real difference, there is a path forward that levels up your leadership and accelerates your team, game, and career. Sign up here to learn more: https://forms.gle/nqRTUvgFrtdYuCbr6

Are you inadvertently forcing your team to serve a tool, instead of letting your tools serve your team and game?

In a recent conversation with Clinton Keith, Ben asked how Clint would help all of game development. Clint's response? "Delete Jira" - and Ben laughed to keep from crying.

Jira is a powerful tool, but in the hands of uninformed game development leadership, it often becomes a weapon against the very teams it's meant to help. Ben, who has used Jira and other tools as a producer within large studios, dissects the common, catastrophic misuses of Jira.

While you might be better off deleting the tool, the real work is about fixing the broken cultural and organizational patterns that turn a simple work management system into the "boss" of your game studio. Learn the four cascading failure patterns that are draining your team's effectiveness and how to correct them, making collaboration and player outcomes your true north.

What You'll Learn In This Episode:

• Why senior leaders keep breaking Jira without realizing it
• How Jira causes centralization and decision bottlenecks
• What Jira DOESN'T tell you, and why that makes it dangerous
• How perverse incentives emerge from overreliance on Jira and other tools like it
• The reason you end up feeling like a slave to the tool
• How to avoid the traps Jira leads you into

Connect with us:

🔗Ben's LinkedIn: https://www.linkedin.com/in/benjamin-carcich/

🔗BBG's LinkedIn: https://www.linkedin.com/company/building-better-games/

🔗Instagram: https://www.instagram.com/buildingbettergames/#

🔗Website: https://www.buildingbettergames.gg

🔗YouTube: https://www.youtube.com/channel/UCZpMT-dUwQR-R4Mb4uub6Sw

#gamedevleadership #jiraantipatterns #gamedevelopment #agilefailure #buildingbettergames