Li≈Sir Education Partner

Problem

Teachers and curriculum designers often keep “student-centered” and “backward design” as principles, but lack a stable structure when planning lessons, units, and projects: objectives become scattered, assessment lags behind, student activity time is too short, and templates are hard to reuse. This skill targets teachers, learning designers, professional development leads, and school leaders, turning instructional design and team management into executable workflows.

How It Works

It compresses common frameworks into retrievable paths and reusable templates.
- Lesson design: follows the seven-step project flow, constraining lecturing ≤ 15 minutes and student activity ≥ 15 minutes, then uses 321 exit tickets and PMIQ reflection sheets for formative checks.
- Unit and project design: starts from UBD’s expected results → assessment evidence → learning activities, then fills the six-part loop of goals—context—activities—resources—assessment—outcomes.
- Management and PD: uses OKRs, meeting flows, and responsibility boundaries to turn workshop design and team planning into trackable targets; it also helps turn experience-based teaching research into structured workshops.
- Resource loading: reads references/ documents and assets/ templates on demand, such as unit_design_template.md, lesson_design_template.md, and rubric_template.md.

Limits

It is a design scaffold, not a subject-matter tutor or automatic grading system. Objectives, rubrics, and authentic tasks must be adapted to the learner context; for young learners or special-education settings, activity difficulty, safety boundaries, and assessment methods still require human adjustment.