DGMD E-70 Principles of Game Design LESSON #2: Design Through Usability Testing.

DGMD E-70 Principles of Game Design

LESSON #2: Design Through Usability Testing

TODAY:

1. Game Design through Focus Testing: principles and methods.

2. Radical Revision

WHY DO WE TEST?

WHY DO WE TEST?

• Creation is 1% inspiration and 99% revision.

WHY DO WE TEST?


• Our reality is not the only reality.

WHY DO WE TEST?



• Culture: common modes of consumption, presentation, or interaction.

WHY DO WE TEST?



• Culture: common modes of consumption, presentation, or interaction.

• Testing is how we come to understand our Audience’s needs.

Accessing Audience

• PRODUCT FIRST: We have a game we want to make, and must identify the audience that will enjoy that game.

• AUDIENCE FIRST: We have an audience we

want to reach and so we design a game to fulfill their interests.

Testing as Marketing Strategy

GAMER AUDIENCE

• 30 years of game history and conventions to integrate in your game mechanics and interface.

• Developers of games for core Gamer audiences need a level of knowledge of past games to understand the expectations of their audience

• Testing can help illuminate Gamer expectations, but you also need to play many games. For example:

Why can’t I punch something spiky?

Mario Bros defined/ruined spikes for everyone

GRAYBOXING

• When testing digital games to decide if the core mechanic is fun, avoid including much art: use simple forms so the audience can focus on the mechanic: “Grayboxing”

• Good Mechanics = fun game.• Art+ Audio can create greater immersion, a

more memorable experience, but cannot fix a mechanic that is not fun.

DESIGN METHOD #2: FOCUS TESTING• IDENTFY A PLAYTESTING GOAL: What about your game

do you want to improve?• OBSERVE OTHERS PLAYING YOUR GAME. Avoid

influencing their experience, where possible. • LISTEN: Ask them to speak while playing and write

down everything they say and you see them do which offers a new perspective on any aspect of gameplay or user interface.

• INTEGRATE: Iterate your game mechanics and interface with this feedback in mind, while also listening to your own instincts; listen but do not treat all feedback as infallible.

PLAYTEST DESIGN EXAMPLE:

Dragon Day Care“Nurturing” card game by Jason Wiser

Three cards types: Egg, Love, and Poach

Playtesting Goal: Speed-up play• PLAN: Multiple days of playtests, quick

changes between each to test rule adjustments, timing games and frequency of egg hatches.

• TESTED VARIATIONS: Adjusted card type numbers balance in deck, reduced number of Love cards needed to hatch an Egg, removed most devastating Poach cards and overly- complicated Love cards

Coolest innovation: Stack Eggs

How We Test:

• Testing Set-up.• Communicate to Testers the Plan:– Game is broken: bad at being a game!– Silent note-taking – Talk out-loud while playing

• During Testing: Stay Silent, Take Lots of Notes!• Debriefing, After Testing, Potential Pitfalls.

Design Exercise #2a: Usability Testing• Pair your team up with another team. Designate one team A and

the other B.• “A” will test “B”’s game first. “B” teams: run a playtesting session

according to the Focus Testing handout: prepare writing materials, set up the game for play, provide your testers with the instructions, let them read and try to play.

• Write down where they get stuck or confused, and what they enjoy. • Only speak when they get too completely stuck to proceed!• When the game is done (or has been tried for 15 minutes) form a

circle and discuss the game. As a group come up with 3 adjustments you want to explore. Hand-write a copy for the teacher of those 3 (along with game name, designer name, and testers names).

• Do the same for “B” testing “A”’s game! Be sure to keep play to 15 minutes.

Question: What is radical revision?

Question: What is radical revision?

Revision that explores complete overhauls of your ideas: Dangerously sweep away all of the sweat and blood you have shed so

far and imagine impossible new directions.

You don’t have to follow those paths—you just need to give yourself the chance to consider them, to permit those ideas to

percolate and enrich your games.

Fire Hose Games: Fall 2008

Fire Hose Games: Fall 2010

Builder Brawler #1: Initial 2D Prototype:

Builder Brawler #2: 3D Build-out:

Builder Brawler #2: Building materials from shattered enemies:

Builder Brawler #2: Moving screens, long boss fight:

USER TESTING: Lukewarm responses:

“Somewhat fun”

Tried to fix with better art, but just wasted time.

We didn’t know what really excited playtesters looked like.

Builder Brawler #3: Competitive weaponized tower- building using pieces from beaten monsters. Just a mini-

game?

Builder Brawler #3: Just a mini-game?Nope. HUGELY positive responses. We refocused on this

direction, scrapping a year of development.

Builder Brawler #3: Build-out of multiple competitive levels.

Builder Brawler #3: Campaign Mode

Design Exercise #2a: Radical Revision 1. Review notes from playtesting. Where did players get

stuck/confused? Where did the game drag? Where was there less awesome?

2. ID a core idea in your game to radically reposition in new modes of play.

3. Consider a mechanic: how players move, gather assets, interact with other players. Look for opportunities to streamline play.

4. Focus more on one big change rather a few smaller tweaks.

Due Next Week:

HOMEWORK #2: With your first team, radically revise your first game based on usability testing. Submit 1-2 typed pages (3-sentence game idea, gameplay rules) board design, and set-up/play photos.

ALSO: Read McGonigal's "Reality is Broken" Part 2: Reinventing Reality, chapters 7 & 8 (pp119-167)

Have a Splendid Week!

And don’t forget to email us with questions:

Instructor: JASON [email protected]

Available daily by email.

DGMD E-70 Principles of Game Design LESSON #2: Design Through Usability Testing.

Documents

Transcript of DGMD E-70 Principles of Game Design LESSON #2: Design Through Usability Testing.