"The Servant Leader – Between Ideal and Reality"

January 2026 9 min read Opinion + Coaching Perspective

Servant Leadership is one of the most cited and least understood concepts in Agile. It is frequently described as the antidote to command-and-control management. In practice, it is often used as a justification for avoiding the difficult parts of leadership entirely. Real servant leadership is harder, not easier, than the command-and-control model it replaces.

---

The Hook: The Leadership Style That Got Lost in Translation

Robert Greenleaf coined the term “servant leader” in a 1970 essay titled “The Servant as Leader.” His central idea was that the most effective leaders start from the position of wanting to serve – and that the desire to lead emerges from that foundation, rather than from the desire for power, status, or control. The servant leader’s first question is not “how do I get results?” but “what do my people need to do their best work?”

The Scrum Guide adopted this language explicitly, describing the Scrum Master as a “true leader who serves the Scrum Team and the larger organisation.” This was a deliberate choice – the Scrum Guide’s authors wanted to distinguish the Scrum Master’s leadership style from the traditional project manager’s directive authority.

What happened next was predictable. “Servant leader” became a job title modifier. It appeared in Scrum Master job descriptions, in leadership training programmes, and in Agile coaching certifications. It was defined, simplified, and in many cases, fundamentally misunderstood. The result is a concept that is universally endorsed and rarely practised.

---

The Reality: Three Misreadings of Servant Leadership

Misreading 1: Servant Leadership Means Doing What the Team Wants

The most common misreading. If the leader serves the team, surely the team’s preferences should drive the leader’s decisions? This interpretation produces leaders who avoid difficult conversations, accommodate poor performance, and prioritise team harmony over team effectiveness.

Greenleaf’s original concept is more demanding than this. He describes the servant leader as asking: “Do those served grow as persons? Do they, while being served, become healthier, wiser, freer, more autonomous, more likely themselves to become servants?” This is not a question about team comfort. It is a question about team growth – which sometimes requires discomfort.

A leader who never challenges the team, never delivers difficult feedback, and never holds anyone accountable for poor work is not a servant leader. They are a conflict avoider with a noble vocabulary.

Misreading 2: Servant Leadership Means Having No Authority

Another common misreading, particularly in the Scrum Master context. The Scrum Master has no formal authority over the Development Team – they cannot assign tasks, override technical decisions, or mandate behaviours. This is sometimes interpreted as meaning that the Scrum Master has no power at all.

This confuses formal authority with influence. Effective servant leaders exercise significant influence – through expertise, through relationship quality, through the clarity of their thinking, and through their willingness to have the difficult conversations that others avoid. The absence of formal authority does not make a leader powerless. It makes them dependent on a different, and arguably more sustainable, form of power.

Servant leaders who believe they have no authority tend to become passive. They facilitate. They support. They observe. And they avoid the challenging, uncomfortable work that genuine service to a team sometimes requires.

Misreading 3: Servant Leadership Is Inherently Selfless

The word “servant” carries connotations of selflessness, of subordinating one’s own needs to others’. This creates an image of the servant leader as endlessly patient, never frustrated, always available, perpetually subordinating their own judgment to the team’s.

This is neither psychologically sustainable nor actually effective. Servant leaders have judgment. They use it. They have values. They act on them. They have boundaries. They enforce them. The service orientation is about the direction of the leader’s energy – toward the team’s development and effectiveness – not about the absence of the leader’s own perspective and agency.

“Servant leadership is not about making yourself small so others can be big. It is about making yourself useful in the ways that help others become capable. Sometimes that requires being very direct and very challenging.” Markus – agile-checksum.com

---

The Checksum: What Genuine Servant Leadership Requires

Genuine servant leadership, as Greenleaf described it and as the most effective Agile leaders practise it, has several characteristics that are demanding rather than comfortable.

It Requires Courage, Not Comfort

The servant leader’s orientation toward the team’s growth and effectiveness means they must sometimes deliver feedback that is uncomfortable to give and uncomfortable to receive. They must challenge the team member whose work is below standard – not because they want to be confrontational, but because genuine service to that person requires honest feedback. They must raise the conflict that the team is avoiding – not because conflict is desirable, but because leaving it unresolved is more damaging than addressing it.

Servant leadership done correctly is not easier than command-and-control. It is harder, because it requires the leader to hold two things simultaneously: genuine care for the people they serve and genuine commitment to challenging them when they need to be challenged.

It Requires Systemic Thinking, Not Task Management

The servant leader’s question is not “what tasks need to be done?” but “what conditions need to exist for this team to do their best work?” This requires a different kind of attention – to the team’s relationships, to the organisational environment, to the processes that help or hinder, to the implicit norms that shape behaviour.

This systemic orientation is why effective Scrum Masters spend time on things that look unproductive from the outside – observing team dynamics, building relationships across the organisation, understanding the political landscape that determines which impediments can be resolved and which cannot. These activities serve the team’s effectiveness even when they do not look like direct contribution to sprint goals.

It Requires Accountability Without Authority

