How to make a good game? Just what is playtesting? Watch the presentation to learn more about playtesting and why it is crucial if you want to make really great games. This presentation explains the basic principles of playtesting
2. 2013
Who are we?
Rene Rebane
• UX Architect
• Graphic designer
• Test moderator
• Gamer
Marko Nemberg
• Marketer
• Technology geek
• Test moderator
• Biometrics and
neurogaming evangelist
7. 2013
Game design is just hypothetical
until it’s actually been played by
your target audience; only then will
you know if your idea works.
– Sid Meier, creator of Civilization seriesSource: http://www.edge-online.com/features/are-gamers-tiring-same-old-thing/
8. 2013
Goal is a
fun game
Design is
hypothesis
Playtest is
experiment
Evaluate
results
12. 2013
Why test?
• To make informed decisions
• Find out usability problems
• Players know what is best
• Understand how players think
• Reduce risks and unwanted surprises
14. 2013
Common misconceptions
• Playtests are not important
• The players don’t know what they want
• Bug testing is enough
• Players will probably just ignore the problems
• It is ok to have some usability and accessibility
issues, players won’t notice anyway
16. 2013
Colour blindness
• 285 million people are visually impaired
worldwide
• 39 million are blind and 246 have low vision
• Up to 10% of men in the world are color blind
• 1% of women
• In some regions this percentage is even higher
Source: 2012 WHO statistics
18. 2013
Hearing loss
• 360 million people worldwide have disabling
hearing loss
• Players lose out on video games if information
about impending danger is coming only through
sound effects or music
• Never give players information using just one
sense – audio or visual
20. 2013
Reduced cognitive and
motor functions
• Over a billion people, about 15% of the world’s
population, have some form of disability
• Between 110 million and 190 million adults have
significant difficulties in functioning
• How can we include players who have limited
cognitive or motor functions?
34. 2013
How to analyze?
• Write down what happened
• Why it is unexpected
• Why it is bad (longer process,
wrong element usage)
• Remember it is not statistics
35. 2013
Next steps
• What to keep
• What to change
• What to test more
• What to measure later