workshop-handson

Start by defining 3-5 learning outcomes describing what participants will do, then design progressive exercises with clear success criteria. Plan infrastructure and prerequisites early, build a facilitator guide with timing, and run a full dry-run on a clean environment before the event.

Organize teams of 3-5 with mixed skill levels, use a competitive scoring dashboard, and inject failures progressively from easy to hard. Offer a hint system with score penalties and hold a thorough debrief sharing intended solution paths.

An Immersion Day typically runs 4-6 hours with roughly 30% lecture and 70% hands-on labs. Use AWS Workshop Studio for account provisioning and end with a discussion on how the content applies to the participants' own environment.

Plan for at least one helper per 8-10 participants. Helpers should circulate during exercises, watch for confused faces rather than waiting for raised hands, and escalate issues affecting 3 or more people to the whole room.

Exercises often fail due to untested assumptions about operating systems, permissions, or network conditions, and dependencies that were never version-pinned. Always test on a clean machine, provide a pre-check script, and keep a pre-provisioned backup environment ready.