Final Showcase and DemonstrationActivities & Teaching Strategies
Active learning works for the Final Showcase because students must transfer knowledge from internal planning to external communication. Rehearsals and role-play reveal gaps that silent planning misses, ensuring clarity for real audiences. These activities make the invisible design process visible to both presenters and listeners.
Learning Objectives
- 1Demonstrate the functionality of the designed solution to an audience unfamiliar with the project.
- 2Explain the iterative design process undertaken, including challenges and modifications.
- 3Analyze the most significant technical challenge encountered and the strategies used to overcome it.
- 4Predict potential improvements or extensions for the solution given additional time or resources.
Want a complete lesson plan with these objectives? Generate a Mission →
Rehearsal Rounds: Demo Practice
Teams rehearse their full presentation three times, recording the second on devices for self-review. Peers then provide feedback using a simple checklist on clarity and timing. Teams adjust and perform a final run. This builds fluency step by step.
Prepare & details
Explain how we can best demonstrate our solution to someone who hasn't seen it before?
Facilitation Tip: During Rehearsal Rounds, circulate with a timer to simulate real presentation constraints and build pacing skills.
Setup: Tables or desks arranged as exhibit stations around room
Materials: Exhibit planning template, Art supplies for artifact creation, Label/placard cards, Visitor feedback form
Gallery Walk: Journey Feedback
Each team creates a visual timeline poster of their design process and challenges. Groups rotate to view others' posters, ask two questions, and leave sticky-note suggestions. Teams review feedback and revise their talk scripts accordingly.
Prepare & details
Analyze the most difficult technical challenge we overcame.
Facilitation Tip: For the Gallery Walk, provide sticky notes in three colors so peers can mark strong explanations, confusing moments, and kind suggestions.
Setup: Wall space or tables arranged around room perimeter
Materials: Large paper/poster boards, Markers, Sticky notes for feedback
Mock Audience: Role-Play Switch
Divide class in half: one half presents to the other as 'audience.' Audience members ask prepared novice questions and score on a rubric. Groups switch roles for second round, incorporating prior feedback.
Prepare & details
Predict how we would improve our design if we had more time.
Facilitation Tip: In the Mock Audience activity, assign clear roles such as 'curious parent' or 'technical expert' to push teams to adjust their language.
Setup: Tables or desks arranged as exhibit stations around room
Materials: Exhibit planning template, Art supplies for artifact creation, Label/placard cards, Visitor feedback form
Reflection Carousel: Key Questions
Set up four stations, one per key question. Teams spend 4 minutes per station, discussing and charting responses. Rotate until all addressed, then consolidate into presentation notes.
Prepare & details
Explain how we can best demonstrate our solution to someone who hasn't seen it before?
Facilitation Tip: Use the Reflection Carousel to rotate groups every three minutes so students synthesize ideas from multiple perspectives.
Setup: Tables or desks arranged as exhibit stations around room
Materials: Exhibit planning template, Art supplies for artifact creation, Label/placard cards, Visitor feedback form
Teaching This Topic
Teachers should model how to balance product demonstration with process storytelling, using their own past projects as examples. Avoid over-correcting early rehearsals; instead, let confusion surface naturally so students feel ownership over clarifying their work. Research supports peer feedback as a way to normalize iteration without shame, building resilience before the final event.
What to Expect
Successful learning looks like teams explaining their design journey with confidence, audiences asking questions that show genuine curiosity, and students reflecting on both technical and communication choices. Evidence includes clear demonstrations, balanced narratives, and thoughtful responses to feedback.
These activities are a starting point. A full mission is the experience.
- Complete facilitation script with teacher dialogue
- Printable student materials, ready for class
- Differentiation strategies for every learner
Watch Out for These Misconceptions
Common MisconceptionDuring Rehearsal Rounds, some students think demonstrations only need to show the working product; process details bore audiences.
What to Teach Instead
During Rehearsal Rounds, stop teams after two minutes to ask, 'Did a visitor understand why you built this?' Then replay the feedback, focusing on moments where context was missing.
Common MisconceptionDuring Mock Audience, students believe mentioning challenges or failures weakens the presentation.
What to Teach Instead
During Mock Audience, ask listeners to jot down one obstacle they heard about and one way the team explained overcoming it, reinforcing that struggle is part of innovation.
Common MisconceptionDuring Gallery Walk, teams assume classmates already know the project, so full explanations are unnecessary.
What to Teach Instead
During Gallery Walk, hand out index cards labeled 'I was confused by...' and 'I now understand...' to show teams where their stories missed key details for newcomers.
Assessment Ideas
During Rehearsal Rounds, have teams present to another team and use a checklist: Did the presenting team clearly explain the problem? Did they show how the solution works? Did they mention one challenge? Did the audience team give one specific suggestion for improvement?
After the Gallery Walk, facilitate a class discussion using these prompts: What was the most creative solution you saw today? What made a demonstration particularly clear or confusing? How did explaining your process help you understand it better?
After the Reflection Carousel, students write on an index card: One thing they learned about presenting their work. One technical challenge a classmate overcame that impressed them. One question they still have about another team's solution.
Extensions & Scaffolding
- Challenge students finishing early to create a two-minute 'elevator pitch' version of their presentation for quick transitions.
- Scaffolding for struggling teams: provide sentence starters like 'Our biggest challenge was...' and 'We solved it by...' to structure explanations.
- Deeper exploration: invite teams to research real-world products similar to theirs and note differences in design choices or user needs.
Key Vocabulary
| Demonstration | The act of showing how something works or is done, often to an audience. |
| Iterative Design | A design process that involves repeating cycles of designing, prototyping, testing, and refining. |
| Technical Challenge | A specific problem or difficulty encountered during the design or building process that requires technical knowledge or skill to solve. |
| Audience Analysis | Considering the knowledge, needs, and interests of the people who will be watching or listening to a presentation. |
Suggested Methodologies
More in The Grand Challenge
Deep Dive: Problem Research
Students conduct in-depth research into their chosen problem, gathering data and understanding constraints.
2 methodologies
Brainstorming Solutions for the Challenge
Teams brainstorm a wide range of potential digital or hybrid solutions for their identified problem.
2 methodologies
Planning the Digital Solution
Students plan the sequence of actions (algorithms) and the visual layout (user interface) for their digital solution.
2 methodologies
Developing the Digital Solution
Teams begin coding and building their digital solution using block-based programming or other tools.
2 methodologies
Adding Interactive Elements
Students incorporate interactive elements like buttons, sliders, or simple sensors (if available) to enhance their digital solution.
2 methodologies
Ready to teach Final Showcase and Demonstration?
Generate a full mission with everything you need
Generate a Mission