The school as an organization: why good ideas die in the staff room

At the end of August it looked great. At the opening staff meeting, someone proposed a shared drive where everyone would store lesson prep and worksheets by subject and grade. Nobody objected. The principal backed it, one colleague set up the folders and sent the link. By October there were nine files in it, seven of them from the same person. By January nobody remembered it existed.

Every staff room knows this story, and it has at least a hundred variants: a digital absence form, a unified format for topic plans, a shared test bank, a substitute-teaching system, a shared events calendar. The idea was good, nobody objected, and yet nothing happened. The easy explanation is "teachers are set in their ways." It's convenient, and it's wrong. The previous chapters in this series looked at the individual teacher — their energy, their prep, their grading, their attention in the classroom. This one looks a level up and makes an uncomfortable claim: most of what exhausts teachers most doesn't come from the classroom, but from how the school is organized as an institution — and no personal system can fix that.

A school is a peculiar type of organization. It looks like a company with a director, staff, and a budget, but it functions completely differently. Anyone who imports corporate management practices wholesale will hit a wall. Anyone who gives up on organization altogether, on the grounds that "schools are just different," condemns the staff room to reinventing the same thing every year. The path runs through the middle, and it starts with understanding why things get stuck here.

Three reasons why anything systematic is hard to introduce in a school

Teacher autonomy is a value, not defiance

By the nature of the job, a teacher is an independent professional. Behind the closed door of the classroom they decide alone and carry the responsibility alone. This autonomy isn't a shortcoming — it's the condition that lets them respond to specific children in a specific moment. No policy can spell out what to do when a child whose parents are divorcing bursts into tears in second period.

But autonomy has a price. When everyone on staff has the right to do things their own way, nobody has a natural mandate to tell everyone else "from now on we do it like this." In an ordinary company, a team has a manager who makes that call and stands behind it. In a school, the gap between the principal and thirty autonomous professionals is thin, and a decision often turns into a request. A request can be ignored without consequences — and in an overloaded operation, almost anything that isn't mandatory gets ignored.

Practical consequence: no change in a school gets adopted just because it's logical. It has to be adopted as something that concretely saves a specific teacher time or worry. The rest of this chapter is essentially about that.

The middle layer of management is missing

In a company of fifty people, there are typically five to eight managers who spend most of their time coordinating others' work. In a school of fifty staff, there are usually two or three people in leadership — and they're teaching at the same time, plus handling inspections, building operations, budget, HR, and complaints.

Subject-department heads and coordinators of teaching teams are supposed to be that middle layer, but they almost never have the essential thing: time, mandate, and tools. A department head usually has no reduced teaching load, can't require anything of anyone, and their role in practice shrinks to calling two meetings a year and submitting a plan. As a result, there's nobody whose job it is to follow through on what got agreed at a meeting.

Introducing change then inevitably rests on a volunteer enthusiast. The enthusiast carries it as long as they have the energy, and when they run out, it falls apart. A school that wants functioning material-sharing or a unified absence system needs to create real conditions for this role — an hour a week built into the teaching load, clearly defined authority, and visible backing from leadership. Without that, it's a hobby, not a process.

There's no time, because it's fragmented

A teaching day is made of forty-five-minute blocks, between which there are ten minutes for moving, duty, the copier, and four questions in the hallway. There's no hour of uninterrupted calm in it during which something could be thought through or set up. Anyone wanting to introduce a new system has to introduce it in time the schedule simply doesn't have.

That's why changes that require an upfront investment don't work in schools ("first everyone upload their materials, it'll pay off later"). The investment never happens, because there's no time for it. What works are changes that fit into an already-existing moment — into a meeting that's happening anyway, into a Friday afternoon someone's already set aside for paperwork, into prep they're writing anyway. The personal rhythm of prep discussed in earlier chapters of this series is therefore only half the story — the other half is making sure the school's own operations don't break it.

A meeting that's actually worth having

A staff meeting is the one moment when the whole staff is in one room. Precisely because of that, everything gets crammed into it — and that's exactly what devalues it. When forty people sit for ninety minutes listening to information that could have been read in four, the school just burned sixty person-hours on something that could have been one email. And worse: next time, nobody listens, because they've learned that nothing important gets said in a meeting.

The decision rule is simple and could be posted on the staff room wall. A meeting is for things that require a decision, aligning perspectives, or a genuine discussion. Everything that's just information belongs in an email or a shared document. Deadlines, event logistics, schedule changes, results, notices, lists — all of that is information, not a meeting. Information gets read faster than it gets listened to, and crucially, it can be looked up again, which nobody ever remembers to do after a meeting.

The test for whether something belongs on a meeting agenda is: what happens if I write it down? If the answer is "people will read it and it'll be clear," it doesn't belong in the meeting. If the answer is "five questions will come up and two people will object," you've got a ready-made agenda item.

