Building a Whole-School PD Plan That Actually Sticks

Most schools run professional development like a playlist on shuffle.

You book a speaker for the first staff meeting. Someone runs a session on differentiation in Term 2. There is a wellbeing workshop before the winter break. The sessions are fine. The speakers are good. But by November, when you look back across the year, there is no through-line. No build. No compounding effect. Just a list of things that happened to a staff who are no closer to working differently than they were in January.

A whole-school PD plan is not a calendar of events. It is a system that creates coherent skill development, embeds accountability, and builds the conditions for teachers to actually change how they work. The difference between a plan that fades and a plan that sticks is not the content of the sessions. It is the decisions you make before the first session ever runs.

I put together this list of 25 planning steps that separate random PD from the kind that transforms a school.

FOUNDATION: BEFORE YOU BOOK A SINGLE SESSION

The first seven steps happen before you put a single date in the calendar. This is the architecture. Get this right and the rest becomes easier. Get this wrong and every session you run will fight against a system that was never designed to support follow-through.

1. Audit what your staff are already juggling before you add anything new

Your teachers are already carrying compliance training, curriculum updates, reporting deadlines, and whatever initiative the previous leadership team started and never formally ended. Adding a PD plan on top of that without clearing space first guarantees shallow engagement.

Most schools plan PD in isolation from the rest of the workload calendar. The PD looks great on paper. It collapses the moment it hits a reporting week or a parent-teacher evening.

Start by mapping the full calendar. Not just the school terms, but every standing meeting, every reporting cycle, every major event. Identify the weeks where cognitive load is already at capacity. Mark them as no-fly zones for new PD content.

Then look at what is already on the books. Are there compliance sessions that can be consolidated? Are there initiatives from two years ago that nobody has formally killed but also nobody is driving? Clear the dead weight before you build the new plan.

Three questions to ask during the audit:

• What standing commitments are non-negotiable and cannot be moved?

• What existing PD or initiatives can be archived or merged?

• Where in the calendar does the staff actually have mental space to learn something new?

The audit is not about finding empty time. It is about creating protected time by removing what no longer serves the school. A PD plan built into a cluttered calendar is a plan built to fail.

2. Name the one behavioural shift you want to see by December

A whole-school PD plan that tries to address every gap at once addresses none of them well. The staff experience it as noise. You need a single, named behavioural change that every session, every resource, and every follow-up conversation is designed to create.

Not a vague aspiration like "improve student outcomes" or "strengthen collaboration." A specific behaviour you can observe in a classroom or a staff meeting. Something like: teachers using formative assessment data to adjust their teaching within the same week. Or: middle leaders running team meetings that produce decisions, not just information sharing.

The behavioural shift becomes the filter for every decision in the plan. If a session does not directly build the skill or the habit that supports that shift, it does not belong in the plan. This is not about narrowing your ambition. This is about focusing your coherence.

Most schools try to run three or four unrelated improvement agendas at once. The staff cannot hold that much change in working memory. They default to what they have always done because the new behaviours never get the repetition required to become automatic.

One named shift, repeated and reinforced across every term, has more impact than five competing priorities that each get surface attention.

Choose the shift that, if it happened consistently across the whole staff, would move the school further than anything else you could do this year. Then build every session in service of that.

3. Decide whether your PD will be differentiated or uniform, and own the trade-offs

Some schools run the same PD for every teacher. Some schools split the staff into experience bands or role groups and deliver different content to each. Both approaches work. Both have costs. The mistake is trying to do both without the infrastructure to support differentiation, or doing neither and hoping one-size-fits-all lands for everyone.

Uniform PD is easier to plan, easier to resource, and creates a shared language across the whole staff. The cost is that your veteran teachers sit through content they already know while your early-career teachers are lost in the deep end.

Differentiated PD meets people where they are and accelerates growth faster. The cost is that it requires more facilitators, more resources, more logistical complexity, and a clear framework so the different streams still ladder up to the same whole-school goal.

What uniform PD requires to work:

• Content pitched at the middle of the experience curve, with extension challenges for veterans and scaffolding for newer staff

• Small-group application time during sessions where teachers work at their own level

• Follow-up support that differentiates even if the input session does not

What differentiated PD requires to work:

• A clear taxonomy that sorts staff into streams without creating status hierarchies

• Enough facilitators to run multiple concurrent sessions well

• A shared framework so every stream is building toward the same behavioural shift

The worst version is the school that runs uniform PD but tells itself it is differentiated because there is a handout with extension questions nobody uses. Decide which model you are actually running. Resource it properly. Own the trade-offs.

