Growth Mindset Isn't Just for Students. It's How Schools Actually Change.

As an instructional coach, I've spent years sitting in the space between leadership decisions and classroom reality — close enough to see both, responsible for neither. It's a particular kind of vantage point. You watch initiatives land well and initiatives collapse, and over time you start to see that the difference rarely comes down to the quality of the idea. It almost always comes down to what happens after the idea gets introduced.

A few years ago I watched an assistant principal deliver one of the best beginning-of-year professional development sessions I'd seen in a long time. Her topic was reading foundations. The slides were clean. The content was solid. The activities were ones teachers could immediately use in the classroom. Teachers were engaged — asking questions, nodding, taking notes. The feedback forms were overwhelmingly positive.

That afternoon, while teachers were staying late to set up classrooms for the first day of school, she sent a follow-up email. It contained a few links to resources and a single line about implementation: we'll be looking for these strategies during walkthroughs.

The questions started immediately. Teachers wanted to know what "looking for" meant. Which strategies, specifically? What if the strategies didn't align to what they were teaching that week? Would materials be provided? Would there be time to plan together? Who could they go to when they got stuck?

She read the questions as resistance. Teachers had seemed so engaged during the PD — why were they pushing back now?

She got defensive. She pulled back. And the instructional strategies that had generated so much genuine energy in that room that morning never made it into classrooms in any consistent way. Students who needed a shift in their reading instruction didn't get one — not because the approach was wrong, but because the implementation collapsed before it started.

This is how change efforts die. Not dramatically. Quietly, in the gap between a great training and an unclear Monday morning.

The Cost Nobody Talks About

Every school year, districts spend significant money on curriculum adoptions, edtech tools, instructional frameworks, and professional development. And then implementation gets uneven — some teachers run with it, others do something vaguely related, a few wait it out knowing the initiative will likely pass. Because in their experience, it usually does.

The direct costs are obvious: wasted budget, wasted time, wasted teacher goodwill. That last one matters more than most leaders account for. Teacher goodwill is a finite resource. Every initiative that launches with fanfare and dies without follow-through makes the next one harder to land. The skepticism that reads like resistance from the outside is usually just pattern recognition from the inside.

The harder cost is this: when implementation is inconsistent, you can't evaluate whether the approach actually works. You end up abandoning things that could have helped because you never gave them the conditions to succeed. That's what happened with the reading foundations work. The approach was sound. It never got a real chance.

It's Not the People. It's the Conditions.

Here's what I see leaders get wrong most often: they diagnose the people when they should be diagnosing the system.

When a new curriculum or instructional framework launches, teachers are temporarily in novice mode. They're learning new routines, new materials, new language — often while managing thirty students who don't know it's a transition year. There's a predictable dip: slower pacing, uncertainty, mistakes. That's not a warning sign. That's learning.

But if the dip gets treated as incompetence — through vague walkthrough threats, impatient timelines, or feedback that feels punitive — adults do what any reasonable person does in an unsafe situation. They protect themselves. Surface compliance without real instructional change. Selective adoption when someone's watching. Critique without iteration — it's flawed, so I'm out.

None of that is a character problem. It's a predictable response to unclear expectations and insufficient support.

The assistant principal's follow-up email was a version of this, unintentionally. We'll be looking for these strategies communicated evaluation without support — observation without infrastructure. Teachers weren't pushing back on the ideas. They were telling her, as directly as they knew how, that they didn't have what they needed to actually use them. That's not resistance. That's useful information.

The right question is never why won't people commit. It's what in the system is making consistent implementation hard — and what can we remove or build to change that?

What Growth Mindset Leadership Actually Requires

Here's the part that doesn't get said enough: leading change is its own form of novice mode.

Designing and sustaining a school-wide instructional shift is a skill. Most leaders weren't explicitly trained in it. They're learning it in real time, in front of staff, while managing budgets and schedules and parent phone calls. The dip that teachers experience during implementation? Leaders feel a version of it too — and usually with less support and less permission to admit it.

Which means the growth mindset you're trying to build in your staff has to start with you. Not as a performance of humility, but as a genuine operating condition. The leader who can say "I'm still figuring out how to support this well — tell me what's not working" creates an entirely different culture than the leader who can't afford to be wrong.

