Lesson 1, Topic 1

In Progress

Unit 3 – Teacher Guide

Unit 3 Teacher Guide - Teacher Guide | Knowledge Pillars · AWS AI Explorers

📐

At a Glance

Modules: 3.1 - 3.3

50 pts

Capstone Project

Build

Phase

Quiz Q (3.2 + 3.3)

PartyRock

Build Tool

Lines of Code

#	Title	Core Ideas	Interactive Elements	Est. Time
3.1	Community Challenge Project	Pick a real problem Design and build Responsible AI in the build Iterate	Interactive 50-pt rubric Starter ideas Submission checklist	1+ session
3.2	Present and Reflect	Tell the story AI vs judgment Build vs answer tool	Flip cards Knowledge Check (5 Q) Activity: Two-Minute Pitch	~40 min
3.3	Closing Reflection	What you built Your role Keep building	Flip cards Knowledge Check (5 Q) Activity: My Next Step	~20 min

📚 Lesson-by-Lesson Resources

🎯

Lesson Purpose

Lesson 3.2 Purpose: Help students communicate and reflect. The goal is a clear, honest two-minute presentation that names the problem, the approach, the decisions, and crucially what AI did versus what the student decided. Reflection should surface the shift from using AI to building with it.

📖

Learning Objectives

📖 Students will know:

What a clear app presentation includes
The difference between AI's contribution and human judgment
AI as a build tool versus an answer tool
That their skills transfer to other tools

⚡ Students will be able to:

Present an app with a clear story
Name what AI did and what they decided
Reflect on building versus asking
Give specific, useful peer feedback

🔑

Quiz Answer Key: Lesson 3.2

Q1. A good app presentation explains:

The problem, who it helps, and your design decisions

A clear story beats a code walk-through.

Watch for: Common wrong - A: code alone does not explain the why.

Q2. 'What AI contributed versus human judgment' means:

You can say which parts AI generated and which you decided

Honesty about AI's role is responsible practice.

Watch for: Common wrong - A: AI did not do everything; the student decided.

Q3. AI as a build tool versus an answer tool:

Building puts AI inside something you make; answering just replies to you

This is the core mindset shift of the course.

Watch for: Common wrong - A: they are not the same.

Q4. The skills you practiced (prompting, iterating, evaluating):

Transfer to other AI tools and projects

Transfer is the long-term value of the program.

Watch for: Common wrong - A: they are not single-app skills.

Q5. Good peer feedback is:

Specific, kind, and useful

Model this norm before presentations.

Watch for: Common wrong - A/C: vague praise or pure criticism does not help.

💬

Discussion Prompts

AI did, I did

Have each student name one thing AI did and one thing only they could decide. Why does the distinction matter?

Look for: Look for honest, specific attribution and an understanding that human judgment is the responsible core.

What changed

Ask: how is the way you use AI now different from day one?

Look for: Look for the shift from consuming answers to designing and checking a tool.

⚠️

Common Misconceptions

❌

Misconception

"If AI built it, I cannot take credit."

✅

The reality

You chose the problem, shaped the prompts, checked outputs, and decided what shipped. That judgment is the work.

❌

Misconception

"A good presentation needs slides and lots of detail."

✅

The reality

A clear two-minute story with a live demo is stronger than slides full of detail.

🎯

Lesson Purpose

Lesson 3.3 Purpose: Close with agency. Students reflect on how AI could help their community, the role they want to play, and a concrete next step. The message to land is that they are builders now, and that is a choice they can keep making.

📖

Learning Objectives

📖 Students will know:

How AI could help their community
The difference between using and building
That growth comes from continued building
What agency means

⚡ Students will be able to:

Reflect on a community problem AI could help
Choose a role they want to play
Write one specific next step
Articulate that they are a builder

🔑

Quiz Answer Key: Lesson 3.3

Q1. After this course, you are:

A builder who can make AI tools

Name the identity shift explicitly.

Watch for: Common wrong - A: they are more than a user now.

Q2. A strong next step is:

One specific thing you will build or learn

