Computer Science · 9th Grade

Active learning ideas

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.

• Common Core State Standards
• CSTA: 3A-AP-19
• CSTA: 3A-AP-22

• 20–50 min
• Pairs → Whole Class
• 3 activities

Activity 01

• 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.

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.

What to look for

Pose the question: 'Imagine you've developed a simple note-taking app. What are three specific types of user feedback you would actively seek, and how would you use that feedback to change your app in the next version?' Facilitate a class discussion where students share their ideas.

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

Activity 02

• 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.

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.

What to look for

Provide students with a short, fictional user feedback report for a hypothetical app (e.g., 'Users find the save button hard to locate'). Ask them to write down two specific design changes they would implement based on this feedback and explain why each change addresses the user's concern.

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

Activity 03

• 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').

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.

What to look for

Students pair up and present a simple feature they designed for a hypothetical app. Their partner acts as a user, providing one piece of constructive feedback. The presenter then explains how they would incorporate that feedback into their design. Partners then swap roles.

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

A few notes on teaching this unit

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.

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

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

  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.

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

  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.

---

Methods used in this brief

• Simulation Game
• Gallery Walk
• Think-Pair-Share