Lesson Plan Template for Demo Lesson

Standard Operating Procedure: Demo Lesson Plan Architecture & Execution

Document ID: SOP-TR-EDU-409 Effective Date: October 24, 2023 Version: 2.1.0 Review Cadence: Semi-Annual

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the rigorous engineering lifecycle for designing, validating, and executing high-stakes demonstration lessons at Template Registry. The purpose of this document is to eliminate variance in instructional delivery, ensure strict alignment between pedagogical objectives and audience evaluation criteria, and maximize cognitive engagement within constrained deployment windows (typically 15 to 45 minutes). Adherence to this protocol is mandatory for all internal and client-facing instructional prototypes.

---

2. Scope & Prerequisites

2.1 Scope

This SOP applies to all technical trainers, instructional designers, and engineering leads tasked with preparing and delivering a demo lesson for hiring committees, enterprise clients, or internal capability reviews.

2.2 Prerequisites & Tooling

• Hardware: Dual-display workstation or laptop with verified video-out capabilities; universal adapter kit; dedicated presentation clicker.
• Software:
  • Presentation Environment: Keynote, Google Slides, or Markdown-to-Slide engine (Marp).
  • Version Control: Git repository for artifact versioning.
  • Collaboration Suite: Miro or physical whiteboard for interactive artifacts.
• Documentation: Approved institutional Template Registry Lesson Plan Schema (v4.0).
• Environment Configuration: Pre-loaded sandbox environments, cached code repositories, or physical props (no live-coding without a static failover artifact).

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Procedure

Phase 1: Requirements Analysis & Scoping

• 1.1 Extract evaluation rubric parameters from the requesting stakeholder and map criteria to time-box allocations.
• 1.2 Define a single, atomic learning objective (SWBAT: "Students Will Be Able To...") that can be definitively proven within the time constraint.
• 1.3 Conduct audience profiling to determine baseline technical proficiency, cognitive load tolerance, and domain familiarity.

Phase 2: Artifact Generation & Template Integration

• 2.1 Initialize the standard Template Registry Demo Lesson schema within the designated workspace.
• 2.2 Structure the timing breakdown using the 10-20-70 rule: 10% Hook/Context, 20% Direct Instruction/Model, 70% Active Application/Validation.
• 2.3 Draft the formative assessment mechanism (e.g., poll, rapid code review, guided output) to occur at the midpoint and terminal boundary of the lesson.
• 2.4 Build explicit cognitive offloading artifacts (cheat sheets, skeleton code, or summary slides) to mitigate learner fatigue.

Phase 3: Stress Testing & Dry-Run Validation

• 3.1 Execute a dry run in a simulated environment matching the target venue's hardware and network constraints.
• 3.2 Time-box each section strictly; enforce a hard stop rule for the instructional delivery phase to protect the application phase.
• 3.3 Submit draft artifacts to the Peer Reviewer (C) and iterate based on rubric-alignment feedback.

Phase 4: Execution & Post-Mortem

• 4.1 Execute pre-flight environmental checks 15 minutes prior to deployment (AV systems, staging links, asset visibility).
• 4.2 Deliver instruction adhering strictly to the validated timing manifest and engagement protocols.
• 4.3 Capture evaluator feedback immediately post-session and commit the final lesson artifact to the Template Registry repository for future auditing.

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• The "Zero-Latency" Rule: Never introduce a new tool, software interface, or complex syntax without a visual anchor or prior scaffolding. Reduce extraneous cognitive load.
• Redundancy Engineering: Assume live-coding will fail. Maintain fully functional, step-by-step git branches or hidden slides to instantly transition past broken environments.

5.2 Common Pitfalls

• Scope Creep: Attempting to teach a 2-hour curriculum in a 20-minute window. Restrict content to one foundational competency.
• Monologue Trap: Exceeding 5 consecutive minutes of uninterrupted lecture without an interactive check for understanding (CFU).

5.3 Metric Thresholds

• Time-Box Adherence: Must finish within $\pm 60$ seconds of the allocated target time.
• CFU Success Rate: Target $\ge 80%$ audience comprehension on the primary formative assessment metric before session closure.

---

6. Frequently Asked Questions (FAQ)

Q1: What is the protocol if the primary software environment or sandbox fails mid-demo?
A: Execute the pre-planned failover protocol immediately. Pivot seamlessly to the static backup slides or cached local execution branch without breaking eye contact or apologizing excessively. Acknowledge the anomaly neutrally, demonstrate the recovery path or explain the expected state, and maintain forward momentum.

Q2: How do we handle an audience member who dominates the Q&A or disrupts the pacing?
A: Acknowledge the input professionally, validate its relevance, and use the parking lot technique: "That is a critical nuance regarding [Topic]; let’s capture that on our parking lot board so we can dedicate proper depth to it during the post-session debrief." Immediately transition back to the structured timeline.