Servant leadership is a way of leading in which the leader's first job is to find out what the team needs in order to deliver and then to supply it. The term comes from an essay by Robert Greenleaf published in 1970, and PMI adopted it as the expected posture of a project manager on an adaptive team. It appears in the People domain of the examination and throughout the Agile Practice Guide.
The posture reverses the usual direction of a team's attention. A conventional leader decides what will happen and hands the decision down, so the team spends its energy working out what the leader wants. A servant leader starts from what the team needs and spends their own energy supplying it, so the questions run upward. The sections below describe what that looks like in a working day, why PMI expects it on adaptive work and where it stops.
What a servant leader does each day
Most of the daily work in this posture is finding out what stands in the way of the team and removing it. A dependency nobody has chased, an approval that has sat with a manager for a fortnight, a test environment shared with three other teams and a specification that two people read differently are all typical. None of them appears on a plan and each of them costs more than the tasks around it.
The team usually sees the obstacle long before the leader does. What the team often cannot do is reach the person who could clear it, and this is where the leader's standing in the organisation is useful. Much of the role consists of walking into a conversation the team would have waited a week to have. That standing is spent on the team's behalf each time it is used, and it has to be earned again.
The same situation led two ways
The posture is easier to recognise in actions than in tone, because a directive leader and a serving leader may use the same words and then do opposite things.
| The situation | The directive act | The serving act |
|---|---|---|
| A test environment shared with three teams keeps being wiped mid run | Tells the team to schedule around the others and rerun what failed | Gets the three teams and their managers to agree an owner and a booking rule, then tells the team what changed |
| An estimate comes back at twelve weeks against a sponsor's eight | Trims the estimate to ten and asks the team to find the difference | Takes the twelve to the sponsor alongside the scope that would fit eight, and comes back with a decision |
| Two developers disagree about the integration approach | Picks one approach and moves the meeting on | Puts the constraint that decides between them in front of both, and holds a deadline for choosing |
| A stakeholder interrupts the team daily for status | Forwards each question to the team asking for a quick answer | Absorbs the questions, agrees a weekly slot and answers most of them without touching the team |
| A milestone slips because a junior missed a dependency | Reassigns the work and adds a checkpoint | Resets the milestone with the sponsor, then walks the junior through how the dependency would have been spotted |
The right hand column follows one pattern. The leader takes the part of the problem that needs their position and leaves the part that needs the team's expertise. This is the test to apply when a situation arrives that no table covers. Whoever holds the information makes the call, and whoever holds the standing clears the path to it.
Why PMI makes servant leadership the default on adaptive work
That division of labour is also the reason PMI places servant leadership at the centre of how a project manager works with an adaptive team. Adaptive delivery moves the detailed decisions to the people doing the work, because on such projects whoever is closest to the problem knows the most about it, and information goes stale fastest at the top. A leader who assigns tasks in that setting becomes a bottleneck on exactly the decisions the approach was designed to spread out. The sponsor then receives a late project while everybody follows instructions correctly.
Hybrid delivery keeps the posture and narrows its range. Governance, funding and the interfaces with the rest of the organisation are led directly, while how the work is done inside the team remains with the team.
How a servant leader differs from a passive one
Both a passive leader and a servant leader stop issuing instructions, and from inside the team the two may look alike for a week. The difference is what each one does with the time. A servant leader works the organisation while the team works the problem, chasing the approval, renegotiating the shared environment and briefing the sponsor before the sponsor asks. Most of that happens outside the team's line of sight.
Accountability stays where it began. The leader is still answerable for the outcome, the budget and the commitments made to sponsors, and being helpful transfers none of it.
Agreement is a separate matter again. A leader who contradicts nobody has stopped contributing a judgement of their own, and that judgement is one of the things a team is entitled to expect from whoever holds the wider view.
The three acts a servant leader performs
Judgement, standing and time are spent on three kinds of act. Shielding comes first. A team interrupted every hour by a stakeholder wanting a quick answer is not working on the project, and the leader is the one person placed to absorb those interruptions and gather them into something the team can answer once.
Clearing blockers the team cannot clear itself comes second, and the qualification matters. When the leader removes an obstacle the team could have handled, the team learns to escalate. The useful question is whether the obstacle genuinely sits beyond the team's reach. Preferring not to deal with it does not count.
Making the decisions the team should not have to make comes third, and this act is the one most often left off such a list. Some decisions carry a political cost that colleagues cannot be asked to pay. Which of two directors gets their scope, whether to spend contingency and which commitment breaks when something has to break all belong to that class. Handing such a decision to the team in the name of empowerment is a way of making the team pay the cost.
When the servant leader takes command
The posture described here is a default, and a default can be overridden. Safety, legal exposure and a genuine emergency all override it, and a team that discovers a data breach needs someone to take control of the response and say who does what. The part that takes discipline is the return to the ordinary posture afterwards, once the clarity that command brought has become comfortable.