#paper prototypes

Today we were doing more paper prototyping with the game we made last week... by that i mean making a new game from scratch because of serious problems inherent in our genre choice.

An Introduction to paper prototyping.

Again, I instructed subject to start at the top left panel, and work through flow.  Instructed her that there were two tasks that I wanted her to complete, but did not tell her what the tasks were (to see if the app is intuitive and simple enough for her to figure out on her own).  She was able to complete both tasks, without prompts from me, in the correct order!  Provided excellent suggestions to simplify user flow further (add a first-run experience).  Another success!

Interview Notes:

Subject was able to understand purpose of app and successfully complete both tasks outlined without explanation.  I did not even have to specify what tasks he should attempt to complete.  Rather, he saw the interface, and was able to successfully walk through and complete both tasks by himself.  Provided suggestions for incremental features, but was very pleased with P0 implementation.  From a design standpoint, this was a success.

Interview Notes:

So, we're finally working on a new game! Judging from the photos, the game will be made from paper, some bits of wood, and...plastic coins? If you're thinking "Hey, this is a board game!" then you're right, this IS a board game, well, sortof. This is what we like to call a Paper Prototype.

What's a Paper Prototype?

When game designers make new games, they often start by creating a prototype made from cheap materials like paper, cardboard, and small items that are readily available.

Why not go straight to the computer?

Despite the wonders of technology, it's still way easier to get ideas and images down on paper, thus making early development fast and cheap. What's more, you can easily set up a play session with some playtesters so you can get immediate feedback and make direct modifications.

Recipe for a paper prototype

Here's what we used for our prototype: 🔸A.Timer: Used for timing play sessions. We simply googled "timer" on our laptop.

🔸B. Random Number Generator: Used for determining results when the game involves chance. We googled for a number generator as well. But you can use dice, or even flip a coin!

🔸C. Paper: Simple and versatile, can be used for maps, interfaces, and even for keeping track of progress

🔸D. Game pieces: For representing the player character, items, or currency. We used plastic coins and bits of wood, but feel free to use anything!

Always seems to be a debate between paper and electronic means. In favor of paper: it’s possible to iterate quickly.

Wireframes come later, and they should be shared

(1) Focus on the primary task

(2) Create use case scenarios

(3) Identify mental models

(4) Check the flow

7 myths about paper prototyping

(1) Not being able to draw well enough. Does not need to be neat and pretty. And there are stencils and other helpful tools.

(2) That wireframes are the same as paper prototypes. Wireframes are much too concerned with layout. Also, wireframes come later on in the design process.

(3) Electronic solutions are better. Really, paper can accomplish whatever the initial prototype is supposed to. Starting with electronic also starts with constraints earlier than is necessary. And it can make you too focused on commercial gains.

(4) Whiteboards are just as effective. Its good for brainstorming and design, but not for testing things. “This is because paper prototyping isn't just about design — it's about iterative design: creating stuff you can test quickly and then discard or improve upon.”

(5) Users will behave differently with paper.

(6) It looks unprofessional