Week 9 Tutorial Plan — Industry Engagement and AI Applications
Facilitator guide · 2-hour connected-classroom tutorial (MY + AU) · LO2, LO5
Mapped LOs: LO2 (articulate to stakeholders), LO5 (evaluate deployment).
Hinge: reality contact — an industry guest + "Alpha Lab," where teams run real think-aloud tests on each other's MVPs, triage, and advise. The pitch (Assessment 2) is next week, so everything points there.
Decks: slides.pptx (lecture recap, optional) · activity_slides.pptx (project live through Alpha Lab).
Materials: activity worksheet (class_activity.md), each team's working MVP on a laptop, breakout space, build diaries open. Guest speaker booked (IBM / Grab / Shopee / local AI practitioner) — confirm format below.
Co-teaching: Lead A hosts the guest + frames reality contact; Lead B runs Alpha Lab + the build/pitch bridge. Hand-offs marked [SWITCH]. If no live guest is available, run the "industry advisor" part of Alpha Lab as the substitute (students play the role) and use a recorded talk in pre-class.
Pre-tutorial checklist (5 min before)
- Confirm the guest: arrival time, format (talk + Q&A, or panel, or fireside), and tech (in-room or Meet for cross-campus). Brief them: 15–20 min, focus on real deployment + failures, then student Q&A.
activity_slides.pptx open and projected.- Pair teams in advance for Alpha Lab (Team A ↔ Team B); ensure each has a working MVP and a laptop.
- Build diaries open; have the triage buckets (fix-now/later/won't) visible.
Run sheet (120 min)
1 · Arrival & frame (8 min) — Lead A
- One line: for three weeks you've built; today it meets reality — an industry guest, and real users.
- Put up the spine: a demo is not a product; this week trades opinion for evidence. Name the stakes: the pitch is next week, and "we tested it" wins.
2 · Industry guest (30 min) — Lead A hosts
- Guest talk (~18 min): real AI deployment — what's hard, what failed, what they'd tell a student team. Ask them explicitly to share a failure, not just wins.
- Structured student Q&A (~10 min): teams already prepared two product questions + one failure question (pre-class). Call on a few; model the LO2 skill of translating the guest's answer back into plain language.
- Hold ~2 min for the cross-campus handover and thanks — connected-classroom transitions eat real time.
- No guest? Substitute: play a short recorded practitioner talk (5 min) and extend Alpha Lab Parts 1 and 3 to fill the time.
3 · Mini-recap: how to alpha-test (12 min) — [SWITCH] Lead B
Fast, example-led (slides optional). Land four things only:
- Small / friendly / observed, to find what's broken — not applause.
- The three recruiting traps (cousin / over-friendly / over-broad) → recruit real target users, not family.
- Think-aloud — watch them use it, stay quiet. This is the technique of the week.
- Triage — fix-now / fix-later / won't-fix. End on: "now you'll do all of this, on each other, for real."
4 · Alpha Lab — Part 1: think-aloud swap (20 min) — Lead B, both circulate
- Project activity slides 3–4. Restate the golden rule: observers stay SILENT.
- Pairs run think-aloud sessions both directions (~8 min each). The observing team logs stuck points.
- Leads circulate and enforce silence — the most common failure is teams jumping in to help. Gently stop them: "let them struggle — that's the data." (For AU teams, drop into Meet breakouts.)
5 · Alpha Lab — Part 2: triage (20 min) — both coach
- Project slide 5. Each team sorts the findings about their own product into fix-now / fix-later / won't-fix.
- Coaches push for honesty about severity — "did it block the core task, or is it cosmetic?" Each team writes its top 3 fix-now items.
6 · Alpha Lab — Part 3: advisor swap (20 min) — Lead A
- Project slide 6. Each team gives the other three honest things: the one thing they'd fix, the demo-to-real gap, the trust question.
- Keep it kind, specific, honest. This rehearses the feedback they'll get from real judges next week.
7 · Debrief & pitch bridge (10 min) — Lead B
- Quick round (slide 7): each team names one thing a real user did that surprised them. Reinforce: if nothing surprised you, you watched too gently.
- Bridge to Week 10 (slide 8 + close): the pitch is next week, in class, assessed individually. Post-class = run your own alpha (3–5 users) + write the alpha note + start the pitch. Tell teams to run the alpha early so they can act on it.
- Remind: re-read the Asst 2 brief + rubric; decide who speaks; judges ask live questions — no script-reading.
Cross-campus & co-teaching notes
- Guest logistics: if the guest is on one campus, pipe them over Meet to the other; assign Lead on the remote campus to manage that room's Q&A so it isn't one-sided.
- Pairing: pair MY↔AU teams where the timetable allows — testing across cultural assumptions surfaces richer findings.
- The discipline to protect: silence during think-aloud. It feels rude; it's the whole point. Both leads police it.
- Equity: in Part 3, ensure quieter students deliver at least one piece of advice — it's low-stakes rehearsal for the individually-assessed pitch.
If you're short on time
- Trim the guest Q&A to 5 min; never cut Alpha Lab Part 1 (the think-aloud) — it's the core learning.
- Run Part 3 (advisor swap) as a single round (one direction) if needed.
- Always keep the pitch bridge — Asst 2 is in seven days.
What good looks like (facilitator's eye)
- Observers genuinely stayed silent and have written, specific stuck-points (not "it went fine").
- Each team leaves with a ranked fix-now list and looks slightly rattled — that's reality landing.
- Every team has a pitch plan with named speakers and knows the alpha is the strongest card.