4. Identify the internal expertise you already have before you book external facilitators

Most schools have teachers on staff who are already doing the thing the PD plan is trying to build. They are using the strategy. They are running the structure. They are getting the results. The staff do not know this because nobody has surfaced it, named it, or built a session around it.

External facilitators bring fresh energy and new models. Internal facilitators bring proof that the change is possible here, with these students, under these constraints. Both matter. The mistake is defaulting to external voices when the most credible expert for your context is already in the building. When you do need external voices, look for professional development speakers for schools with genuine experience in educational settings, or review the best school PD providers in Australia to find facilitators who understand the specific pressures of Australian schools.

Run an internal expertise audit before you book anyone. Ask your middle leaders and your high-trust teachers: who on staff is already doing excellent work in the area the PD plan is targeting? Whose classroom would you send a new teacher to observe? Who has figured out a version of this that works?

Then decide how to use that expertise:

• Feature the internal expert as a co-facilitator alongside the external provider

• Have the internal expert run a follow-up session that shows what the external model looks like in your specific context

• Build observation rounds where other staff visit the internal expert's classroom and debrief what they saw

A PD plan that never highlights internal expertise sends the message that good practice only exists outside the school.

The other benefit is cost. Internal facilitators are already on payroll. Using them well means you can invest external budget in fewer, higher-leverage sessions rather than spreading it thin across a year of generic workshops.

5. Map the follow-up structure before you design the input sessions

The session is not the intervention. The session is the introduction. The intervention is what happens in the 12 weeks after the session when teachers try to use what they learned, hit obstacles, and either push through or revert to old habits.

Most PD plans are front-loaded. All the energy goes into designing the workshop. Follow-up is an afterthought, if it happens at all. This is why most PD does not stick. The input is fine. The follow-through structure does not exist.

Before you design a single session, map the follow-up cadence:

• What will teachers be asked to try in their classrooms in the two weeks after the session?

• When will they come back together to share what worked, what did not, and what they are adjusting?

• Who will observe them attempting the new practice and give them feedback?

• What micro-credential, reflection task, or accountability checkpoint will close the loop?

The follow-up structure should be decided at the same time as the session content. Not bolted on later. If you cannot name the follow-up before the session runs, the session is not ready.

Three follow-up models that work:

Micro-cycles: Session on Monday, teachers try the strategy Tuesday to Thursday, 20-minute debrief on Friday afternoon. Repeat every two weeks across the term.

Peer observation rounds: Session in Week 1, teachers visit each other's classrooms in Weeks 2 and 3 to watch the strategy in action, debrief together in Week 4.

Coaching partnerships: Session introduces the strategy, then pairs of teachers meet fortnightly to coach each other through implementation, with a shared reflection task due at the end of term.

The model matters less than the commitment. The follow-up cannot be optional. It has to be built into the calendar, protected from other demands, and treated as seriously as the input session itself.

6. Decide how you will measure whether the PD worked before the first session runs

If you wait until the end of the year to decide what success looks like, you will default to satisfaction surveys and attendance rates. Those tell you whether people showed up and whether they enjoyed it. They do not tell you whether anything changed.

The measurement framework has to be decided before the plan starts. Not because you need a research-grade evaluation, but because clarity on what you are measuring changes what you design.

Three levels of measurement to consider:

Engagement: Did teachers attend? Did they complete follow-up tasks? Did they participate in observation rounds? This is the easiest to measure and the least meaningful on its own.

Behaviour change: Are teachers using the strategy in their classrooms? Can you observe the new practice in action? Are middle leaders running meetings differently? This is harder to measure but far more meaningful.

Student impact: Has the behavioural change translated to different student outcomes? Better formative data usage, higher engagement, stronger work samples? This is the hardest to measure cleanly but the most important in the long run.

Most schools measure engagement and hope it correlates to behaviour change. The best schools measure behaviour change directly and track student impact as a lagging indicator.

For each session in your PD plan, name the observable behaviour you expect to see in classrooms within six weeks. That becomes your success metric. If you cannot name the observable behaviour, the session content is not concrete enough yet.

Then decide how you will collect the evidence. Classroom observations with a targeted rubric. Learning walks focused on the specific strategy. Teacher self-reports in a shared reflection doc. Video samples submitted to a shared drive. The method matters less than the commitment to look.

7. Lock in the non-negotiable calendar dates before anything else gets scheduled

PD sessions that get moved twice, shortened once, and finally cancelled because something more urgent came up are worse than no PD at all. They teach the staff that the plan is not serious and that follow-through is optional.