Specific beats vague for follow-through.

Watch for: Common wrong - A: 'use AI more' is not actionable.

Q3. AI could help your community by:

Solving real local problems you care about

Keeps the focus local and meaningful.

Watch for: Common wrong - C: the aim is helping people, not replacing them.

Q4. 'Agency' means:

You can take action and shape what you build

Agency is the core takeaway.

Watch for: Common wrong - A: agency is not waiting for permission.

Q5. The best way to keep improving is to:

Keep building things you care about and checking your work

Reinforces build plus verify as a habit.

Watch for: Common wrong - C/D: copying and avoiding feedback stall growth.

💬

Discussion Prompts

Your next build

Ask each student to name one more community problem and a first step they would take.

Look for: Look for a specific, realistic next step tied to a real problem.

From user to builder

Ask students to finish: 'I am a builder, and next I will...' Share a few aloud.

Look for: Look for ownership and a concrete commitment.

⚠️

Common Misconceptions

❌

Misconception

"The program is over, so I am done with AI."

✅

The reality

This is a starting point. The skills transfer, and the next build is up to them.

❌

Misconception

"Only experts or companies build with AI."

✅

The reality

Students just built a working AI app. Building is open to anyone willing to try and check their work.

📚 Program Alignment

AWS AI Explorers

Student Journey · Part 3: Building with AI

Module 3.1 Community Challenge Project (PartyRock)
Module 3.2 Present and Reflect
Module 3.3 Closing Reflection

The Build and Present phase, ending in the PartyRock capstone.

Project Rubric · 50 pts

Capstone Grading (on the Project page)

Problem and Audience (10)
Design and Build (10)
Responsible AI (10)
Iteration and Testing (10)
Communication (10)

Plus up to 2 bonus points. The interactive rubric on the Project page totals automatically.

🎯 Differentiation Strategies

🌱 Scaffolded Support

For students who need more support

Let students start from one of the starter challenge ideas rather than a blank page
Provide the prompt template they built in Unit 2 to reuse in the app
Offer a fill-in presentation outline for Lesson 3.2

📘 Core Pathway

For most students

Build a functional PartyRock app for a self-chosen community challenge
Run a responsible-AI checkpoint mid-build
Present with the two-minute structure and complete the self-assessment rubric

🚀 Extension Challenges

For students ready for more

Add a second iteration or extra feature that serves more people
Build both a Flow and an App version
Write a short reflection on the app's limits and who it might exclude

📅 Pacing Guide

Lesson	Self-Paced	Camp / Cohort	Key Checkpoint
3.1 Project (PartyRock)	Self-paced build, 1+ session	Main build session with check-ins at start, midpoint, and end	Working app; responsible-AI check done; ≥ 30/50
3.2 Present and Reflect	~40 min	Presentations with structured peer feedback	Two-minute pitch delivered; feedback given
3.3 Closing Reflection	~20 min	Short reflection and next-step commitment	A specific next step written

📌 Facilitator tip: Time-box the build and run a responsible-AI checkpoint before any team presents. The Project page has the full interactive rubric; have students self-assess on it before they present.

❓ Facilitator FAQ

Can students use a starter idea instead of their own?+

Yes. The Project page lists starter community-challenge ideas. A self-chosen, cared-about problem is stronger, but starters are fine for students who need a launch point.

How strict should I be on the responsible-AI category?+

Hold the line here, it is the heart of the program. A working app that ignores bias, verification, or who it serves should not score full marks. Use it as a teaching moment and allow a quick revision.

What if a student's app is very simple?+

Simple and finished beats ambitious and broken. Score on whether it genuinely helps someone and meets the rubric, not on complexity.

Do students need coding skills for the project?+

No. PartyRock is no-code. Students build by describing what they want, which is why prompting from Unit 2 matters so much here.

How do the two lesson quizzes work?+

Lessons 3.2 and 3.3 each have a 5-question Knowledge Check with instant feedback. The Project (3.1) is graded with the interactive rubric on the Project page, not a quiz.