Skip to Content

Instructor Training and Support

Hand off the course package and support instructor training so instructors can run the simulation, not just deliver content.

What you need before starting

  • QA approved; final assets, facilitator guide, simulation support materials.
  • Instructor support templates and timeline (e.g. 30 days before cohort start).

What you need to produce

Implementation handoff: final assets, instructor-facing materials, Canvas setup notes, simulation support assets (FG, stand-up prompts, KPIs), known issues and escalation contacts. Training scheduled; materials in place.

What to do

  1. Assemble implementation handoff package (see Reference).
  2. Deliver at least 30 days before cohort start; begin Canvas build.
  3. Schedule instructor onboarding and course walkthrough.
  4. Share facilitator guide and simulation materials; clarify daily routines (stand-up, monitoring, coaching).
  5. Finalize Canvas by Week -1; support Day 1 launch.
Canvas setup checklist (step 5)

Before handoff, the delivery lead must confirm:

  • Modules and content are published in correct order
  • Assessments configured with rubrics and due dates
  • Group discussions set up for team-based activities
  • External tools (Google Drive, labs, forms) integrated and tested
  • Permissions and grade posting settings confirmed
  • Instructor-only content hidden from students

Exit criteria

Implementation handoff is complete when: package delivered; training scheduled; Canvas setup in progress or done; instructors have materials and know how to facilitate the simulation.

Common mistakes

  • Instructor gets the course but not the why behind the simulation (train on facilitation, not just content).
  • Canvas setup is technically correct but instructionally weak (routines, prompts, visibility).
  • Daily routines (stand-up, retros, KPIs) not visible or clear enough for instructors to follow.

What must be ready in Canvas before instructor handoff?

  • Select an answer to view feedback.

Instructor support

Launch timeline

Course Delivery Timeline

Minimum Delivery Deadline

  • All course materials must be finalized and delivered at least 30 days before the cohort start date.
  • Allows time for Canvas setup, instructor onboarding, simulation training, QA review, and technical alignment.

Launch Preparation Timeline

  • Week -4 (Minimum) — Course Delivery Handoff: All module content, labs, assessments, and slide decks submitted; QA review completed via PS ID Companion; course marked 'Ready for Implementation'; Canvas build process begins.
  • Week -2 — Instructor Preparation: Instructor assigned and onboarded; course walkthrough completed; instructor materials reviewed.
  • Week -1 — Final Canvas Setup: Canvas shell finalized and tested; all modules, assignments, discussions, and groups published or scheduled; learner teams assigned; kickoff slides and welcome messages posted.
  • Day 1 — Course Launch: Simulation introduction delivered; learner teams formed or activated; first stand-up initiated; instructor begins daily facilitation cycle.

Instructor daily routines and facilitation tips

Daily routines:

  • Morning Kickoff: Post or deliver a short scenario-framing message (2-3 mins)
  • Monitor Canvas Discussions: Review stand-ups, retros, and team threads
  • Active Coaching: Join discussions or labs; guide through questions
  • Progress Tracking: Use a KPI tracker or instructor log to capture team progress and blockers

Facilitation best practices:

  • Active Listening: Watch for team conflicts, blockers, or disengagement
  • Socratic Questioning: Lead with questions to encourage learner decision-making
  • Simulation Anchoring: Tie all activity back to the role or workplace task
  • Normalize Challenge: Encourage learning from mistakes and reflection
Common challenges and instructor responses

  • Learner disengagement: Prompt check-ins, adjust simulation pacing, re-engage in stand-up discussions
  • Simulation goes off-track: Re-anchor scenario in Canvas or live, clarify expectations
  • Missed assignments: Identify root cause, support time management, scaffold next deliverable
  • Curriculum bugs or clarity questions: Respond to Canvas tickets from learners — address broken links, unclear instructions, or content issues
  • Technical issues in Canvas: Follow internal escalation process or contact LMS support
  • Instructor support — training requirements and templates
  • Reference — handoff package
  • Canvas Course Shell (pre-built or duplicated)
  • KPI Tracker (Google Sheet or Airtable template)
  • Scenario Kickoff Slides (per module)
  • Facilitation Guide (timing, coaching tips, and red flags)
  • PS ID Companion  — used during development and for final QA

Next step

EvaluationCollect feedback, log changes, and improve curriculum for the next cohort.

Last updated on