A leadership team does not become confident because someone tells it to believe.
It becomes confident when it remembers what it has already carried together.
I worry that collective efficacy has become one of those phrases school leaders are expected to value without always being given enough precision about how it is built. It is invoked as belief, mindset, positivity, shared confidence, or professional hope. Those words hover near the idea, but none of them is strong enough to carry it.
When collective efficacy is treated as a feeling to be lifted, leaders reach for encouragement when the team actually needs proof. They try to raise belief when the deeper work is to create evidence. They ask people to feel more confident before the team has generated enough shared experience to make that confidence reasonable.
Real collective efficacy is not optimism. It is not morale. It is not the emotional lift of a good meeting or the temporary confidence that follows a strong professional learning day. At its most useful, collective efficacy is the confidence a team earns when shared effort repeatedly becomes evidence.
The team acted together, and something held. The decision travelled. The difficult conversation opened a cleaner path. The pressure was carried by the team rather than absorbed by one or two people. The work produced enough coherence that the next piece of leadership became clearer, not heavier.
That is where efficacy begins to deepen: not in the declaration that “we can do this”, but in the remembered evidence that “we have carried difficulty together before, and our effort made something more stable, more coherent, or more possible.”
For leadership teams, this is more than an academic distinction. School leadership is too complex to be sustained by individual capability alone. A principal may be highly capable. Deputies and assistant principals may be deeply committed. Each leader may be working hard in their own portfolio. But a group of capable individuals does not automatically become a collectively efficacious team.
Collective efficacy grows when shared effort becomes evidence. Over time, that evidence changes what a team expects of itself.
Effort becomes evidence. Evidence becomes expectation. Expectation becomes efficacy.
That is the arc.
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.
Why Belief Needs Proof
Albert Bandura defined collective efficacy as a group’s shared belief in its conjoint capability to organise and execute the courses of action required to produce desired results (Bandura, 1997). The definition is more demanding than everyday uses of the term often suggest. It is not belief in a general sense. It is belief in shared capability to act together.
The word conjoint is important because collective efficacy is not the sum of individual confidence. It is not a room full of competent people privately believing they are capable. It is the team’s shared judgement that, together, they can organise action, adapt to conditions, carry difficulty, and produce meaningful progress.
That judgement is built through proof.
A team may say it believes in itself, but belief becomes durable only when experience keeps confirming it. When shared action produces coherence, confidence strengthens. When effort repeatedly disappears into rework, confusion, uneven load, or fragile follow-through, confidence weakens. People may still care deeply. They may still be committed. They may still speak positively about the school. But the team’s belief in its shared capacity begins to thin if it cannot see its effort producing something that holds.
Reducing collective efficacy to positivity strips the concept of its discipline. Positivity can lift a room for a moment. Evidence changes what a team expects of itself.
In leadership teams, expectation is everything. A team with evidence of shared capacity enters difficulty differently. It does not assume every challenge will be easy, but it has a memory of coordinated effort. It has previous proof that people can align, communicate clearly, distribute responsibility, repair trust, and keep a decision alive beyond the meeting. That memory becomes part of the team’s working confidence.
Collective efficacy is what a team remembers about its own capacity.
Morale Is Not Efficacy
Morale changes how a team feels about the work. Efficacy changes what a team expects its work can do.
That difference is crucial because many leadership teams try to solve efficacy problems with morale strategies. They encourage the team, celebrate the work, remind people of purpose, or try to lift the emotional tone. Those moves can be useful. Exhausted and demoralised teams rarely do their best work. People need encouragement, appreciation, connection, and hope.
But morale does not replace efficacy.
A team can have pleasant morale and weak collective efficacy. People may enjoy each other. They may respect each other. They may speak warmly about the school’s purpose. But when the work becomes complex, they may not yet trust the team’s collective capacity to hold pressure, coordinate action, and produce progress that lasts beyond the meeting.
The reverse can also be true. A team can be tired and still have strong collective efficacy because it has proof. It has been through difficulty before. It has seen its decisions travel, its conversations mature, its commitments hold, and its coordinated effort create durable movement.
That kind of confidence is not sentimental. It is earned.
A leadership team with strong morale may feel better in the room. A leadership team with growing efficacy carries a stronger expectation out of the room.
That is the difference leaders need to understand.
Collective Efficacy as Organisational Memory
Every leadership team is building a memory of itself.
Not a formal memory. A lived one.
The team remembers whether shared effort usually holds. It remembers whether decisions travel. It remembers whether difficult conversations lead somewhere. It remembers whether people follow through. It remembers whether load is shared or quietly redistributed to the same few people. It remembers whether trust can be repaired after tension.
Those memories become expectations.
If the team repeatedly experiences shared effort disappearing into confusion, delay, rework, or uneven carrying, it learns something about itself. It learns that collective work is unreliable. It learns that the safest path may be to retreat into individual portfolios. It learns that the team talks well but does not always follow through strongly. It learns that difficult issues eventually land with the same people, regardless of what is said in the room.
Those lessons weaken collective efficacy.
When the team repeatedly experiences coordinated effort producing something durable, it learns something different. It learns that shared work can hold. It learns that tension can be named without destroying trust. It learns that decisions can travel when the team aligns properly. It learns that pressure can be carried together. It learns that the team is more capable than any one leader acting alone.
Those lessons strengthen efficacy.
This is where the research on collective efficacy in schools becomes useful. Goddard, Hoy, and Woolfolk Hoy describe collective teacher efficacy as a shared perception that the efforts of the faculty as a whole will have a positive effect on students (Goddard et al., 2000). Their work focuses on teachers, and that focus should not be blurred. But the leadership implication is significant: collective efficacy is tied to the group’s perception of shared influence.
For leadership teams, the question becomes: does this team experience its shared leadership as capable of shaping the conditions of the school?
If the answer is no, stronger language about belief will not be enough. The team needs new evidence.
When Effort Does Not Become Evidence
Some leadership teams are not short on effort. They are short on evidence that effort is becoming shared capacity.
A leadership team may be working constantly. Meetings are full. Communication is steady. Problems are being solved. Leaders are responsive, committed, and visible. From the outside, the team may look highly functional.
But if the same decisions keep needing to be re-secured, the same clarity keeps needing rescue, the same emotional load keeps collecting in predictable places, and the same work keeps expanding without producing durable movement, the team may not be building efficacy. It may be building fatigue.
Effort that does not hold rarely builds confidence. It usually builds exhaustion.
This is one reason teams can become quietly discouraged even while working hard. The discouragement is not always about workload alone. It is about the weakening relationship between effort and evidence. People can sustain effort for a long time when they can see that effort becoming capacity. They struggle when effort feels repeatedly absorbed without becoming progress.
Donohoo, Hattie, and Eells have helped bring collective efficacy to the centre of school improvement conversations, particularly by emphasising the importance of educators’ shared belief that they can positively influence student outcomes (Donohoo et al., 2018). The important point for leadership teams is that belief strengthens when teams can see evidence of impact. Collective efficacy is not a slogan placed over effort. It develops through the repeated interpretation of evidence that effort is making a difference.
Leadership teams therefore need to ask a more disciplined set of questions. What held because we acted together? What became clearer because we coordinated? What pressure was better carried because it was not left to one person? What trust was strengthened because we returned to the conversation? What became more possible because the team moved as a team?
These are not soft questions. They are efficacy questions.
Evidence Changes Expectation
When effort does not become evidence, teams do not simply lose energy. They lose expectation.
A team with little evidence of shared capacity may still show up professionally, but it often approaches difficulty with quiet caution. People protect their own areas. They manage what they can control. They become careful about relying too heavily on collective movement because collective movement has not yet proven reliable enough.
A team with growing collective efficacy carries a different expectation. It may still feel the difficulty. It may still be tired. It may still know that the work is complex. But it has proof. It has moments it can remember where coordinated effort made something better.
That memory becomes a resource.
This is deeply practical. A leadership team that expects shared effort to work is more likely to invest in shared effort again. It is more likely to stay with a difficult conversation, distribute responsibility, align communication, review honestly, and repair when something weakens. Efficacy strengthens future action because the team has evidence that action is worthwhile.
The arc is simple but powerful:
Effort becomes evidence. Evidence becomes expectation. Expectation becomes efficacy.
When this arc is broken, teams may keep working without growing more confident. When the arc is strengthened, even difficult work can become a source of collective confidence.
Tschannen-Moran’s work on trust in schools is useful here because trust is built through repeated evidence of benevolence, reliability, competence, honesty, and openness (Tschannen-Moran, 2004). Leadership teams do not trust their collective capacity in the abstract. They come to trust it by experiencing one another acting reliably, honestly, competently, and openly in the work itself.
Trust and collective efficacy reinforce each other. Trust helps teams take the risks needed for shared action. Shared action that holds gives the team more reason to trust its own capacity.
That is how confidence becomes earned.
The Evidence Loop
If collective efficacy is built from evidence, leadership teams need to stop letting evidence disappear.
They need a way to capture what held, name what it proved, and carry that proof into the next challenge. Otherwise, the next urgent issue can overwrite the team’s memory of what actually worked. The progress happened, but it was not interpreted. The decision held, but the team did not name why. The effort produced movement, but the evidence was never converted into confidence.
The Evidence Loop is not a reflective exercise for its own sake. It is a way of protecting the team’s memory from being overwritten by the next crisis.
It begins with five questions.
The first question is: What are we trying to carry together?
Collective efficacy depends on shared work, not parallel effort. Many leadership teams are full of committed people working hard in adjacent lanes. Each person carries their portfolio, solves problems, responds to pressure, and tries to protect the school. But parallel effort does not automatically build collective efficacy. The team needs to know what it is carrying together.
The second question is: What coordinated move did we make?
This shifts attention from intention to behaviour. The team may have talked about the issue, but what did it actually do together? Did it align communication, share responsibility, slow a decision, protect a vulnerable conversation, distribute emotional load, or create a clearer pathway for follow-through?
The third question is: What held because we acted together?
This is the evidence question. What became more stable, coherent, discussable, or durable because the team acted in a coordinated way? Did the decision travel? Did the message remain clear? Did staff experience less confusion? Did the team reduce the amount of rework required? Did a difficult issue become easier to carry because it was no longer held by one person alone?
The fourth question is: What did this show us about our shared capacity?
This is where evidence becomes learning. The team is asking what the experience revealed about its capacity to act together. Perhaps it showed that the team can slow down without losing momentum. Perhaps it showed that candour can be held without damaging trust. Perhaps it showed that load can be redistributed when it is named early. Perhaps it showed that the team’s communication is stronger when it aligns before speaking outward.
The fifth question is: What will we strengthen next time?
The loop closes with improvement. Efficacy is not built by pretending everything worked. It is built by learning from what held and what did not. A mature team can acknowledge progress and still ask what needs to become stronger.
The loop is simple. Its discipline is not.
It asks the team to stop rushing past its own evidence.
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.
Schools Experience Coherence, Not Intentions
Schools do not experience leadership as a collection of individual intentions. They experience it as coherence, contradiction, steadiness, confusion, trust, or noise.
That is why collective efficacy in the leadership team matters. A school may have a capable principal and committed deputies, but staff do not experience those qualities as separate abstractions. They experience the way leadership decisions travel, the way priorities align, the way communication lands, the way tension is handled, and the way the team holds pressure.
When collective efficacy is weak, leadership can become fragmented even while individual leaders are working hard. One person carries culture. Another carries operations. Another carries staff wellbeing. Another carries curriculum. Another carries parent communication. Each leader may be diligent, but the team may not experience enough evidence that its shared effort is producing coherent movement.
That fragmentation has a cost. Staff hear different messages. Priorities compete rather than align. Decisions are made but not sustained. Trust depends on individual relationships rather than team coherence. Pressure gets passed through the system because the leadership team is not yet experiencing itself as a coordinated source of steadiness.
When collective efficacy strengthens, the team becomes a different kind of presence in the school. Difficulty does not disappear, but the team has more evidence that it can carry difficulty together. It can coordinate around shared priorities, stay steadier under pressure, and learn from its own effort.
Leithwood, Harris, and Hopkins argue that leadership contributes significantly to student learning by shaping the conditions in which teaching and learning occur, including direction, people development, organisational design, and the management of teaching and learning (Leithwood et al., 2020). Those functions require more than individual excellence. They require leadership teams capable of acting coherently enough for their work to be experienced across the school.
Collective efficacy helps a leadership team become more than a group of capable individuals. It helps the team experience itself as a source of shared influence.
Conclusion
A leadership team does not build collective efficacy by talking itself into confidence.
It builds efficacy when shared effort becomes evidence.
When decisions travel. When difficult conversations lead somewhere. When pressure is carried by the team rather than absorbed by the same few people. When trust becomes behaviour. When coordinated work produces something more durable than temporary relief.
That evidence changes what the team expects of itself.
Leadership teams often meet the next challenge with the memory of the last one. If the memory is that shared effort disappeared into confusion, uneven load, or fragile follow-through, the team carries that memory into the next moment of difficulty. If the memory is that shared effort held, the team carries proof.
That is why collective efficacy is not optimism.
It is confidence with evidence.
The question for a leadership team is not simply, “Do we believe we can do this?”
The deeper question is:
What proof are we accumulating that shared leadership works?
If this is surfacing something familiar in your leadership team — if effort is being given, but the team is not yet seeing enough evidence that shared effort is holding — I offer a complimentary Leadership Pressure Diagnostic. It is a focused conversation to help identify where pressure may be weakening collective confidence, where coordinated effort may be breaking down, and what kind of leadership response may now be required.
References
Bandura, A. (1997). Self-efficacy: The exercise of control. W. H. Freeman.
Donohoo, J., Hattie, J., & Eells, R. (2018). The power of collective efficacy. Educational Leadership, 75(6), 40–44.
Goddard, R. D., Hoy, W. K., & Woolfolk Hoy, A. (2000). Collective teacher efficacy: Its meaning, measure, and impact on student achievement. American Educational Research Journal, 37(2), 479–507.
Leithwood, K., Harris, A., & Hopkins, D. (2020). Seven strong claims about successful school leadership revisited. School Leadership & Management, 40(1), 5–22.
Tschannen-Moran, M. (2004). Trust matters: Leadership for successful schools. Jossey-Bass.
