Technologies · Year 10

Active learning ideas

Introduction to Human-Computer Interaction (HCI)

Active learning works for HCI because students need to experience frustration, discovery, and redesign firsthand. When students test real apps, prototype interfaces, and role-play different users, they confront misconceptions about design that passive lessons cannot. This hands-on approach builds empathy and technical reasoning simultaneously, which is essential for user-centered problem solving.

• ACARA Content Descriptions
• AC9DT10P03

• 25–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Think-Pair-Share
• 35 min · Pairs

Pair Critique: Everyday App Testing

Pairs select a common app or website. One student completes tasks like 'find settings' while the partner observes and notes frustrations without helping. Switch roles, then share findings and suggest fixes in a class gallery walk.

Explain the significance of user-centered design in software development.

Facilitation Tip

During Pair Critique, ask students to focus on one task each partner completes, such as logging in, to ground observations in real user actions.

What to look for

Present students with screenshots of two different app interfaces for the same task (e.g., saving a document). Ask them to identify one element in each interface that follows good HCI principles and one that could be improved, explaining their reasoning.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 02

• Think-Pair-Share
• 50 min · Small Groups

Small Group Prototype: Redesign Challenge

Groups sketch wireframes for a school app dashboard using paper and markers. Test prototypes with another group for usability, record feedback on sticky notes. Iterate designs based on peer input in a second round.

Analyze common frustrations users experience with poorly designed interfaces.

Facilitation Tip

For Small Group Prototype, provide sticky notes for rapid iteration so students feel safe discarding ideas that don’t work.

What to look for

Pose the question: 'Think about a time you encountered a frustrating digital interface. What specific design choices made it difficult to use? How could a user-centered approach have prevented these issues?' Facilitate a class discussion where students share examples and potential solutions.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 03

• Think-Pair-Share
• 40 min · Whole Class

Whole Class Demo: Good vs Bad Interfaces

Project screenshots of poor and effective interfaces. Class votes on frustrations via polls, discusses patterns like navigation consistency. Students then pair to redesign one bad example on shared slides.

Differentiate between good and bad user interaction patterns.

Facilitation Tip

In Whole Class Demo, freeze the interface on moments where users hesitate to highlight cognitive load issues.

What to look for

Provide students with a scenario: 'You are designing a new feature for a school's learning management system.' Ask them to write down two key questions they would ask potential users to ensure the feature is user-friendly and accessible.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 04

• Think-Pair-Share
• 25 min · Individual

Individual Reflection: User Journey Map

Students map a personal task on a device, noting pain points and ideal flows. Share one insight with a partner for validation. Compile class maps to identify common HCI issues.

Explain the significance of user-centered design in software development.

Facilitation Tip

During Individual Reflection, prompt students to annotate their User Journey Maps with times they felt confused or confident.

What to look for

Present students with screenshots of two different app interfaces for the same task (e.g., saving a document). Ask them to identify one element in each interface that follows good HCI principles and one that could be improved, explaining their reasoning.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

A few notes on teaching this unit

Teachers should model how to observe without judgment during usability testing, because students often assume their own preferences are universal. Research shows that novices benefit from structured critique frameworks, so provide sentence stems like, 'This button confuses users because...' to move beyond vague complaints. Avoid letting discussions drift into aesthetics only—always tie feedback to task efficiency or error reduction.

Successful learning looks like students justifying design choices with evidence from user testing, not just stating opinions. They should critique interfaces by naming specific HCI principles and propose improvements based on user needs. By the end, students will articulate why some designs fail certain users while others succeed.

---

Watch Out for These Misconceptions

• During Pair Critique, watch for students who assume their own preferences represent all users.

  Use this activity to redirect students by asking, 'What evidence do you have that others find this intuitive?' Have them plan a quick usability test with a partner to gather data.

• During Small Group Prototype, watch for students who prioritize visual appeal over function.

  During prototyping, assign roles: one student must complete a task in under 30 seconds using only the interface, forcing the team to focus on usability metrics.

• During Whole Class Demo, watch for students who generalize about 'bad design' without considering user diversity.

  Use this activity to highlight specific personas. For example, ask, 'How would a color-blind user interpret this error message?' to shift focus to inclusive design.

---

Methods used in this brief

• Think-Pair-Share