Preparation for a User Day

Planning Meeting

The usability specialist or quality manager should invite the participants to the planning meeting. The User Day checklist is used to decide when and for which areas of the application a User Day should be held.

Typical reasons for a User Day are:

  • We have a new product concept and want to check how well this is received by users.
  • We have an initial idea about the application and want to test its basic structure.
  • We have a new interface design and first want to test it with a paper prototype before implementing it.
  • We want to have our new executable system tested by several users so that we can integrate their feedback before completing development.
  • We are more or less finished with the application and want to find and correct any undetected weaknesses.

Another way of getting feedback about the usability of the application from users is a customer visit with a presentation of a new prototype or a new application on a laptop.

The following aspects should be cleared up during the planning meeting:

When Should the User Day Take Place?

During planning, you should keep in mind that it could take several weeks to invite the users. Creating the tasks and preparing the test system or prototype should take only two to four days.

Whom Should We Invite?

  • Use existing user roles from the user/task analysis and define the user profile.
  • Define an optimal number of test users (three to six are recommended).
  • Target potential customers.
  • Establish who is responsible for initially contacting the customer and coordinating with the central test organization.
  • Distribute the "Test Participant Invitation" check list.
  • Send invitations to customers.

How Do We Test the Application?

  • Decide on a focus for your User Day. Create a list of focus questions.
  • Select suitable testing methods depending on the development status and focus questions (design concept, application structure, interface design).
  • Establish which PC(s) or system(s) will be used for the User Day or who will create the paper prototypes.
  • Establish who is responsible for the creation tasks and for inputting the required data in the system.
  • Define a deadline for the creation of tasks.

 

Source:  User Day Toolkit