User Feedback and Iteration

Active learning works for user feedback and iteration because students need to practice speaking about their work in real time, just as they would in a professional setting. These activities push students to refine their message and respond to audience reactions, building communication skills that textbooks alone cannot teach.

• 9th Grade
• Computer Science
• 3 activities
• 20 min–50 min

Learning Objectives

1. Analyze user feedback to identify key areas for software improvement.
2. Design a feedback loop mechanism for a software application that incorporates user input.
3. Evaluate the impact of user feedback on the iterative development of a software project.
4. Explain how user-centered design principles influence Agile development methodologies.

Simulation Game

⏱ 30 min·Pairs

Simulation Game: The 60-Second Elevator Pitch

Students have one minute to explain their software idea to a 'busy executive' (a peer). They must focus on the problem it solves and why it is unique, avoiding overly technical jargon.

Prepare & details

Explain how constant user feedback changes the direction of a project.

Facilitation Tip: During the Elevator Pitch, set a timer and enforce strict time limits so students practice concise communication, simulating a real-world scenario.

Setup: Flexible space for group stations

Materials: Role cards with goals/resources, Game currency or tokens, Round tracker

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Gallery Walk

⏱ 50 min·Whole Class

Gallery Walk: Prototype Demo

Students set up their working software at stations. Half the class acts as 'users' who walk around, try the software, and ask questions, while the other half practices their 'pitch.' Then they switch roles.

Prepare & details

Design a feedback loop mechanism for a software application.

Facilitation Tip: For the Gallery Walk, assign each student a specific role during feedback rounds—speaker, listener, or note-taker—to ensure everyone contributes meaningfully.

Setup: Wall space or tables arranged around room perimeter

Materials: Large paper/poster boards, Markers, Sticky notes for feedback

• Understand
• Apply
• Analyze
• Create
• Relationship Skills
• Social Awareness

Think-Pair-Share

⏱ 20 min·Pairs

Think-Pair-Share: Technical vs. Benefit

Students list three technical features of their app (e.g., 'uses a SQL database'). They pair up to translate those into user benefits (e.g., 'saves your progress automatically').

Prepare & details

Analyze the importance of user-centered design in Agile development.

Facilitation Tip: Use the Think-Pair-Share to explicitly compare technical details with user benefits, helping students distinguish between what they built and why it matters.

Setup: Standard classroom seating; students turn to a neighbor

Materials: Discussion prompt (projected or printed), Optional: recording sheet for pairs

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

Teaching This Topic

Teachers should model clear, concise pitches first and provide sentence stems to support struggling students. Avoid letting students focus on code details or features during presentations; redirect their attention to the user’s problem and the solution’s impact. Research shows that students improve faster when they receive immediate, structured feedback from peers, so keep feedback rounds short and specific.

What to Expect

Successful learning looks like students confidently explaining their software’s value in clear, user-focused terms without relying on technical jargon. They should also demonstrate an ability to listen to feedback and identify actionable improvements for future iterations.

Watch Out for These Misconceptions

Common Misconception

During the Elevator Pitch, watch for students listing features or technical specs instead of explaining the user’s experience.

What to Teach Instead

Stop the pitch at the 30-second mark and ask, 'Who benefits from this, and what problem does it solve?' Have students rewrite their opening line to focus on the user.

Common Misconception

During the Gallery Walk, watch for students assuming their prototype is perfect and dismissing feedback that contradicts their design choices.

What to Teach Instead

Hand out sticky notes with prompts like, 'I noticed...' and 'I wonder if...' to guide feedback. Require each presenter to ask, 'What’s one change you’d make?' before responding.

Assessment Ideas

Discussion Prompt

After the Elevator Pitch, pose the question: 'If your pitch convinced someone to try your app, what are three types of feedback you would prioritize when improving it?' Facilitate a class discussion where students share their ideas and justify their choices.

Quick Check

During the Gallery Walk, provide students with a feedback form that asks, 'What’s one thing you found valuable about this app? What’s one confusing or missing feature?' Collect these to assess whether students can identify actionable feedback.

Peer Assessment

During the Think-Pair-Share, have students use a rubric to evaluate their partner’s explanation of a feature’s benefit. Focus on whether the partner clearly connected the feature to the user’s needs, not the feature’s technical details.

Extensions & Scaffolding

• Challenge: Ask students to revise their pitch script after receiving feedback, then record a final version to compare growth over the unit.
• Scaffolding: Provide a template with fill-in-the-blank sentences like, 'Our app helps [user group] by [solving problem] because [benefit].'
• Deeper exploration: Have students analyze a well-known product pitch (e.g., Apple’s 2007 iPhone launch) and compare its structure to their own.

Key Vocabulary

User Feedback	Information provided by users about their experience with a product or service, used to identify issues and suggest improvements.
Iteration	The process of repeating a process or action, especially in software development, to refine and improve a product based on feedback.
Feedback Loop	A system where the output from one stage is fed back as input to an earlier stage, enabling continuous improvement and adaptation.
User-Centered Design	A design philosophy that puts the user's needs, wants, and limitations at the center of every stage of the design process.
Agile Development	An iterative approach to project management and software development that emphasizes flexibility, collaboration, and customer feedback.