Why Leadership Teams Need Agreements They Can Return To

Key takeaways:

1. Leadership insight is real progress, but insight has to become shared practice.

2. When pressure returns, teams need a clear agreement they can return to, not only a clearer description of the pattern.

3. Protocol does not need to feel bureaucratic. At its best, it is a way of protecting what the team values when pressure makes familiar habits easier.

4. A useful agreement can be simple: one pressure signal to notice, one pattern to interrupt, one behaviour to protect, one repair move, and one review question.

5. The deeper question is not only, “What do we now understand?” but, “What does this insight now require from us?”

Why Leadership Teams Need Agreements They Can Return To

Transcript

There is a particular kind of clarity that comes when a leadership team finally sees itself.

Not in a harsh way. Not in a blaming way. More like the moment when the fog lifts slightly and people can say, “Yes. That is what has been happening.”

The conversation becomes more honest. The pattern has a name. The tension that had been sitting beneath the surface becomes easier to talk about. What one person had been carrying privately begins to feel less isolated, because others can now see it too.

I think that moment matters.

Many leadership teams need that moment. They need language for what pressure has been doing to the way they communicate, decide, listen, carry responsibility, and interpret each other. Without that language, everything stays local: the repeated issue, the meeting that feels tighter than it should, the decision that needs revisiting, the silence that is difficult to read, the same person quietly stepping in again.

When the pattern finally becomes visible, it can feel like progress.

And it is progress.

But it is not the whole journey.

There is another moment that often follows. It may come a week later, or a month later, or the next time the pressure rises. The team finds itself back inside a familiar situation. The same urgency returns. The same ambiguity returns. The same emotional load returns. And even though the team now understands more than it did before, the familiar pattern quietly becomes available again.

Someone carries more, someone speaks less, someone steps in, someone smooths the tension, and someone speeds the decision along.

The earlier conversation mattered. The insight was real. The team’s commitment may still be strong. But the next pressure cycle will test whether the team has turned that insight into a shared agreement.

That is what I want to explore in this episode.

What happens after a leadership team sees something important about itself?

And what does that insight now require from the team?

The Moment After Insight

There is a quiet vulnerability in the moment after insight.

The team has seen something. People have recognised the pattern. There may even be a sense of relief in the room, because what had been difficult to name now has language around it.

But insight, by itself, is delicate.

It can clarify the pattern without changing the conditions that allow the pattern to return. It can make the team more aware without yet making the team more coordinated. It can help people recognise what has been happening without giving them an agreed way to respond the next time it happens.

That is why I think leadership teams sometimes need to be careful with the relief that insight brings. The relief is real. It should be honoured. But relief can feel like resolution before resolution has actually been built.

A team may now understand that it moves too quickly under pressure. It may understand that emotional labour tends to collect in one or two people. It may understand that silence in the room is often being misread. It may understand that certain leaders rescue clarity so reliably that the team has slowly become dependent on them.

All of that understanding matters. But the next question is different.

• What will the team do with that understanding?

• What will it agree to notice earlier?

• What will it agree to protect?

• What will it agree to say when the familiar pattern starts to reappear?

That is the shift from awareness to agreement. And I think that shift is where a great deal of leadership maturity lives.

The aim is not simply to become more articulate about the team’s patterns. The aim is to become more capable of leading differently when those patterns are activated again.

Why Familiar Patterns Return

Old patterns often return because they are familiar.

In a calm room, most leadership teams can speak thoughtfully about the kind of team they want to be. They can talk about trust. Shared ownership. Candour. Professional respect. Ethical judgement. The importance of slowing down when the decision requires more than speed.

And often, they mean all of it. But pressure has a way of making familiar behaviour feel sensible.

A principal steps in because someone needs to create clarity. A deputy carries the emotional residue because the team needs to keep functioning. An assistant principal softens the conversation because the staff are already stretched. A strategic leader stays above the detail because the bigger picture still needs protecting. A reflective leader waits a little longer because the situation is complex. A driven leader pushes ahead because momentum feels essential.

In the moment, much of this may be generous, responsible, even necessary.

The issue is whether the team has a shared way to notice when familiar strengths are becoming automatic patterns.

