Technologies · Year 10

Active learning ideas

Usability Testing and Feedback

Active learning works for usability testing because students must experience the gap between design intent and real user behavior to truly grasp its importance. Watching a peer struggle to complete a task they assumed was obvious creates memorable insights that lectures cannot match.

• ACARA Content Descriptions
• AC9DT10P07

• 30–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Simulation Game
• 45 min · Small Groups

Rotating Roles: Prototype Testing Cycle

Divide class into small groups with roles: designer sketches a simple website wireframe, tester completes tasks, observer notes hesitations without speaking, recorder logs data. Groups rotate roles twice over two prototypes. End with 5-minute debrief per group to share pain points.

Design a usability test plan for a new website feature.

Facilitation Tip

During Rotating Roles, assign each student a clear role script and rotate every 5 minutes so everyone practices both testing and being tested.

What to look for

Provide students with a short video clip of a user interacting with a website prototype. Ask them to write down: 1. One observable user pain point. 2. One potential design improvement based on that pain point. 3. One question they would ask the user after the session.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 02

• Simulation Game
• 30 min · Pairs

Pair Testing: Think-Aloud Protocol

Pairs create a quick paper prototype for a login feature. One acts as user, verbalizing thoughts while navigating tasks; the other observes and asks neutral follow-ups. Switch roles, then discuss adjustments needed based on feedback.

Analyze common pitfalls in conducting usability tests.

Facilitation Tip

In Pair Testing, interrupt gently after 2 minutes to model how to prompt without leading, then let them try again with the new insight.

What to look for

Pose the question: 'Imagine you are testing a new online learning platform. What are two common pitfalls you must actively avoid when observing students and asking them questions?' Facilitate a class discussion, encouraging students to share specific examples of leading questions or biased observations.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 03

• Gallery Walk
• 35 min · Small Groups

Gallery Walk: Feedback Synthesis

Groups post test findings charts from peer prototypes around the room. Students walk the gallery, adding sticky notes with improvement ideas. Regroup to prioritize changes and sketch revised designs.

Evaluate the importance of user feedback in iterative design.

Facilitation Tip

For Gallery Walk, tape feedback sheets at eye level and require each student to add at least two specific suggestions before moving on.

What to look for

Students share their drafted usability test plans with a partner. The partner reviews the plan, focusing on: 1. Clarity of task scenarios. 2. Appropriateness of data collection methods. 3. Potential for observer bias. Partners provide written feedback using a simple checklist.

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Activity 04

• Simulation Game
• 40 min · Whole Class

Whole Class: Mock User Panel

Project a shared prototype screen. Select 5-6 students as 'users' to test tasks live while class observes and tallies issues on a shared board. Discuss patterns and vote on top fixes as a class.

Design a usability test plan for a new website feature.

Facilitation Tip

In Mock User Panel, give observers a checklist of non-verbal cues to watch for, then debrief immediately after each 3-minute test.

What to look for

Provide students with a short video clip of a user interacting with a website prototype. Ask them to write down: 1. One observable user pain point. 2. One potential design improvement based on that pain point. 3. One question they would ask the user after the session.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

A few notes on teaching this unit

Teach this topic by modeling the mindset first. Demonstrate how to observe without interpreting, then gradually release responsibility to students. Avoid the trap of letting students focus only on the prototype's flaws; instead, guide them to notice their own assumptions in the tasks they write. Research shows that structured feedback cycles build deeper understanding than one-off critiques.

By the end of these activities, students should confidently run test sessions, distinguish signal from noise in user feedback, and use findings to refine prototypes with purpose. They will move beyond vague ideas of 'making things better' to systematic problem-solving.

---

Watch Out for These Misconceptions

• During Rotating Roles, students may assume they need a large group to get 'good' data.

  During Rotating Roles, set a timer for each pair to find three issues in their 5-minute test. The rapid cycle shows how small groups reveal patterns quickly, proving five users uncover most problems.

• During Pair Testing, students expect users to articulate every problem clearly.

  During Pair Testing, have observers jot down silent cues like sighs or repeated clicks. After the session, ask observers to share what they noticed that the user did not say aloud, highlighting the gap between stated and actual struggles.

• During Mock User Panel, students think usability testing belongs only at the end of design.

  During Mock User Panel, frame each 3-minute test as a chance to catch issues early. After the session, ask students to revise their prototype notes and mark which flaws they would address first, reinforcing iterative testing.

---

Methods used in this brief

• Simulation Game
• Gallery Walk