I have seen this happen in capable leadership teams. The conversation finally becomes honest. The pattern is named. People recognise what has been happening beneath the surface. The room feels clearer, not because the pressure has disappeared, but because the team finally has language for something it had been carrying without fully naming.
For a moment, the insight itself feels like progress. The team can see how urgency has been reshaping its conversations. It can recognise where one person has been carrying too much emotional load. It can name where decisions have been made quickly but not held strongly. It can see how the same compensating behaviours keep returning whenever the pressure rises.
Then the next difficult week arrives. A staff issue sharpens, a parent complaint escalates, a timetable disruption creates urgency, or a system deadline collides with a human problem. The team is tired, the agenda is full, and there is less space than everyone needs. Almost without noticing, the old behaviour returns.
The same person steps in too early. The same person absorbs the tension privately. The same voice becomes quiet. The same decision is made before enough shared meaning has formed. The same compensating behaviour reappears, not because the team lacks insight, but because the team has not yet agreed what insight now requires.
This is one of the more sobering truths of leadership development: insight does not automatically change behaviour, especially under pressure. A leadership team can see the pattern and still repeat it. It can name the dynamic and still return to it. It can recognise that pressure is narrowing judgement, redistributing emotional load, or weakening coordination, and still behave in familiar ways when urgency returns.
That does not mean the insight was false. It means the insight was incomplete.
Because awareness is not the same as agreement. Recognition is not the same as redesign. Naming the pattern is only the first move. The deeper work is deciding how the team will behave when that pattern returns.
That is the move from insight to protocol.
Prefer to watch first?
Here’s the short video version of this week’s idea if you’d like a quicker way into the argument before reading further.
The Relief of Naming the Pattern
There is a genuine relief that comes when a leadership team finally names what has been happening. The conversation changes. What felt personal becomes more discussable. What felt vague becomes more precise. What had been carried privately begins to take shape as a shared leadership pattern. People do not have to keep treating every repeated tension as an isolated event. They can begin to see the structure beneath the repetition.
That matters. Leadership teams need language. They need ways to name what pressure is doing to behaviour, judgement, trust, decision-making, emotional load, and coordination. Without that language, teams often remain trapped inside symptoms: the repeated meeting, the unresolved tension, the decision that does not hold, the quiet withdrawal, the over-functioning of a few people.
Language gives the team a mirror. It does not give the team a method.
That is where many teams stop too early. They experience the relief of recognition and mistake it for change. The room feels clearer, so the team assumes progress has been made. People leave with a stronger shared vocabulary, but not necessarily with a stronger shared agreement.
The next pressure cycle then reveals the gap. The team did not need more vocabulary. It needed an agreed response.
This is why insight can be both powerful and fragile. It gives leaders a way to see. But unless it becomes operational, it remains vulnerable to the very pressure it helped reveal. The team may now understand itself more clearly, but it has not yet changed the conditions under which old behaviour becomes the easiest behaviour.
Hackman’s work on team effectiveness is useful here because it challenges a common assumption: capable individuals do not automatically become a capable team. Effective teamwork depends on enabling conditions — clear purpose, sound structure, supportive context, and disciplined opportunities to learn from the work itself (Hackman, 2002). In a school leadership team, insight may clarify the pattern, but it does not by itself create those enabling conditions.
That is why the question has to shift. Not only, What do we now understand? But, What have we now agreed to do?
Why Pressure Pulls Teams Back to Familiar Behaviour
Under calm conditions, most leadership teams can speak intelligently about how they want to lead. They can name the importance of trust, shared ownership, ethical judgement, relational steadiness, strategic clarity, and professional honesty. They can often identify the behaviours they want more of and the patterns they want to avoid. In a reflective conversation, the team may sound deeply aligned.
Pressure is a different test. The real test is not what a team values when it has time to think. The real test is what it does when urgency rises, ambiguity tightens, and emotional load increases.
That is when teams tend to return to familiar behaviour. Not because they are careless. Not because they lack integrity. But because familiar behaviour is available. It has worked before, at least well enough to keep things moving.
The decisive leader steps in. The relational leader softens the tension. The dependable leader carries more. The strategic leader moves above the detail. The reflective leader waits for more information. The driven leader accelerates. The team does what it knows.
Insight lives in reflection. Pressure activates habit.
Heifetz, Grashow, and Linsky’s work on adaptive leadership helps explain why this matters. Adaptive work requires people to stay present to complexity rather than reducing discomfort too quickly through familiar technical responses (Heifetz et al., 2009). Yet under pressure, leadership teams often reach for the response that restores short-term movement, even when the deeper pattern remains untouched.
In schools, this can look entirely reasonable from the outside. The principal makes the call because the issue is urgent. The deputy absorbs the staff tension because the team needs to keep functioning. The assistant principal softens the message because the staff are already stretched. The executive team moves quickly because the deadline is real.
None of these responses is inherently wrong. The question is whether they have become automatic. Because once a response becomes automatic, the team may no longer be choosing. It may simply be repeating.
This is where protocol becomes essential. Not because leaders need less judgement, but because they need a way to protect judgement when pressure makes familiar behaviour feel like the safest available option.
Protocol Is Care Made Operational
The word protocol can sound cold in leadership work. It can sound procedural, managerial, even bureaucratic. For some leaders, it evokes compliance rather than judgement, rigidity rather than responsiveness, control rather than trust.
That is too narrow.
A good protocol does not replace professional judgement. It protects it. It does not remove humanity from leadership. It helps preserve humanity when pressure threatens to compress it. It does not assume leaders are incapable. It recognises that even capable leaders need shared agreements when the stakes are high and the room is under strain.
In that sense, protocol is care made operational. It is care for the team’s judgement. Care for the quality of its conversations. Care for the people most likely to over-carry. Care for the voices most likely to become quiet. Care for decisions that deserve more shared understanding than urgency wants to allow. Care for the culture the team is creating through repeated behaviour.
Without protocol, teams often rely on personality. The same people do what they have always done. The same strengths carry the same pressure. The same informal roles reappear. The team may function, but its functioning depends too heavily on habit, goodwill, and unspoken expectation.
With protocol, the team makes a different move. It pre-decides what it wants to protect.
That matters because pressure should not be the moment a team improvises its values. If a leadership team says it values shared ownership, what does that mean when one person keeps rescuing clarity? If it says it values candour, what does that mean when the room becomes tense and people begin editing themselves? If it says it values trust, what does that mean when silence appears and the team is tempted to interpret it as disengagement? If it says it values ethical judgement, what does that mean when speed starts to feel more attractive than deliberation?
Values become real when they are translated into behaviours. Protocols help that translation happen before pressure decides for the team.
What Effective Teams Protect Under Pressure
Team research is clear on one point: collective performance is not simply the sum of individual capability. Wageman and colleagues argue that senior leadership teams require deliberate design, not merely shared seniority or goodwill. They need clarity about purpose, membership, structure, norms, and the conditions that allow interdependent work to happen well (Wageman et al., 2008). This matters in schools because many leadership teams are filled with capable people who are each carrying heavy portfolios, but capability alone does not guarantee disciplined collective behaviour under strain.
A team can be experienced and still poorly protected against pressure. It can be relational and still avoid necessary tension. It can be committed and still over-rely on the same people. It can be strategic and still make decisions that do not travel beyond the room. It can be caring and still allow emotional labour to collect in predictable places.
That is why the work has to become more precise.
Edmondson’s research on psychological safety is useful here because it shows that teams learn more effectively when people can speak up, question, challenge, and name risk without disproportionate interpersonal cost (Edmondson, 2019). But psychological safety is not sustained by aspiration alone. A leadership team cannot simply say, “We want people to be honest,” and assume honesty will survive the next high-pressure moment.
Honesty needs protection.
If a deputy principal slows a decision because the team is moving too quickly, what happens next? If an assistant principal names that emotional load is collecting unfairly, is that treated as useful information or as resistance? If someone says, “This feels like our old pattern,” does the room have an agreed way to receive that observation?
Without agreement, candour depends on personal courage. With agreement, candour becomes part of the team’s design.
Research on team coordination makes the same point from another angle. Salas, Sims, and Burke identify core teamwork behaviours such as shared mental models, mutual performance monitoring, backup behaviour, adaptability, and team orientation as central to effective team performance (Salas et al., 2005). Marks, Mathieu, and Zaccaro similarly distinguish between transition processes, action processes, and interpersonal processes that help teams plan, coordinate, monitor progress, manage conflict, and adjust over time (Marks et al., 2001).
These are not abstract ideals. They are practical disciplines. A leadership team needs to know how it will notice pressure, how it will share information, how it will check assumptions, how it will support overloaded members, how it will slow decisions that need more shared judgement, and how it will repair when the team slips into old behaviour.
That is what protocol protects. Not compliance. Collective discipline.
The Problem With Awareness Without Agreement
Awareness can become strangely passive if it is not followed by agreement. A team may become better at describing what happens without becoming better at interrupting it. People may recognise the same pattern in real time, but still hesitate to name it. They may know that one person is over-carrying, but still allow that person to carry. They may know that decisions are becoming too fast, but still keep rewarding speed. They may know that silence needs interpretation, but still move past it because the agenda is full.
This is where awareness can become another form of avoidance.
That may sound severe, but leadership often requires that kind of honesty. Once a team has seen a pattern, the work changes. The team is now responsible not only for noticing it, but for deciding what noticing requires.
If the team keeps recognising the same pattern without changing its response, awareness becomes a kind of comfort. It gives people language without changing the load. It allows the team to sound more sophisticated while behaving in ways that remain largely unchanged.
Awareness that never becomes agreement eventually becomes another form of avoidance.
This does not happen because leaders are insincere. More often, it happens because the team has stopped at diagnosis when the next move is design. A useful diagnosis should lead somewhere. It should lead to clearer commitments, better questions, more disciplined conversations, and shared behavioural expectations. It should make the team more capable of acting differently when the pressure that created the pattern returns.
The question is not only, What do we now see? The question is, What have we now agreed to do?
What a Pressure Protocol Makes Possible
A Pressure Protocol is a simple leadership team agreement for how the team will behave when pressure rises and familiar patterns begin to return. It is not a long document. It is not a compliance checklist. It is not a script for complex leadership work. It should not become another artefact that looks impressive and changes little.
It needs to be simple enough to remember under strain and serious enough to change behaviour.
At its best, a Pressure Protocol helps the team do five things: name the pressure signal early, interrupt the automatic pattern, protect the behaviour that matters, repair when the team drifts, and review what pressure revealed.
The first discipline is naming the pressure signal early. Every team has signals. The room gets quieter. Certain people talk more. Decisions accelerate. Meetings become more efficient but less thoughtful. Emotional labour starts collecting in familiar places. A principal begins carrying ambiguity privately because naming it feels risky. A deputy becomes the informal container for staff anxiety. An assistant principal stops offering unfinished thinking because the team’s pace no longer seems to welcome it. These signals are not accusations. They are information. When the team has agreed to notice them, it becomes easier to name them without blame.
The second discipline is interrupting the automatic pattern. Naming pressure is not enough. The team needs to know which pattern it is trying to pause. Is the team rushing, avoiding, over-consulting, over-carrying, smoothing tension, repeating old role patterns, or treating urgency as permission to bypass shared judgement? A protocol gives the team language for interruption. It is much easier to say, “This feels like the pattern we agreed to watch for,” than to say, “You are doing it again.” The first invites the team back to agreement. The second often creates defensiveness.
The third discipline is protecting the behaviour that matters. This is where values become operational. If the team values candour, how will candour be protected when the conversation becomes difficult? If the team values shared ownership, how will ownership be protected when one person is tempted to take over? If the team values reflection, how will reflection be protected when urgency rewards speed? Aspirational language says, “We value honesty.” Behavioural agreement says, “Before we finalise a major decision, we will name the trade-offs and invite dissenting concerns.” Aspirational language says, “We support each other.” Behavioural agreement says, “When emotional load is collecting in one person, we will name it and redistribute what can be shared.” Aspirational language says, “We trust each other.” Behavioural agreement says, “We will check silence before interpreting it.”
The fourth discipline is repairing when the team drifts. Every team drifts. The aim is not perfection. The aim is faster recognition and cleaner repair. A mature team can say, “We have slipped back into the old pattern. Let’s reset the conversation.” That kind of repair is not a sign of failure. It is a sign that the team’s agreement is becoming usable. Repair should not depend on the courage of one person. The team can agree in advance that anyone can call a reset. It can normalise phrases such as, “This feels like the pattern we agreed to watch,” or, “I think we are moving too quickly,” or, “Before we decide, can we name what is being carried here?” These are not scripts to recite mechanically. They are examples of authorised interruption. The point is not the exact wording. The point is that the team has made repair legitimate before the moment requires it.
The fifth discipline is reviewing what pressure revealed. The team needs to learn from pressure, not simply survive it. After a difficult period, it can ask what it noticed early, what it protected, where it still compensated, what was carried silently, what agreement helped, what agreement was missing, and what needs to be strengthened before next time. Without review, the team may keep surviving pressure without becoming wiser through it.
This is where protocol becomes developmental rather than procedural. It does not simply help the team get through the moment. It helps the team learn from the moment.
Why This Matters in Schools
Leadership teams shape the emotional and strategic weather of a school. When the executive team is under pressure, its behaviour travels. The quality of its communication, decision-making, trust, and coordination affects far more than the people in the room. It affects how uncertainty is interpreted across the organisation. It affects how staff experience direction. It affects whether tension becomes discussable or hidden. It affects whether urgency is handled with clarity or absorbed through quiet over-functioning.
This is why the move from insight to protocol matters. A leadership team that has no protocol under pressure often exports its unexamined patterns. If the team rushes, the organisation feels the rush. If the team avoids tension, the organisation learns avoidance. If the team relies on silent compensation, the organisation becomes dependent on invisible labour. If the team repeatedly makes decisions that do not hold, the wider culture absorbs that instability.
But when a leadership team has clear agreements, something else becomes possible. The team can notice earlier. It can pause sooner. It can speak more honestly. It can distribute load more wisely. It can repair more cleanly. It can model the kind of leadership culture it wants others to experience.
This is not about becoming mechanical. It is about becoming more trustworthy under pressure. The strongest leadership teams are not the ones who never revert to old patterns. They are the ones who notice quickly, return to their agreements, and keep learning how to lead together with greater discipline and care.
From Diagnosis to Design
This is why diagnostic work matters. A serious diagnostic conversation is not simply about naming what is wrong. It is about helping the team identify what must now be designed differently. The value is not only visibility. It is translation.
What does this pattern require from us? What agreement is missing? What behaviour do we need to protect? What do we keep leaving to personality, goodwill, or informal compensation? What do we need to pre-decide before pressure returns?
These are design questions. They take the team beyond recognition and into responsibility. They help leaders move from, “That explains us,” to, “This is what we will do differently.”
That shift is essential because leadership teams do not change through insight alone. They change when insight becomes shared practice. They change when the team stops relying on individual effort to carry collective patterns. They change when agreements become strong enough to interrupt habit.
The purpose of protocol is not to control the team. The purpose is to give the team a more reliable way to remain itself when pressure rises.
Prefer to listen more deeply?
I explore this idea more fully in this week’s podcast episode, where I unpack the research, the relational dynamics, and the practical leadership implications in greater depth.
Conclusion
A leadership team can see the pattern and still repeat it. That is not hypocrisy. It is not weakness. It is not proof that the insight was wrong. It is a reminder that insight and behaviour are not the same thing, especially under pressure.
Insight gives the team language. Protocol gives the team a way to act.
That distinction matters because pressure will return. The next urgent decision will arrive. The next difficult conversation will test the room. The next moment of ambiguity will tempt the team back towards familiar responses. When that happens, the team will not rise to the level of its language. It will fall back on the strength of its agreements.
That is why awareness is not enough.
The serious question for a leadership team is not only: What pattern can we now see? It is: What agreement do we need before that pattern returns?
Because awareness that never becomes agreement eventually becomes another form of avoidance. But awareness that becomes protocol gives a team something far more useful: a shared way to lead when pressure makes old behaviour easier than better behaviour.
If this is familiar in your leadership team — if you have named the pattern but still find yourselves repeating it when pressure rises — I offer a complimentary Leadership Pressure Diagnostic. It is a focused conversation to help you identify what pressure is 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.
References
Edmondson, A. C. (2019). The fearless organisation: Creating psychological safety in the workplace for learning, innovation, and growth. Wiley.
Hackman, J. R. (2002). Leading teams: Setting the stage for great performances. Harvard Business School Press.
Heifetz, R., Grashow, A., & Linsky, M. (2009). The practice of adaptive leadership: Tools and tactics for changing your organisation and the world. Harvard Business Press.
Marks, M. A., Mathieu, J. E., & Zaccaro, S. J. (2001). A temporally based framework and taxonomy of team processes. Academy of Management Review, 26(3), 356–376.
Salas, E., Sims, D. E., & Burke, C. S. (2005). Is there a “Big Five” in teamwork? Small Group Research, 36(5), 555–599.
Wageman, R., Nunes, D. A., Burruss, J. A., & Hackman, J. R. (2008). Senior leadership teams: What it takes to make them great. Harvard Business Press.
