Systems Without the Replacement Panic

Every school we speak with has the same quiet fear about its management system. Not that it is bad. That changing it will eat a year.

The fear is rational. Migrations disrupt timetables, data, staff habits and parent expectations all at once. So schools stay on systems that no longer fit, paying for the disruption they avoided in instalments: duplicated data, workarounds, spreadsheets holding the whole thing together.

Our position is unfashionable and it saves schools enormous pain. Before recommending any replacement, improve the flow of information around the systems you already have.

We begin with the operational reality. Where do staff lose time? Where is the same data typed into two places? Where does information arrive too late to change anything? The answer is rarely the whole platform. It is a seam between two of them.

From there the work may be an integration, a focused internal tool, a redesigned workflow, or, when it is genuinely justified, a new platform. The principle does not change: improve the load path before increasing the load.

Some schools do need a full replacement. When they do, the work done on the seams first makes the migration smaller, safer and faster, because the flow is already understood.

The point is not to defend old software. The point is that replacement is a decision you earn the right to make, not one you are panicked into.

Cover image: Lars Bugge Aarset on Pexels.