Perhaps the most demanding aspect of servant leadership: holding people accountable without the formal authority to impose consequences. The servant leader cannot fire someone for poor performance, cannot mandate behaviour change, cannot override decisions they believe are wrong. They can only influence – through relationship, through coaching, through making consequences visible, through escalation to those who do have formal authority.

This requires significant skill and patience. It also requires the willingness to escalate when influence alone is insufficient – and the judgment to know when that point has been reached.

---

Real-World Examples: The Gap Between Ideal and Practice

The Servant Leader Who Served the Wrong Thing

A Scrum Master I coached prided himself on his servant leadership approach. He was available to the team constantly. He removed impediments quickly. He protected the team from external disruption with real effectiveness. The team liked him and trusted him.

The problem was that he was serving the team’s comfort rather than their growth. When a senior developer on the team consistently produced code that created technical debt – writing fast, functional code that ignored the team’s agreed architecture – the Scrum Master did not address it. The developer was well-liked. The conversations would have been difficult. The Scrum Master convinced himself that it was not his place to address technical quality issues.

Two years later, the team’s velocity had declined significantly as the accumulated technical debt made every new feature harder to build. The problem had been visible for eighteen months. Nobody had said anything difficult. The Scrum Master had served the team’s preference for harmony. He had not served their effectiveness.

The Commander Disguised as a Servant

A department head had attended a servant leadership programme and enthusiastically adopted the language. He described himself as a servant leader in every relevant context. He asked his team what they needed. He removed obstacles. He said his door was always open.

In practice, his leadership style had not changed. Decisions were still made by him, with team input that was rarely incorporated. Feedback from the team was welcomed in the meeting and ignored in practice. The open door existed for the team to bring him problems he would then solve – not for the team to exercise genuine influence over direction and decisions.

He had learned the vocabulary of servant leadership without the underlying orientation change. The result was more damaging than straightforward command-and-control would have been, because the gap between the stated style and the actual behaviour created confusion and eroded trust.

The Servant Leader Who Got It Right

A technical lead I worked with in a pharmaceutical organisation had never heard of servant leadership as a concept. She had arrived at the orientation independently through twenty years of managing technical teams.

Her approach was simple and consistent. She asked her team what was in their way, and then spent her time removing those obstacles. She attended every sprint review not to present but to listen. When she disagreed with a team decision, she said so clearly, explained her reasoning, and then – if the team still disagreed after the discussion – she accepted their decision and supported it. She gave feedback that was direct and specific, framed always in terms of the impact on the team’s work rather than personal criticism.

When I described servant leadership to her, she said: “That’s just what leadership is. Everything else is management theatre.” She was not entirely wrong.

---

A Framework for Servant Leadership in Practice

Situation	Servant Leadership Response	Common Misapplication
Team member performing below standard	Direct, specific feedback focused on impact and development	Avoid the conversation to preserve harmony
Team making a decision the leader believes is wrong	State disagreement clearly, explain reasoning, accept team decision if they persist	Either override the decision or say nothing and let it fail
Organisational impediment blocking the team	Escalate specifically and persistently until resolved	Note the impediment, work around it, move on
Team conflict between members	Create conditions for direct resolution, facilitate if needed, do not resolve it for them	Mediate privately, resolve for them, pretend it did not happen
Team requesting something counterproductive	Decline, explain why, explore what need underlies the request	Accommodate the request to appear supportive

---

The Takeaway: Service Is Not Submission

Servant leadership, properly understood, is one of the most demanding leadership orientations available. It requires leaders to hold their own judgment and their team’s autonomy in productive tension. To be direct without being directive. To challenge without controlling. To serve the team’s growth rather than their comfort, the team’s effectiveness rather than their preferences.

The organisations that have reduced servant leadership to “being nice and removing obstacles” have not adopted a new leadership model. They have adopted a new vocabulary for an old avoidance pattern. The difficult parts of leadership – the honest feedback, the accountability without authority, the courage to challenge the team when the team is wrong – do not disappear in a servant leadership model. They become more important, because they cannot be hidden behind formal authority.

Run the checksum on your servant leadership practice:

1. When did you last deliver feedback to a team member that was genuinely difficult to give? What was the outcome?
2. When did you last disagree with your team’s decision and say so clearly? Did you accept their decision when they maintained it?
3. Is the team more self-sufficient than it was six months ago, or more dependent on you? Which direction are you serving?

The direction of the dependency tells you more about your servant leadership than any self-assessment. A servant leader, over time, creates a team that needs them less. If the team is becoming more dependent, something in the service orientation has inverted.

---

Glossary Terms Used in This Article

• Servant Leader – A leadership philosophy focused on serving the team’s growth and effectiveness rather than directing them.
• Scrum Master – The Scrum accountability described explicitly as a servant leader in the Scrum Guide.
• Psychological Safety – The shared belief that it is safe to take interpersonal risks within a team.
• Technical Debt – The implied cost of rework caused by choosing quick solutions over better ones.
• Agile Transformation – The process by which an organisation attempts to adopt Agile values and practices at scale.