Week 1 Tutorial Plan — Facilitator Guide

Foundations of AI in Business · 2 hours · connected classrooms (MY + AU)

Audience: students who have watched the Week 1 lecture and done the pre-class reading (flipped model — do not re-teach the lecture). Co-teaching: two leads (one per campus, or two in-room). Roles below as Lead A (drives the room/agenda) and Lead B (drives the chat, breakouts, and cross-campus parity). Swap each week. You need: slides.pptx (recap slides), activity_slides.pptx projected during the activity (advance through it as students progress — it carries the stack reference, the six scenarios, and the reveal-at-the-end answer key), printed or shared class_activity.md worksheet, the Assessment 1 brief open, Google Meet with breakout rooms pre-created, a shared timer on screen.

Cross-campus note. MY and AU students share this tutorial. Every breakout room should be mixed-campus where rosters allow. Lead B owns Meet: admitting students, opening breakouts, and making sure the AU room isn't talked over by the MY room (and vice-versa). Put one instruction on screen at all times so a student who drops and rejoins always knows what to do.

At a glance

Time	Segment	Lead	Mode
0:00–0:10	Welcome + icebreaker	A	Whole class
0:10–0:30	Recap of the three acts (interactive, not a re-lecture)	A & B	Whole class
0:30–1:30	"Spot the AI" activity (Parts A–C)	B drives breakouts	Teams
1:30–1:50	Debrief + answer key + the 6% lesson	A	Whole class
1:50–2:00	Assessment 1 walkthrough + this week's to-do	A & B	Whole class

0:00–0:10 — Welcome + icebreaker (Lead A)

60-second unit welcome: "This is the unit where you build a real AI product. Today is the map."
Icebreaker (whole class, fast): "In the chat / on a sticky, name one AI tool you actually used this week." Lead B collates the chat live; Lead A reads out 5–6 and tags each with a stack layer on the fly ("Spotify recs — classical ML; ChatGPT — foundation model…"). This warms up the exact skill the activity drills.
Set the norm out loud: "This room runs on disagreement. If you think someone's wrong, say so — politely. That's the learning."

0:10–0:30 — Recap of the three acts (Lead A & B, interactive)

Do not replay the lecture. Instead, pull the answers out of the room using the recap slides: - Act I — the stack. Lead A shows the stack slide blank-ish and asks the room to fill the five layers + "none." Cold-call gently; Lead B seeds the chat for quieter/AU students. - Act II — five eras. One question only: "Why is everyone losing their minds about AI now and not in 2016?" Target answers: ChatGPT made it usable by anyone (Nov 2022); cost fell ~280×; you talk to it in plain English. 3 minutes, no more. - Act III — the puzzle. Put up "88% adopt / ~6% capture significant value" and ask: "Why the gap?" Land the one-sentence answer: the bottleneck isn't the tech, it's redesigning the work, governance, and the boring plumbing. This sentence is the spine of the activity debrief — flag that you'll return to it.

[HAND-OFF] Lead A → Lead B to run the activity.

0:30–1:30 — "Spot the AI" activity (Lead B drives, Lead A floats)

Use class_activity.md. Timing inside the hour: - 0:30–0:35 — Set up. Teams of 3–4, mixed-campus. Lead B opens breakout rooms and drops the worksheet link + the stack reference into each room's chat. Put the Part A instruction on the main screen so it persists. - 0:35–1:05 — Part A (classify the six scenarios). Teams work in breakouts. Both leads rotate through rooms (Lead A through in-room groups, Lead B hops Meet rooms). Prompt, don't answer: "What's the one-line test for that layer? Did a human write the rules, or did the system learn them?" Watch for the two productive traps — Scenario 3 (deep learning, but the explainability worry) and Scenario 6 (it's not AI — AI-washing). Let teams fall into them; that's the lesson. - 1:05–1:20 — Part B (defend & disagree). Pair teams; they argue Scenarios 3, 5, 6. Lead B reopens breakouts as pairs-of-teams. Listen for: does the disagreement survive scrutiny, or did someone misread the tech? - 1:20–1:30 — Part C (bridge to project). Pull everyone back to the main room. Individual 3-minute write (one real annoyance → problem statement → which layer to try first). Then 4-minute team share. Lead A: "That annoyance is a candidate for your Assessment 1. Keep it."

1:30–1:50 — Debrief (Lead A)

Walk the answer key (in class_activity.md) scenario by scenario — but ask the room first, reveal second. Spend most time on Scenario 6 (AI-washing) and Scenario 2 (rules can be the right answer — higher isn't better).
Land the 6% lesson explicitly: "Notice your value calls depended on the problem and the stakes, not on how fancy the AI was. That's the whole game. The ~6% who win are the ones who match the layer to the problem and then do the work around it."
One forward-link: "In Weeks 3 and 4 we'll come back to Scenario 3's 'it can't explain why' — that's the governance problem, and it's why we put ethics early."

1:50–2:00 — Assessment 1 + to-do (Lead A & B)

Lead A: open the Assessment 1 brief on screen. 3-minute orientation: it's individual, due Week 4, 20%, and it starts exactly where today ended — a real problem, the AI landscape, justify your choice with the stack, then a Business Model Canvas (taught next week).
Lead B drops into chat: the brief link, the Week 1 post-class task link, and next week's pre-class link.
Close: "This week — read the Assessment 1 brief, do the post-class task (it feeds your assignment), and next week we turn your annoyance into a business model."

Co-teaching protocol (quick reference)

Lead A owns the clock, the agenda, and whole-class teaching. Lead B owns Meet (admits, breakouts, chat), cross-campus parity, and seeding questions for quieter rooms.
Hand-offs are verbal and explicit ("Over to you, [name], for the activity") so the recording and the room both track the switch.
Parity check every segment: Lead B confirms the remote campus can hear, see the screen, and has the same instruction visible. If AU has been quiet for >5 min, Lead B pulls a name from there.
If tech fails (Meet drops): keep the in-room activity running on the worksheet alone — it's designed to work offline — and Lead B re-establishes the remote link. The activity does not depend on slides.

Contingencies

Few people watched the lecture. Don't re-lecture. Run the icebreaker longer, and use the recap segment to teach the stack from scratch via the activity itself — the six scenarios are the content. Push the lecture as required before Week 2.
Activity runs long. Cut Part B to 5 minutes; protect Part C and the Assessment 1 walkthrough — those feed the graded work.
Activity runs short / strong cohort. Add a 7th scenario from the room: ask a team to describe a real system and have another team classify it live.