The first thing you do after the audit is lock the PD calendar. Every session date. Every follow-up window. Every observation round. Every debrief meeting. These dates go into the master calendar as non-negotiable blocks that other events must work around, not the other way around.

What gets locked into the calendar:

• The input session dates for every major PD topic across the year

• The follow-up debrief or reflection sessions that happen two to four weeks after each input

• The observation windows where teachers visit each other or middle leaders conduct learning walks

• The end-of-term review sessions where the whole staff reflects on progress toward the behavioural shift

Then communicate the calendar to the whole staff in Term 1. Not as a draft. Not as a proposal. As the locked plan. This is when PD happens. This is when follow-up happens. Plan accordingly.

The moment you move a session to make room for something else, you signal that PD is lower priority than whatever replaced it. Do that twice and the staff stop preparing. Do it three times and they stop showing up mentally even when they are in the room.

The calendar is the contract. Protect it the same way you protect exam periods and reporting deadlines.

CONTENT DESIGN: BUILDING SESSIONS THAT LEAD TO ACTION

Once the foundation is set, the next eight steps focus on designing the sessions themselves. These are the planning decisions that determine whether a session produces new thinking or new action. Most PD fails not because the content is wrong, but because the design does not create the conditions for teachers to use what they learn.

8. Start every session with the problem, not the solution

Teachers sit through dozens of PD sessions each year. Most of them open the same way: here is a framework, here is why it is good, now let me show you how to use it. The session might be excellent. The framework might be powerful. But if the teachers do not feel the problem the framework solves, they experience the session as interesting theory, not urgent practice.

The first 10 minutes of every PD session should be spent making the problem visible and personal. Not with abstract data about other schools. With specific moments from your school that every teacher in the room has lived. If you want ideas on how great facilitators open sessions, the guide on making a school PD day staff love walks through the techniques that consistently shift teacher engagement from passive to active.

Three ways to open with the problem:

Name the frustration: "How many of you have run a formative assessment, collected the data, and then had no idea what to do with it by Monday? That is the problem we are solving today."

Show the gap: "Our student voice surveys say they want more feedback. Our teacher surveys say we are already giving tons of feedback. Both are true. The problem is not the amount. It is the type."

Surface the pattern: "Three times this term, middle leaders have told me their team meetings feel like information dumps, not conversations. If that is you, this session is built for you."

When you start with the problem, the solution lands as relief. When you start with the solution, it lands as extra work.

The mistake is assuming everyone in the room already feels the problem. They do not. Some teachers have found workarounds. Some teachers do not notice the gap. Some teachers are so buried in survival mode they cannot see past Friday. Your job in the first 10 minutes is to make the problem undeniable and shared.

Then, and only then, introduce the framework as the answer to the problem they now feel.

9. Build application time into every session, not just discussion time

Most PD sessions end with a discussion. Teachers talk about how they might use the strategy. They share ideas. They ask clarifying questions. Then the session ends and everyone goes back to their classrooms, where the strategy never makes it past good intentions.

Discussion is useful. Application is essential. If teachers do not leave the session with something they created, adapted, or planned during the session itself, the transfer from theory to practice has to happen later, alone, when they are tired. It will not happen.

What application time looks like in practice:

• Teachers bring their upcoming unit plan to the session and adapt one lesson using the new strategy before they leave

• Teachers write the first formative assessment question they will use next week, share it with a partner, and refine it based on feedback

• Teachers script the exact sentence they will say when introducing the new classroom routine, then rehearse it aloud with a colleague

The application task has to be concrete, specific, and completable in the time available. Not "think about how you might use this." Not "plan to try this next term." Complete a usable first draft of the thing you will use next week.

How to structure application time so it actually produces work:

• Give a tight, specific prompt. Not "adapt this for your class" but "rewrite question 3 on your next assessment using the framework we just covered."

• Set a timer. 15 minutes of focused work beats 30 minutes of wandering effort.

• Have teachers share what they created with a partner or small group. Public commitment increases follow-through.

• Collect the work or have teachers photograph it and upload it to a shared space. What gets captured gets used.

The session is successful when teachers leave with a tangible artifact they can use Monday morning, not just a set of notes they might look at later.

10. Differentiate the depth, not the content, so the whole staff stays on the same page

If you are running whole-staff PD rather than split streams, you have teachers in the room at wildly different levels of readiness. Some are hearing the concept for the first time. Some have been using a version of it for years. Pitching to the middle leaves both groups disengaged.

The solution is not to split the session. The solution is to keep the content the same and differentiate the depth of application. Everyone learns the same framework. What they do with it during application time varies based on where they are starting.

Three-tier differentiation structure:

Entry level: Use the framework to solve a simple, constrained problem. Example: write one question using the new formative assessment approach.

Proficiency level: Use the framework to redesign an existing lesson or unit. Example: take a lesson you taught last term and rebuild the assessment sequence using the new approach.

Extension level: Use the framework to solve a complex, multi-layered problem or coach another teacher. Example: plan how you will introduce this framework to your faculty and support them through first implementation.

The facilitator introduces the framework to the whole group, then releases teachers into differentiated application tasks. Teachers self-select their entry point based on honest self-assessment. No ability grouping. No public sorting. Just clarity on what each level requires and permission to start where you are.

This keeps the shared language and the shared goal while honouring the reality that a five-year teacher and a 25-year teacher need different challenges.

The risk is that experienced teachers skip the session entirely because they assume it is pitched too low. The three-tier structure solves that. If the extension task is genuinely difficult and genuinely valuable, the veterans stay engaged.

11. Script the exact follow-up task teachers will complete before the next session

Vague follow-up produces vague action. "Try this in your classroom and see how it goes" produces nothing. Teachers need to know exactly what they are being asked to do, by when, and in what format.

At the end of every session, name the follow-up task in writing. Not as a suggestion. As an assignment with a due date and a submission method. Treat it with the same seriousness you would treat a student assignment.

What a well-scripted follow-up task includes:

• The specific action: "Use the formative assessment question stem from today's session to write three questions for your Year 9 unit on ecosystems."

• The due date: "Submit by Friday, Week 3."

• The format: "Post your three questions in the shared Google Doc under your name. Read two other teachers' questions and leave one piece of feedback on each."

• The purpose: "This task ensures you have practised writing the question type before we debrief together in the next session."

The task has to be small enough to complete in 30 to 45 minutes but meaningful enough that skipping it creates a gap in the next session. If someone shows up to the debrief without having done the task, they should feel behind.

How to hold the line on follow-up completion:

Make the next session dependent on it: If the debrief starts with "share what you noticed when you tried the strategy," teachers who did not try it have nothing to contribute.

Build peer accountability: If the task includes reading and responding to a colleague's work, skipping it means letting a peer down, not just disappointing leadership.

Track completion visibly: A simple shared tracker that shows which teachers have submitted creates gentle public accountability without shaming.

The moment you let follow-up become optional, the whole plan becomes optional. Hold the line early. The staff will rise to the expectation if the expectation is clear and consistent.

12. Use video or observation to show the strategy in action, not just to explain it

Teachers are practitioner learners. They trust what they can see working in a real classroom more than they trust what someone describes in a presentation. If you want a strategy to transfer, show it in action before you ask teachers to try it themselves.

This means every session should include video of the strategy being used well, or live observation of a teacher demonstrating it, or at minimum a detailed walkthrough that names the exact moves in sequence.

Three ways to show rather than tell:

Video exemplar: A three-to-five minute edited clip of a teacher using the strategy with real students. Pause the video at key moments to name what the teacher just did and why it worked.

Live demonstration: A teacher from your school demonstrates the strategy with a small group of students in the room, or in a fishbowl format where the rest of the staff observe and debrief.

Annotated walkthrough: A detailed written or visual breakdown of a lesson that names every move, every transition, every piece of teacher language, with commentary on what each part accomplishes.

Explanation builds understanding. Observation builds belief. Teachers need both before they will risk trying something new in their own classroom.

The video or observation does not have to be perfect. In fact, slightly imperfect examples are more useful because they show the strategy working under real constraints, with real student behaviour, in a real 50-minute period. Polished examples can feel out of reach. Authentic examples feel replicable.

13. Name the obstacles teachers will hit before they hit them

Every new strategy comes with predictable failure points. Teachers try it, hit an obstacle, assume they did it wrong, and abandon the strategy before they have given it enough repetition to work.

The session should name the obstacles in advance. Not to scare teachers off, but to normalise the struggle and script the response. When teachers know the obstacle is expected, they are far more likely to push through it.

Common obstacles to name and script responses for:

Obstacle	Scripted Response
The strategy takes longer than expected and you run out of time	Shorten the application task, not the instruction. Give students fewer problems to work through, but do not skip the modelling phase.
Students resist the new routine because it is unfamiliar	Name the resistance explicitly. Say: "This will feel different for the first two weeks. That is normal. We are building a new habit."
You try it once, it does not work as well as you hoped, and you abandon it	Commit to trying it three times before you evaluate it. The first attempt is always rough. The strategy shows its value by attempt three.

