What school leaders keep telling me about their systems

Much of my work starts with a first conversation: an initial call or meeting with a school principal, deputy principal, business manager or digital learning lead, almost always in an Australian secondary or K-12 school.

The patterns are remarkably consistent. Some of them surprised me. Most of them, in retrospect, I should have expected.

The first pattern. Almost every leader I speak with already knows what the school's biggest operational problem is. They have known for a while. They have not had the time, the political room, or the clear permission to go fix it. The conversation is rarely "tell us what is wrong". It is "tell us we are not crazy and help us build the case for fixing this".

The second pattern. The people doing the heaviest operational work are rarely the ones in the meeting. The placement coordinator. The administration officer. The technician who has quietly become the integration layer between three platforms. The leaders know their names. They want them to be heard. They also know that those staff are not in a position to walk into the principal's office and explain what is broken. Part of my job, very early on, is to spend time with those people and bring back what they say.

The third pattern. The school's last bad experience with a vendor is almost always more recent and more painful than the leadership team admits in the first conversation. There is nearly always a previous platform that was bought, oversold, underdelivered, and quietly replaced or worked around. The trauma is real and entirely justified. The hardest work in the early stages is not technical. It is rebuilding the trust that the previous vendor used up.

The fourth pattern. Cost is rarely the biggest blocker, and yet cost is the thing leadership teams talk about first. When I follow up six weeks later, the actual blocker is almost always something else. Internal alignment. Concerns about staff capacity to absorb change. A specific personality that needs to be brought along. The cost conversation was the conversation it was easiest to start with.

The fifth pattern. The schools that move fastest are not the schools with the most resources. They are the schools where the principal has named the problem out loud and given a specific person clear permission to drive the fix. Those schools can move faster on a five-thousand-dollar engagement than schools with five-figure budgets but no internal owner.

The sixth pattern. The schools that move best, not just fastest, are the schools where the leadership team is willing to be wrong in front of the staff. To acknowledge that the previous workflow wasn't working. To accept that some decisions made two years ago were the wrong ones in light of what they know now. To put that on a slide in a staff meeting and not minimise it. Those schools earn the staff trust that makes any change work.

The seventh pattern, which surprised me the most. The fundamental texture of school operations work is the same regardless of size, sector, and location. The problems at a 1500-student suburban secondary are recognisably the same problems as at a 350-student rural P-12. The scale changes. The nature of the work doesn't. Which is why I keep building software that is meant to work for both, and why most of the engagements end up being more similar than different.

I'll make notes again at 200.