That's the standard. Here's what it actually looks like:

Name reality without drama. "Our implementation is uneven. That's predictable. We're going to tighten the conditions." People can handle hard news. They struggle with unclear news. Clarity lowers defensiveness and keeps the work visible instead of in hallway conversations.

Audit the system before you assess the people. Do teachers have the materials? Is there protected time to plan? Are the look-fors specific enough to act on? Are coaches deployed to support practice, or just to observe it? Blame produces compliance theater. Design produces practice.

Treat mistakes as data — including your own. Normalize the early dip: "The first cycle will be messy. We're not drawing conclusions until we've done this twice." If leaders can't model public learning, they can't credibly ask teachers to do it.

Hold the standard and remove the barriers. "We are doing this — and here's what we're putting in place so you can do it well." Growth mindset isn't permissive. It's structured, and it runs in both directions.

The Patterns That Stall Implementation

In my work as a coach I see three patterns that derail implementation — and all three were present in some form in what happened that year.

The first is mistaking engagement for readiness. The assistant principal saw teachers nodding and taking notes and read it as a signal that the work was done. It wasn't. Engagement in a PD room is real, but it's also the easiest part. The harder question is what's in place when teachers leave that room and have to try something new in front of actual students. A follow-up email with links is not an answer to that question.

The second is pulling back when the questions get hard. When teachers pushed back with questions, what they needed was a leader who leaned in — who said these are the right questions, let's work through them together. What they got instead was a leader who experienced the questions as criticism of something she'd worked hard to build, and retreated. That retreat sent a clear message: this isn't a space where uncertainty is welcome. And so the uncertainty went underground, along with any real attempt at implementation.

The third is autonomy without a baseline. Once the follow-up collapsed, there was no shared expectation left — no non-negotiables, no support structures, no follow-up loops. Teachers who were confident moved forward on their own. Teachers who were uncertain waited. In practice that meant implementation was random, determined by individual comfort level rather than any shared standard. And the students in the classrooms of the least confident teachers got the least.

What Could Have Gone Differently

She had done something genuinely hard. Building a coherent, engaging, well-researched PD on reading foundations takes real expertise. She had earned the positive energy in that room. And then, a few hours later, she was fielding questions she didn't have answers to — in an email thread, while teachers were stressed about the first day of school, without a coach or a mentor helping her navigate it.

She was in her own implementation dip. And she didn't know it.

If I had been coaching her through what happened, these are the questions I'd want her to sit with — not to assign blame, but to surface what the plan was missing before that email ever went out:

How will teachers be supported beyond a few links? Will materials be purchased for them? Is there protected time each week for teams to meet and plan together? What specifically will coaches and administrators be looking for during walkthroughs — and will teachers see those look-fors before they're evaluated against them? What happens when the strategies don't align to what's being taught that week? How can the instructional coaches and existing PLC time carry this work forward over the coming months?

None of these are punitive questions. They're design questions. And a leader with a growth mindset hears teacher questions as the same thing — as useful data about where the plan needs work, not as a verdict on the work already done.

Instead, she heard the questions as criticism, and closed the door on the very feedback that could have made it work. Coaches weren't deployed. Follow-up structures were never built. Teachers who had genuinely engaged with the ideas that morning moved on, because there was nothing concrete to move toward.

And the students in their classrooms — students who needed a shift in how reading was being taught — didn't get one. Not because the approach was wrong. Not because teachers were unwilling. Because a leader who was herself in novice mode didn't have the tools to stay curious under pressure.

The Standard Goes Both Ways

We ask teachers to be learners in public. To try new things in front of students, make mistakes, adjust, and keep going — without shutting down or opting out when it gets uncomfortable.

That's a significant ask. And it only lands if the leader is doing the same thing.

You can't ask more of your teachers than you're willing to ask of yourself. But when you do ask it of yourself — when you stay curious instead of defensive, when you treat hard questions as information instead of opposition, when you model what it looks like to not-yet-know something and keep working anyway — you make it possible for everyone else.

That's where change actually starts.