A teacher once told me my session was great but completely impractical. She was right.

I have been running teacher development sessions for years. And one of the most useful things that ever happened to me in that work was a teacher pulling me aside after a session and telling me, directly and without any cruelty: "Everything you said was good and ideal. But none of it is practical in an actual classroom."

She was not wrong. And I have been thinking about that moment ever since.

It is easy to dismiss feedback like that as resistance. As the kind of thing tired or cynical teachers say when they do not want to engage. But if you sit with it honestly — and I mean really sit with it, not just nod and move on — it points to something important about how professional development for teachers is usually designed.

> We design CPD for the ideal classroom. Teachers live in the actual one.

The gap nobody talks about openly

The ideal classroom has twenty students who are engaged, prepared, and roughly at the same level. It has adequate resources, predictable behaviour, and enough time to implement what you have just been trained to do. It has a school leadership team that has aligned its expectations with what the CPD session asked teachers to change.

The actual classroom has thirty-two students at five different ability levels, two of whom have not done the homework, one of whom has a situation at home that is affecting their attention, and a curriculum deadline that means there is no room to try a new approach this week. It has a timetable that was designed by someone who has not taught in years. And it has a teacher who attended a CPD session last Tuesday and came back energised, and who is now standing at the board on Thursday morning wondering how any of what they heard applies to what they are looking at.

This is not a problem with teachers. It is a problem with how CPD is designed.

What I changed after that conversation

After that teacher's feedback, I started asking a different question at the start of every session I designed. Not "what do teachers need to know" but "what do teachers need to be able to do differently on Monday morning."

It sounds like a small shift. It is not. Designing from that question changes almost everything about a session. It changes what you include and — more importantly — what you leave out. It changes how you sequence content. It changes what counts as a successful outcome. And it changes what you ask teachers to do during the session itself, because practising something in a training room is different from being told about it.

It also changed how I think about the follow-up after a session. One of the persistent failures of CPD in schools is that it is designed as an event. A day. A workshop. A series of inputs. And then it ends. Teachers return to their classrooms and the institution moves on to the next event.

Genuine professional development does not work like that. It works the way learning works — through repeated application, reflection, feedback, and adjustment over time. A single session, however well designed, cannot produce lasting change in practice without something that continues after it.

What actually changes teacher practice

In my experience — across more than a thousand teachers trained across schools in India, including Cambridge-affiliated, ICSE, and CBSE schools — the sessions that produced real, visible changes in classroom practice had a few things in common.

They started with the teacher's actual context. Not a generic challenge. A specific one that teachers in that school, at that level, with those students, recognised as real. The closer the content of a session was to a teacher's actual daily experience, the more likely it was to transfer.

They included genuine practice, not just exposure. Watching someone demonstrate a technique is not the same as trying it yourself, getting it slightly wrong, and figuring out why. The sessions that stuck were the ones where teachers did things, not just heard about them.

They had a specific, small, actionable commitment at the end. Not "implement this approach in your teaching" — that is too large and too vague. But "try this one technique in your next lesson and notice what happens" — that is specific enough to actually do.

There was some form of follow-up. Even a brief check-in — a message, a question in the next session, a short reflection exercise — made a measurable difference to whether the practice change survived contact with the actual classroom.

The teacher who changed something

I want to be specific here because generalities are easy and specifics are where the real insight lives. A teacher I worked with in a session on feedback practices — she had been giving written feedback on student writing the same way for years. Comprehensive, detailed, margin notes, end summary. She was good at it. It took her a long time and she was not sure students were reading it carefully.

In the session we looked at research on feedback — specifically on the difference between feedback students act on and feedback students file. We practised a different approach: shorter, more targeted, focused on one or two things rather than everything, and structured so the student had to do something with the feedback rather than just receive it.

She tried it the following week. It took her less time. Three students came to her after class to ask questions about their feedback — something that had not happened before. She sent me a message about it. Not because it was a dramatic transformation. Because something small had shifted and she had noticed.

That is what genuine CPD produces. Not a transformation. A shift. And shifts, accumulated over time, are how teachers grow.

> The question is not whether a CPD session was good. It is whether anything in a classroom changed because of it.

If you are thinking about teacher development for your school — whether a single workshop or a longer programme — I would be glad to have a conversation about what actually works. denver@denverd.in or denverd.in/contact.