Computer Science · 9th Grade

Active learning ideas

Basic Input/Output and User Interaction

Active learning works for this topic because input/output design is inherently interactive—students must experience the gap between what a program says and what a user understands. Direct practice with prompts, testing, and output formatting makes abstract concepts concrete, helping students see why clarity matters in real interactions.

• Common Core State Standards
• CSTA: 3A-AP-13

• 15–40 min
• Pairs → Whole Class
• 3 activities

Activity 01

• Think-Pair-Share
• 15 min · Pairs

Think-Pair-Share: Prompt Quality Critique

Show three versions of the same input prompt, ranging from vague to specific. Students individually rank them from best to worst and write one sentence explaining their top choice. Partners compare rankings, then the class discusses which prompt characteristics produce the fewest user errors.

Design a program that prompts a user for input and provides a relevant output.

Facilitation Tip

During Think-Pair-Share, assign specific roles (e.g., prompt critic, user advocate) to ensure all students engage with the quality of the prompt, not just the activity structure.

What to look for

Provide students with a short code snippet that takes input and produces output. Ask them to write down what the output will be for a given input, and identify the prompt and the output statement in the code.

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

Activity 02

• Project-Based Learning
• 35 min · Pairs

User Testing Swap: Blind Program Run

Students write a simple input/output program without showing it to a partner. Partners then use each other's programs without seeing the source code, noting any moments of confusion. They return the feedback and the original author revises the prompts and output labels accordingly.

Evaluate different methods for presenting information clearly to a user.

Facilitation Tip

For User Testing Swap, have students physically cover their screens with paper so they cannot see the code during testing, forcing reliance on the prompt and output alone.

What to look for

Students exchange programs they have written. Each student acts as a user for their partner's program, noting down any confusing prompts or unclear output. They then provide specific feedback to their partner on how to improve clarity.

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

Activity 03

• Project-Based Learning
• 40 min · Small Groups

Design Sprint: Mad Libs Generator

Small groups design and build a Mad Libs-style program that collects user inputs, labels them clearly (noun, verb, adjective), and produces a formatted story. The group must agree on prompts before coding, then test with students outside their group.

Explain the importance of clear instructions for user interaction.

Facilitation Tip

In the Design Sprint, require students to submit a draft Mad Libs template before coding to ensure they focus on prompt design first, not just the fun of the output.

What to look for

Ask students to write one sentence explaining why a clear prompt is more effective than a vague one, and one sentence explaining the purpose of displaying output to the user.

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

A few notes on teaching this unit

Teachers should treat prompt design as a communication skill, not just a coding task. Model how to write prompts by thinking aloud about what a user might misunderstand, and avoid assuming students will intuitively grasp the difference between program logic and user experience. Research shows that students improve faster when they see the consequences of unclear design through user testing, so prioritize real-time feedback over isolated coding exercises.

Successful learning looks like students writing prompts that anticipate user needs, testing programs with real users to spot ambiguities, and designing output that is immediately interpretable without explanation. By the end, students should confidently explain why vague prompts or unlabeled output create user frustration.

---

Watch Out for These Misconceptions

• During Think-Pair-Share: Prompt Quality Critique, students may believe a program can infer user intent even with unclear prompts.

  Use the activity’s prompt critique worksheet to have students rewrite vague prompts like 'Enter value:' and then compare how many correct inputs different users provide. The data from user trials will clearly show the cost of ambiguity.

• During User Testing Swap: Blind Program Run, students may assume output formatting doesn’t affect usability as long as the numbers are correct.

  During the blind run, have students attempt to use their partner’s program without seeing the code. Collect their notes on which outputs required guesswork (e.g., '42' vs. 'Your BMI is 21.3'), then debrief as a class to identify which formatting choices resolved the confusion.

---

Methods used in this brief

• Think-Pair-Share
• Project-Based Learning