The Classroom Walkthrough Problem: It’s Not the Visit, It’s What Comes After
Principals who do frequent classroom walkthroughs see better teaching. The research is clear on this point. But most principals manage to visit each classroom about once a year. The gap between what the research says and what actually happens is not a mystery: the walkthrough itself takes 10 minutes, and the feedback write-up takes two hours. So principals stop doing walkthroughs.
The classroom walkthrough problem is not about getting into classrooms. It is about what happens after you leave. The observation-to-feedback pipeline is broken, and no checklist or protocol can fix it, because the bottleneck is the writing, not the watching.
What the Research Says About Classroom Walkthroughs
Dr. Justin Baeder, author of Now We’re Talking! 21 Days to High-Performance Instructional Leadership, recommends that principals complete three classroom visits per day, roughly 15 per week, totaling about 500 visits across a school year. His research suggests 18 biweekly visits per teacher per year as the target for building strong professional relationships and gathering useful instructional data.
Jane L. David, director of the Bay Area Research Group, synthesized walkthrough research for ASCD and found something worth pausing on: observers consistently reported learning more from walkthroughs than the teachers being observed. In other words, principals benefit from the visit, but teachers often get little from it because they rarely receive meaningful individual feedback.
RAND Corporation research across three urban districts confirmed this pattern. Administrators found walkthroughs useful. Teachers did not, largely because the feedback loop never closed.
The research points in one direction: walkthroughs work when they lead to feedback. They become “drive-bys” when they don’t.
Why Principals Can’t Do More Walkthroughs
If you ask principals why they aren’t in classrooms more, the honest answer is usually time. But it is not the walkthrough itself that takes the time. A 10-minute classroom visit fits between any two meetings. The problem is the unwritten contract: if you walk in, you owe the teacher something back.
That something is usually a written summary of what you observed, aligned to the school or district instructional framework, with specific evidence from the classroom and a suggestion for next steps. For a single observation, that write-up routinely takes one to three hours. Multiply that by 500 visits a year and you have an impossible math problem.
Principals respond to this math in predictable ways. Some use checklists and walkthrough forms to speed things up. Baeder’s research found that no evidence supports the effectiveness of walkthrough forms, and teachers tend to receive them poorly, calling them impersonal. Megan Kortlandt and Samantha Keesling, literacy and math consultants at Oakland Schools, wrote in ASCD that “time constraints and an evaluative culture” undermine walkthroughs, turning what should feel like formative assessment into something closer to a summative test.
Other principals simply stop providing written feedback and try to catch teachers for a quick hallway conversation instead. This works for a few teachers, but it does not scale, and it leaves no record for professional growth planning.
The result is a cycle most school leaders recognize: start the year with good intentions about walkthroughs, get buried in the feedback obligation, fall behind, and quietly stop visiting classrooms by November.
The Real Bottleneck: From Notes to Feedback
Every article, book, and professional development session about walkthroughs focuses on the same things: how to observe, what to look for, how to build trust, how to have a conversation afterward. These are all worth getting right. But they miss the structural problem.
The structural problem is the gap between raw observation notes and finished, framework-aligned feedback. A principal walks into a classroom, sees a teacher using think-pair-share with uneven student participation, jots down a few notes, and leaves. Turning those notes into a useful written response means pulling up the instructional framework, finding the relevant domain or indicator, writing evidence statements that match what was observed, and crafting a next-step suggestion grounded in the evidence. This is skilled professional work. It just should not take two hours per teacher.
David’s ASCD research review warned that “checklists focused on surface features are not likely to provide useful information.” The alternative, open-ended evidence-based observation, produces richer data but takes longer to process into feedback. Principals face a direct tradeoff: depth of observation versus volume of walkthroughs. Most school leaders want both. The current tools force them to choose.
What Changes When Feedback Takes Minutes, Not Hours
If the notes-to-feedback step took five minutes instead of two hours, everything changes. A principal could do Baeder’s recommended three visits per day and still have feedback ready for each teacher by the end of the week. The walkthrough-to-feedback cycle drops from many days to hours, which means teachers get feedback while the lesson is still fresh, not as a “postmortem” that arrives long after the moment has passed.
This is the problem that Observation Copilot was built to solve. Principals enter their observation notes and select their instructional framework. With one click, the platform generates a structured first draft of written feedback, aligned to the framework, with evidence statements drawn from the principal’s own notes and suggested next steps for the teacher. The principal reviews, refines, and delivers.
Adam Oakley, principal of Spokane Garry Middle School in Spokane Public Schools, described the difference: “A typical observation takes me two to three hours to complete the write-up. But using Observation Copilot, I’m down to about 20 to 30 minutes.”
Observation Copilot supports the Danielson Framework for Teaching and other popular instructional frameworks, with the option to upload a custom framework that matches your district’s approach. Lee Kappes, Ed.D., CEO of The Danielson Group, noted that integrating the framework into the platform helps “principals spend less time on paperwork and more time engaging in thoughtful, evidence-based conversations with teachers.”
Walkthroughs as a Development Tool, Not a Compliance Exercise
When feedback arrives quickly and consistently, something shifts in school culture. Teachers stop asking “Why are you here?” because the answer is obvious: the principal is here because they were here last week, too, and the feedback was useful. Walkthroughs become normal. Trust problems dissolve when the purpose is visible and the follow-through is reliable.
Kortlandt and Keesling advocate for walkthroughs that “celebrate and build upon good work already happening,” moving away from walkthroughs as high-stakes events. That shift requires a principal who is in classrooms often enough to notice momentum and specific enough in feedback to reinforce it. Neither is possible when the feedback write-up consumes the time that should be spent on the next visit.
The best walkthrough practice, from any source, comes down to two things: be in classrooms frequently, and close the feedback loop quickly. Everything else is implementation detail.
What to Do Next
If your walkthrough practice has stalled, start with the bottleneck, not the visit. Ask yourself how long it takes from the moment you leave a classroom to the moment the teacher has written feedback in hand. If the answer is more than 48 hours, the issue is not your observation skills or your time management. The issue is the pipeline from notes to feedback.
Three concrete steps:
- Set a frequency goal you can sustain. Baeder’s three-per-day target is a useful benchmark. Even two per week is better than the current average if feedback follows every visit. The number matters less than the consistency: teachers respond to predictable presence, not occasional check-ins.
- Drop the walkthrough form. Baeder’s research found no evidence that walkthrough forms are effective, and teachers tend to receive them as impersonal. Compare a form entry reading “Student engagement: Developing” to an open-ended note: “Students in rows A and C off-task during independent practice; teacher redirected once, didn’t follow up; three students finished early with nothing to do.” The note gives you something to discuss. The form gives you a checkbox.
- Fix the feedback step. The goal is to get the write-up time under 30 minutes so you can spend your time where it matters: in classrooms and in conversations with teachers. Observation Copilot is built for exactly this. Principals enter their notes, select their instructional framework, and get a structured first draft they can review and refine in minutes.
Principals can try Observation Copilot for free at ObservationCopilot.com to see what the feedback step looks like when it takes 20 minutes instead of two hours.
Frequently Asked Questions
How long should a classroom walkthrough take?
Most research recommends 10 to 15 minutes per visit. The visit itself is not the time-consuming part. The challenge is producing useful feedback afterward, which can take one to three hours without a structured process.
How often should principals do classroom walkthroughs?
Dr. Justin Baeder recommends three visits per day, or about 15 per week, which adds up to roughly 500 across a school year. The target is 18 biweekly visits per teacher, enough to build a genuine picture of instructional practice.
Should principals use walkthrough forms or checklists?
Research has not found walkthrough forms to be effective. Teachers tend to receive them as impersonal. Open-ended, evidence-based notes lead to richer feedback conversations and more useful data for instructional planning.
What’s the difference between a classroom walkthrough and a formal observation?
Formal observations are typically scheduled, longer (30-60 minutes), and tied to teacher evaluation. Walkthroughs are brief (10-15 minutes), informal, and focused on instructional growth rather than evaluation. When done well, walkthroughs build trust and provide ongoing developmental feedback.
