Servant Leadership: Serve First, Lead Second

THE MENTAL MODEL: Servant leadership flips traditional hierarchy on its head. Coined by Robert K. Greenleaf, the philosophy is simple: be a servant first, then aspire to lead. This contrasts sharply with a "leader-first" person, who may be driven by a need for power or possessions. A servant-leader shares power, puts the needs of others first, and views their role as supporting the team, not commanding it from the top of a pyramid.

HOW IT WORKS: The primary focus is on the growth and well-being of people and the communities they belong to. A servant-leader's success is measured by the progress of those they serve. Greenleaf proposed a test: Do those served grow as persons? Do they, while being served, become healthier, wiser, freer, more autonomous, and more likely themselves to become servants? The goal is to help people develop and perform as highly as possible by ensuring their needs are met.

WHEN TO USE IT: This model is highly effective in environments that depend on collaboration and individual expertise, such as modern software engineering teams. It is the philosophical foundation for roles like the Scrum Master in Agile, whose job is to remove impediments for the development team. It is also ideal for managers focused on coaching, mentoring, and building a resilient, high-performing team for the long term.

WHEN NOT TO USE IT: The servant-first approach can be less effective in an acute crisis that requires rapid, top-down, unilateral decisions. In a command-and-control environment, or during a major organizational turnaround, a more directive style may be necessary for immediate survival. It can also be difficult to practice in cultures that view sharing power as a sign of weakness.

ONE CANONICAL EXAMPLE: An engineering manager practicing servant leadership doesn't ask, "What did you get done for me?" but rather, "What do you need to be successful?" They spend their time removing organizational blockers, securing budget for training, coaching engineers through technical challenges, and protecting the team from distractions. Their success is not their personal output, but the team's increasing autonomy and performance.