That is where insight needs support.

It is helpful for the team to know that pressure can narrow its range. It is more useful when the team has a shared agreement that helps it remain deliberate when pressure makes old habits attractive again.

That is why I keep coming back to the idea of agreement.

Not agreement as politeness. Not agreement as everyone thinking the same thing.

Agreement as a shared commitment to protect certain behaviours when the team is under strain.

Agreement as Support

The word protocol can feel a little cold, especially in education. Schools already have enough procedures, policies, checklists, compliance requirements, and administrative expectations. So when we talk about protocol in leadership, it can sound as though we are adding another layer to people who are already carrying too much.

That is not what I mean here.

A good protocol should not make leadership more mechanical. It should make leadership more humane under pressure. It should protect judgement. It should give the team something steady to return to when the room starts to tighten.

At its best, protocol is care made practical.

It is a way of saying, “When pressure rises, this is how we will protect the quality of our conversation.”

Or, “When one person starts carrying too much, this is how we will make that visible without blame.”

Or, “When we are moving too quickly, this is how we will slow down without shaming the urgency.”

Or, “When silence appears in the room, this is how we will check what it means before we interpret it.”

That kind of agreement is deeply relational.

It says the team matters enough to protect. The work matters enough to do with discipline. The people in the room matter enough to ensure the hard moments are not left to whoever has the courage, stamina, or positional authority to interrupt them.

This is one of the reasons psychological safety matters so much in team leadership. Amy Edmondson’s work reminds us that teams learn better when people can speak up, question, name risk, and contribute honestly without paying an unreasonable interpersonal price. But that kind of safety is created through repeated behaviours that show people what happens when they do.

A team’s agreement is tested in the small moments: when someone slows a decision, names that one person is carrying too much, or notices that the old pattern is returning. The question is whether the team receives that as useful information and returns to the agreement.

Without agreement, speaking up depends on personal courage.

With agreement, speaking up becomes part of the team’s design.

What a Simple Agreement Can Hold

A useful agreement does not need to be elaborate.

In fact, if it is too elaborate, it probably will not help much when pressure rises. The most useful agreements are often simple enough to remember and serious enough to shape behaviour.

A leadership team might begin with one pressure signal it agrees to notice earlier. That signal might be the room becoming unusually quiet, the decision moving too quickly, the same person beginning to hold all the emotional weight, the conversation becoming efficient but less thoughtful, or the agenda being completed while the real tension remains untouched.

The signal matters because it gives the team a way to notice without accusation. It is much easier to say, “I think this is one of our pressure signals,” than to say, “You are doing it again.” That small shift in language matters. It allows the team to return to the pattern without making one person the problem.

The team might also agree on one automatic pattern it wants to interrupt. Perhaps it tends to rush. Perhaps it tends to avoid. Perhaps it over-consults because no one wants to disappoint anyone. Perhaps it over-functions because a few people are very good at rescuing the group. Perhaps it softens necessary tension too quickly because everyone is already tired.

Again, the point is not to shame the pattern. The point is to give the team a way to notice it while there is still time to choose something better.

Then the team can name one behaviour it wants to protect. This is where values become more than words. If the team values candour, it may agree to name trade-offs before finalising major decisions. If it values shared ownership, it may agree to notice when the same person is rescuing clarity again. If it values trust, it may agree to check silence before interpreting it. If it values reflection, it may agree that urgency does not automatically remove the need for shared judgement.

These agreements do not need to be grand. They need to be usable.

A team might also agree on one repair move, because every team will drift. Every team will forget itself at times. Every team will have moments when pressure gets into the conversation before anyone names it.

The aim is not perfection.

The aim is return.

A repair move might be as simple as, “Can we pause and reset?” Or, “I think we are moving back into the old pattern.” Or, “Before we decide, can we name what is being carried here?” Or, “Can we check what silence means before we move on?”

These are not magic phrases. They are ways of giving the team permission to return to itself.

And finally, the team might agree on one review question after the pressure passes. Not a long debrief. Not another meeting for its own sake. Just one honest question: What did this pressure reveal about the way we are leading together?

That question helps the team learn from pressure, rather than simply endure it.

