Principle 6: Demonstrate Leadership Behaviors

PMBOK 7 Statement: "Demonstrate leadership behaviors that align with the project vision and goals, and that create a shared sense of purpose among the project team and other stakeholders, in order to achieve the desired outcomes."

Leadership is one of the most discussed yet most misunderstood concepts in project management. PMBOK 7 addresses this head-on by making leadership one of its 12 guiding principles — and by broadening its definition far beyond the traditional view of "the project manager as boss." In PMBOK 7, leadership behaviors can and should be demonstrated by anyone involved in the project, regardless of title or position. This principle connects directly to the People domain in the PMP Exam Content Outline, which devotes extensive attention to leading a team, empowering members, and supporting performance.

Leadership vs. Management

One of the foundational distinctions in PMBOK 7 — and one that frequently appears on the PMP exam — is the difference between leadership and management. These are not the same thing, and effective project managers must excel at both.

Dimension	Management	Leadership
Focus	Planning, budgeting, organizing, controlling — maintaining order and consistency	Vision-setting, inspiring, motivating, aligning — driving change and progress
Direction	Executes the plan; works within the system	Sets the vision; works on the system to improve it
Approach to People	Directs, monitors, evaluates performance against targets	Empowers, coaches, develops, builds trust and relationships
Time Horizon	Short-term: today's tasks, this week's milestones, current sprint	Long-term: project vision, career development of team members, organizational impact
Power Source	Formal authority from position or title	Referent and expert power earned through respect and trust
Risk Orientation	Risk-averse; focuses on compliance and predictability	Risk-informed; willing to take calculated risks to achieve vision

PMBOK 7 does not position leadership as superior to management. Both are essential. A project manager who only manages will keep the project on schedule but may fail to inspire the team or navigate change. A project manager who only leads may generate enthusiasm but miss deadlines and budget targets. The PMP exam will test your ability to recognize when a situation calls for management behaviors (e.g., updating the schedule, enforcing a process) versus leadership behaviors (e.g., motivating the team, resolving a values conflict, articulating the vision).

Situational Leadership

PMBOK 7 explicitly recognizes that there is no single "best" leadership style. Effective leaders adapt their approach based on the situation, the team's maturity, the project phase, and the organizational culture. This concept, known as situational leadership, was originally developed by Paul Hersey and Ken Blanchard and is directly referenced in the PMBOK 7 standard.

Situational leadership identifies four primary styles that correspond to the team's readiness level:

Directing (High Directive, Low Supportive)

Used when the team is inexperienced or the task is critical and time-sensitive. The leader provides clear instructions, defines roles precisely, and closely supervises execution. This is appropriate during project initiation with a new team, during a crisis, or when onboarding new members. However, staying in this style too long stifles growth and autonomy.

Coaching (High Directive, High Supportive)

The leader still provides direction but also explains the "why" behind decisions, seeks input, and encourages development. This style works well when the team has some competence but lacks confidence or commitment. The leader explains the reasoning, solicits questions, and builds the team's capability while maintaining guidance.

Supporting (Low Directive, High Supportive)

The team has the skills but may lack confidence or motivation. The leader shifts to a facilitative role — listening, praising, encouraging, and involving the team in decision-making. The leader does not tell the team what to do but helps them find their own solutions. This is the dominant style in mature agile teams where the Scrum Master serves as a servant leader.

Delegating (Low Directive, Low Supportive)

The team is both competent and committed. The leader delegates responsibility and trusts the team to execute. The leader's role shifts to monitoring from a distance and providing support only when requested. This style is appropriate for senior, high-performing teams and for team members who have demonstrated reliable judgment.

Emotional Intelligence and Leadership

PMBOK 7 explicitly ties leadership to emotional intelligence (EQ), which Daniel Goleman popularized as the ability to recognize, understand, and manage one's own emotions and the emotions of others. The PMBOK 7 standard identifies emotional intelligence as a critical leadership competency, and the PMP ECO includes it as an enabler under multiple tasks.

The four components of emotional intelligence in the context of project leadership are:

Self-Awareness

The ability to recognize your own emotions, triggers, strengths, and weaknesses. A self-aware project manager knows when they are becoming frustrated, anxious, or impatient — and manages those emotions rather than projecting them onto the team. Self-awareness also means seeking honest feedback and being open to personal development. Without self-awareness, all other leadership competencies are compromised.

