The central contradiction

Training teachers to adapt while
evaluating them for complying.

The most common failure mode for agile teaching implementation is not teacher resistance — it is institutional contradiction. A school trains teachers in agile teaching principles in September, then observes them in October using a framework that rewards: clear objectives written on the board, smooth transitions between activities, lesson completion within the period, and teacher control of the class at all times.

Every one of those criteria is potentially in tension with agile teaching. An agile teacher might change their stated objective mid-lesson because the exit ticket revealed the class wasn't ready for it. They might spend 10 extra minutes on a concept because the data showed a systematic misconception. They might run a full reset that leaves activities unfinished. Under a compliance-based observation framework, this teacher looks like a poor planner. Under an agile teaching framework, they look like a skilled professional responding to real-time information.

The institutional message is contradictory, and the evaluation system always wins. Teachers are rational: if they are observed and evaluated on compliance, they comply. The agile teaching workshop is filed away as “interesting but impractical in this school.” This is not teachers' failure — it is a leadership failure to align the evaluation system with the stated instructional goal.

⚠️The most expensive mistake in school improvement
Investing in teacher professional development for a practice that the evaluation system penalises. Every pound spent on agile teaching training is wasted if the observation framework rewards the opposite behaviours. Change the observation framework before — or at the same time as — training teachers in the practice.
What to change

The five leadership behaviours that
build agile culture.

1
Change the observation question
From "did they follow the plan?" to "did they respond to the evidence?"

The single highest-leverage leadership action for agile teaching culture is changing the primary observation question. 'Did the teacher follow their lesson plan?' rewards compliance. 'What evidence did the teacher collect, and how did they respond to it?' rewards responsiveness. This one change — audible in every post-observation debrief — signals to teachers what quality looks like in this school.

In practice
Ask at the start of every debrief: "What did you notice about student understanding during the lesson, and what did you do with that information?" Teachers who have good answers to this question are practising agile teaching. Teachers who cannot answer it are not.
2
Celebrate departures from the plan
Publicly recognise good pivot decisions

Culture follows what gets publicly celebrated. When a teacher explains that they abandoned their planned activity because an exit ticket revealed a foundational gap — and successfully rebuilt understanding instead — this should be recognised explicitly: 'That is precisely the kind of professional judgment that improves student outcomes.'

How often
Once a year is not enough. Once per observation cycle, minimum. The celebration needs to be frequent enough that teachers internalise the message: in this school, adapting to evidence is a mark of skill, not a failure to plan.
3
Model it yourself
School leaders who admit uncertainty teach teachers that uncertainty is safe

A school leader who presents a curriculum change, receives feedback that it didn't work as expected, and says 'thank you — I'm going to iterate on that based on what you've just told me' is doing agile leadership. The same mechanism that works in classrooms — showing that adapting based on evidence is valued, not shameful — works in staff meetings.

The specific behaviour to model
In a staff meeting: "We tried X last half-term. The data shows it didn't produce the outcome we were looking for. Here's what we're changing and why." Transparent, evidence-based, non-defensive. Teachers will replicate the behaviour they see their leaders model.
4
Protect the iteration infrastructure
Don't cancel retrospectives; don't remove the iteration log

The two structures that make agile teaching visible (the log) and cumulative (the retrospective) are the first things cut when school schedules become pressured. A leader who protects them — explicitly, by scheduling them immovably and refusing to replace them with admin meetings — signals that agile improvement is a priority rather than an extra.

What protection looks like
Schedule retrospectives as recurring calendar events at the start of the year. Communicate explicitly: "These sessions will not be rescheduled for admin or external requirements." The commitment is what matters — teachers need to trust the structures will be there.
5
Make the iteration log visible to leadership — as support, not surveillance
Use it as a signal for support, not accountability

When a leader reads the iteration log and responds with 'I notice you've had three consecutive entries on the osmosis misconception — would a different resource help?' rather than 'I see you've been struggling with that lesson', the log becomes a tool teachers value. When it's used for accountability, teachers stop making honest entries.

The framing is everything
"I see you've been working on this lesson — can I help?" vs "I see you've been struggling with this lesson." The first is support. The second is surveillance. The difference is not subtle to a teacher who is deciding whether to make an honest entry tonight.
The long view

Three years to a school where
agile teaching is the norm.

Real cultural change in schools takes time that most improvement programmes underestimate. Year 1 is awareness and early adoption. Year 2 is observation framework update and visible wins. Year 3 is majority adoption and skill deepening. Years 4–5 are institutional norm.

The leadership behaviours in this article need to be sustained across that timeline — not deployed once in a launch event and then allowed to fade as the next improvement priority arrives. The schools that successfully embed agile teaching are the ones where the same leader continued asking the same observation question, celebrating the same types of professional decision, and protecting the same structures for three consecutive years.

The school that improves is the school where changing your approach is treated as evidence of professionalism — not as evidence of a mistake.
P6 · Agile teaching — C6 · School-wide culture
You've finished C6

C6 has scaled the practice.
C7 designs for it.

C6 has covered the structures that make agile teaching visible (iteration log), cumulative (retrospective), and sustainable (leadership behaviours). The next cluster — C7 — covers how to design curriculum that is built for agile delivery from the start, so that iteration is structurally supported rather than grafted onto a fixed curriculum.

Continue to C7: Curriculum for agile →← Back to A2