Perspectives
Why Capable Leadership Teams Keep Having the Same Conversation
It's usually about forty minutes into a leadership meeting. Someone says, with more weariness than irritation, that they're fairly sure this came up last term.
They're right. It did. It came up the term before that too, with a different name attached.
The team is not incompetent, and nobody has forgotten. What's happening is more specific than that, and more fixable.
Each instance really is different
The reason the pattern stays invisible is that every appearance of it is genuinely distinct. Last term it was a communication problem with the science department. This term it's a handover between two year leads. Different people, different context, different urgency.
So the team does the sensible thing and treats it as new. It gets discussed on its own terms, a reasonable resolution is found, and everyone moves on with the meeting.
That resolution works. That's the problem. If it didn't work, somebody would go looking for a cause.
Competence is what keeps the pattern hidden
This is why it happens to capable teams rather than struggling ones. A team that handles instances well never accumulates enough unresolved pain to force a different question. Each one gets absorbed, and the absorption is the achievement.
A struggling team would have a crisis, and a crisis would make somebody ask what's actually going on here. A capable team just gets slightly more tired, three or four times a year, without ever having the conversation that would connect those occasions to each other.
The skill that makes them effective is the same skill that keeps the underlying condition out of view.
A pattern needs two cases side by side
Nothing about an individual incident announces that it belongs to a set. Patterns only become visible when two or three instances are put next to each other deliberately, and almost nothing in a school's normal operation does that.
Minutes record what was decided, not what kept recurring. Agendas are organised by topic, so the same underlying condition arrives under a different heading each time and gets filed separately. Handovers pass on live issues, not resolved ones, which means the resolved instances vanish precisely because they were handled.
The information exists. It's just never assembled in a form where the shape would be obvious.
What actually surfaces it
In practice it takes two things, and neither is a new framework.
It takes someone whose job it is to notice recurrence rather than resolve incidents, which is not a natural role for anyone in the room when the room is under time pressure. And it takes a place where the instances are held long enough to be compared, which usually means writing down not what was decided but what the situation was.
Teams that do this tend to find the same thing: the recurring conversation was never really about communication or handover or workload. It was about a condition nobody owned, because it never belonged to any single incident.
The conversation doesn't stop because a team resolves to be more strategic about it. It stops when the pattern becomes something you can point at.
Until then it will keep returning, wearing whichever set of names the term happens to supply.
Where this goes next. The Waterline Lab is this work done on a school's own recurring problems: six lenses applied to real patterns until the shape is visible enough to act on. The output is a System Visibility Map rather than a list of fixes. The Six Principles sets out what decides where a team's attention goes in the first place.