Leadership Styles: Adapt Your Style to the Situation

"What is the best leadership style?" is a question wrong in its framing, not in its answer. Style is a dependent variable: it shifts with who you are leading, what the task is, how hard time is pressing, and how the organization works. The practical problem is that most managers own one style, apply it to everyone, and then explain weak results by blaming the team. The Eighth Edition states the rule plainly: leaders should be versatile and able to switch between different leadership styles to achieve a better outcome.

Definition and Foundation

The Eighth Edition holds that there are many leadership styles members of a project management team can adopt, chosen on the basis of five stated factors:

• Individuals — who you are leading, with their experience and motivations.
• Situations — the nature of the current circumstances and their pressures.
• Team structures — how decision-making is distributed inside the team.
• Stakeholders — those outside the team who affect it and are affected by it.
• Organizational processes and culture — what the environment permits and rewards, the factor that bounds the other four.

Among these styles the guide singles out situational leadership as particularly relevant for project management teams. Its essence is flexibility and adaptability in leadership based on the evolving demands of the project. A project management team should adjust its style to suit three things: the specific needs of the team, the time sensitivity of tasks, and the complexity of the project.

The guide gives a concrete example of that switching: shifting from a more directive approach during critical project phases to a supportive style when team autonomy is beneficial. Adapting one's style is crucial for navigating the diverse challenges projects typically present.

Another passage adds the individual test: a project manager should be sensitive to the willingness and ability of team members to perform their work, and should adjust their management and leadership styles to account for these factors as needed. Both variables are personal rather than phase-based: willingness speaks to motivation and commitment, ability to competence and experience. They are measured on a specific task rather than in the abstract, so the same person can sit in a different place from one week to the next depending on what they are assigned.

How It Works in Practice

Servant leadership as a style

The practice of leading the team by focusing on understanding and addressing the needs and development of team members in order to enable the highest possible team performance, performed in service to the project's business or mission objectives. It is named among the tools of Lead the Team, so in the guide it is a technique rather than a philosophy.

Centralized management and leadership

A management structure of top-down leadership and instructions for decision implementation at other levels. Decision-making and authority are centralized within top management and conducted by a small number of senior leaders. Where management activities are centralized, accountability — being answerable for an outcome — is usually assigned to one individual such as the project manager or a similar role. A project charter or other authorizing document can provide approval for the project manager to form a project team to achieve the project outcomes.

Distributed management and leadership

A structure emphasizing teamwork and empowered individuals, where decision-making and authority are decentralized and distributed among various individuals and teams. Project management activities are sometimes shared among a project management team, with members responsible for completing the work. There are also situations where a team may self-organize: rather than a designated project manager, someone within the team may serve as facilitator enabling communication, collaboration, and engagement, and that role may shift among members.

The governing distinction: management and leadership activities

This distinction precedes any choice of style. Management activities focus on the means of meeting project objectives: effective processes, planning, coordinating, measuring, and monitoring work. Leadership activities focus on people: influencing, motivating, listening, enabling, and other activities to do with leading the team. Both matter in delivering the intended outcomes. The common failure is leaning toward whichever half you are good at: a technical background absorbs itself in processes and measurement while neglecting motivation and listening, and a relational one absorbs itself in people while neglecting planning and coordination. Either leaves a gap the project pays for. Note too that the guide says leadership activities should be practiced by all team members, while it is management activities that may be centralized or distributed — leadership is not the preserve of whoever holds a title.

On the Exam

The 2026 ECO makes this an enabler in its own words: Domain I, People — the heaviest domain at 33% — Task 3, lead the project team, carries "determine an appropriate leadership style," alongside establishing expectations at the team level, empowering the team, solving problems, representing the voice of the team, supporting the team's varied experiences, skills, and perspectives, and establishing clear roles and responsibilities.

The dominant pattern is a scenario describing a situation and asking which style fits. Four keys settle most of it:

• A critical phase or a highly time-sensitive task → a more directive approach.
• A capable team that benefits from autonomy → a supportive style.
• A member willing but unable on a specific task → training, mentoring, and coaching to close the skill gap.
• A stem generalizing one style across the whole team → styles are chosen by individuals, situations, team structures, stakeholders, and organizational culture.

What deceives is options presenting one style as always correct — delegation because it "empowers," or direction because it is "disciplined." Both are absolutes contradicting the explicit rule that leaders should be versatile and able to switch. So does an option deriving the style from team maturity alone, while the guide names five factors for choosing and three for adjusting, of which the team is one rather than all.

Detailed Mistakes

Confusing style with structure

Servant leadership is a style a leader chooses. Centralized or distributed management is an organizational structure setting where decisions are made and who is answerable. Declaring a distributed style inside a centralized structure that assigns accountability to one individual creates a contradiction: distributed decisions with concentrated accountability. The team decides while the manager answers for it, so the manager retreats from distribution at the first wrong call and the team loses faith in the empowerment that was announced. A style changes on the manager's decision; a structure changes only on an organizational one. Correct diagnosis begins by asking whether what you face is a style constraint or a structural one.

Tying style to team maturity alone

The guide's test is twofold and individual: willingness and ability. Both vary task by task for the same person: an expert in their field may be low on ability with a new technology, and someone generally enthusiastic may be low on willingness for one particular assignment. Assessing "team maturity" as a single block misses that variance and hands every member the same style on every task. The sharper reading assesses each member on each task along two axes: do they have the ability, and do they have the willingness? That is four situations rather than one, each calling for a different response.

Treating leadership as a title rather than an activity

The guide is explicit: leadership activities should be practiced by all project team members, while management activities may be centralized or distributed. Confining influencing, motivating, and listening to whoever carries the "manager" label disables a source of leadership already inside the team, and makes that one person a transit point for every interaction — an organizational bottleneck that worsens as the team grows.

Where It Does Not Apply

A note for exam preparation: the three widely circulated styles labelled directive, supportive, and delegating as a named model, along with transformational leadership, do not appear as such in the Eighth Edition. What appears in the text is that styles are many, that situational leadership is particularly relevant, and that switching runs from a more directive approach to a supportive style as circumstances require. The styles the guide does name are three: servant leadership, centralized management and leadership, and distributed management and leadership. Anything else appears as description rather than the name of a model. One last constraint holds: style choice is bounded by organizational processes and culture — one of the five stated factors. An organization that measures progress against baselines and manages by direction will not be changed by one manager announcing a supportive style; the switching available is what the structure can carry, not what the leader prefers. Style begins with reading the environment, then the task, then the person — in that order.