Structured Usability Test

Collaborate observe the interaction between the user and the prototype and gain deeper insights into how to improve and optimize the idea.

Structured Usability Test

Step 1. Planning Phase Begin Planning your test. Define the goal of your test and describe what should be discovered. Map out the chronological sequence of the test. Then, choose the location, assignment of roles, test personas, and measuring devices. Lastly, conduct a dry run of your test to ensure your Structured Usability Testing will succeed.

Step 2. Test Phase After planning your Structured Usability Test, conduct the test with the users. Before conducting the test, make sure you stick to the chronological sequence of the test to ensure each user has the same experience. You can rate the tasks as "success, struggle, or fail" for easier evaluation.

Step 3. Completion Phase Finally, for the Completion Phase, evaluate the finding from your Structured Usability Test. Use the findings to refine and optimize your solution and present results to relevant parties or stakeholders.

Structured Usability Test

Observe the interaction between the user and the prototype and gain deeper insights into how to improve and optimize the idea. Collaborate with your team to plan your test and the procedure and documentation of your results. Collaborate as a team in 2-4 member groups to observe the interaction between the user and the prototype in a defined scenario. Work together to plan the test, determine the testing sequence and how you will evaluate the test. Then, at later date conduct your structured usability test.

Group Size: 2-4

Materials Needed: Structured Usability Testing,Pens, Markers, Video Camera, and Post-its

Duration: 40-90 mins

Structured Usability Test

Conduct a Structured Usability Test to observe the interaction between the user and your prototype through uniform tasks or scenarios. Begin by planning the test and what you aim to discover. Next, conduct the test stick to the uniform scenario and testing sequence. Finally, document and evaluate findings present to stakeholders.

  • Observe the interaction between the user and prototype in a defined task.

    Gain insight from user interactions to improve the prototype.

    Find new ways to optimize your solution.

    Improve the efficiency and usability of your prototype.

  • Collaborate as a team in 2-4 member groups to observe the interaction between the user and the prototype in a defined scenario. Work together to plan the test, determine the testing sequence, and how you will evaluate the test. Then, at a later date, conduct your structured usability test.

  • Step 1. Planning Phase Begin Planning your test. Define the goal of your test and describe what should be discovered. Map out the chronological sequence of the test. Then, choose the location, assignment of roles, test personas, and measuring devices. Lastly, conduct a dry run of your test to ensure your Structured Usability Testing will succeed.

    Step 2. Test Phase After planning your Structured Usability Test, conduct the test with the users. Before conducting the test, make sure you stick to the chronological sequence of the test to ensure each user has the same experience. You can rate the tasks as "success, struggle, or fail" for easier evaluation.

    Step 3. Completion Phase Finally, for the Completion Phase, evaluate the finding from your Structured Usability Test. Use the findings to refine and optimize your solution and present results to relevant parties or stakeholders.

  • Break down your prototype and perform a specific test, testing a specific task.

    Plan the Structured Usability Test and test phase/agenda. Then at a later date, conduct the Structured Usability Test. Perform a dry run with the team to ensure proper procedure.

    Have the user "Think Aloud" as they conduct the specific task and video record the test.

    The level of detail of the prototype should match the test scenario.

    Be sure the individuals within your testing group match your persona.

    Remember, you are testing your solution, not the person.

    Avoid leading questions or demonstrations. Simply document the user mistakes and update your prototype/solution, not the user.

    Document when and where the user gets stuck and ask the user, "What should happen next?"