Why Most Coaching Cycles Stall at Week Three

If you've coached teachers for any length of time, you probably know this pattern.

Week one feels great. You and the teacher sit down, talk through what's happening in their classroom, and land on a goal. There's energy in the room. The teacher is interested, maybe even a little excited, and you leave thinking this could be a good one.

Week two is still solid. You get into the classroom, you model something or co-teach, you debrief. The teacher tries a few things. You're both still showing up on time.

Then week three happens. The teacher emails that morning to ask if you can push the debrief to next week. There's a data meeting, or a parent conference, or a sub shortage and they're covering a class during their planning period. You reschedule. Next week something else comes up. By week five, you're not really in a coaching cycle anymore. You're just two people who used to meet.

Nobody decided to stop. Nobody was unhappy with how it was going. It just faded out.

This happens so often that a lot of coaches start to treat it as normal. It shouldn't be. When coaching stalls, the teacher loses support right at the point where the work was about to get useful, and the coach loses the chance to see whether anything they did actually made a difference for students. It also quietly teaches everyone on campus that coaching is optional, something that happens when things are calm, which in a school is almost never.

The good news is that the week-three stall is usually predictable, and most of the causes are things you can plan around.

What's actually going on in week three

It helps to understand why the drop-off lands where it does. In my experience, it's rarely one thing. It's a few things that pile up at the same time.

The novelty wears off. Starting something new has its own energy. The first meeting feels like a fresh start, and teachers often come in hopeful. By week three, the work has shifted from talking about change to actually doing it, and doing it is harder. The teacher is trying something unfamiliar in front of real students, it isn't going smoothly yet, and the early excitement doesn't carry them through that.

The goal was bigger than anyone realized. A lot of cycles start with a goal like "improve student engagement" or "strengthen small group instruction." Those sound reasonable in a planning meeting. But they're so broad that there's no clear finish line and no clear way to tell if you're making progress. By week three, the teacher can't point to anything that's different, so it starts to feel like effort without payoff.

The coach has been doing most of the work. Early in a cycle, coaches often carry a lot of the load. They model the lesson, bring the resources, suggest the moves. That's fine at the start. But if the teacher hasn't taken over much of the work by week three, the cycle starts to feel like something the coach is doing to the classroom instead of something the teacher owns. And when the teacher doesn't feel ownership, it's easy for them to let it slide.

The feedback gets real. The first couple of debriefs tend to be pretty comfortable. There's a lot of "I noticed this went well" and "what did you think about that?" By week three, if the coach is doing their job, the conversation gets more honest. That's where growth happens, but it's also where some teachers start to feel exposed. Rescheduling is a very polite way to avoid a conversation you're not sure you want to have.

The rest of the school year shows up. Week three of a cycle that started in September lands right around progress reports, the first round of benchmark data, parent conferences, and whatever else your district has scheduled for October. Coaching is almost always the first thing to get moved because it feels like it can wait. A data meeting has a hard deadline. A coaching debrief doesn't.

None of these are about a bad teacher or a bad coach. They're about how the work is set up. That means the fixes are mostly about setup, too.

Start with a goal you can actually see

The single biggest change you can make is to narrow the goal. A good cycle goal should be small enough that you'd expect to see some change in two weeks, and it should describe what students will be doing, not just what the teacher will be doing.

Compare these two goals:

"Increase student engagement during math."

"By the end of the cycle, at least three-quarters of students will explain their thinking to a partner during the warm-up."

The first one is a direction. The second one is a target. With the second goal, you and the teacher both know what to look for when you walk in the room. You can count it. You can see it get better. And when it does, the teacher has something concrete to feel good about.

It can feel like you're thinking too small when you set a goal like that. You're not. A narrow goal that gets met builds momentum for the next cycle. A big goal that gets abandoned in week three just leaves the teacher feeling like coaching didn't work for them.

It also helps to write the goal in the teacher's words as much as possible. If the teacher says, "I want my kids to actually talk to each other instead of waiting for me to give the answer," that's a great starting point. Tighten it up together, but keep their language in it. People hold on to goals they helped write.

Put every meeting on the calendar before you start

Coaching cycles fall apart when each meeting gets scheduled one at a time. If the plan is "let's find a time next week," you're relying on both of you to find space in a week that will already be full.

At the first meeting, put the whole cycle on the calendar. Every observation, every co-teach, every debrief, all the way to the end. Pick times that are least likely to get eaten up. Planning periods on days without standing meetings. The same time slot each week if you can manage it, so it becomes a habit.

Then treat those times like you'd treat a meeting with your principal. If something has to move, move it within the same week, not to "sometime next week." One missed meeting doesn't kill a cycle. Two in a row usually does.

This sounds simple, and it is. It's also one of the most effective things you can do. A cycle that's already on the calendar has a much better chance of surviving October than one that has to be rebuilt every week.

Shift the work to the teacher on purpose

Most coaches know the idea of gradual release: I do, we do, you do. It's worth applying that to the coaching cycle itself, and being deliberate about it.

In the first week, it's fine for the coach to model and bring most of the materials. By the second week, you should be co-planning and co-teaching, with the teacher taking the lead on some parts. By the third week, the teacher should be running the lesson while the coach observes and collects evidence.

That shift matters because week three is exactly when ownership needs to be in place. If the teacher is leading the work by then, the cycle belongs to them. It's their goal, their lesson, their students. They're much less likely to cancel a debrief about something they're invested in.

