Principles over practices
In most businesses, it's natural—and often necessary—to pursue repeatable processes that yield consistent outcomes. This mindset, drawn from manufacturing models and and a desire for operational efficiency, emphasizes predictability and control. However, game development is a creative endeavor, not an assembly line. Applying rigid, standardized practices in an environment defined by novelty and innovation can do more harm than good.
The Pitfall of Prescriptive Practices
Experienced leaders and contributors in game development understand that no two projects are exactly alike. Yet, there remains a strong temptation to impose familiar solutions—processes that worked well on past projects—without first considering the unique challenges of the current one.
These practices are often not a response to a present, clearly defined problem. Instead, they’re carried forward because they were successful elsewhere, or they’re applied broadly in reaction to a localized issue affecting only part of the team. When such solutions are imposed organization-wide, they can introduce friction, disrupt momentum, and create waste—undermining the very efficiency they were meant to provide.
Context Before Convention
This isn’t a rejection of process altogether. Game development organizations absolutely benefit from shared practices and operational clarity. But effective practices must be grounded in a clear understanding of the specific context: the team, the game, and the problem at hand.
By leading with principles—such as transparency, iteration, player-first thinking, or autonomy—teams can develop tailored approaches that fit their current reality. Practices can then emerge organically from these principles, ensuring they are relevant, useful, and sustainable.
In this way, even proven practices from other projects can be valuable—not as templates to be imposed, but as starting points to be reinterpreted through the lens of present challenges.
Why Principles Must Lead
When principles frame our decisions, we empower teams to think critically, adapt wisely, and own their solutions. This creates a culture of thoughtful experimentation and responsive design, rather than one of dogmatic adherence to process.
At its core, game development thrives on creativity, collaboration, and iteration. To foster these effectively, we must prioritize the flexible application of principles over the rigid implementation of practices.
In our organization, we value principles over practices—not because practices are unimportant, but because principles ensure those practices are truly fit for purpose.