The Admin Angle: Why Administrators Should Eliminate “Gotcha” Walkthroughs

I. Introduction

Ask any group of teachers what they dread about observations, and it shows up fast: the “gotcha” walkthrough—the surprise pop-in with a clipboard, a checklist, and zero context. A leader appears in the doorway, watches for a few minutes, taps on a phone or laptop, and leaves without a word. Days later, a vague comment or mysterious score shows up in an email or evaluation document. Instruction doesn’t get better; trust erodes.

The original intent behind walkthroughs is usually good. Principals want to be in classrooms, see instruction, and identify trends. But when walkthroughs are compliance-driven, secretive, or tied to hidden evaluation, they stop being a tool for growth and become a source of anxiety. Teachers shift from thinking, “How can I make this lesson great for students?” to “What will admin think if they walk in right now?” That’s not a mindset that produces deep learning.

Check out our engaging printable posters. CLICK HERE to explore!

This article makes the case for eliminating “gotcha” walkthroughs entirely and replacing them with transparent instructional walks: visits with shared look-fors, brief pre-briefs, clear feedback loops, and data that’s used for support, not punishment. You’ll get a concrete model you can drop into your school: how to redesign your walkthrough system, how to communicate the shift, and what you should expect to see when trust starts to grow.

II. What “Gotcha” Walkthroughs Really Do

“Gotcha” walkthroughs change behavior—but not in the way you want.

They push teachers toward performance instead of authenticity. When educators don’t know what observers are looking for, they default to whatever they think “looks good” for the 5–7 minutes you’re in the room. That might mean:

• Overusing one “approved” strategy even when the class needs something else
• Avoiding riskier, higher-cognitive-demand tasks in case they “flop” while someone is watching
• Sticking rigidly to a script instead of adjusting instruction based on what students are actually doing

They also damage psychological safety. In any profession, people grow fastest when they feel safe to:

• Show work in progress instead of only finished products
• Ask for help when something isn’t working
• Admit they’re trying something new and aren’t sure how it will go

Gotcha walkthroughs do the opposite. Teachers feel surveilled. They close their doors more tightly, share less, and stop inviting leaders into the parts of their practice that need support the most.

Finally, “gotcha” walkthroughs confuse accountability with ambush. Real accountability sounds like:

• “Here are our shared goals for student learning.”
• “Here’s what we’ll look for together.”
• “Here’s how I’ll support you if things aren’t where we want them to be.”

Gotcha walkthroughs sound like:

• “You’ll find out later if what you did was acceptable.”

That’s not accountability—it’s a trust problem dressed up as quality control.

III. How “Gotcha” Culture Took Hold

It’s helpful to be honest about how schools ended up here. Principals don’t wake up thinking, “How can I stress teachers out today?” Most are responding to real pressures and inherited systems.

Common drivers include:

• Inherited tools and habits
  • A district-mandated walkthrough form focused on visible “look-fors”
  • A culture of “you must complete X walkthroughs per week” without guidance on purpose
  • Evaluation frameworks that subtly blur the line between informal and formal data
• External accountability
  • Supervisors asking, “How do you know teachers are using the program?”
  • Pressure to show “evidence” that leaders are in classrooms
  • Comfort in numbers: “We did 300 walkthroughs this semester” feels like proof, even if they weren’t helpful
• Leadership comfort zone
  • For a newer principal, a checklist can feel safer than an open-ended instructional conversation
  • It’s easier to scan for a posted objective than to decode the quality of student thinking

It’s understandable. But understandable doesn’t mean effective. The next step is to keep the good impulse—being in classrooms and seeing instruction—while redesigning the entire experience around trust and learning.

IV. What Teachers Actually Need from Walkthroughs

Teachers don’t hate feedback. They hate unclear, unhelpful, or weaponized feedback. When walkthroughs are done well, most teachers actually want leaders in their rooms.

What they need from walkthroughs includes:

• Clarity and predictability
  • Knowing what the focus is this cycle
  • Understanding how walkthroughs connect to school goals
  • Trust that informal notes won’t secretly appear in formal evaluations
• Authentic visibility
  • Leaders seeing their real learners, not staged “observation lessons”
  • Observers who understand the context (unit, group dynamics, learning goals)
• Specific, usable feedback
  • Concrete examples of what went well (“Here’s what I saw students doing…”)
  • One or two realistic next steps instead of a page of checkboxes
• Evidence of support, not just surveillance
  • PD, coaching, or resources that clearly respond to patterns
  • Leaders who follow up on issues they themselves identified

