There is a version of leadership that receives applause.
It is visible. It launches things. It arrives with a strategy, a framework, a set of priorities and a timetable for implementation. It is easy to recognise because it leaves footprints everywhere it goes.
There is another version that is harder to see.
It leaves behind no programme named after itself. No signature initiative. No dramatic before-and-after story. It rarely appears in conference keynotes because, from the outside, it often looks as though nothing happened at all.
And yet, years later, its effects remain.
This second version has become the subject of a book I have been writing over the last year: Leadership Without Applause: A Philosophy of Institutional Stewardship.
It began with an observation that has followed me through every school I’ve worked in.
Most schools do not fail because nobody cares.
They fail because everybody cares.
The difficulty is that care often arrives disguised as activity.
A new intervention is introduced because nobody wants a child to be overlooked. A monitoring process is added because leaders want reassurance. A structure is adjusted because someone is worried about a particular outcome. Every decision is reasonable. Every decision is made in good faith. Gradually, however, the system becomes crowded with layers of well-intentioned interference.
Nothing breaks.
Everyone stays busy.
Everyone grows tired.
The institution remains functional while becoming steadily less coherent.
The book argues that the defining challenge of leadership is not usually transformation. It is protection.
That claim feels almost unfashionable.
Contemporary leadership literature is full of movement: innovation, disruption, agility, transformation. These are valuable ideas, particularly when systems are genuinely broken. But what about institutions that are already working? What if they almost work? What about schools with committed staff, sensible structures, and a clear sense of purpose?
The leadership challenge changes.
The question becomes less:
“What should we add?”
and more:
“What should we stop disturbing?”
I have become increasingly interested in the difference between leadership that depends upon presence and leadership that survives absence.
Some leaders create movement.
Others create conditions.
The first produces visible impact. The second produces continuity.
When I look back at the leaders who have influenced me most, it is not their charisma I remember. It is the culture they left behind. It is the way people continued to work, to think, and to care when those leaders were no longer in the room.
The strongest leadership often resembles infrastructure.
Nobody notices a well-designed road while driving on it. Nobody celebrates a timetable that simply works. Nobody applauds a bridge every time it remains standing.
The same is true of institutions.
When leadership matures, people stop noticing it because it has become embedded in shared habits, shared expectations, and shared understanding.
The irony is that this is often precisely when leadership has become most successful.
One of the central questions running through the book is deceptively simple:
What currently depends on me that should not?
It is a question I find myself returning to repeatedly.
Where does the organisation pause until I arrive?
What decisions are travelling upward unnecessarily?
What problems exist because, over time, I have made it easier to ask than to decide?
These questions are uncomfortable because they challenge a temptation many leaders quietly carry: the desire to be needed.
The book argues that leadership reaches its highest form not when people become dependent upon the leader, but when people become increasingly capable without them.
That idea sits alongside another that has emerged throughout the writing process.
Human beings rarely lose their way all at once.
We drift.
Not because we are careless. Not because we are malicious. Not because we lack integrity.
We drift because uncertainty is uncomfortable.
We drift because relief often feels like progress.
We drift because most departures from our values arrive disguised as reasonable exceptions.
Over time I have become less interested in why leaders fail and more interested in how leaders return.
How do people find their way back after disappointment?
How do they recover their orientation after pressure?
How do they continue to act with integrity when recognition does not arrive?
Perhaps the greatest lesson I have learned in leadership is that purpose cannot be anchored to applause.
Applause is intermittent.
Recognition is uneven.
Promotion is unpredictable.
If those become the foundations of commitment, commitment eventually becomes fragile.
The leaders I most admire continue doing the work long after the reward has been withdrawn. They return, repeatedly, to the same responsibilities, the same obligations, and the same values, even when nobody is watching particularly closely.
That, I suspect, is the real work of leadership.
Not the launch.
Not the speech.
Not the initiative.
The return.
Leadership Without Applause is my attempt to explore that return: what threatens it, what sustains it, and why some leaders continue finding their way back long after easier alternatives have appeared.
Because what remains, in the end, is rarely the applause.
What remains is the work.
Leave a comment