Technologies · Year 8

Active learning ideas

Low-Fidelity Prototyping

Active learning works well for low-fidelity prototyping because students need to experience the iterative process firsthand. Building, testing, and revising physical models helps them see why simple sketches save time later, aligning with how designers actually work in the field.

• ACARA Content Descriptions
• AC9TDI8P06

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

Activity 01

• Problem-Based Learning
• 30 min · Pairs

Pairs: Wireframe Swap

Pairs sketch wireframes for a mobile app login screen in 5 minutes, focusing on buttons and flow. They swap sketches with another pair, note one strength and one improvement, then revise their own. Discuss changes as a class.

Justify the use of low-fidelity prototypes in the early stages of design.

Facilitation Tip

During Wireframe Swap, circulate to ensure pairs focus on explaining navigation flows rather than just sharing drawings.

What to look for

Provide students with a scenario: 'You are designing a new feature for a school library app to help students find books.' Ask them to draw a simple wireframe for one screen of this feature and write one sentence explaining why they chose a wireframe over a mockup for this early stage.

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

Activity 02

• Problem-Based Learning
• 45 min · Small Groups

Small Groups: Paper App Prototype

Groups select a simple app feature like a shopping cart, cut paper elements for screens, and connect with folds or tabs to simulate swipes. Test by passing to another group for 2-minute user trials. Iterate based on observations.

Differentiate between a wireframe and a mockup.

Facilitation Tip

For Paper App Prototype, give groups strict time limits for each iteration to mimic real-world pressure and decision-making.

What to look for

Present students with two images: one clearly a wireframe and one a mockup. Ask them to identify which is which and list one key difference they observe. For example: 'Image A is a wireframe because it shows layout and buttons without color. Image B is a mockup because it includes specific colors and fonts.'

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

Activity 03

• Problem-Based Learning
• 25 min · Whole Class

Whole Class: Feedback Gallery Walk

Display all prototypes around the room. Students use sticky notes to add feedback on usability. Return to stations to review notes and prioritize one revision per prototype.

Construct a paper prototype for a simple mobile application feature.

Facilitation Tip

During the Feedback Gallery Walk, provide sentence stems on sticky notes to scaffold constructive feedback.

What to look for

Students create a paper prototype for a simple app feature. In pairs, they present their prototype to a partner, explaining its purpose. The partner then asks one question about the user flow and provides one suggestion for improvement, which the creator records.

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

Activity 04

• Problem-Based Learning
• 20 min · Individual

Individual: Wireframe vs Mockup Match

Provide examples of wireframes and mockups. Students label features, then draw their own wireframe and mockup for the same screen. Share one key difference with a partner.

Justify the use of low-fidelity prototypes in the early stages of design.

Facilitation Tip

In Wireframe vs Mockup Match, assign roles so one student sketches while the other explains differences aloud, reinforcing verbal reasoning.

What to look for

Provide students with a scenario: 'You are designing a new feature for a school library app to help students find books.' Ask them to draw a simple wireframe for one screen of this feature and write one sentence explaining why they chose a wireframe over a mockup for this early stage.

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

A few notes on teaching this unit

Effective teaching blends direct instruction with hands-on practice to show why low-fidelity prototyping matters. Avoid starting with digital tools, as students need to experience the speed and flexibility of paper first. Research suggests this builds better mental models of user-centered design before adding complexity.

Students will confidently explain the purpose of low-fidelity prototypes, distinguish between wireframes and mockups, and use paper models to test and improve design ideas. Their artifacts and feedback will show clear alignment with user needs and design goals.

---

Watch Out for These Misconceptions

• During Wireframe Swap, students may assume wireframes are only for decoration and skip testing navigation flows.

  Circulate during the swap and ask each pair to physically walk through the app flow using their partner’s wireframe, noting where peers hesitate or get lost.

• During Wireframe vs Mockup Match, students might focus only on visuals and miss the purpose of each design stage.

  Have students physically separate their matched pairs into two columns labeled ‘Structure’ and ‘Visuals’ and explain their reasoning aloud before revealing the answers.

• During Paper App Prototype, students may think prototyping comes after all design decisions are made.

  Give groups a two-minute timer before each iteration and remind them to change or remove features based on peer questions, reinforcing that prototypes evolve early and often.

---

Methods used in this brief

• Problem-Based Learning