That leads to a few concrete habits that cost almost nothing:

• An agenda in advance, or the meeting doesn't happen. Whoever calls the meeting notes for each item whether it's information, discussion, or a decision, and how many minutes it gets. More on this discipline in the tip no agenda, no meeting.
• Minutes within 24 hours, and specifically minutes of decisions. Not a retelling of the discussion, but what we decided, who's doing it, and by when. Without that, the meeting was just time spent together.
• Check on commitments at the start of the next meeting. Three minutes on whether what was promised actually happened. Nothing raises the seriousness of agreements as reliably as knowing you'll be asked about them next time.

A complete system, including an audit of your own meetings, timeboxing individual items, and minutes with action items, is in the tip the meeting that won't eat your day. If you run a pedagogical council or a subject department, the part on minutes will save you the most work — you get a structured output from a recording or your own notes that separates decisions from discussion. The how-to is in the tip meeting minutes with action items, and one basic rule applies here as it does across the whole site: AI proposes, the human approves. Minutes from a pedagogical council are signed by you, not by the model.

A special category is meetings that aren't really meetings, but collective document-writing. A session where forty people jointly wordsmith a sentence for an annual report is the most expensive way of writing that humanity has ever invented. One person writes the draft, everyone else comments on it asynchronously, the meeting only handles the contested points.

Parent communication as a process, not improvisation

Most of the exhaustion from parent communication doesn't come from parents being hostile. It comes from unpredictability: a message can arrive at any time, through any channel, with any expectation about how fast the reply should be. A teacher who has boundaries set in the classroom often has none toward the thirty families writing to them in the school system, on their personal phone, over a WhatsApp group, and on Messenger.

The fix isn't being more disciplined. It's the school — as a whole, not individual teachers — agreeing on three things and telling parents right at the start of the year.

Channels. How many there are and what each is for. A reasonable minimum is two: the school system for anything official (absence notes, grades, forms) and a school email for questions and arrangements. A teacher's personal phone is not a channel. A parents' group chat is not a school channel, whatever happens in it. When a school has clearly stated where communication flows, declining a different route stops being personal rudeness and becomes a rule that applies to everyone.

Turnaround times. By when a teacher replies — a realistic, achievable window is two working days. A parent who knows a reply will come within two days doesn't send a second message three hours later. A teacher who knows they have two days doesn't have to reply at ten at night in the middle of grading. It's worth spelling out what the window doesn't mean too: in urgent situations, you call the school office, you don't message the homeroom teacher.

Escalation. What happens when something doesn't get resolved between a parent and a teacher. Who's next in line (homeroom teacher, guidance counselor, deputy, principal) and at what point that happens. A school without a described escalation path has two bad variants: either the teacher handles alone what should go to leadership, or a parent writes straight to the principal and the teacher finds out third-hand. Both destroy trust.

This framework does its best work in hard cases — underperformance, a discipline issue, suspected bullying. When a situation is heated, it's enormously valuable to already know in advance who writes to whom, by when, and what happens next. For wording such messages, for prep for parent evenings and three-way meetings, and for converting ongoing notes into a matter-of-fact narrative comment, there's a dedicated guide: narrative comments and parent communication. One hard condition applies to it: data about specific students is sensitive data. It belongs only in a paid account with contractual data protection, and even there it gets anonymized. A message sent to a parent is always read and signed by the teacher.

Documentation: what's required and what we added ourselves

In staff rooms it's commonly said that paperwork has grown to unbearable proportions. It's true, but there's a trap hidden in it. When a specific school actually sits down and goes through, piece by piece, everything it fills in, it usually finds that a significant share of it didn't come from the law or from an inspection requirement, but from its own decision — often long forgotten, adopted after some unpleasant experience, or copied from another school.

A useful exercise for leadership and subject departments: take the list of everything teachers fill in, and answer three questions for each item. Who requires it? Who actually reads it? What happens if it doesn't get done?

The answers sort into three piles. The first is genuine requirement — the class register, the pupil file, documentation for support measures, things that follow from regulations. Those can't be touched, only simplified in form. The second is things that make sense but nobody would think of — like a record of a conversation with a parent, which comes in handy if the matter goes further. Those are worth keeping, but the reason for keeping them should be stated out loud. And the third pile is habits with no owner: a table nobody reads, a report duplicating data already in the system, a filing requirement introduced because of an event from 2017.

That third pile is the one place where school leadership can genuinely and quickly cut work. Scrapping one unnecessary form is worth more to staff trust than three motivational speeches about wellbeing. And the reverse also holds: before a school introduces a new report, it should answer the question "and what are we scrapping in exchange."

