I don’t yet have as defined a game design process as my software process, but I’ve evolved a simple methodology for recording and refining my game design ideas. The technology needed is a pen, a journal, and a wiki. The process involves three activities:

For one, I write down (with the pen, in the journal) every random gameplay thought, with little regard for feasibility or conformity to the rest of the design. From my technical background, I tend to auto-cull things that would be impossible to implement. From my board game background, I tend to prefer strategic mechanics, rather than fuzzy “wouldn’t it be cool if” concepts.

The second activity also involves a pen and a journal (I use the same one from above). The goal is to refine the random thoughts into coherent game mechanics. Terminology like “attributes” and “weapons” and their interactions must be defined. The goal is to draft and refine the game systems.

The final activity, which I had underestimated, is concisely documenting the final game design. This phase forces decisions, exposing gaps and conflicts. If you can’t play the game in your head from these designs, and design the software, then there is something missing. I’ve found that a wiki provides the best balance between formality and flexibility.

All of these activities happen more or less at the same time. This is not a sophisticated requirements tracking system, and document versioning would be needed to coordinate design and software teams, but this works for my team of one.

Overall, this methodology seems rather obvious, but it’s important to be aware of the process, and write it down. Unless something is well documented, it cannot be well understood.

Share and Enjoy:
  • StumbleUpon
  • Facebook
  • Twitter
  • Digg
  • del.icio.us
  • Reddit
  • Technorati
  • Google Bookmarks
  • Slashdot
  • N4G