10 design lessons from 10 years in games
10 years ago I started working in the games industry. Along the way I've picked up a few things that I wanted to record (for my own sake!) and share with you. 1. Understand the problem before chasing a solution Don't be tempted to start designing a solution when the problem is not fully explored and understood, take the time to focus on what you're trying to resolve. Make sure you understand what the solution needs to accomplish then formalize your findings, write them down. Develop goals. Present these to other team members, discuss and amend them as required. It's always better to debate the purpose of a feature than to debate a feature with no obvious purpose. 2. Don't pop an idea before it's fully inflated When a new idea or feature is proposed it's tempting to start immediately identifying flaws or concerns. Avoid writing ideas off or designing fixes based on these assumptions. Although these concerns are likely valid it's worthwhile giving the peop