What Team Research Helps Us Understand

This is not only a practical instinct. It is supported by what we know about effective teams.

J. Richard Hackman’s work on team effectiveness challenged the assumption that capable people naturally become an effective team. Teams need enabling conditions. They need clarity, structure, support, and opportunities to learn from their work.

Ruth Wageman and her colleagues make a similar point about senior leadership teams. A group of senior people is not automatically a well-designed team. Shared responsibility does not automatically create shared discipline.

That distinction matters in schools, because school leadership teams are often full of capable, committed people who are each carrying significant portfolios. But a collection of capable people is not the same as a team with clear agreements for how it will behave under pressure.

Research on team coordination points in the same direction. Effective teams rely on shared understanding, mutual monitoring, backup behaviour, adaptability, and the ability to adjust together. Those are everyday behaviours.

They show up in whether the team notices who is carrying too much.

Whether the team checks assumptions before acting.

Whether information travels clearly.

Whether decisions hold beyond the meeting.

Whether tension can be named early enough to be useful.

Whether the team can repair without blame.

This is why agreement matters. Agreement creates the conditions under which the team’s best intentions can survive the pressure of the work.

When Awareness Remains Unfinished

There is one risk here that is worth naming carefully.

Awareness remains unfinished when it helps a team describe the pattern but does not yet help the team respond differently.

A team can become more fluent in describing its patterns without becoming more capable of changing them. It can recognise the same dynamic in meeting after meeting and still not know what to do when the dynamic appears. It can speak with more sophistication about pressure while leaving the same people to carry it.

This usually happens when insight has not yet become shared practice.

And that is why the move from recognition to agreement is so important. It allows the team to ask: What does this insight now require from us? What would it look like to protect our best intentions before pressure makes them harder to access? What do we need to agree on while we are calm, so we have something to return to when we are not?

Those are practical questions, but they are also deeply human questions.

They ask the team to understand itself and to care for the conditions that allow it to lead well together.

What Travels Through the School

This matters because leadership behaviour does not stay in the leadership room. It travels.

The quality of the team’s communication travels. The way it handles urgency travels. The way it carries tension travels. The way it makes decisions travels. The way it repairs trust travels.

Staff may not see every executive conversation, but they often feel the effects of those conversations. They feel whether decisions are clear. They feel whether tension has been named or avoided. They feel whether urgency is being held with steadiness or passed down as pressure. They feel whether the leadership team is coordinated enough to carry complexity without scattering it through the organisation.

So when a leadership team creates better agreements for how it will lead under pressure, it is shaping the wider emotional and strategic climate of the school.

That is why this work matters.

The way a leadership team behaves under pressure becomes part of the culture others are asked to live inside.

Reflection

Perhaps the question is not, “Does our team have insight?”

Many teams do.

The more useful question is: what does this insight now require from us?

Where have we named a pattern but not yet created an agreement?

Where do we understand what happens under pressure but still rely on the same people to interrupt it?

Where do we value candour, but have not protected the conditions for candour?

Where do we value shared ownership, but still allow invisible over-carrying?

Where do we value trust, but still interpret silence too quickly?

That is where the next piece of work may be.

Begin with one agreement.

One pressure signal the team will name earlier.

One pattern it will interrupt with more care.

One behaviour it will protect when pressure rises.

One repair move it will authorise before the moment requires it.

One review question it will ask after pressure has passed.

That may sound small, but small agreements can carry significant weight. They create a bridge between what the team understands and how the team behaves.

Because insight matters.

It gives the team language.

But agreement gives the team somewhere to return.

And when pressure comes back, as it always does, that return point may be what allows the team to lead with more steadiness, more honesty, and more care.

If your leadership team has recognised a pattern but still finds itself returning to it when pressure rises, I offer a complimentary Leadership Pressure Diagnostic. It is a focused conversation to help identify what pressure may be activating in your team, what agreements may be missing, and what kind of leadership response may now be required.

The goal is not simply more awareness.

It is to help your team move from recognition to a more deliberate way of leading when pressure returns.

Thanks for listening.

I also encourage you to download my latest complimentary leadership paper: The Leadership Pressure Triangle