Overview
Activity 1
Activity 2
Activity 3
Activity 4

User Testing Toolkit

Overview

The InGAME User Testing Toolkit is a suite of guides, tools, resources and processes developed to undertake various types of User Testing for games. It guides you through the planning and running user testing activities, covering both remote and in person studies.

Every project is different and may require some adjustment, but the overall process has been tested in a range of scenarios.

Throughout this toolkit are links to documents or resources which can be used as guidance or templates. These assist the planning and execution of a fast turnaround user testing process, all syncing with the game development process.

Quickstart Guide

The toolkit process is made up of four activities:

  1. Goals & Objectives – Establish the aims and objectives at the start of any user testing.

  2. Session Planning – Plan your user testing sessions, participants and logistics.

  3. Sessions – Run user testing sessions capturing relevant data.

  4. Analysis & Reporting – Produce a findings report to distribute to the development team

You can either start at Activity 1 and follow the guide to plan and run a user testing activity, or jump to the section of most relevance.

Activity 1: Goals & Objectives

Establish the aims and objectives at the start of any user testing.

You will plan the user testing through three steps:

Aligning Goals: You will identify key project details, opportunities for user testing, the information being sought, and who from.

Research Question Data: You will dig deeper into the questions the user testing will be answering, and what data will answer these questions.

Method Planning: You will consider what approaches will be used to gather the information you need, and the practicalities of the methods.

Use the Goals and Objectives Miro to capture information on the goals and objectives of the user testing. Follow the instructions on the board to complete all steps.

The activity is ideally completed as a group, but can be completed individually. It will take around 2 hours.

Resource 1: User Testing & Development Timeline

Activity 2: Session Planning

Plan your user testing sessions, consider who will be taking part, the logistics for running the session and the game version you shall be testing. It is relevant for Interviews, Focus Groups, Playtests, Usability Playtests and Surveys. You will plan the user testing through the following four steps and will need the miro board below to get started.

Plan your user testing session by considering the recruitment, scheduling and technology. Then, if the method requires it, finalise a list of questions you will ask to participants. 
Open the Miro board ›
Note: If you are conducting interviews or surveys where the participants will not be playing a version of the game, skip this step.When you have a version of the game ready for testing, complete the Build Checklist to ensure the build is suitable for the testing. If it fails any of the points, either seek an updated version or adjust the test plan.
Build checklist link ›

With the session planned, you can start recruitment for the number of participants from the sources you have planned for in Step 1.

Recruitment of participants can be one of the time consuming and challenging parts of the user testing process. Below are some tips:

  • Keep a record of people signed up, such as a spreadsheet or shared document

  • Record all relevant information, for example, contact details or session dates

  • It is likely that some participants will drop out. If you have a minimum requirement, consider having backups or extra participants to cover this situation.

  • The longer the time passes between the signup and the sessions, the more likely it is that some participants will drop out

  • Be sure to leave sufficient time to recruit the numbers you need – this may take longer than you anticipate

  • Consider if you need to screen participants. For example, if you are looking for players with prior experience of the game, you may need to confirm this during the recruitment process.

  • Be sure to clearly state any requirements (such as age, game experience or session dates/times) to reduce sign ups who will need to be filtered out later

  • If you are struggling to recruit sufficient participants, consider if there’s a method you can use with lower requirements – signing up participants who aren’t in your target groups to make up the numbers will reduce the validity of any findings

Activity 3 - Sessions

This activity helps you run the user testing sessions, creating a reliable and consistent process to capture the data needed to answer the research questions in a way that minimises bias and error.

A resource with tips on running a user testing session, sharing best practice knowledge around do’s and don’ts for running sessions in a way to reduce bias and produce reliable and valid data.Review the information in the Session Tips. This will outline some tips, suggestions and best practice for planning and running user testing sessions.
Session tips slides ›
Capture the key session information on the Session Miro Board, ready for use in the steps below. This is a short process that reviews and summarises previously captured information, and should take around 45 minutes.
Session Miro Board ›
Using the information from Activity 2 and Activity 3 Steps 1 and 2, create a Moderation Guide. This will be used to manage the flow of each session, making sure all sessions are consistent and cover all required areas.
  • Use the Moderation Guide Template as a guide for format and contents
  • Test out the moderation guide
  • Are you conformable with the flow of each session?
  • Are the participants getting all the information they need to?
  • Is it clear what everyone’s responsibilities are?
  • Are you comfortable with the scripts / questions?
  • Distribute to session moderators/facilitators
  • Ensure all moderators/facilitators are familiar and happy with the guide, and their roles
  • Revise the moderation guide as needed
  • This will likely take 90 minutes.
Moderation Guide Template ›
Using the Moderation Guide created in Step 3, you will run the planned number of user testing sessions and capture the data needed to answer the research questions.Everything should be in place to run the user testing sessions.Consider if you need to run a pilot test. This can be useful to test a process or any tech/software. The moderation guide or other documents can be updated after the pilot test to address any issues and software/hardware can be adjusted or fixed if there were any issues.Using the Moderation Guides created in Step 3, run each of the scheduled user testing sessions:
  • Collect all paperwork for each participant
  • Collect all data from the sessions
  • Recordings, Analytics, Observation Notes etc using templates such as the Note Taking Template
  • Store the data according to the policy outlined at the start of the project.
Note taking template ›

Activity 4 - Analysis & Reporting

This activity helps you to produce the findings report and distribute it to the development team.

The process and guides will assist in analysing the data in a bias free manner, and producing an actionable report which the development team can use to improve the user experience of the game.

A short review of Data Analysis and Reporting, shares best practice knowledge around do’s and don’ts for analysing data and producing an actionable findings report.Review the information in Data Analysis Tips. This gives advice on best practice, tips and suggestion for the Data Analysis and Reporting process.

Slides ›
You will analyse the data gathered from the user testing sessions and use this to produce findings to answer the research questions.Using the data captured from Activity 3: Sessions
  • Perform the data analysis to produce the findings for the report
  • This should be focussed on answering the key questions identified in Activity 1
  • Other observations and issues such as bugs can also be catalogued, but should be treated separately
Data Analysis Flow Guide ›
You will gather the findings produced from Step 2 and create a report, which will be distributed to stakeholders in the development team.The report should cover the findings for each of the research questions and testing objectives, and be in the format(s) decided in Activity 2 as optimal for the stakeholders.Use the Example Report Templates to assist with content and flow:
Once the report(s) have been completed, distribute it to the project stakeholders.
Once the report has been shared, a meeting to present and discuss the findings, and create an action plan for improving the user experience.The findings from the report should be reviewed by the stakeholders within the development team. This can fit into any process or structure familiar within the organisation, but should allow for:
  • Making stakeholders aware of the findings
  • Allowing for any questions answered or clarifications to be made
  • Deciding and capturing actions and next steps
The process should result in an action plan for implementing the changes identified. An example is provided in the Developer Action Plan Template.Action Plan Template ›