Practice / Instructional Leadership
πŸ“š Instructional Leadership

Instructional Leadership Toolkit

Instruction is the core work of the school, and the principal is its lead learner. This toolkit brings together the protocols, templates, and routines that make instructional leadership concrete: classroom walkthroughs, observation and feedback, teacher coaching cycles, curriculum monitoring, assessment analysis, professional-learning planning, and the dashboards that keep it all visible.

Research Foundation

Instructional leadership is among the leadership practices most strongly associated with improved teaching and student learning. The protocols below pair frequent, low-inference observation with growth-focused coaching β€” and treat feedback as development, not evaluation. (Research applied to inform practice; scenarios illustrative.)

Instructional Leadership Dashboard

A snapshot of the instructional routines in motion this month.

Walkthroughs this month
0
β–² 18% vs. last month
Coaching cycles active
0
On pace for the term
Feedback turnaround
0
β–² within 48h target
Teachers in a cycle
0
β–² coverage growing

Protocols & Templates

Each protocol is ready to adapt to your context. Click to expand for purpose, steps, and a short worked example.

β–ΈπŸ“‹ Classroom Walkthrough Protocol5–10 min

Purpose: Gather frequent, low-inference evidence of teaching and learning across many classrooms.

Steps: Enter with a focus look-for β†’ observe 5–10 minutes β†’ capture objective evidence β†’ leave a brief affirming note β†’ log to the trend tracker.

Example: "Focus: student talk. Observed 4 classrooms; in 3 of 4, students explained their reasoning to a partner. One room used a turn-and-talk every ~6 minutes β€” shared as a bright spot at the next team meeting."

β–ΈπŸ“ Formal Observation TemplateScheduled

Purpose: Document a full lesson against a clear instructional framework, separating evidence from judgment.

Steps: Pre-conference on goals β†’ script low-inference evidence β†’ align to framework indicators β†’ identify one glow and one grow β†’ debrief.

Example: Evidence column: "T posed an open question and waited 7 seconds." Indicator: Questioning & Discussion β€” proficient. Grow: distribute response opportunities more equitably.

β–ΈπŸ’¬ Feedback Conversation GuideGrowth-focused

Purpose: Turn observation evidence into a supportive, action-oriented conversation.

Steps: Open with the teacher's reflection β†’ name a specific strength β†’ name one high-leverage next step β†’ co-plan the action β†’ set a follow-up date.

Example: "You named the lesson objective three times β€” students could state it. Next step: add a 2-minute checkpoint mid-lesson. Let's revisit in our walkthrough Thursday."

β–ΈπŸ“š Curriculum Monitoring ProtocolMonthly

Purpose: Confirm the intended curriculum is the taught curriculum, with appropriate rigor and pacing.

Steps: Review pacing guides β†’ sample tasks and student work β†’ check alignment to standards β†’ note gaps β†’ plan supports.

Example: A task review showed assignments below grade-level demand in one unit; the team co-planned a stronger culminating task and a rubric exemplar.

β–ΈπŸ“Š Assessment Analysis ProtocolData team

Purpose: Move from data to instructional decisions in a focused team meeting.

Steps: Review the data display β†’ identify a pattern β†’ ask "why?" β†’ name one instructional response β†’ assign owners and a check-in date.

Example: "Inference questions trailed literal questions by 22 points. Response: model think-alouds for two weeks; re-check on the next common assessment."

β–ΈπŸŽ“ Professional-Learning Planning TemplateTerm plan

Purpose: Connect walkthrough and assessment trends to targeted, job-embedded professional learning.

Steps: Name the schoolwide trend β†’ set a measurable learning goal β†’ choose a job-embedded format β†’ embed practice & feedback β†’ measure transfer.

Example: Trend: uneven use of checks for understanding. Plan: 3 PLC cycles with peer observation; success measure is checks observed in 80% of walkthroughs.

Walkthrough Look-Fors

A shared, low-inference lens keeps walkthrough evidence consistent across leaders.

DomainLook-forEvidence (illustrative)
Clarity of learningObjective is posted and students can state it"3 of 4 students named the goal when asked."
Rigor of taskWork matches grade-level demandTask required justification, not recall.
Student engagementStudents do the cognitive workPartner talk every ~6 minutes; high participation.
Checks for understandingTeacher gathers evidence mid-lessonWhiteboard check before release to practice.
Feedback to studentsSpecific, actionable, timely"Add evidence from paragraph 2" written on work.
Climate for learningSafe, respectful, high expectationsErrors treated as learning; warm tone.

The Coaching Cycle

A simple, repeatable cycle keeps coaching focused on one high-leverage move at a time.

  • Step 1
    Pre-conference
    Agree on a single focus and what success will look like. Surface the teacher's own goal.
  • Step 2
    Observation
    Script low-inference evidence tied to the agreed focus β€” no judgment, just what was seen and heard.
  • Step 3
    Feedback
    Lead with reflection, name one strength and one high-leverage next step, and co-plan the action.
  • Step 4
    Follow-up
    Return to see the next step in practice, celebrate progress, and start the next cycle.

Getting Started

  • Block recurring, protected walkthrough time on the calendar.
  • Adopt one shared set of look-fors so evidence is consistent.
  • Commit to a feedback turnaround target (e.g., within 48 hours).
  • Run coaching cycles with volunteers first, then scale.
  • Review walkthrough trends in PLCs and connect them to professional learning.