Technologies · Year 9

Active learning ideas

High-Fidelity Prototyping

Active learning works for high-fidelity prototyping because students must experience the gap between intention and interaction firsthand. By building and testing mockups, they confront real usability issues, which builds durable understanding of design constraints and user needs.

• ACARA Content Descriptions
• AC9DT10P06

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

Activity 01

• Project-Based Learning
• 40 min · Pairs

Pairs: Figma Prototype Build

Pairs select a simple app interface, such as a weather app, and recreate it in Figma with interactive elements like buttons and navigation. They apply visual hierarchy using color, size, and spacing. After 20 minutes, pairs swap prototypes for 10-minute usability tests, noting issues.

Justify why it is beneficial to fail early in the prototyping phase.

Facilitation Tip

During the Figma Prototype Build, circulate to ensure pairs are balancing aesthetics with functional interactivity, not just adding visual polish.

What to look for

Students swap high-fidelity prototypes. Ask them to identify one element that is unclear or difficult to interact with and explain why. Then, they should suggest one specific change to improve it, referencing visual hierarchy principles.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 02

• Project-Based Learning
• 45 min · Small Groups

Small Groups: Usability Testing Circuit

Divide class into groups of four; set up three testing stations with sample prototypes. Each station focuses on one aspect: navigation flow, visual appeal, or error handling. Groups rotate every 10 minutes, collect feedback data, and suggest iterations.

Analyze how visual hierarchy influences user interaction with a screen.

Facilitation Tip

In the Usability Testing Circuit, set a strict 5-minute timer per test to force concise feedback and prevent over-explaining during trials.

What to look for

On an index card, have students write: 1) One reason why failing early in prototyping is beneficial. 2) One example of how visual hierarchy helped them navigate their own prototype. 3) One question they have about design systems.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 03

• Project-Based Learning
• 30 min · Whole Class

Whole Class: Design System Showdown

Project two prototypes on screen: one using a consistent design system, one with unique layouts. Class votes on usability via polls, discusses pros and cons in a guided debate, then refines a shared prototype collaboratively.

Compare the benefits of using a design system versus unique layouts.

Facilitation Tip

During the Design System Showdown, assign roles so every group member contributes to the comparison and debate, not just the confident speakers.

What to look for

Present students with two versions of a simple screen layout: one with a clear visual hierarchy and one without. Ask them to quickly sketch or describe which one is easier to understand and why, focusing on element placement and size.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

Activity 04

• Project-Based Learning
• 25 min · Individual

Individual: Iteration Sprint

Students receive peer feedback on their prototype, then spend 15 minutes iterating one key change, such as improving visual hierarchy. They document before-and-after screenshots and rationale in a shared class folder.

Justify why it is beneficial to fail early in the prototyping phase.

Facilitation Tip

In the Iteration Sprint, remind students to document each change with a timestamp and brief rationale to track their design decisions.

What to look for

Students swap high-fidelity prototypes. Ask them to identify one element that is unclear or difficult to interact with and explain why. Then, they should suggest one specific change to improve it, referencing visual hierarchy principles.

• Apply
• Analyze
• Evaluate
• Create
• Self-Management
• Relationship Skills
• Decision-Making

A few notes on teaching this unit

Teach prototyping as a cycle of building, testing, and reflecting rather than a linear task. Use analogies students know, like debugging a video game level before the final release or editing a draft essay. Avoid letting students treat prototypes as polished products; frame them as disposable tools for learning. Research shows that students learn iteration best when they see the immediate impact of small changes on user experience, so prioritize frequent, low-stakes testing over long build phases.

Successful learning looks like students confidently testing prototypes, identifying usability flaws, and iterating based on evidence rather than assumption. They should articulate how visual hierarchy and design systems influence user behavior and explain why early failure is a productive step in the design process.

---

Watch Out for These Misconceptions

• During the Figma Prototype Build, watch for students treating their mockup as a final product by adding unnecessary details or animations.

  Redirect by asking, 'What user problem are you trying to solve with this element?' and challenge them to remove anything that doesn’t directly support the task flow.

• During the Usability Testing Circuit, watch for students assuming that one failed test means their entire prototype is 'bad.'

  After each test, ask the student to summarize what the tester could do easily and where they hesitated, then focus on fixing only those specific issues.

• During the Design System Showdown, watch for students equating 'consistency' with 'boring' layouts.

  Have groups present screens side-by-side and time how long it takes a new user to complete a task on each, making the functional benefit of consistency visible.

---

Methods used in this brief

• Project-Based Learning