When you name the obstacle and script the response, teachers do not have to solve the problem alone in the moment. They have a pre-loaded move. This is the difference between a strategy that survives first contact and a strategy that gets abandoned after one bad lesson.

14. End every session with public commitment, not private reflection

Private reflection is comfortable. Public commitment is sticky. If you want teachers to follow through, do not end the session by asking them to quietly think about what they will try. End by asking them to say aloud, in front of peers, what they are committing to do.

Public commitment works because it activates social accountability. The teacher is not just making a promise to themselves. They are making a promise in front of colleagues who will ask how it went.

Three formats for public commitment:

Pair share: Teachers turn to a partner and say: "The one thing I am committing to try this week is [specific action]." The partner writes it down and follows up in a week.

Whole-group share: Go around the room and have each teacher name one specific action they will take. Keep it fast. One sentence per person. No elaboration.

Written commitment posted publicly: Teachers write their commitment on a sticky note and post it on a shared board, or type it into a shared doc where everyone's commitments are visible.

The commitment must be specific enough that someone else could observe whether it happened. Not "I will try to use this more." But "I will use this strategy in my Year 8 class on Wednesday during the ratios unit."

The other benefit of public commitment is that it surfaces who is genuinely planning to try the strategy and who is still skeptical. The skeptics are not the problem. The problem is when the skeptics stay silent and you assume everyone is on board. Public commitment makes engagement visible.

15. Build reflection prompts that produce insight, not performance

Most PD reflection prompts are too broad to produce useful thinking. "What did you learn today?" gets generic answers. "How will you use this in your classroom?" gets aspirational answers that do not translate to action.

Reflection prompts should be specific, diagnostic, and focused on obstacles. The goal is not to have teachers perform gratitude for the session. The goal is to have them think hard about what will make implementation succeed or fail in their specific context.

High-yield reflection prompts:

• "What is the one part of this strategy that will be hardest to implement in your classroom, and what is your plan for working through that difficulty?"

• "Describe the exact moment in your upcoming lesson where you will use this strategy. What will you say? What will students do?"

• "What existing practice will you need to stop doing or do less of to make room for this new approach?"

• "If you try this strategy and it does not work the first time, what will you adjust before you try it again?"

These prompts force specificity. Teachers cannot answer them with vague positivity. They have to think through the actual mechanics of implementation, which is where the learning deepens.

The reflection should happen at the end of the session, not days later. Capture it in writing. Then reference it in the follow-up debrief. Ask teachers: "You said the hardest part would be X. Was that true? What did you do about it?"

IMPLEMENTATION SUPPORT: MAKING SURE THE NEW PRACTICE STICKS

Content is necessary. Support is what makes the content stick. The next six steps focus on the infrastructure that surrounds the sessions and creates the conditions for sustained behaviour change. This is where most PD plans collapse. The sessions run. The follow-up does not.

16. Assign peer coaching pairs before the plan starts, not after the first session

Peer coaching works when it is built into the plan from the beginning. It does not work when you announce it halfway through Term 1 and hope people pair up on their own.

Before the plan starts, assign coaching pairs. Not based on friendship. Not based on who sits near each other in the staff room. Based on complementary strengths, teaching contexts that overlap enough to make observation useful, and existing trust.

What makes a peer coaching pair effective:

• Both teachers teach similar year levels or subjects so the strategies they are trying are directly transferable

• The teachers have different strengths so each person has something to learn from the other

• The pair has existing professional respect even if they are not close friends

• Their timetables allow them to observe each other without requiring expensive casual coverage

Once the pairs are assigned, give them a structure. Not just "support each other." A specific cadence and a specific task.

Peer coaching structure that works:

• After each PD session, pairs meet for 20 minutes to discuss what they are each planning to try and what obstacles they are anticipating.

• Within two weeks, each teacher observes the other attempting the new strategy in their classroom. The observation is short, 15 to 20 minutes, focused only on the specific strategy being implemented.

• Immediately after the observation, the pair debriefs for 10 minutes. What worked? What was harder than expected? What will you adjust next time?

• The pair co-writes a one-paragraph reflection on what they learned and submits it to the PD coordinator.

Peer coaching only works if it is as protected and non-negotiable as the PD sessions themselves. If it is optional, it will not happen.

17. Run learning walks with a narrow focus, not a broad observation rubric

Learning walks are most useful when they are focused on one specific element of practice, not when they try to evaluate everything at once. A broad observation rubric produces broad, unhelpful feedback. A narrow focus produces actionable insight.

If your PD plan is building toward a specific behavioural shift, the learning walks should be looking for evidence of that shift and nothing else. Not overall lesson quality. Not classroom management. Just the one thing the PD is designed to change.

