Servant Leadership Is the Goal, Not the Starting Point

The conviction is real and it is old. Robert Greenleaf coined servant leadership in 1970, and his test for it has stuck with me because it refuses to let you fake it: do those served grow as people, become healthier, wiser, freer, more autonomous, more likely themselves to serve? (Greenleaf, The Servant as Leader, 1970). That is the leadership I want to practise. It is also, on a troubled programme, the leadership you are sometimes not yet permitted to practise.

This is a school, not a personality trait

It would be easy to file "I'm a servant leader" under self-flattery, so it is worth saying that this is a researched tradition, not a vibe. A 2019 systematic review of two decades of studies defined servant leadership as an other-oriented approach built on prioritising followers' individual needs, and found consistent links to trust, engagement and performance (Eva et al., The Leadership Quarterly, 2019). The validated measure of it lists "empowering" and "helping followers grow" as explicit dimensions (Liden et al., 2008). Empowering leadership has its own evidence base, and one honest nuance inside it: it reliably buys commitment and trust, and less reliably buys raw output (Kim, Beehr & Prewett, meta-analysis, 2018). Empowerment alone does not deliver. It needs scaffolding. That is exactly why the way I lead is not just "trust people," but three disciplines that make trusting them safe.

Clarity

People cannot do good work inside fog. Most of what looks like underperformance is actually unclear structure, and the fix is unglamorous. A team charter so everyone knows how we work before we are under pressure. DevOps or Jira used properly, with the hygiene actually kept, so the board tells the truth. A decision tree so people know what they can decide and what they escalate. A RAID log the team owns together rather than something I maintain alone. Explicit do's and don'ts for client communication. A meeting cadence with a reason to exist. Roles and responsibilities written down, not assumed.

None of that is bureaucracy for its own sake. It is the applied version of a well-evidenced finding: specific, clear goals and roles outperform "do your best" almost every time, because they focus attention and remove the friction of not knowing (Locke & Latham, goal-setting theory). Clarity is how you give people room without giving them chaos.

Consistency

Trust, but verify. I give people genuine autonomy and I also check, not because I expect failure, but because standards only become real when they are upheld every time. I will stay on someone's case, warmly, until a standard is embedded rather than performed once. The principle underneath is behavioural consistency: when similar behaviour gets a similar response every single time, people can predict you, and predictability is most of what trust actually is.

Consistency has a public and a private face. I praise achievements in the open, because public recognition teaches the whole team what good looks like. I coach in private when something falls short, because criticism delivered without an audience lowers defences and keeps the learning intact. This is older than any of us, but it sits comfortably inside Kim Scott's Radical Candor (2017): care personally and challenge directly, and do each in the setting that makes it land. The one caveat I hold lightly is that praise-public, coach-private is a strong default, not an iron law; sometimes accountability needs to be visible too.

Transparency

The customer should hear about a problem from me, early and honestly, not discover it late. The same goes for internal stakeholders. And when a problem does arrive, I try never to bring just the problem. I bring a clear read of the situation and a couple of options, because dumping a crisis on someone is not candour, it is abdication.

This is the operational form of psychological safety, Amy Edmondson's finding that the best teams report more problems, not fewer, because they can (Edmondson, Administrative Science Quarterly, 1999). Her point is easy to misread: psychological safety is not niceness, it is the precondition for telling the truth. A programme where nobody is raising concerns is not calm. It is usually one where concerns cannot travel. Transparency, done as options-plus-a-read rather than alarm, is how you keep the channel open without flooding it.

Why servant leadership comes second

Here is the part most leadership writing skips. The research on servant leadership is also research on its limits, and the limits explain my "not always allowed." In a genuine crisis, when a decision has to land in minutes, consensus-seeking is the wrong tool and people want a steady, directive hand. In hierarchical, high power-distance settings, a service posture can read as a lack of authority. And in an environment where the last leadership burned the team, servant behaviours get misread as weakness or manipulation until the relational debt is paid down.

A failing programme is frequently all three at once. So I usually start more directively than I would like: stabilise, set the structure, make the calls that need making. Clarity, consistency and transparency are how I then pay down the trust debt. As the programme steadies and the team proves it can be trusted, I hand power back. The directive start is not a contradiction of servant leadership. It is how you create the conditions in which servant leadership is finally allowed to work.

Under-promise, over-deliver, done honestly

I take real pride in bringing programmes in under budget, and in spotting things mid-delivery that make the product richer or the return higher and folding them in while we still can. I would rather a client be pleasantly surprised than managed into disappointment.

But I want to be straight about the trap in "under-promise, over-deliver," because the naive version corrodes the trust it is meant to build. Routinely beating your own numbers eventually tells people you padded them, and they start discounting everything you commit to. Tied to targets, it quietly rewards setting the bar low. So I do not treat it as a permanent operating model. It is a trust-building heuristic for a low-trust start. As trust matures, the goal shifts from lowballing to calibrating: forecasts that are honest rather than conservative, and genuine value added inside scope rather than expectations deliberately set short. The pride is in the value, not in the gap between the promise and the result.

Leadership as conditions-creation

None of this is a claim to have it figured out; I am still learning it, engagement by engagement. But the shape has held across enough programmes that I trust it. Servant, empowering leadership is not something you declare on day one. It is a state you engineer, through clarity, consistency and transparency, until the team and the client can be trusted, empowered and genuinely served. On a recovery, the first job is rarely to serve. It is to build the conditions in which serving becomes possible.

The thinking behind it

Greenleaf, R.K., The Servant as Leader (1970). · Eva, Robin, Sendjaya, van Dierendonck & Liden, "Servant Leadership: A Systematic Review," The Leadership Quarterly (2019). · Liden, Wayne, Zhao & Henderson, "Servant Leadership: Development of a Multidimensional Measure," The Leadership Quarterly (2008). · Kim, Beehr & Prewett, "Employee Responses to Empowering Leadership: A Meta-Analysis," Journal of Leadership & Organizational Studies (2018). · Locke & Latham, A Theory of Goal Setting and Task Performance (1990). · Edmondson, A., "Psychological Safety and Learning Behavior in Work Teams," Administrative Science Quarterly (1999). · Scott, K., Radical Candor (2017).