Self-Management

The ability to regulate your emotions and adapt to changing circumstances. A project manager who can stay calm during a crisis, maintain composure during a difficult stakeholder meeting, and pivot gracefully when a plan fails models the behavior they want to see in the team. Self-management also includes transparency — admitting mistakes and modeling accountability.

Social Awareness (Empathy)

The ability to understand others' perspectives, emotions, and concerns. Empathy is essential for stakeholder engagement, conflict resolution, and team building. A project manager with strong social awareness can detect when a team member is burning out, when a stakeholder is not expressing their true concern, or when the team culture is shifting. Empathy does not mean agreeing with everyone — it means understanding where they are coming from so you can respond appropriately.

Relationship Management

The ability to build rapport, influence others, resolve conflicts, and inspire collaboration. This is the most visible leadership competency. It includes communication, negotiation, conflict resolution, and the ability to create an environment where people feel valued and motivated. Relationship management is the outward expression of the other three EQ components.

EQ Component	What It Looks Like in a PM	PMP ECO Task Connection
Self-Awareness	Recognizes personal bias in decision-making; seeks feedback from team	Task 4: Empower Team; Task 14: Use Emotional Intelligence
Self-Management	Stays calm under pressure; adapts approach when plans fail	Task 2: Lead a Team; Task 15: Lead a Project in a Virtual Environment
Social Awareness	Detects stakeholder concerns beneath the surface; reads team morale	Task 9: Collaborate with Stakeholders; Task 18: Engage Stakeholders
Relationship Management	Builds trust; resolves conflict constructively; inspires commitment	Task 1: Manage Conflict; Task 10: Build Shared Understanding

Leadership at All Levels

One of the most important shifts in PMBOK 7 is the recognition that leadership is not limited to the project manager. Anyone on the project can — and should — demonstrate leadership behaviors. A team member who speaks up about a risk, a technical lead who mentors a junior developer, a stakeholder who champions the project's value to their organization — these are all acts of leadership.

PMBOK 7 encourages project managers to create an environment where leadership at all levels can flourish. This means:

• Empowering team members to make decisions within their area of expertise
• Encouraging initiative by rewarding proactive behavior rather than punishing mistakes
• Delegating meaningful authority, not just tasks — give team members ownership of outcomes
• Providing visibility and recognition for leadership contributions from all levels
• Creating psychological safety so people feel comfortable taking interpersonal risks

This approach is especially important in agile environments, where the Scrum Master is explicitly not a traditional manager but a servant leader who enables the team's self-organization. However, even in predictive environments, PMBOK 7 advocates for a leadership culture where direction emerges from expertise and collaboration rather than from hierarchy alone.

Servant Leadership

Servant leadership is a philosophy that PMBOK 7 explicitly endorses, particularly in agile and adaptive contexts. Coined by Robert K. Greenleaf, servant leadership flips the traditional power hierarchy: the leader's primary role is to serve the team, removing impediments, providing resources, and creating conditions for success. The servant leader asks, "What do you need to succeed?" rather than "Why haven't you done this yet?"

Key servant leadership behaviors include:

• Listening actively — Understanding team concerns before proposing solutions
• Removing impediments — Clearing organizational, technical, and interpersonal roadblocks
• Building community — Creating a sense of belonging and shared purpose
• Developing people — Prioritizing team growth over personal recognition
• Practicing stewardship — Taking responsibility for the team's and organization's well-being

Developing Leadership Competencies for the PMP Exam

The PMP Exam Content Outline's People domain — which accounts for 42% of exam questions — is essentially a leadership competency framework. Tasks such as "Lead a team" (Task 2), "Support team performance" (Task 3), "Empower team members" (Task 4), "Ensure team members are adequately trained" (Task 5), "Build a team" (Task 6), and "Address and remove impediments" (Task 7) all require robust leadership skills.

To prepare for leadership questions on the PMP exam, focus on understanding the PMI mindset: the project manager is a facilitator, coach, and enabler, not a commander. Answers that demonstrate servant leadership, emotional intelligence, situational adaptation, and empowerment are consistently preferred. Practice questions that force you to choose between a directive approach and a collaborative approach — PMI almost always prefers collaboration.

← Previous: Principle 5 — Systems Thinking  |  Back to PMBOK 7 Principles  |  Next: Principle 7 — Tailoring →