The rest of the paperwork can be sped up. Topic plans derived from the curriculum, material for the annual report, evaluations, grant applications, and inventory orders all share the fact that they're recurring structures that just need to be written well once and then updated. The process, plus a set of templates that means the same paper never gets written twice, is in the tip department admin with AI.

Sharing materials: why it doesn't work on its own

Let's go back to the shared drive from the opening. It failed for four reasons, and all four can be fixed in advance.

Nobody knows where anything goes. An empty drive is an invitation for everyone to invent their own logic. Half a year later, there are twenty structural ideas inside and nothing can be found. Structure has to exist before content, has to be stupidly simple (subject → grade → topic unit), and has to have a specific person watching over it.

Uploading costs more than taking. Whoever uploads has to name the file, file it, possibly clean it up. Whoever takes just downloads. This asymmetry of cost reliably kills sharing. It can be shrunk with a single trick: allow imperfection. Material gets uploaded as it is, margin notes and typos included. A shared drive where only polished materials are allowed will stay empty.

Nobody sees that it's being used. A teacher who uploaded fifteen files and never heard that anyone opened them will stop. A small thing is enough — saying out loud at a department meeting, "I used your fractions worksheet and it worked." Visible use is the only reward this system offers, and it has to be voiced.

There's no reason to upload right now. The strongest habit is one tied to the moment the material gets created anyway: whatever I'll use in class, I save straight to the shared folder, not to my own "new stuff" directory. Sharing as a separate task at the end of the semester never happens.

The most valuable thing to share isn't finished materials, but assignments and criteria. Two teachers of the same subject who swap a test and its grading criteria learn more about their own teaching than from ten classroom observations. It's also the fastest route to aligning expectations across parallel classes — something parents notice far more sensitively than staff rooms tend to assume.

How to introduce change in a staff room

There's a pattern that works far better in schools than a blanket mandate. It's not a trick to work around people — it's a way of letting something prove itself before it becomes an obligation.

Three notes on what this approach does differently.

First, the order: evidence instead of a mandate. An imposed change spends the leadership's authority, which then has nothing left when it's needed for something more serious. A change backed by a colleague's experience builds authority instead.

Second, the scope: one change per semester. A staff room hit in September with a unified prep format, a new absence system, and mandatory material sharing all at once will manage none of them. An overloaded person doesn't resist a specific new thing — they resist the pile-up.

Third, the right to fail. A pilot that gets scrapped after a semester because it didn't prove itself isn't a loss — it's the cheapest possible outcome, and it dramatically increases willingness to try the next thing. A staff where every introduced idea has to be defended at all costs will stop proposing ideas at all.

Leadership's role: what only the principal can do

Most of what this chapter discusses can be done from the bottom up too. But three things nobody except leadership can do.

Protect time. The decision that a meeting lasts fifty minutes, not ninety, that the same data doesn't get filled in twice in two different reports, that Friday afternoon is meeting-free — all of that is leadership's authority, and it can't be worked around by teachers' goodwill alone. Time in a school is zero-sum: anything new has to displace something, and deciding what that is is the principal's job.

Give the middle layer a mandate and conditions. A department head tasked with following something through needs to hear, out loud and in front of others, that the principal has put them in charge and that their decisions stand. And they need room in their teaching load for it, not just trust.

Cover the pilot. When three volunteers are trying something and someone objects that it's never been done this way, leadership has to stand behind the attempt. One moment of unspoken lack of support reliably kills willingness to try anything else for years.

And one more thing that can't be mandated: leadership determines what counts as normal at a school. A principal who sends emails at eleven at night has just told the staff when work happens — whatever their email signature says. Organizational culture isn't transmitted through documents, but through what visible people do. How similar mechanisms work outside a school is covered in the chapter Team productivity; the section on tools and asynchronous communication carries over into a staff room almost without change.

Key takeaways

• A school isn't conservative, it's built differently. Teacher autonomy, a missing middle layer of management, and fragmented time are three structural reasons systemic changes get stuck — and all three can be worked around once you plan for them.
• A meeting is for decisions, an email is for information. The test is simple: try writing the item down first. If it's clear once written, you just saved yourself a meeting; if questions come up, you have an agenda.
• Parent communication needs channels, turnaround times, and escalation — agreed by the school, not individuals, and communicated to parents at the start of the year. Without that, every teacher carries the unpredictability alone.
• Sort paperwork into required, meaningful, and habitual. Scrapping one unnecessary report does more for staff trust than a speech about wellbeing. Before adding a new one, say what disappears in exchange.
• Sharing materials doesn't happen on its own: it needs structure set up in advance, permission to be imperfect, visible use, and a tie to the moment the material gets created anyway.
• Introduce change through volunteers, a pilot, and evidence, not a mandate — one per semester, with a named owner, and the right to scrap the pilot after evaluation.