When walkthroughs provide these things, teachers tend to relax, open their doors, and start to see leaders as thinking partners instead of critics.

V. Redefining the Purpose of Walkthroughs

If the purpose isn’t crystal clear and constantly repeated, people will assume the worst. Redefine the purpose of walkthroughs in plain language.

Instead of purposes like:

• “To ensure teachers are implementing strategies with fidelity”
• “To monitor compliance with instructional expectations”

Shift to something like:

• “To understand how students are experiencing learning across our school.”
• “To identify strengths and needs in instruction so we can provide the right support.”
• “To create frequent, low-stakes opportunities for feedback and reflection.”

When you roll this out, do more than just send an email. Try:

• Saying it out loud at a staff meeting
• Putting it at the top of your walkthrough form
• Repeating it at the start of each new walkthrough cycle

Over time, staff will decide whether to believe the new purpose based on whether your actions match your words. The definition is step one; your behavior is step two.

VI. Core Principles for Transparent Instructional Walks

Once the purpose is clear, build your walkthrough system on a few simple principles. Everything you design should align with these.

• No surprises on look-fors
  • Teachers know ahead of time what the focus will be for a walkthrough cycle.
  • Faculty understand why these look-fors matter for student learning—not just because the district says so.
• Short, frequent, and focused
  • Visits are 5–10 minutes, not full-period observations.
  • Each cycle concentrates on a narrow slice of practice (for example, student talk or checks for understanding), not on everything at once.
• Students at the center
  • Observers look first at what students are doing, saying, writing, and understanding.
  • Evidence comes from student work and dialogue, not just from teacher actions.
• Feedback that is fast and actionable
  • Teachers receive something back—note or quick conversation—within a day.
  • Feedback always includes at least one specific strength and one concrete next step.
• Data used for support, not punishment
  • Pattern summaries are shared to guide PD, coaching, and resource decisions.
  • Walkthrough records are not used as “gotcha” evidence in surprise evaluation comments.
• Teachers as partners, not targets
  • Educators can request visits when they’re trying something new.
  • There are opportunities to ask questions, clarify context, and respond to what observers saw.

If your current process doesn’t line up with these principles, that’s your redesign checklist.

VII. Building Shared Look-Fors with Staff

Instead of handing teachers a finished checklist, co-create your look-fors. This turns walkthroughs into something you build with staff instead of something you impose on them.

A simple process might look like this:

• Start from your instructional vision
  • Ask teachers in small groups: “If a student walked into any classroom here, what experiences do we want them to consistently have?”
  • Generate ideas like:
    • Students know what they’re learning and why
    • Students have chances to talk, write, and think
    • Teachers check for understanding and adjust
• Translate into observable indicators
  • Work together to turn those ideas into look-fors, such as:
    • “Students can explain the learning goal in their own words.”
    • “All students respond to at least one check for understanding during the lesson.”
    • “Student tasks require more than recall (explain, justify, compare, create).”
• Limit the number per cycle
  • Choose 3–4 look-fors for a walkthrough cycle, not 12–15.
  • Plan how focus areas will rotate across the year (for example, goals and clarity in September, checks for understanding in October, student discourse in November).
• Publish and revisit
  • Share a one-page document each cycle with:
    • The look-fors
    • Why they matter for student learning
    • How teachers can ask for feedback on a specific element
• Connect back to real work
  • Use these look-fors in PLCs to examine student work and lesson plans.
  • Let teachers suggest refinements as you see what’s actually happening in classrooms.

When teachers see their language and ideas reflected in the walkthrough tool, they’re far more likely to trust the process.

VIII. The Pre-Brief: A Small Move with a Big Impact

One of the biggest differences between “gotcha” and “growth” is whether teachers get a chance to frame what you’re about to see.

You don’t have to schedule a formal meeting before every visit. But build in simple pre-brief routines like:

• A quick hallway conversation:
  • “I’m focusing on how students show their thinking this week. Is there a part of your lesson you’d especially like feedback on?”
  • “You mentioned you were trying a new questioning routine. Want me to watch that part?”
• A short pre-brief form teachers can fill out if they choose:
  • “Here’s the context for this lesson (unit, day in sequence).”
  • “Here’s something I’d like you to look for.”
  • “Here’s what I’m not sure is working yet.”

Pre-briefs matter because they:

• Acknowledge teacher goals and intentions instead of assuming you know them
• Reduce the power imbalance, turning the visit into a joint inquiry
• Increase the quality of your feedback, because you know what the teacher was trying to accomplish

Even if you only pre-brief some visits, the signal is clear: walkthroughs are collaborative, not ambushes.

