Switch course ▾
Session 5. Sustaining PLCs Through Change and Making the Case
Objective. Build routines that outlast individual leaders, run a succession stress test on your network, and write and present a one-page briefing that asks the board or education department for a clear decision.
A network that works only while its founder is present is a project, not a system. School leaders change, grants end and good teachers move, and each of those events is a test your network will meet within a few years. This session asks you to run that test now, on paper, while the cost of failing is only a bad afternoon. You will leave with a handover pack, a plan for four kinds of change, and a one-page briefing that asks for one clear decision.
Key ideas
Why PLCs fade
- Many PLC networks start well and fade within two or three years. Typical causes: the champion leaves, a new head teacher arrives with a different priority, exam pressure fills the timetable, a grant ends, or the network lived in one person's memory.
- Hargreaves and Fink (2004) studied eight schools over three decades and argue that leadership matters most when its effects last beyond one leader's time. Their principles include planning for succession from the first day, spreading leadership, valuing diversity over standardisation, and making resources and well-being part of the plan.
- The point is not to stop change but to make the PLC survive it. Ask of each part of your system: if the person who runs it left tomorrow, what would stay?
Build into routines, not into a person
- Write the system down in a handover pack of five items: the one-page charter, the calendar, the evidence folder (pupil work before and after), a who-is-who with roles and terms, and a list of what we stopped and why. A new leader can read it in 30 minutes.
- Put the PLC into the places that outlast people: the school development plan, the timetable (the shared period), the role description of a deputy or methodist, and the induction of new teachers. What is in the timetable survives a change of head teacher more often than what is in a speech.
- Grow the next leaders on purpose: every team has a co-leader, leadership of teams rotates every two years, and the steering group always includes someone who joined in the last two years.
Surviving four kinds of change
- New head teacher: send the handover pack before they start, offer a 20-minute briefing in the first month and invite them to sit in on one team meeting. Present the PLC as how the school already learns, not as a request for support for your project.
- Staff leave: pair every newcomer with a buddy and let them attend two meetings before taking a role. Budget cut: separate the core (the protected hour and the pupil-evidence meeting) from extras (visits, printing) and shrink the extras first. Exam pressure: agree a lighter mode for exam weeks, such as one meeting instead of two, rather than silent abandonment.
- A decision rule for all four: protect the meeting where teachers look at pupils' learning evidence first. Everything else can shrink; that meeting is the reason for the whole system.
Making the case to the board
- A board, governing council or education department reads many papers. Write one page with five parts: the situation in two sentences, what we did, what we saw (with honest limits), what it costs in hours and money, and the decision we ask for. Put the decision first if the reader has only a minute.
- Ask for something specific and small: protect the shared period for another year, accept a one-page cluster report instead of ten school reports, recognise network hours as professional development under current ministry regulations. A vague request such as 'support us' gets a vague answer.
- Prepare for five questions: What does it cost? What did pupils gain? What do you stop? What if you leave? How do other schools get involved? Remember DeWitt's reading of Hargreaves and O'Connor: collaboration should challenge thinking and focus on real problems of practice, so show a real problem you worked on.
Two ways to keep a network alive
Depends on a person
Fragile
- The calendar is in one head
- Hours are a favour of the head teacher
- Evidence is in private folders
- A grant pays for everything
Built into routines
Durable
- Handover pack and co-leaders
- The hour is in the timetable and school plan
- Evidence folders in a shared place
- Core is cheap; extras can shrink
Knowledge that lives only in one head
Every network has things that only one person knows: where the evidence folders are, why a theme was chosen, who is quietly doing the work. This is tacit knowledge, and it is the first thing lost when the person leaves. The handover pack is a way to put it on paper, but writing it also shows the founder what has never been explained to anyone.
A useful test is to give the pack to a person who has never seen the network and ask them, after 30 minutes, to explain it back. The parts they cannot explain are the parts that will not survive a change of leader. Fix those first. This is also a respectful way to prepare a successor, because it treats them as someone who will lead, not just inherit.
Asking for one decision
Boards and departments act on decisions, not on information. A briefing that describes your work well and asks for nothing gets applause and no change. A briefing that asks for one specific, small decision, with the cost and the evidence and its limits, gives the board something it can say yes or no to. Make the decision something the board can actually grant: a protected period, a merged report, recognition of hours.
Prepare for the questions behind the question: what does it cost, what did pupils gain, what do you stop, what if you leave, and how do other schools join? If you can answer each in a sentence, the briefing is ready. If you cannot, you have found what the network still needs to work on.
Examples from the classroom
The handover test
Scene. Before moving to another district, Malika, a deputy head in a Tashkent-region cluster, writes the five-item pack and gives it to a teacher from another school. After 30 minutes the teacher explains the network but cannot say why Grade 4 teams meet on Thursday or where the evidence folders are. Malika adds a two-line note on the Thursday slot and a list of the nine folders. Her successor starts with the pack and one visit.
Insight. A handover pack is tested by someone who has never seen the network, not by the author.
The new head and the exam results
Scene. A new head arrives at a school in Samarkand and says exam results come first. The coordinator sends the pack, meets her for 20 minutes and invites her to sit in a Grade 9 team meeting that is looking at pupils' written answers to an exam-type task. The head sees pupils' reasoning that she had not known about. She keeps the Thursday period and asks the team to share what it learns with the other Grade 9 teachers.
Insight. Show a new leader how the network serves their priority instead of defending it as your project.
Cut the extras, keep the core
Scene. A grant for printing and travel ends in a Fergana cluster. The steering group lists core items (the Thursday hour, the meeting where teachers look at pupils' work) and extras (travel, printed packs). It moves to rotating host schools, keeps one printed pack per team and asks the district to recognise network hours. A year later all 14 teams still meet, and the cluster has only lost two visits.
Insight. Protect the meeting about pupils' learning first; extras can shrink without killing the system.
Common pitfalls
- Writing a handover pack only when the founder is leaving.
- Presenting a new leader with a long history rather than a short pack and a visit.
- Cutting all activities equally when funding falls, including the core meeting.
- Asking the board for 'support' instead of one decision.
Stress-Test the Network and Brief the Board
- Open the Activity Kit: a SAMPLE network in its third year, four stress-test scenario cards, a handover-pack checklist and a briefing template. In your own cluster use your real network. (5 min)
- Groups of four (25 min): each group takes two scenario cards. For each, write what breaks first, what survives, what you do in the first 30 days and which routine would have prevented the break.
- Pairs (15 min): tick the handover-pack checklist against the sample network and list the missing items. Decide who writes each, and by when.
- Part B, the briefing (25 min): write the one-page briefing to the board (situation, what we did, what we saw, cost, decision asked). Then present it in 3 minutes to another pair who ask the five board questions.
- Alone (15 min): write your final leadership task from the Kit, and list the three documents from this course you will use first.
Your facilitator will guide you through this activity in the session.
Questions to discuss
- Which part of your network would not survive the departure of one person, and what is the first fix?
- What did the board's hardest question reveal about your briefing?
- What will you stop doing so that this network lasts, and who must agree?
Reflect
- If you changed schools next month, what would your network keep doing?
- Who is your most likely successor, and what have you shown them?
- What is the one decision you would ask your education department for?
Try it tomorrow
- Write the five items of a handover pack for your network and give them to someone who has not seen it.
- List which parts of your network would break if you left tomorrow, and who could take each part.
- Write the first line of a briefing that asks for one specific decision, and read it to a colleague.
Further reading and links
Write the network into routines, a handover pack and the timetable, protect the meeting about pupils' learning first, and ask the board for one specific decision.