How to structure a learning walk around the PD focus:

• Identify the specific observable behaviour the PD is designed to create. Example: teachers using formative assessment data to group students flexibly within the lesson.

• Build a one-page look-for guide that names what that behaviour looks like in action. Be concrete. Not "students are engaged" but "students are working in groups that were formed based on their responses to the entry question."

• Walk into classrooms for five to eight minutes. Look only for the specific behaviour. Take notes on what you see.

• Debrief with the leadership team immediately after the walk. What percentage of classrooms showed evidence of the behaviour? Where is it showing up? Where is it not?

The learning walk is not an evaluation. It is data collection. The goal is to understand how widely the new practice is being adopted so you know where follow-up support needs to be targeted.

What to do with the data:

If most teachers are using the strategy: Celebrate it publicly. Name specific examples of what you saw in classrooms without identifying individual teachers. Reinforce that the change is happening.

If some teachers are using it and some are not: Offer additional support to the teachers who have not yet adopted it. A follow-up coaching session, a peer observation opportunity, or a one-on-one check-in.

If almost no one is using the strategy: The PD design failed. Either the strategy was not concrete enough, the follow-up structure was not strong enough, or the behavioural shift was too big a leap. Adjust before the next cycle.

Learning walks give you real-time feedback on whether the PD is working. Use them early and often.

18. Create a shared resource bank where teachers upload what they create

One teacher writes a formative assessment using the new framework. Another teacher builds a slide deck that scripts the new questioning strategy. A third teacher creates a student handout that scaffolds the new structure. All of that work stays on individual hard drives and gets used once.

A shared resource bank captures the work teachers are already doing and makes it available to everyone. This multiplies the value of every artifact and reduces the duplication of effort.

What belongs in the resource bank:

• Lesson plans or unit plans that incorporate the new strategy

• Assessment questions or rubrics built using the new framework

• Student handouts, graphic organizers, or scaffolding tools

• Video of the strategy being used in a classroom, with the teacher's permission

• Reflection notes from peer coaching conversations

The resource bank has to be organized well enough that teachers can find what they need. Not a dumping ground. A curated library with clear categories, naming conventions, and quality control.

How to keep the resource bank useful:

• Assign one person to curate it. Their job is to organize submissions, remove duplicates, and highlight exemplars.

• Build submission into the follow-up tasks. When teachers complete an application task, they upload the result to the shared bank.

• Reference the resource bank in sessions. When introducing a new strategy, show teachers an example from the bank that a colleague created last term.

• Celebrate contributions. At the end of each term, name the teachers who contributed the most useful resources. Make contribution visible and valued.

The resource bank should become the first place teachers go when they are planning a lesson that uses the new strategy. If it is not being used, it is not organized well enough or not promoted enough.

19. Schedule debrief sessions at the midpoint and endpoint of each PD cycle

PD cycles need reflection points where the whole staff comes back together to share what is working, what is not, and what needs to be adjusted. These are not new input sessions. These are debrief sessions where teachers do most of the talking.

The midpoint debrief happens halfway through the implementation window. The goal is to surface obstacles early enough to solve them before they become reasons to quit.

The endpoint debrief happens at the end of the cycle, just before the next PD focus begins. The goal is to consolidate learning, celebrate progress, and name what carries forward into the next phase.

Midpoint debrief structure:

• Small groups share what they have tried so far and what early results they are seeing.

• Each group identifies the single biggest obstacle they are hitting. Write it on a chart.

• The whole staff looks at the list of obstacles and problem-solves together. What has someone else tried that worked? What adjustment would help?

• Teachers leave with one new move to try based on what they heard from peers.

Endpoint debrief structure:

• Teachers reflect individually on what changed in their practice over the cycle. What are they doing now that they were not doing 10 weeks ago?

• Pairs or small groups share their biggest win and their biggest remaining challenge.

• The whole staff identifies which elements of the new practice will continue and which will be adjusted or dropped.

• Leadership names what they observed during learning walks and what it tells them about readiness for the next PD focus.

The debrief sessions are where collective learning happens. Teachers hear what worked for others. They realize they are not alone in the struggle. They get ideas they would never have come up with in isolation.

If you skip the debrief, teachers move into the next PD cycle without consolidating the learning from the last one. The cycles stop compounding.

20. Build micro-credentials or badges that recognize skill development, not attendance

Most schools recognize PD completion with hours logged or sessions attended. This rewards showing up, not learning. If you want to reward actual skill development, you need a recognition system tied to demonstrated competence.

Micro-credentials and digital badges work when they are attached to specific, observable skills that teachers can demonstrate through evidence of practice. Not through a quiz. Through work they have done in their classroom.

