Leadership styles and servant leadership

No single leadership style works for every team, every stage of a project or every crisis. A style that energizes an experienced agile team can leave a new graduate lost; a style that rescues a failing project in a week can exhaust a healthy team in a month. The ECO asks project managers to "determine an appropriate leadership style", which means knowing the main styles, recognizing the signals that call for each and being able to shift deliberately. This lesson surveys the styles PMP candidates meet most often and then looks closely at servant leadership, the style most associated with agile and hybrid delivery.

From traits to situations

Leadership theory has moved through several waves. Early trait theories asked what personal qualities leaders share, such as intelligence, confidence and integrity. They found some correlations but could not explain why the same person led well in one setting and poorly in another. Behavioral theories, such as the Ohio State and Michigan studies, looked instead at what leaders do and identified two broad dimensions: task-oriented behavior (organizing work, setting standards) and people-oriented behavior (supporting, building relationships). Contingency and situational theories then argued that the best mix depends on the situation: the people, the task and the context. Modern approaches, such as transformational and servant leadership, add an emphasis on purpose, values and developing others.

For project managers, the practical message is that style is a choice. You can read the situation and adjust. The main factors are the team's competence and experience with the task, its commitment and confidence, the urgency and risk of the situation, the organizational culture and the development approach (predictive, adaptive or hybrid).

A catalog of styles

Two pairs are easily confused. Transactional leadership is an exchange: do this and you get that, with management by exception when things go wrong. Transformational leadership raises people's sights: it connects work to a larger purpose and develops individuals. Bass described four components of transformational leadership, often called the four I's: idealized influence (acting as a role model), inspirational motivation (a compelling vision), intellectual stimulation (encouraging people to question assumptions) and individualized consideration (attending to each person's needs). Most effective project managers use transactional tools, such as clear objectives and recognition for meeting them, inside a transformational frame.

Situational leadership

Hersey and Blanchard's situational leadership model, later developed by Blanchard as Situational Leadership II, is one of the most practical tools for project managers. It describes four styles produced by combining two kinds of leader behavior: directive behavior (telling people what, when and how) and supportive behavior (listening, encouraging and involving). The right combination depends on the follower's development level for a particular task, which combines competence (skill and knowledge) and commitment (motivation and confidence).

The key insight is that development level is task-specific. A senior developer may be D4 on coding and D1 on presenting to the board. Treating that person as a self-reliant achiever on the board presentation sets them up to fail; treating them as a beginner on code insults them. Effective project managers diagnose each person on each important task, agree the style openly, and move toward delegating as people grow.

Servant leadership

Robert Greenleaf introduced the term servant leadership in a 1970 essay. His test was whether those served grow as persons: do they become healthier, wiser, freer and more autonomous? In project management, servant leadership has become closely associated with agile teams, where the team facilitator (for example a Scrum Master) is described as a servant leader. PMI's Agile Practice Guide and the PMBOK Guide describe the servant leader as someone who focuses on understanding and addressing the needs and development of team members to enable the highest possible team performance.

Servant leadership is not doing whatever the team asks, and it is not passive. A servant leader still holds standards, protects the vision and makes hard calls. The difference is the direction of service: instead of the team serving the leader's plan, the leader serves the team's ability to deliver value. Practical behaviors include:

• Removing impediments: chasing approvals, resolving tool problems, getting access to people and data.
• Shielding the team: protecting it from constant interruptions and changes in priority that bypass agreed channels such as the product owner or change control.
• Facilitating rather than dictating: running meetings so that the team reaches its own decisions.
• Coaching and developing: helping people build skills and grow into more responsibility.
• Listening first: understanding problems from the team's perspective before proposing solutions.
• Encouraging self-organization: letting the team decide how to do its work and who does what.
• Building a culture of trust, safety and continuous improvement.

Larry Spears, drawing on Greenleaf's writing, listed ten characteristics of servant leaders: listening, empathy, healing, awareness, persuasion, conceptualization, foresight, stewardship, commitment to the growth of people, and building community. You do not need to memorize the list for the exam, but it captures the spirit: servant leaders persuade rather than coerce, think about the long term and take responsibility for the wellbeing of the group.

Choosing and blending styles

Experienced project managers blend styles rather than choosing one forever. They may be directive during a production outage, democratic in a design workshop, transactional when managing a fixed-price supplier and servant-oriented with a mature agile team, all in the same week. The skill lies in reading the signals and switching deliberately, and in explaining the switch: "Normally I'd want everyone's input, but the system is down and customers can't pay, so for the next hour I'm going to make the calls."

Development approach matters too. Predictive projects often place more decision authority with the project manager, and a blend of transactional and transformational leadership is common. Adaptive projects distribute decisions: the product owner decides what to build, the team decides how, and the team facilitator serves both. Hybrid projects require the project manager to shift between these modes, sometimes on different work streams at the same time (PMP-140 covers agile roles in detail).

Organizational culture also shapes what styles people expect. US workplaces generally reward individual initiative and fairly direct communication, but expectations differ across industries, between unionized and non-unionized environments, and across the cultural backgrounds of team members. In unionized settings, the collective bargaining agreement may also define how work is assigned and how performance concerns are handled.

Leadership on the exam

When a PMP question describes a self-organizing or agile team, answers in which the project manager assigns tasks or tells people how to do the work are almost always weaker than answers in which the project manager coaches, facilitates or removes impediments. When a question describes a crisis or safety threat, decisive direction is appropriate. When a question describes a team member who is new to a task, providing direction and training is appropriate; when it describes a capable but unsure person, support and encouragement fit better. Look for clues about competence, commitment, urgency and approach, and choose the style that fits.