It helps to talk about this plan openly at the start. Something like, "For the first week, I'll model this so you can see it. After that, we'll plan it together, and by week three you'll be teaching it and I'll be watching for what the kids are doing." That way the teacher knows what's coming and it doesn't feel like the coach is suddenly stepping back.

Look for an early win and point it out

Teachers need to see that the work is paying off, and they need to see it early. If the only proof of progress is supposed to show up at the end of a six-week cycle, most teachers won't make it that far.

Build in a small checkpoint around week two. Collect a few samples of student work, or do a quick tally of how many students did the thing your goal is about. Compare it to what you saw at the start. Even a small change counts.

Then make sure the teacher notices it. Sit down with the student work and point to specifics. "Look at these three kids. In the first week, they wrote one word. Now they're writing full sentences explaining how they got the answer." That's the kind of evidence that keeps people going. It's much more convincing than a general "things are going great."

If you don't see any change by week two, that's important information too. It might mean the strategy needs adjusting, or the goal needs to be smaller. It's better to learn that in week two and adjust than to push forward and have the cycle stall in week three with nothing to show for it.

Name the dip before it happens

One of the most helpful things you can do is tell the teacher at the beginning that week three is usually hard. Something like, "Around the third week, this usually starts to feel messier. The new thing isn't automatic yet, and it might feel like it's not working. That's normal, and it's actually right before things start to click."

When teachers know the dip is coming, it doesn't feel like a sign that they're failing. It feels like part of the process. And when it does show up, you can say, "Remember when I said week three would feel like this? This is it. Let's keep going."

This works the same way it does with students. When you tell a class that a new skill will feel awkward at first, they're more likely to push through the awkward part. Adults aren't much different.

Think about shorter cycles

A lot of coaching models use six-week cycles, and some go longer. There's nothing wrong with that, but it's worth asking whether every cycle needs to be that long.

A three- or four-week cycle with a tight goal can accomplish a lot. It also means you're finishing right around the time you'd otherwise be stalling. The teacher gets to see a complete cycle through to the end, reflect on what worked, and decide on a next goal. That sense of finishing something is valuable. It makes the next cycle easier to start.

If a teacher wants to keep going on the same goal, you can always extend it. But starting with a shorter commitment makes it easier for teachers to say yes, and easier to actually finish.

What campus leaders can do

Coaches can do a lot on their own, but whether coaching survives October often depends on what campus leaders do.

Protect coaching time. This is the biggest one. If coaches are regularly pulled to cover classes, run testing, or handle duties, their cycles will stall no matter how well they're planned. Some of that is unavoidable, especially with staffing shortages. But if coaching time is always the first thing sacrificed, teachers notice. They learn that coaching isn't a priority, and they treat it accordingly.

Keep coaching separate from evaluation. Teachers need to know that what happens in a coaching cycle isn't going to show up in their evaluation. If they think the coach is reporting back to the principal about their weaknesses, they won't be honest about what's hard, and the work won't go anywhere. Leaders can make this clear by saying it directly and by not asking coaches for information about specific teachers' performance.

Ask teachers about their cycles. When you see a teacher who's in a coaching cycle, ask them how it's going. Ask what they're working on and what they're noticing with their students. This tells the teacher that you care about their growth, and it keeps the cycle visible without putting the coach in an awkward spot.

Look at the calendar. If a lot of cycles are stalling in October, look at what's on the campus calendar that month. Sometimes a school has scheduled so many meetings, trainings, and data days that there's simply no room for coaching. That's a leadership decision, and it can be changed.

When a cycle stalls anyway

Even with good planning, some cycles will stall. A teacher will cancel twice in a row, or show up to debriefs without having tried anything, or seem checked out. When that happens, the worst thing to do is let it quietly fade away.

Instead, have a direct conversation. Keep it low pressure. Something like, "I've noticed we've had to move our last couple of meetings. I don't want this to feel like one more thing on your plate. What's going on, and what would make this more useful for you?"

Sometimes the answer is that the teacher is overwhelmed with something else, and the best move is to pause the cycle and set a date to restart. That's fine. A planned pause is very different from a cycle that just disappears.

Sometimes the answer is that the goal isn't something the teacher cares about. Maybe it came from a campus initiative, or it sounded good in the first meeting but isn't what they're actually struggling with. In that case, change the goal. It's much better to work on something the teacher is invested in than to push through on something they're not.

And sometimes the answer is that the teacher is uncomfortable with where the feedback is going. That's worth talking about honestly. You might say, "I know some of what we've been talking about is hard. That's usually a sign we're working on something that matters. How can I make these conversations feel more useful and less like a critique?" Giving the teacher more control over what gets observed and discussed can help a lot.

Whatever the reason, the conversation itself matters. It shows the teacher that the coaching relationship is worth protecting, and it gives you a chance to fix things before they're too far gone.

It's worth getting right

Coaching is one of the best tools schools have for helping teachers grow. It's personal, it's tied to real classrooms, and it happens over time instead of in a single afternoon of PD. But it only works if it lasts long enough to make a difference.

Week three is where a lot of that potential gets lost. Not because anyone gave up, but because the setup didn't account for how hard the middle of a change can be.

A narrow goal, a full calendar, a planned shift in ownership, an early win, and an honest heads-up about the dip will get most cycles through. And when one stalls anyway, a direct conversation can usually get it back on track.

The teachers you coach are going to hit the hard part either way. The goal is to still be in the room with them when they do.