What a micro-credential requires:

• A clearly defined skill or practice that the PD is designed to build

• A submission task where the teacher provides evidence they can use the skill in their own classroom

• A simple rubric or checklist that defines what good-enough looks like

• A review process where someone with expertise verifies the evidence and awards the credential

Example micro-credential structure:

Skill: Using formative assessment data to adjust instruction within the same week.

Evidence required: Submit a one-page reflection that includes (1) the formative assessment task you used, (2) what the data told you about student understanding, (3) what you adjusted in your teaching based on the data, and (4) what you observed about student learning after the adjustment.

Review criteria: The reflection demonstrates that the teacher collected data, interpreted it, made a specific instructional change, and observed the impact.

Credential awarded: Digital badge posted to the teacher's professional profile, recognized in a staff meeting, and noted in their performance review.

Micro-credentials work because they make skill development visible, portable, and something teachers can take pride in.

The credential does not have to be elaborate. It just has to be meaningful, evidence-based, and genuinely harder to earn than showing up to a session.

21. Protect time for teachers to collaborate on implementation, not just to consume content

Teachers do not need more content. They need more time to work together on turning the content they already have into classroom-ready practice. Most PD plans are input-heavy and collaboration-light.

The plan should include protected collaboration time where teachers work in small groups to co-plan lessons, co-create assessments, and co-solve implementation problems. No facilitator. No new input. Just time to do the work together. One of the clearest signs this is going wrong is fragmentation in the leadership team itself. If you are noticing silos in your school leadership team, protected collaboration time built into the PD plan is one of the most effective structural responses.

What collaboration time should be used for:

• Co-planning a unit that incorporates the new strategy across multiple lessons

• Co-creating formative assessments that use the new question types or rubric structures

• Co-analyzing student work samples to see whether the new strategy is having the intended impact

• Co-solving specific implementation problems that individual teachers are stuck on

The collaboration time has to be long enough to produce something. Not 20 minutes. At least 60 to 90 minutes. And it has to happen during the school day, not after hours when teachers are too tired to think well.

How to structure collaboration time so it produces output:

• Give a specific task with a specific deliverable. Not "work on your unit plan" but "write the three formative assessment checkpoints for Unit 4 and upload them to the shared folder by the end of the session."

• Organize groups by subject, year level, or teaching context so the work is directly relevant to everyone in the group.

• Set a timer and hold the line on the task. Collaboration time drifts into social time if there is no accountability for output.

• Collect what groups produce and use it in the next session as exemplars or as the foundation for further work.

Collaboration time is not a break from PD. It is the most valuable part of PD because it is where theory becomes practice in the hands of the people who will use it.

LEADERSHIP MOVES: WHAT YOU DO TO HOLD THE SYSTEM TOGETHER

A PD plan does not run itself. It requires consistent leadership moves that signal priority, surface problems early, and keep the whole system accountable to the goal. The final four steps are the things you do as the leader to make sure the plan does not drift.

22. Model the strategy yourself in a visible setting before you ask the staff to use it

If you are asking teachers to try something new, you need to try it first in a context where the staff can see you do it. Not perfectly. Just genuinely.

This does not mean you have to teach a full lesson in front of the staff. It means you have to use the strategy in a meeting, a communication, or a leadership moment where teachers can observe you taking the same risk you are asking them to take.

Three ways to model the strategy as a leader:

• If the PD is about better questioning techniques, use those techniques in the next staff meeting. Ask the questions. Wait for the thinking time. Show the staff what it looks like.

• If the PD is about using data to adjust practice, bring student data or staff survey data to a leadership team meeting and walk through how you used it to adjust a decision.

• If the PD is about giving better feedback, give public feedback to a middle leader using the structure you are asking teachers to use with students. Make the model visible.

Teachers watch what you do more closely than they listen to what you say. If you do not use the strategy, they will assume it is not really important.

The other benefit of modelling is that it gives you insight into why the strategy is hard. When you try to use a new questioning technique in a staff meeting and it feels awkward, you understand why teachers are resisting it. That empathy makes your follow-up support better. If you want to go deeper on the leadership behaviours that build a genuine learning culture, the guide to leadership development experts for schools is a strong companion read.

23. Check in on progress weekly, not termly, so you catch problems early

Most schools check on PD progress at the end of term. By then, the teachers who were going to implement have implemented. The teachers who were going to struggle have already given up. The feedback loop is too slow to be useful.

Check in weekly. Not through formal evaluation. Through quick pulse checks that take five minutes and give you real-time data on who is stuck and where.

