Skip to content
Computer Science · 9th Grade

Active learning ideas

Designing Engaging Software Demonstrations

Active learning works for this topic because software demonstrations demand performance skills that cannot be acquired through passive instruction. Students must practice thinking from an audience’s perspective, which requires live interaction and immediate feedback that only active methods can provide.

Common Core State StandardsCSTA: 3A-IC-27CSTA: 3A-AP-23
15–50 minPairs → Whole Class4 activities

Activity 01

Case Study Analysis25 min · Individual

Case Study Analysis: What Makes a Demo Memorable?

Show the class two short (two-minute) software demonstration videos -- one feature-by-feature walkthrough, one narrative-driven demo. Students individually list three specific differences between the approaches. Class builds a shared rubric of effective demonstration elements based on observations.

Analyze what makes a software demonstration engaging and effective.

Facilitation TipFor the Analysis activity, ask students to compare two demos: one that lists features and one that tells a story about solving a problem.

What to look forStudents pair up and present their draft demonstration scripts to each other. Partners provide feedback using a checklist: Does the demo start with a clear user problem? Does it show the software solving that problem? Is the final value clear? Are there at least two specific features demonstrated?

AnalyzeEvaluateCreateDecision-MakingSelf-Management
Generate Complete Lesson

Activity 02

Think-Pair-Share15 min · Pairs

Think-Pair-Share: Demo Story Structure

Partners draft a two-sentence story arc for a demo of a hypothetical school scheduling app: what is the user's problem, and how does the product solve it visibly? Pairs share their story arcs and class votes on which framing would be most compelling to a school administrator.

Design a compelling demonstration for a software product.

Facilitation TipDuring Think-Pair-Share, have students sketch a simple three-part storyboard (problem, solution, value) before sharing with partners.

What to look forAfter analyzing examples of software demonstrations, ask students to write down three specific elements that made a particular demo engaging. Collect these responses to gauge understanding of effective demonstration techniques.

UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson

Activity 03

Gallery Walk50 min · Small Groups

Demo Design Sprint

Groups of three design a three-minute demo script for their current class project. The script must include: an opening problem statement, a live demonstration sequence with narration, and a closing statement about the value delivered. Groups rehearse once and present to another group for feedback using the class rubric.

Evaluate different presentation techniques for showcasing software features.

Facilitation TipIn the Demo Design Sprint, provide a template with sections for problem statement, feature demonstration, and anticipated audience questions.

What to look forStudents receive a prompt: 'Imagine you are demonstrating a new note-taking app. Write one sentence describing the user problem your app solves and one sentence describing how you would show the app solving it.'

UnderstandApplyAnalyzeCreateRelationship SkillsSocial Awareness
Generate Complete Lesson

Activity 04

Gallery Walk35 min · Small Groups

Presentation Technique Showcase

Assign each group one presentation technique to demonstrate for 90 seconds: live demo with narration, screen recording with voiceover, slide-supported walkthrough, or audience-interactive demo. After each showcase, class evaluates which technique works best for which audience type and project complexity.

Analyze what makes a software demonstration engaging and effective.

Facilitation TipDuring the Presentation Technique Showcase, assign each student to spotlight one specific technique (e.g., pacing, visuals, transitions) to observe and give feedback on.

What to look forStudents pair up and present their draft demonstration scripts to each other. Partners provide feedback using a checklist: Does the demo start with a clear user problem? Does it show the software solving that problem? Is the final value clear? Are there at least two specific features demonstrated?

UnderstandApplyAnalyzeCreateRelationship SkillsSocial Awareness
Generate Complete Lesson

A few notes on teaching this unit

Experienced teachers approach this topic by treating demonstrations as performances, not explanations. They model rehearsal behaviors, normalize technical failure as part of the design process, and insist on narrative clarity over feature volume. Research suggests that students retain these skills best when they repeatedly practice with low-stakes feedback before refining for polished presentations.

Students will demonstrate an understanding of narrative structure in demos, use focused feature selection, and prepare contingency plans for technical issues. Peer feedback and quick checks will reveal their ability to craft value-driven presentations rather than feature lists.


Watch Out for These Misconceptions

  • During the Analysis activity, watch for students describing a good demo as one that lists all features clearly.

    Direct students to compare a feature list with a demo that frames those features within a user problem. Ask them to highlight where the narrative creates value and where it simply enumerates functions.

  • During the Demo Design Sprint, some students may assume live demos must proceed without preparation for bugs.

    Have students script a recovery plan for their demo, including fallback steps and exact words to say if a feature fails. Review these plans during the sprint to normalize contingency thinking.

  • During Presentation Technique Showcase, students might think longer demos are more impressive.

    Use the showcase to time each student’s segment and ask the class to discuss why concise, focused demonstrations felt more impactful than extended ones.


Methods used in this brief