IX. What You Do in the Room Matters

Even with a beautifully redesigned tool, the way you act in the classroom sends the loudest message.

Try to standardize a few in-the-moment habits:

• Enter quietly and respectfully
  • Slip in without making a big entrance.
  • Avoid interrupting the teacher’s flow to announce why you’re there.
• Look at students first, then the teacher
  • Glance at student faces, notebooks, screens, or whiteboards.
  • Ask a few students quietly, “What are you working on right now?”
• Capture evidence, not just impressions
  • Write exact student quotes, sample questions, or descriptions of tasks.
  • Note what students did when the teacher checked for understanding.
• Honor the slice you see
  • Remember that you are seeing 5–10 minutes of a much longer arc.
  • Avoid assuming the entire lesson looked like the few minutes you caught.
• Avoid correcting in front of students (unless safety is at stake)
  • If you see something that concerns you, save the conversation for after class.
  • Mid-lesson corrections from an observer can feel undermining and punitive.
• Leave with gratitude
  • A simple “Thank you for letting me be in your room” at the end goes a long way.
  • If something stood out positively, mention it briefly before you go.

These micro-behaviors are how teachers decide whether walkthroughs are truly about learning—or just nicer-looking versions of the same old “gotcha.”

X. Feedback Loops That Actually Help

Feedback doesn’t have to be long to be powerful. It does have to be timely, specific, and focused.

A simple structure you can use consistently:

• Within 24 hours, send a short note or have a 3–5 minute conversation:
  • One clear strength tied to a look-for
  • One concrete suggestion or next step

Examples:

• Strengths might sound like:
  • “Three students I talked to could clearly explain the learning goal in their own words.”
  • “I noticed you paused after asking questions and several quieter students jumped in—that wait time is paying off.”
• Next steps might sound like:
  • “Consider a quick whole-class check (like a 1–4 scale on fingers) before releasing students to independent work so you can see who is ready.”
  • “You might try having students explain their thinking to a partner before calling on volunteers to increase participation.”

Keep feedback:

• Anchored in what you saw
• Linked to the shared look-fors
• Manageable (one move at a time, not a full rewrite of practice)

Over time, teachers should be able to predict that walkthroughs always produce:

• At least one piece of encouragement grounded in evidence
• At least one realistic idea they can test next time

That predictability is what starts to dissolve the “gotcha” feeling.

XI. Using Walkthrough Data for Learning, Not Punishment

When you aggregate walkthrough information, be disciplined about how you use it. The purpose is to improve the system, not to quietly rank individuals.

Some ways to use walkthrough data well:

• Summarize patterns, not names
  • “In 70% of classrooms we visited, students could name the skill but not why it was important.”
  • “We saw strong learning targets in most rooms, but checks for understanding were often limited to volunteers.”
• Design PD around what you see
  • If student talk is weak, run a short learning segment on academic conversation routines—then re-walk with that focus.
  • If exit tickets are strong but not used, plan a PLC where teachers bring exit tickets and decide how they’ll inform the next lesson.

Enjoy science fiction? Check out my space books HERE on Amazon!

• Steer coaching and support
  • Assign instructional coaches based on building-level trends.
  • Prioritize support for teams where walkthrough evidence shows consistent challenges.
• Monitor growth across time
  • Compare early-year and mid-year summaries to see if your supports are actually changing practice.
  • Share those changes with staff: “Here’s how we’ve grown in student talk since September.”

What you should not do with walkthrough data:

• Use it to surprise teachers in summative evaluations
• Share individual “scores” publicly or as competition
• Weaponize pattern data to justify new top-down mandates

If walkthrough patterns lead to more help, not more heat, teachers will start to welcome the process.

XII. A 60-Day Plan to Move Away from “Gotcha” Walkthroughs

You don’t have to rebuild everything overnight. Here’s a practical two-month transition.

Weeks 1–2: Name and Reset

• Acknowledge staff experience honestly:
  • “In the past, walkthroughs may have felt like ‘gotchas.’ That’s not the culture I want.”
• Share a new one-sentence purpose for walkthroughs.
• Invite teacher input on what would make walkthroughs useful.

Weeks 3–4: Design with Staff

• Co-create 3–4 look-fors for your first instructional walk cycle.
• Draft a one-page “Instructional Walk Focus” and share it.
• Decide how feedback will be delivered and within what timeline.

Weeks 5–6: Pilot and Adjust

• Conduct a small number of walks using the new model (for example, one team or grade level).
• Pre-brief with volunteers, then debrief honestly:
  • What felt different?
  • What was helpful?
  • What still felt uncomfortable?
