Today

Today you will conduct a user testing session on your current mockups, practice setting up a test and observing without intervening, and reflect on what is working, what is confusing, and what still needs to change.

Goal: You will leave class today having:

1. Filled out the reflection.
2. Formulated a concrete plan of what must be finished in order for us to integrate your screens into the final wireframe.

Part 1 - Conduct the User Testing Session

Set the stage

Tell your tester:

• what role they are playing
• what task or tasks they are trying to accomplish
• that they should think aloud as they work through the screens

Examples:

• “You are a parent trying to complete today’s activities.”
• “You are an admin trying to create a new content block for a module.”

Conduct the test

Watch the user interact with your screens and take notes.

Important:

• do not give hints
• do not explain what the user “should” do
• pay attention to hesitation, confusion, and places where they make incorrect assumptions
• note places where the workflow feels smooth and natural

Part 2 - Write a Reflection

After the test, write a short reflection that includes both your analysis and your next steps.

Respond to these questions in the Weekly Reflection Form:

• Was your user able to complete the tasks? Why or why not?
• What was confusing for the user?
• What do you think worked well?
• What feedback did you get from your team to improve the usability of your mockup?
• Were there any missing screens that still need to be added?
• Is the look and feel professional? Does it look like other apps out there?
• Is your mockup consistent across screens in terms of conventions, variables, components, and overall look and feel?
• What additions or subtractions would make this more intuitive and user friendly?
• How much work is left, and how much time do you think it will take? Please elaborate.

Share-Out

Be ready to share:

• one task your tester tried to complete
• one thing that confused the tester
• one thing that worked well
• one screen or state you still need to add or revise

Definition of Done

When you’re done with your Figma High Fidelity Prototype Feature, the following should be completed

• You have designs for both mobile and desktop (if your feature is admin-only, desktop is enough).
• All important screen states have been created.
• Important screen states may include:
  • Begin
  • Edit
  • Delete
  • Confirmation screen
  • Empty state (if no data exists yet)
  • Error screen

Your work should also meet these expectations:

• The designs match the look and feel of the PowerPoint.
• You are using the Figma variables and components.
• You have created multiple linked screens that communicate the full workflow of your feature.
• If there are important decision points the client needs to evaluate, you have created multiple screens so you can get feedback on those choices.