Skip to content
Technologies · Year 8

Active learning ideas

Feedback and Affordances in UI

Active learning works because students need to experience how feedback and affordances shape user behavior directly. When students touch a vibrating button or hear a confirmation sound, they grasp design intent faster than with theory alone.

ACARA Content DescriptionsAC9TDI8P05
20–40 minPairs → Whole Class4 activities

Activity 01

Case Study Analysis25 min · Pairs

Pair Prototyping: Feedback Redesign

Pairs sketch a simple app button with no feedback, then one partner 'tests' by mimicking taps and describing confusion. Switch roles, add visual or auditory cues, and retest. Discuss improvements in effectiveness.

Explain how effective feedback improves user interaction and reduces errors.

Facilitation TipDuring Pair Prototyping: Feedback Redesign, have partners alternate between tester and designer roles every two minutes to keep both perspectives active.

What to look forProvide students with screenshots of two different app interfaces. Ask them to identify one example of a clear affordance and one example of effective feedback in each interface, explaining why they are effective.

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

Activity 02

Case Study Analysis40 min · Small Groups

Small Group Hunt: Affordance Analysis

Groups examine classroom devices or apps, list affordances like slider grips or icon shadows, and explain why they work. Design one new affordance for a school app feature. Share findings with class.

Differentiate between different types of feedback (e.g., visual, auditory, haptic).

Facilitation TipIn Small Group Hunt: Affordance Analysis, set a timer for 12 minutes so groups move from observation to discussion quickly.

What to look forStudents create a simple wireframe for a new app feature. They then exchange wireframes with a partner. Partners use a checklist to evaluate: Does the wireframe clearly show affordances for at least two interactive elements? Does it indicate where feedback would be provided? Partners provide one suggestion for improvement.

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

Activity 03

Case Study Analysis20 min · Whole Class

Whole Class Demo: Multi-Modal Feedback

Demonstrate button presses with visual color shifts, claps for audio, and table taps for haptic. Class votes on clarity for different scenarios, like noisy rooms. Brainstorm combined uses.

Design an interface element that clearly communicates its affordances to the user.

Facilitation TipFor Whole Class Demo: Multi-Modal Feedback, prepare three devices with different feedback types switched off and on so students compare side-by-side.

What to look forAsk students to hold up one finger for visual feedback, two fingers for auditory feedback, or three fingers for haptic feedback when you describe a scenario. For example, 'A notification sound plays when you receive a new message.' (Students hold up two fingers).

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

Activity 04

Case Study Analysis30 min · Individual

Individual Sprint: Full Element Design

Each student designs one interface element, specifying affordance and two feedback types. Self-assess against a rubric, then peer review one other's work for intuitiveness.

Explain how effective feedback improves user interaction and reduces errors.

What to look forProvide students with screenshots of two different app interfaces. Ask them to identify one example of a clear affordance and one example of effective feedback in each interface, explaining why they are effective.

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

A few notes on teaching this unit

Teach this topic by making students feel the difference between good and poor design choices. Use live demos where students experience interfaces with missing feedback or unclear affordances, then watch their frustration turn to insight. Avoid lecturing about affordances—let students discover them through frustration and success, which research shows strengthens retention.

Students will identify and apply feedback and affordances in their designs, showing clear understanding through prototypes that guide users intuitively. Success looks like prototypes others can use without explanation, with intentional cues and responses.


Watch Out for These Misconceptions

  • During Pair Prototyping: Feedback Redesign, watch for students who add only visual feedback.

    Have pairs use the blindfold test where one student performs the action while blindfolded, forcing reliance on non-visual cues like sound or vibration.

  • During Small Group Hunt: Affordance Analysis, watch for students who assume affordances must look like physical objects.

    Ask groups to find two examples where digital affordances use motion or scaling instead of realistic imagery, and explain how each suggests interaction.

  • During Individual Sprint: Full Element Design, watch for students who include every possible feedback type.

    Require students to defend each feedback choice in a brief annotation, explaining why it supports the user’s goal rather than just adding features.


Methods used in this brief