While the concept of rapid prototyping might not be new to you, it’s always worth mentioning because I think it's one of the most powerful tools game designers can utilize in the beginning of a design process. In my experience, game developers tend to use prototyping as an assessment of what they have created, rather than using it for exploration. Rapid prototyping can be used to suggest and explore instead of confirming.
Rapid prototyping can be done physically and digitally and are used to test a part of the final product. In the case of game design it’s a part of a game or a specific mechanic. This can both be done digitally or physically but this blog will mainly cover the physical ones. These are typically made of cheap materials like paper, cardboard or wood. These materials are cheap and easy to use. Furthermore they don’t require any technical knowledge, which is great if you aren’t the best programmer.
Most importantly, they’re quick to make! Of course there’s nothing stopping you using a lot of time on a prototype, but a rule of thumb is that you must be willing to throw it out afterwards. This is because the goal of rapid prototyping is not the product you create, but the knowledge you gain from creating it. Another advantage of physical prototypes are the ability to change them quickly and on the fly while testing them.
Want the player to draw 20 cards instead of 5 or introduce a new rule? - no problem! You just brief the testers about the changed and/or added mechanic. Last, but not least, it’s fun to create and use rapid prototypes.
The Rule of the Loop
The number one reason for using rapid prototyping is what Jesse Schell calls the rule of the loop. The rule of the loop is:
“The more times you test and improve your design, the better your game will be” - The Art of Game Design: A Book of Lenses (2008)
Rapid prototyping is the quickest way get hands on experience (for both you and the testers) & test your design. They are easy to understand for the testers and there no problems with people having troubles downloading the game. In my experience, testers have an easier time criticizing and providing feedback for your game when you’re using a rapid prototype. This is because the prototype doesn’t look like you’ve invested a huge amount of time on it and thus making it easier to criticize.
Working with rapid prototyping will also help you thinking about details you might not have considered otherwise. When you test the prototype, you and especially the testers, will find a lot of scenarios in your game that you never considered beforehand.
One example of rapid prototyping was when my colleague David and I got an idea for a game mechanic at a convention. The idea was to design a puzzle where you had to get from A to B by shaping a repeating pattern in a dial that looked kinda like the android pattern lock system. As soon as we got home I started making a rapid prototype. It took me roughly 30 minutes in paint to make 10 levels and two of them looked like this:
Rapid prototyping levels for Sequence Nine
Afterwards, I printed them out and had people play testing the paper version of the game mechanic. During the testing, I tried different levels of explanation of the game idea and with and without time pressure. What I learned from this was that people seem to like the core mechanic of the game, but it required a lot of explanation and most people didn’t enjoy any time pressure.
I have found rapid prototyping an extremely useful (and fun) tool to utilize when designing games. It is a tool I especially have begun to use during game jams, where time is limited and very precious. Physical rapid prototyping does have its limits when it comes to testing game mechanics for certain genres etc. first person shooters, but it great for things like collectible card games (surprise!), turn based games and puzzles games. Next time you come up with an idea for a game, remember to make a rapid prototype.
by Lars Tornbjerg [19-09-2016 12:14:49]