Servant Leadership
Servant Leadership
What is servant leadership?
- Serving first instead of ruling, and helping people grow
- Sharing authority · listening · empathy
- Serving builds more proactive teams
Adopting servant leadership means changing a leader’s daily schedule. More time goes to 1:1 meetings and cross-team coordination than to receiving reports, and the leader who used to speak first in meetings now speaks last. The yardstick shifts too: the leader’s report card is no longer “what did I get done?” but “what can my team members do now that they couldn’t last year?” Because authority is delegated but the leader remains responsible for the results (accountability), it is also the most uncomfortable approach for leaders who can’t let go of hands-on control.
Drawing on Greenleaf’s writing, Larry Spears distilled ten characteristics: listening, empathy, healing, awareness, persuasion, conceptualization, foresight, stewardship, commitment to the growth of people, and building community. Persuasion is the one to note: it moves people by convincing them rather than by pulling rank, which sets it apart from empowering leadership, a term for the delegation technique itself. Empowering is about what to hand over, while servant leadership is about motivation: why you hand it over. It is not a cure-all, though. In situations like fires or recalls that demand second-by-second decisions, a directive style works better, and once a leader has more than 10 direct reports, keeping up weekly 1:1s becomes physically impossible.
The most common failure in practice is treating “serving” as “accepting everything.” Accommodating every request from team members erodes priorities, turns the leader into an approval bottleneck who takes on other people’s work, and around six months in, the leader burns out first. A riskier mistake is holding back hard feedback. If you put off feedback for a low performer, the burden falls on the high performer next to them, and the team slides into a sense of unfairness: “working hard makes no difference.” A servant leader does not lower expectations; they keep expectations high while securing the resources and the path to meet them.
Sungmin JooExpert in diagnostic-based coaching leadership, entrepreneurship education, and design thinking
John KimInstructor John Kim, author of B2B Marketing Design and CEO of Nanum ConsultingThe term was coined by Robert Greenleaf in his 1970 essay “The Servant as Leader.” Its core idea: a leader is someone who serves first (“servant first”).
Let’s look at a hypothetical case: Company A, an industrial automation parts maker with 140 employees and annual revenue of KRW 32 billion (≈ US$23,941,300). Over the past year, 5 people voluntarily left its 12-person control development team, and the “trust in supervisor” item in its internal organizational survey scored 58 out of 100. Team Lead Kim personally approved every technical decision, so approvals waited an average of 4 days. Here is how the next six months played out.
- Team Lead Kim cut his own speaking time in the weekly meeting from 30 minutes to 8, opened with the question “What is blocking you most this week?”, and asked each of his 12 team members in turn.
- The top complaint over three weeks was handling data requests from other departments, so Team Lead Kim agreed with the purchasing and quality leads to route all requests through himself, cutting each developer’s admin work from 4.5 hours a week to 1.2.
- He ran biweekly 30-minute 1:1s with six senior engineers, asking “Name one skill you want to make your own this year,” and then assigned motor control and communication modules on real projects to match their answers.
- He handed authority over outsourcing orders up to KRW 50 million (≈ US$37,400) and schedule changes to three part leaders, setting the rule “report approvals after the fact,” and approval wait times dropped from 4 days to half a day.
- When an incident pushed delivery back by two weeks, Team Lead Kim opened the executive report by saying, “It was my misjudgment to order the design change so late.” In return, Kim gave the 2 underperforming members written improvement goals at the quarterly meeting.
- Six months later, voluntary departures in the control development team fell from 5 to 1, the “trust in supervisor” score in the organizational survey rose from 58 to 79, and sprint goal achievement rose from 61% to 88%.