{"id":1007,"date":"2010-08-10T09:38:11","date_gmt":"2010-08-10T08:38:11","guid":{"rendered":"http:\/\/www.stevebromley.com\/blog\/?p=1007"},"modified":"2019-11-06T17:45:02","modified_gmt":"2019-11-06T16:45:02","slug":"the-right-environment-for-user-testing","status":"publish","type":"post","link":"https:\/\/www.stevebromley.com\/blog\/2010\/08\/10\/the-right-environment-for-user-testing\/","title":{"rendered":"The right environment for user testing"},"content":{"rendered":"

Most games testing, like the user experience testing done at Vertical Slice<\/a>, is done in a quiet room with a comfy sofa and with access to free food and drink. This isn\u2019t just a needless luxury; instead it\u2019s an integral point of the user testing process, and gives superior results to those found in a typical lab environment, with rows of workstations and one way glass.\u00a0 Why is this, and what factors are at play here?<\/p>\n

What is the environment?<\/h4>\n

With user testing, the environment comes down to the context in which the software or product is used. This includes where the user is, when they are using something, and who they are using it with. \u00a0It\u2019s important to not forget the factor that the environment plays when testing a product, otherwise your final results, conclusions and design decisions may end up way off the mark.<\/p>\n

Considering the environment for testing is important for both usability and user experience. \u00a0For usability testing, a realistic setting is needed to understand how a system will perform in that environment when out in the field. User experience focuses on how a system makes the user feel, and to truly understand this, you need to test users in an equivalent setting. This is why you\u2019ll find comfy sofas wherever games are tested, since games are typically played at home in front of the TV.<\/p>\n

\n
\"a

pizza boxes are optional<\/p><\/div>\n<\/div>\n

Getting it wrong<\/h4>\n

Common mistakes with user testing involve inaccurately representing the environment in which a product is to be used (poor \u201cecological validity\u201d).<\/p>\n

This could include an unfair representation of the conditions in which the product would be used \u2013 for example testing a car radio without having the user drive would not give a true understanding of how the radio would function when the user\u2019s attention is diverted.<\/p>\n

Another common mistake is failing to test things in a time sensitive manner. For example, ticket machines are often used in high stress situations, minutes before the train is going to leave. Giving the user ample time in a comfortable lab setting does not recreate a typical interaction with the ticket machine, and would give an unrealistic impression of its usability.<\/p>\n

User tests should also be separated, though concurrent, to the design process, and the development team should not be allowed to run the user sessions (though it\u2019s a good idea to have them spectate from afar). Having the team in the same room as the player can intimidate them into praising the game or product, and reduce the validity of the results.<\/p>\n

\n
\"bouncers\"

you liked it... got that?<\/p><\/div>\n<\/div>\n

Getting it right<\/h4>\n

So how can you be sure to get the environment right for testing?\u00a0 The following things must be kept in mind:<\/p>\n