• Adjust language, timing, or tools based on what you hear.

Weeks 7–8: Scale and Lock In

• Share a simple walkthrough calendar (focus areas, approximate dates).
• Visit all classrooms at least once in the cycle, honoring your feedback commitments.
• Share a pattern summary with staff and explain how it will drive upcoming PD or coaching.
• Gather another round of teacher feedback and make minor refinements.

By the end of 60 days, walkthroughs should feel recognizably different: smaller, clearer, more humane, and more obviously tied to actual support.

XIII. Case Studies (Anonymized)

Elementary School (Urban) Walkthroughs were previously tied to a long checklist of strategies. Teachers never saw the data and only heard about visits when something went wrong. The new principal scrapped the checklist and launched a cycle focused on just three look-fors teachers helped define: clarity of learning goals, student talk, and quick checks for understanding. Walkthroughs became brief, frequent, and always followed by a short email naming one strength and one idea. Within a semester, staff survey data showed a major shift: most teachers now agreed with statements like “My principal’s visits help me think about my instruction” and “I know what leaders are looking for when they come in.”

Middle School (Suburban) Leaders prided themselves on high walkthrough counts, but teachers called them “drive-bys with clipboards.” The admin team rebranded them as “Instructional Walks,” dropped all evaluative language, and adopted a simple cycle: announce the focus, visit with that focus, share anonymized trend data with teams, and design a 20-minute learning activity in PLCs based on what they saw. Teachers began requesting walks during lessons where they were trying new structures. Over time, PLC conversations shifted from “What did they mark us on?” to “What did we learn about how our students think?”

High School (Rural) In a small high school, walkthrough notes had quietly become part of summative evaluations, even though teachers were never told when or how that would happen. This created deep mistrust. The principal drew a clear line: informal walkthroughs would now be non-evaluative and used only to inform coaching and PD. Formal observations would be scheduled separately, with clear tools and timelines. After one year, staff reported feeling safer to try new strategies in front of administrators, and peer observation grew organically as teachers began to see classroom visits as learning opportunities, not threats.

XIV. Common Pitfalls and How to Avoid Them

As you shift away from “gotcha” walkthroughs, watch for these traps:

• Saying it’s not evaluative, then using it in evaluations anyway
  • If walkthrough notes will ever be referenced in formal evaluation, say so clearly up front, and keep the tools aligned.
  • Better yet, keep informal walk tools and formal evaluation tools completely separate.
• Trying to see everything at once
  • If your form feels like a full evaluation rubric, it’s too long.
  • Limit to a handful of look-fors; rotate focus across the year.
• Letting feedback slide
  • If teachers don’t reliably get feedback, walkthroughs feel like surveillance again.
  • Use simple systems (templates, calendar reminders) to keep feedback timely.
• Inconsistent admin behavior
  • If one AP uses walks as coaching and another uses them as “gotchas,” staff will mistrust the whole system.
  • Calibrate as a leadership team; walk together sometimes and compare notes.
• Ignoring teacher voice
  • If you redesign in a vacuum, staff will treat the new system as a rebrand of the old one.
  • Regularly ask, “What would make this more useful to you?” and act on what you hear.
• Drifting back to counting instead of learning
  • It’s tempting to brag about the number of walkthroughs completed.
  • Keep your focus on what you’re learning and how instruction is changing, not just how often you enter classrooms.

XV. Conclusion

Gotcha walkthroughs are a classic example of something that looks like accountability but functions like surveillance. They might produce a stack of forms or a pretty dashboard, but they rarely produce better teaching—and they almost always cost you trust.

You don’t have to choose between being in classrooms and respecting teachers. You can do both. Redefine the purpose of walkthroughs around student learning, co-create look-fors, add simple pre-briefs, behave like a partner in the room, and follow up with specific, fast feedback. Use what you see to design support, not to stockpile evidence.

When you eliminate “gotcha” walkthroughs and replace them with transparent instructional walks, something important shifts: teachers stop wondering, “What are they trying to catch me on?” and start thinking, “How can I use this visit to get better for my students?” That’s when walkthroughs finally become what they were always meant to be—a tool for growth, not a trap.

Check out some of my latest science fiction books HERE on Amazon!

Transform your classroom into an inspiring, vibrant learning space with our beautifully designed printable posters! Perfect for engaging your students and enhancing your teaching environment, our poster bundles cover everything from historical philosophers to animals. CLICK HERE to explore our exclusive collections on Teachers Pay Teachers and give your students the motivational boost they need!