Skip to content
User Experience and Human Centered Design · Term 4

Prototyping and Iteration

Using low fidelity and high fidelity prototypes to test ideas and gather user feedback early in the design cycle.

Need a lesson plan for Technologies?

Generate Mission

Key Questions

  1. Why is it better to fail early with a paper prototype than late with a finished product?
  2. How do we incorporate user feedback without losing the original vision of the project?
  3. What is the minimum viable product for this specific user problem?

ACARA Content Descriptions

AC9DT10P04AC9DT10P07
Year: Year 10
Subject: Technologies
Unit: User Experience and Human Centered Design
Period: Term 4

About This Topic

Prototyping and iteration guide students through creating low-fidelity prototypes, such as paper sketches or cardboard models, to test ideas quickly and collect user feedback. They progress to high-fidelity versions, like digital wireframes, refining based on responses. This approach addresses key questions: why paper prototypes allow early failure over late product disasters, how to integrate feedback while preserving project vision, and what defines a minimum viable product for user problems. It aligns with AC9DT10P04 for producing designed solutions and AC9DT10P07 for evaluating design processes in the Australian Curriculum.

In the User Experience and Human-Centered Design unit, students develop empathy by simulating user interactions, critical thinking through feedback analysis, and resilience via repeated revisions. These skills mirror professional practices in app development and product design, fostering adaptable problem-solvers ready for collaborative tech environments.

Active learning excels with this topic because students build tangible prototypes, role-play users, and conduct peer reviews. These hands-on cycles make abstract iteration concrete, increase motivation through visible progress, and deepen understanding of user-centered principles.

Learning Objectives

  • Critique the effectiveness of low-fidelity prototypes in identifying usability issues.
  • Design a high-fidelity prototype that incorporates user feedback to improve a digital interface.
  • Compare the iterative design process using low-fidelity versus high-fidelity prototypes.
  • Evaluate the trade-offs between speed of iteration and fidelity of representation in prototyping.
  • Synthesize user feedback into actionable design changes for a minimum viable product.

Before You Start

Design Thinking Principles

Why: Understanding empathy and ideation is foundational to effectively using prototypes for user testing.

Introduction to User Interface (UI) and User Experience (UX)

Why: Students need a basic understanding of what makes a digital product easy and enjoyable to use before they can prototype and test it.

Key Vocabulary

Low-fidelity prototypeA preliminary, simple representation of a design, often made with paper, pen, or basic digital tools, used for quick testing of core concepts.
High-fidelity prototypeA detailed and interactive representation of a design that closely mimics the final product's appearance and functionality, used for testing usability and user flow.
IterationThe process of repeating a design cycle, making improvements based on feedback and testing, to refine a product over time.
User feedbackInformation and opinions gathered from potential users about a product or design, used to identify areas for improvement.
Minimum Viable Product (MVP)The version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort.

Active Learning Ideas

See all activities

Real-World Connections

App developers at Google use low-fidelity wireframes to sketch out new features for Android apps, sharing them internally for rapid feedback before investing in detailed design.

Product designers at Dyson create numerous cardboard and 3D-printed prototypes of vacuum cleaners and fans, testing ergonomics and airflow with potential customers before mass production.

UX designers for online banking platforms build interactive high-fidelity prototypes of new features, allowing users to click through simulated transactions to identify any confusing steps.

Watch Out for These Misconceptions

Common MisconceptionPrototypes must look professional from the start.

What to Teach Instead

Low-fidelity prototypes prioritize function over polish to test ideas cheaply. Hands-on paper testing reveals flaws early, and peer feedback sessions help students see that rough starts save time, building confidence in iterative processes.

Common MisconceptionUser feedback requires changing every suggestion.

What to Teach Instead

Prioritize feedback aligned with core vision and user needs. Group discussions during feedback carousels teach students to sort and justify changes, balancing input without derailing the project.

Common MisconceptionIteration happens in a straight line after one test.

What to Teach Instead

Design is cyclical with multiple feedback loops. Role-playing user tests in pairs shows the value of repeated cycles, helping students internalize that ongoing refinement leads to stronger solutions.

Assessment Ideas

Quick Check

Present students with two different paper prototypes for the same app feature. Ask them to identify one advantage and one disadvantage of each prototype for gathering user feedback, and to explain which they would choose for initial testing.

Peer Assessment

Students present their low-fidelity prototype to a small group. Peers act as users, providing feedback on clarity and functionality. The presenter then lists two specific changes they will make based on the feedback received.

Exit Ticket

Ask students to define 'iteration' in their own words and explain why it is crucial in the design process. They should also state one key difference between a low-fidelity and a high-fidelity prototype.

Ready to teach this topic?

Generate a complete, classroom-ready active learning mission in seconds.

Generate a Custom Mission

Frequently Asked Questions

What is the difference between low-fidelity and high-fidelity prototypes?
Low-fidelity prototypes use simple materials like paper or cardboard to test core concepts and user flows quickly with minimal effort. High-fidelity ones employ digital tools for detailed, realistic interactions closer to the final product. Starting low allows early feedback to guide refinements, reducing waste, as students experience in paired testing activities.
Why prototype early in the design process?
Early prototyping with low-fidelity models catches issues before heavy investment in coding or building. It answers the question of failing fast: paper tests reveal usability problems cheaply. Students learn this through gallery walks where peer input drives iterations, mirroring real UX workflows.
How can active learning help students master prototyping and iteration?
Active learning engages students by having them build, test, and revise prototypes hands-on, such as in feedback stations or pair role-plays. This makes cycles tangible, boosts collaboration, and shows real impact of changes. Collaborative critiques build skills in giving and using feedback, leading to deeper retention and enthusiasm for design thinking.
How do you incorporate user feedback without losing project vision?
Categorize feedback by impact on user needs versus nice-to-haves, then decide changes that align with original goals. Students practice this in class pitches, justifying choices to peers. This method, rooted in AC9DT10P07, teaches balanced iteration while maintaining focus.