Schools That Scale: Building Systems for Growth

I've watched the same pattern play out more than once across different institutions and different countries: a school or centre that runs well at a single site, under a manager who knows every teacher and every class personally. This school begins to expand, and somewhere around the second or third site, quality starts to feel noticeably less consistent, without anyone quite being able to point to a single decision that caused it. It isn't usually that standards were deliberately lowered. It's that the systems holding quality together at one site were never actually systems at all. They were a person, and that person cannot be in three places at once.

I think this is one of the more predictable failure points in growing an educational institution, and also one of the more avoidable ones, provided the shift from person-dependent quality to system-dependent quality happens deliberately rather than being left to sort itself out under pressure.

What Breaks First

In my experience, the first thing to break as a school scales is rarely the curriculum itself. It's usually the informal knowledge that never got written down because it never needed to be, while everything ran through one experienced manager who simply knew, without needing a document to tell them, how a particular type of student complaint should be handled, or which teachers needed closer support in their first term, or what a good lesson actually looked like in that specific context. None of that knowledge disappears when a school grows. It simply stops being accessible to the new site, the new manager, or the new intake of teachers who never had the chance to absorb it informally. This kind of knowledge is well documented in leadership research: Gunter (2016) notes that much of what school leaders know, they learn by working alongside others, "not least learning how not to do it," and that this experiential knowledge is rarely made visible or written down.

The second thing to break, usually not far behind, is observation and feedback consistency. A single site with one experienced observer tends to produce a reasonably consistent standard, even an informal one, because the same person is applying broadly the same judgement across every lesson. Add a second site with a second observer, and unless real care has gone into calibrating what "good" actually means between them, you very quickly end up with two different implicit standards operating under one brand, which teachers notice long before management usually does.

"The systems holding quality together at one site were never actually systems at all. They were a person, and that person cannot be in three places at once."

Building Systems Before You Need Them

I think one of the more counterintuitive lessons from watching several schools scale is that the systems worth building are rarely the ones that feel most urgent in the moment. It's tempting to solve today's specific problem with a specific fix, and to leave the underlying pattern for later, but the schools I've seen scale well tended to invest in quality infrastructure earlier than may have seemed necessary: a shared observation rubric that meant "good" carried roughly the same meaning across sites; an induction process detailed enough that a new manager could run it without months of informal mentoring first; documentation of the small operational decisions, such as level-change requests or staff annual leave records, that would otherwise live only in one person's memory.

This is slower and less satisfying than solving the immediate problem in front of you, and I think that's precisely why it's often skipped. It rarely feels urgent until the absence of it becomes an actual crisis, usually at the worst possible moment, such as an experienced manager leaving unexpectedly and taking a great deal of undocumented knowledge with them.

The Role of the Person Who Built It All

Gronn (2000), in his work on distributed leadership, argues that leadership shouldn't be understood as residing in an individual or in a structure alone, but in the interplay between the two over time. The systems a school builds are always downstream of the people who built them, and vice versa. There's a particular tension I've seen play out more than once, where the same manager whose personal judgement made a single site excellent becomes, without quite meaning to, the bottleneck preventing a second or third site from reaching the same standard. This isn't a criticism of that person. It's usually a sign that they did their original job extremely well, so well that nobody noticed how much of the operation depended on things that existed only in their head.

What is required, and it can be difficult for a leader who has enjoyed autonomy and success, is for that leader of the initial site to start treating the documentation and systematisation as part of the job, rather than as a distraction from it. This is harder than it sounds, partly because expert judgement often feels intuitive even to the person exercising it, and partly because writing it down explicitly can feel, at least initially, like it diminishes something that used to feel like a genuine skill rather than a checklist.

What This Looks Like in Practice

The schools I think of as having scaled well share a few habits that seem less glamorous than most growth advice suggests. They tend to have observation and feedback processes detailed enough that two different observers, at two different sites, would likely reach broadly similar conclusions about the same lesson. They tend to have onboarding that assumes nothing informal will be picked up along the way, rather than onboarding that quietly relies on a new manager absorbing culture through proximity to someone experienced. And they tend to treat the departure of any single person, however capable, as an event the organisation should be able to survive without a serious dip in quality, which is really just another way of saying that the knowledge belongs to the institution rather than to the individual.

I don't think any of this removes the value of genuinely excellent individual judgement. If anything, I think the schools that scale best are the ones that take a manager's hard-won judgement seriously enough to actually capture it properly, rather than either ignoring it or, just as commonly, assuming it will simply transfer to new people and new sites on its own.

Building that infrastructure before you need it (QA, induction, and the documentation that turns one person's judgement into an institution's standard) is what Phase Two of The Academic Manager's Survival Manual in Resources is built around.