Weekly pulse check methods:

Slack or Teams poll: Post a two-question poll every Friday. "Did you use the strategy this week? If not, what got in the way?" Responses are anonymous. Data is visible.

Shared tracker: Teachers update a simple shared spreadsheet each week noting whether they tried the strategy and what they noticed. Takes two minutes. Leadership reviews it Monday morning.

Corridor conversations: Walk the hallways with intention. Stop into three classrooms. Ask one question: "How is the new strategy going?" Listen for patterns.

Middle leader reports: Ask middle leaders to report weekly on what they are seeing in their faculty. Not formal evaluations. Just observations. What is working? What is not?

The weekly check-in is not about catching people out. It is about catching problems early enough to fix them. If Week 2 data shows that half the staff tried the strategy and half did not, you know you need to intervene before Week 3.

What to do with the weekly data:

If most teachers are implementing: Send a short email celebrating what you are seeing. Name specific examples without identifying individuals.

If some teachers are stuck: Reach out directly. Offer help. Connect them with a peer who is having success. Schedule a coaching conversation.

If the whole staff is struggling: The strategy or the support structure needs adjustment. Do not wait until the end of term. Adjust now.

Weekly check-ins give you the information you need to support the plan in real time, not to evaluate it after the fact.

24. Celebrate small wins publicly and specifically, not just at the end of the year

Most schools celebrate PD success once, at the end of the year, in a generic way. "Thank you for your commitment to professional growth." That does not reinforce specific behaviour. It does not tell teachers what to keep doing.

Celebrate small wins publicly and specifically every few weeks. Name what you saw. Name who did it. Name why it mattered.

What to celebrate and how:

• A teacher who tried the strategy for the first time and shared their reflection in the follow-up doc. Celebrate them in the next staff meeting. Read their reflection aloud.

• A middle leader who observed three teachers using the strategy and gave them specific feedback. Thank them publicly and ask them to share what they noticed.

• A peer coaching pair who co-created a lesson using the new framework and uploaded it to the resource bank. Feature their work in the next PD session.

• A faculty that hit 100 percent completion on the follow-up task. Recognize them in the staff bulletin and ask what made it possible.

Public celebration does two things. It rewards the people doing the work, and it shows everyone else what good looks like.

The celebration has to be specific. Not "great job everyone" but "Year 7 Humanities used the formative assessment framework to rewrite their entire unit, and early data shows student understanding is stronger than it was last year. That is what we are aiming for."

Specific celebration reinforces the behaviour you want to see more of. Generic celebration reinforces nothing.

25. Review the whole plan at the end of the year and name what you will stop, start, and continue

At the end of the year, run a full review of the PD plan. Not a satisfaction survey. A hard look at what worked, what did not, and what needs to change before you build next year's plan.

The review should involve the whole staff, not just leadership. Teachers know what helped and what was noise. Ask them directly.

Three-part review structure:

Stop: What elements of this year's PD plan did not produce the intended behaviour change and should be dropped? What sessions felt like a waste of time? What follow-up structures were ignored?

Start: What new approaches, structures, or supports do we need to add to next year's plan based on what we learned this year? What gaps became obvious? What would have made implementation easier?

Continue: What elements of this year's plan worked well and should be carried forward unchanged? What sessions produced real change? What follow-up structures were used and valued?

The review data should directly inform next year's plan. If teachers say the peer coaching pairs were the most valuable part of the year, double down on that. If they say the end-of-term reflection tasks were busywork, drop them.

How to run the review session:

• Give teachers 10 minutes to reflect individually on the three questions: stop, start, continue.

• Small groups share their reflections and consolidate their top three answers for each category.

• Each group reports out. Leadership captures the themes on a shared document.

• Leadership commits to reviewing the data and sharing a summary of what will change in next year's plan by the end of the break.

The review is not performative. It is diagnostic. Use it to build a better plan next year, not to defend the plan you just ran.

A PD plan that never changes year to year is a plan that is not learning from its own implementation. The review closes the loop and makes the system self-improving.

A whole-school PD plan is not a list of sessions. It is a system designed to create sustained behaviour change across a full calendar year. The sessions matter. The follow-up structure matters more. The leadership moves that hold the system accountable matter most.

If you can name the one behavioural shift you want to see by December, build a follow-up structure that creates repetition and support, and check in weekly so you catch problems before they become reasons to quit, you will run a PD plan that actually sticks. Your next step is simple. Pick the one planning move from this list that your current plan is missing and build it in before the next session runs. If you want help thinking through how these pieces fit together for your specific school, reach out at jonno@consultclarity.org.