Leadership, Team Performance & Closing

The People domain is the largest on the PMP exam at ~42% of questions. It tests how you lead teams, resolve conflicts, motivate individuals, and bring projects to a proper close — skills no formula can fully capture.

PMI's #1 Leadership Style: Servant Leadership — the PM's job is to serve the team, not command it. Remove obstacles, empower team members, build trust, and prioritize the team's needs. This is the correct answer for most "how should the PM lead?" scenarios, especially on agile projects.

👑 Leadership

How PMs influence and inspire teams without relying on positional authority. The PMP tests situational leadership — knowing which style fits the team's maturity and the situation's urgency.

🔥 Team Performance

Teams don't instantly gel — they progress through predictable development stages. Understanding Tuckman's model, motivation theories, and team dynamics helps PMs accelerate performance.

🏁 Project Closing

Closing is a formal process, not just wrapping up. All deliverables must be accepted, resources released, contracts closed, lessons documented, and final reports produced — in the right order.

📊 PMP People Domain — What Gets Tested

Topic Cluster	Key Concepts	Exam Weight
Leadership styles & emotional intelligence	Servant, transformational, situational, EI, political awareness	High
Team development	Tuckman's 5 stages, virtual teams, ground rules, team charter	High
Motivation theories	Maslow, Herzberg, McGregor X/Y, McClelland, Vroom expectancy	Medium-High
Conflict management	5 techniques, root causes, when to use each, escalation	High
Power and influence	6 power types, Expert + Referent preferred, legitimate = weakest for PM	Medium
Project closing	Formal acceptance, lessons learned, resource release, contract closure	Medium

🧠 Emotional Intelligence (EI)

Goleman's 5 components: Self-Awareness (know your emotions), Self-Regulation (control your reactions), Motivation (internal drive), Empathy (understand others), Social Skills (build relationships).

High EI = better conflict management, stakeholder engagement, and team trust. PMI treats EI as a core PM competency — expect scenario questions where the EI-driven answer wins.

📋 Team Charter

A team charter documents the team's shared values, agreements, operating guidelines, and ground rules. Created collaboratively at project start — increases team buy-in and reduces future conflict.

A team charter is distinct from the Project Charter. The Project Charter authorizes the project; the Team Charter governs how the team will work together.

Leadership Styles & Power Types

Leadership style should match the situation and the team's maturity. Power type determines HOW a PM influences outcomes — the source matters as much as the authority itself.

Key Leadership Styles

Servant Leadership

"Serve first, lead second"

Prioritizes team needs over the leader's own agenda. Removes impediments, empowers team, facilitates rather than directs.

✓ PMI Preferred — Agile & Hybrid

Transformational

"Inspire through vision"

Motivates through a compelling vision of the future. Challenges the team to innovate and exceed expectations.

✓ Strong for change & innovation

Transactional

"Reward for results"

Manages through reward and penalty systems. Clear expectations with defined consequences. Works for structured, routine work.

⚠ Effective but compliance-driven

Situational

"Match style to context"

Flexibly adjusts style based on team member's competence and commitment. Hersey & Blanchard model — Directing, Coaching, Supporting, Delegating.

✓ Flexible and context-driven

Democratic / Participative

"Team decides together"

Invites team input and buy-in before deciding. Builds morale but slower for urgent decisions. Best for experienced, engaged teams.

⚠ Slower — use when time permits

Autocratic / Directive

"PM decides, team executes"

PM makes all decisions without input. Can be appropriate in true emergencies or safety-critical moments — but kills morale if overused.

⚠ Last resort — emergency only

Laissez-Faire

"Hands off, you decide"

PM provides minimal direction. Appropriate for highly experienced, self-managing expert teams. Risky with inexperienced teams.

⚠ Only for mature expert teams

Charismatic

"Inspire through personality"

Relies on personal energy and charm to motivate. Can be powerful for galvanizing teams during uncertainty — but outcomes depend heavily on one individual.

⚠ Personality-dependent

The 6 Power Types — Ranked Best to Worst for PMs

Personal Power

Expert Power

Influence through knowledge, technical skill, and subject-matter credibility. Team follows because you know what you're doing.

★ BEST — earned, lasting

Personal Power

Referent Power

Influence through trust, respect, charisma, and personal relationship. People follow because they like and admire you.

★ BEST — most lasting of all

Formal / Positional

Legitimate Power

Authority granted by formal role or title. Valid but limited — people comply, not necessarily commit.

✓ Reliable but shallow

Formal / Positional

Reward Power

Ability to grant bonuses, promotions, recognition, and benefits. Effective but diminishes when rewards run out.

✓ Useful, limited by budget

Informational

Informational Power

Control over access to important data or knowledge. Relevant in high-stakes decision environments.

✓ Situational

Formal / Positional

Penalty / Coercive Power

Ability to punish, demote, or threaten. Creates compliance through fear — breeds resentment and reduces engagement.

✗ WORST — fear-based, avoid

PMP Exam Rule: Expert and Referent power are the BEST because they are earned rather than assigned. Penalty/Coercive power is the WORST — the exam will always prefer an option that builds trust over one that uses threats. Legitimate power (title/role) is necessary but insufficient for effective PM leadership.

Team Development — Tuckman's Model

All teams progress through predictable stages before reaching peak performance. The PM's role changes at each stage — knowing when to direct vs. coach vs. empower is heavily tested.

Tuckman's 5 Stages of Team Development

Stage 1

Forming

Polite, excited, but roles unclear. High dependency on leader.

PM: Direct and guide. Clarify goals, roles, and expectations.

Stage 2

Storming

Conflicts emerge. Personalities clash. Work styles collide.

PM: Coach and facilitate. Resolve conflicts, establish norms.

Stage 3

Norming

Consensus emerges. Team norms and processes established.

PM: Support collaboration. Enable the team's growing cohesion.

Stage 4

Performing

High trust, interdependence, and productivity. Self-directed.

PM: Delegate and empower. Remove impediments, celebrate wins.

Stage 5

Adjourning

Project ends. Team disbands. Can trigger loss or grief.

PM: Recognize contributions. Transition team. Close lessons learned.

Key Exam Rule: When a new team member joins a performing team, the WHOLE team often regresses back to Forming. The team must re-establish roles and norms with the new member. This is why team composition changes are disruptive even to high-performing teams.

🌍 Virtual Teams — Special Considerations

Virtual teams face extra challenges: time zones, cultural differences, communication gaps, and loss of informal interaction. They require more deliberate communication planning and explicit team norms.

PMP tips: Establish communication protocols early. Schedule overlap hours. Use video calls for complex discussions — text removes tone and nuance. Build social connection intentionally.

📋 Ground Rules & Team Charter

Ground Rules: Explicit behavioral expectations for the team — how meetings are run, response time expectations, how decisions are made. Reduces conflict by making norms visible.

Team Assessment Tools: Used to evaluate team effectiveness, identify development areas, and track improvement over time. Results inform training and coaching plans.

📈 Team Performance Assessment — What to Measure

Dimension	What to Look For	PM Response if Lacking
Technical skills	Can team members execute their assigned work?	Provide training, pair with expert, or get additional resources
Interpersonal dynamics	Are team members collaborating effectively?	Team-building activities, conflict coaching, ground rules
Motivation & engagement	Are team members committed and energized?	Apply appropriate motivators (recognition, growth, autonomy)
Delivery velocity	Is the team meeting commitments consistently?	Remove impediments, re-estimate, adjust staffing
Psychological safety	Do team members feel safe raising issues?	Model vulnerability, reward honest communication, no blame culture

Motivation Theories

Five major motivation theories appear on the PMP exam. Know them by name, their key distinctions, and the specific vocabulary each theory uses — the exam tests terminology precisely.

Maslow's Hierarchy of Needs

1 · Physiological — food, shelter, pay

2 · Safety — job security, safe environment

3 · Social / Belonging — teamwork, relationships

4 · Esteem — recognition, status, achievement

5 · Self-Actualization — growth, purpose, mastery

Exam Key Points

Lower needs must be satisfied BEFORE higher needs motivate. A person worried about job security (Level 2) is not motivated by recognition (Level 4).

Self-Actualization (Level 5) is the highest motivator — people seek growth and purpose when all other needs are met.

The PMP exam tests which need level applies to a given scenario — match the scenario to the correct tier.

Herzberg's Two-Factor Theory

Hygiene Factors

PREVENT Dissatisfaction — do NOT create satisfaction

Salary & compensation
Job security
Working conditions
Company policies & rules
Quality of supervision
Relationships with coworkers

Motivators

CREATE Satisfaction and drive true motivation

Achievement & accomplishment
Recognition for work done
The work itself (interesting tasks)
Responsibility & ownership
Advancement & promotion
Personal growth & learning

Critical Distinction: Improving hygiene factors (raising salary, better office) removes dissatisfaction but does NOT motivate. Only motivators (recognition, growth, achievement) drive higher performance. This is the most commonly tested Herzberg concept on the PMP exam.

McGregor's Theory X & Theory Y

Theory X

"People are lazy and must be controlled"

Employees inherently dislike work
Must be supervised closely
Motivated by threats and penalties
Avoid responsibility if possible
Management style: directive, top-down
Consistent with Autocratic leadership

Theory Y

"People are self-motivated and seek growth"

Work is as natural as play or rest
Self-directed when committed to goals
Motivated by achievement and growth
Seek responsibility and ownership
Management style: empower, delegate
Consistent with Servant Leadership

🏆 McClelland's 3 Needs Theory

Need for Achievement (nAch): Sets challenging goals, prefers personal responsibility, seeks feedback, takes moderate risks. Goal-driven, task-focused.

Need for Affiliation (nAff): Values harmonious relationships and belonging. Avoids conflict, wants to be liked. Collaborative but conflict-avoidant.

Need for Power (nPow): Seeks to influence and control others. Can be personal power (self-serving) or institutional power (organization-serving).

Exam tip: High nAch = best individual performers. High nPow (institutional) = strong managers. High nAff = great team players but poor at tough decisions.

⚙️ Vroom's Expectancy Theory

Formula: Motivation = Expectancy × Instrumentality × Valence

Expectancy: "Can I do this task?" — belief that effort will lead to performance. Low if skills are insufficient or resources are unavailable.

Instrumentality: "Will doing this lead to the reward?" — belief that performance leads to the promised outcome. Low if rewards are inconsistent or unpredictable.

Valence: "Do I actually value this reward?" — individual's emotional attachment to the outcome. Zero valence = zero motivation regardless of other factors.

If ANY factor is zero, motivation = zero. All three must be present.

Conflict Resolution & Project Closing

Conflict is natural and not always negative — managed well, it surfaces better solutions. Project closing is a formal process that must be completed in full even when a project is cancelled early.

5 Conflict Resolution Techniques — Best to Worst

1

Collaborating / Problem-Solving

Also called: Confronting, Integrating

All parties openly address the conflict to find a mutually acceptable solution. Requires trust and time. Addresses root causes. Most durable resolution.
Win-Win — best long-term outcome
2

Compromising / Reconciling

Also called: Give and Take

Both parties give up something to reach a middle ground. Faster than collaborating. Appropriate when time is limited or a temporary solution is needed.
Lose-Lose — partial satisfaction
3

Smoothing / Accommodating

Also called: Calming

Emphasizes areas of agreement, downplays differences. Maintains harmony and relationships but does not resolve the underlying issue. Temporary relief only.
Surface harmony — issue persists
4

Forcing / Directing

Also called: Competing

One party's view is imposed on the other. Fast and decisive — appropriate for safety-critical or urgent situations. Creates winners and losers; breeds resentment.
Win-Lose — fast, leaves resentment
5

Withdrawal / Avoiding

Also called: Retreating

Postpones or sidesteps the conflict entirely. No resolution occurs — the problem persists and often worsens. Appropriate only if conflict is truly trivial or needs cooling time.
Lose-Lose — worst, conflict remains

Exam Rule for Conflict: The PMP exam almost always selects Collaborating/Problem-Solving as the correct answer. When you see a conflict scenario, first check if collaborating is an option. Forcing is appropriate ONLY when safety or ethics are at stake and immediate action is needed. Avoiding is almost never the right answer.

Project Closing — Required Steps in Order

Step 1

Verify & Accept Deliverables

Obtain formal, documented acceptance of ALL project deliverables from the customer/sponsor. No acceptance = project not complete.

Step 2

Close Procurements

Confirm all vendor contracts are fulfilled. Process final payments. Issue formal procurement closure. Resolve any open claims.

Step 3

Document Lessons Learned

Capture what went well, what didn't, and recommendations for future projects. Store in the OPA lessons learned repository.

Step 4

Release Project Resources

Formally release team members to their functional managers or next assignments. Release equipment, facilities, and budget.

Step 5

Archive Project Documents

Store all project records, plans, reports, and contracts in the organizational archive. These become OPAs for future projects.

Step 6

Final Project Report & Administrative Closure

Produce the final report summarizing performance vs. baselines. Complete all administrative closure activities and communicate final status.

⚠️ Early Project Termination

Even when a project is cancelled early (business case invalidated, budget cut, change in strategy), closing processes MUST still be performed. Deliverables must be transferred or disposed of, resources released, contracts closed, and lessons documented.

Exam trap: "The project was cancelled so we can skip closing." Wrong. Closing is always required — even for failed or terminated projects.

📋 Phase Closing vs. Project Closing

Closing processes apply to each phase of the project, not just the final phase. At the end of each phase: verify deliverables, update lessons learned, archive phase documents, and get formal phase approval before proceeding to the next phase.

This is why closing is not a one-time event — it is a recurring discipline throughout the project lifecycle.

🤝 Common Conflict Sources on Projects (Top 7)

Conflict Source	Why It Occurs	Best Resolution Approach
Schedules	Unrealistic deadlines, dependency conflicts	Collaborating with team and stakeholders to re-plan
Priorities	Competing demands on shared resources	Escalate to sponsor if PM cannot resolve; otherwise collaborate
Resources	Insufficient staffing, skill gaps, shared allocation	Collaborate with resource managers; negotiate allocation
Technical approach	Disagreements on HOW to build or solve	Collaborating; involve technical lead; prototype to validate
Administrative procedures	Disagreement on PM processes, reporting, governance	Reference project management plan; clarify norms
Costs	Budget constraints, estimation differences	Data-driven analysis; escalate if approval authority required
Personality	Interpersonal friction, communication style differences	Direct conversation; coaching; team norms reinforcement

Practice Quiz — Leadership, Team Performance & Closing

10 PMP-style scenario questions. Select your answer to see instant feedback and explanation.

Question 1 of 10

Which leadership style is PMI's preferred approach for agile and hybrid project environments?

AAutocratic — the PM makes all decisions to maintain control

BTransactional — rewards for performance, penalties for failure

CServant Leadership — the PM serves the team's needs and removes impediments

DLaissez-Faire — the team operates completely autonomously

Correct. PMI strongly endorses Servant Leadership — the PM's role is to serve the team, remove obstacles, empower individuals, and facilitate rather than direct. This aligns with agile's self-organizing team principle and the Scrum Master's servant-leader role.

Question 2 of 10

A high-performing Scrum team has been working together effectively for 6 months. A new developer joins the team mid-project. In which Tuckman stage does the ENTIRE team most likely return to first?

ANorming — they quickly re-establish norms with the new member

BStorming — the new member immediately triggers conflict

CForming — the team composition change resets the group dynamic

DPerforming — the team is mature enough to absorb new members

Correct. When any team member changes, the team typically regresses to Forming. Roles, norms, and trust must be re-established with the new composition. Even a highly performing team must re-form before it can return to peak performance. This is a classic PMP exam trap.

Question 3 of 10

Two team members disagree about the technical approach for a critical module. The PM listens to both perspectives, then makes the final decision unilaterally. Which conflict resolution technique is the PM using?

ACollaborating — the PM engaged both parties

BForcing / Directing — the PM imposed a decision

CCompromising — both parties gave something up

DSmoothing — the PM minimized the conflict

Correct. Forcing/Directing means one party's view is imposed on others — even if the PM listened first. The key indicator is that the PM made the final decision unilaterally rather than reaching a consensus with both parties. Collaborating would result in a jointly owned solution.

Question 4 of 10

According to Herzberg's Two-Factor Theory, which of the following is a TRUE MOTIVATOR that drives higher performance and satisfaction?

ACompetitive salary and annual bonus

BSafe and clean working environment

CRecognition for a specific achievement

DJob security and stable employment contract

Correct. Recognition for achievement is a Motivator — it creates genuine satisfaction and drives higher performance. Salary, safe environment, and job security are all Hygiene Factors — they prevent dissatisfaction but do NOT motivate. Improving hygiene only reduces negative feelings; only motivators increase positive engagement.

Question 5 of 10

A project manager believes their experienced team is self-motivated, seeks responsibility, and will perform well with autonomy. This assumption best aligns with which theory?

AMcGregor's Theory X — employees avoid work and need control

BMcGregor's Theory Y — employees are self-motivated and seek responsibility

CMcClelland's Need for Power — team members are competing for influence

DMaslow's Safety Need — team members are motivated by job security

Correct. McGregor's Theory Y assumes employees are inherently motivated, enjoy their work, seek responsibility, and can self-direct when committed to goals. This PM's assumption directly mirrors Theory Y. Theory X would describe a belief that employees are lazy and need close supervision.

Question 6 of 10

Which type of power is considered MOST LASTING for a project manager and comes from personal trust and respect rather than formal authority?

ALegitimate — authority granted by the PM's job title

BReward — ability to give bonuses and recognition

CReferent — influence through personal trust, admiration, and likability

DPenalty — ability to discipline and punish team members

Correct. Referent power is earned through personal trust, respect, and relationships — it persists even when a PM changes roles or loses positional authority. Expert power is also highly regarded. Penalty power is the weakest approach. Legitimate power is positional — it ends when the role ends.

Question 7 of 10

A project is in its final week when the customer informs the PM that one deliverable has not yet received formal acceptance. What should the PM do?

AArchive all documents and release the team — closing is already overdue

BNote the gap in the final project report and proceed with closure

CWork with the customer to resolve any issues and obtain formal acceptance before closing

DTransfer the unaccepted deliverable to operations for post-project resolution

Correct. Formal acceptance of all deliverables is a prerequisite for project closing. The PM must work to obtain that acceptance — resolving any gaps, defects, or misunderstandings — before the project can be formally closed. Closing before acceptance creates legal and contractual risk.

Question 8 of 10

A project team is in the Storming stage with increasing interpersonal conflicts and missed commitments. What is the PM's BEST action?

ADo nothing — Storming resolves itself naturally over time

BImmediately replace the team members causing the most disruption

CFacilitate conflict resolution, establish clear team norms, and coach the team through the stage

DEscalate all conflicts to the project sponsor for resolution

Correct. During Storming, the PM's role is to coach and facilitate — resolve conflicts constructively, establish or reinforce team norms, and help the team build trust. Avoiding the conflict (A) prolongs it. Replacing team members (B) resets the team to Forming. Escalating to the sponsor (D) is disproportionate for normal team conflict.

Question 9 of 10

According to McClelland's Needs Theory, an employee who consistently sets stretch goals, prefers individual feedback, and seeks personal accountability is MOST driven by which need?

ANeed for Affiliation — they want strong team relationships

BNeed for Power — they want to influence others

CNeed for Achievement — they set challenging goals and own their results

DNeed for Security — they want stable, low-risk assignments

Correct. McClelland's Need for Achievement (nAch) describes individuals who set challenging goals, prefer personal responsibility over group credit, want direct feedback on performance, and take moderate calculated risks. These are high-nAch behaviors. Need for Affiliation is about relationships; Need for Power is about influencing others.

Question 10 of 10

A project has been cancelled due to budget cuts before completion. What should the project manager do FIRST?

AImmediately release all project resources to their functional managers

BArchive project documents and skip formal closing since the project failed

CSkip closing processes — only successful projects require formal closure

DPerform project closing — document lessons learned, handle deliverables disposition, close contracts, and release resources formally

Correct. Project closing is mandatory even when a project is cancelled early. The PM must: document what was accomplished, capture lessons learned, properly handle or transfer any completed deliverables, formally close all vendor contracts, and release resources following proper procedures. Skipping closing creates legal, financial, and organizational risks.

0/10

Practice Quiz Score

Review explanations above for any missed questions.

Memory Hooks & AI Advisor

Lock in the highest-tested People domain concepts with mnemonics and visual anchors. Use the Advisor for focused exam guidance.

🏃

Tuckman's Stages — FSNPA

Forming → Storming → Norming → Performing → Adjourning. PM role shifts: Direct → Coach → Support → Delegate → Celebrate & Close.

"Finally Stormy Nights Produce Amazing results"

⚔️

Conflict Techniques — CCSFWA

Best to Worst: Collaborating → Compromising → Smoothing → Forcing → Withdrawal/Avoiding. Collaborating = always the first PMP answer to check.

"Cool Cats Smoothly Force Weak Arguments away"

🏔️

Maslow — Bottom to Top

Physical → Safety → Social → Esteem → Self-Actualization. Lower needs must be met first. Job security concern (Level 2) blocks motivation from recognition (Level 4).

"Please Stay Safe Enough to Shine" — P, S, S, E, Self-A

🔬

Herzberg Two-Factor Rule

Hygiene PREVENTS dissatisfaction (salary, safety, job security). Motivators CREATE satisfaction (achievement, recognition, growth). Improving hygiene never motivates — it just removes the negative.

"Hygiene cleans; Motivators energize"

⚖️

McGregor X vs Y

X = eXtra control needed. Employees are lazy, avoid work, need close supervision. Y = trust and empower. Employees are self-motivated, seek responsibility.

"X = eXtra watching. Y = Yes, you can do it."

⚡

Best & Worst Power Types

Best: Expert (knowledge) + Referent (trust) — earned, lasting. Worst: Penalty/Coercive — fear-based, destroys morale. Legitimate (title) is necessary but insufficient.

"Expert Referees win respect; Penalty losers breed resentment"

🏁

Project Closing Sequence

In order: Verify deliverables accepted → Close contracts → Lessons learned → Release resources → Archive documents → Final report.

"Very Careful Leaders Release All Files"

💡

Servant Leadership Behaviors

Remove impediments. Empower the team. Coach rather than command. Prioritize team needs. Build psychological safety. Trust people to self-organize. Focus on enabling, not directing.

"Serve first, lead second — the team does the work"

Flashcards

Click each card to flip and reveal the answer.

Tuckman's Model

What are the 5 Tuckman stages in order and what triggers regression?

Click to flip

Answer

Forming → Storming → Norming → Performing → Adjourning. Any change in team composition (new member leaving or joining) typically triggers regression to Forming

Conflict Resolution

Which conflict technique is BEST and which is WORST on the PMP exam?

Click to flip

Answer

Best: Collaborating/Problem-Solving (win-win, addresses root cause). Worst: Withdrawal/Avoiding (problem persists). Forcing acceptable ONLY for safety/ethics emergencies

Herzberg

What is the key difference between Hygiene Factors and Motivators?

Click to flip

Answer

Hygiene factors (salary, security, conditions) PREVENT dissatisfaction — they do NOT motivate. Motivators (achievement, recognition, growth) CREATE satisfaction and drive performance

Power Types

Which 2 power types are considered BEST for PMs and why?

Click to flip

Answer

Expert (knowledge-based) and Referent (trust/relationship-based) are best — both are earned, not assigned, and persist beyond a formal role. Penalty power is worst

McGregor

What are the core assumptions of Theory X vs Theory Y?

Click to flip

Answer

Theory X: employees dislike work, need close control, avoid responsibility. Theory Y: employees are self-motivated, seek responsibility, and can self-direct when committed

Project Closing

What must happen BEFORE a project can be formally closed?

Click to flip

Answer

Formal, documented acceptance of ALL deliverables from the customer/sponsor. Closing is also required for cancelled projects — skipping it creates legal and financial risk

Maslow

A team member is worried about layoffs. What Maslow level are they at, and what motivates them NOW?

Click to flip

Answer

Level 2 — Safety Need (job security). They cannot be motivated by recognition (Level 4) or growth (Level 5) until the safety concern is addressed first. Lower needs block higher ones

Vroom's Expectancy

What is the Expectancy Theory formula and what happens if one factor is zero?

Click to flip

Answer

Motivation = Expectancy × Instrumentality × Valence. If ANY factor is zero, total motivation = zero. All three must be present: "Can I do it?", "Will I be rewarded?", "Do I care about the reward?"

AI Advisor

Select a category for focused exam guidance.

Leadership Styles & Power

Team Development

Motivation Theories

Conflict Resolution

Project Closing

Leadership Styles & Power

Servant Leadership is PMI's default: When a scenario asks what a PM should do to support the team, Servant Leadership behaviors (remove obstacles, empower, facilitate) are almost always the correct answer.
Transformational vs. Transactional: Transformational inspires through vision (innovation, change). Transactional manages through carrots and sticks (task-oriented work). Both are valid but transactional alone limits engagement.
Autocratic is almost never correct: Except in genuine emergencies (safety, ethical breach, imminent project failure) where immediate action is needed. The exam rewards collaboration over command.
Expert + Referent = best powers: Both are earned through behavior, not assigned. They persist after the project ends. Legitimate power (title) is necessary but weak — it ends when the role ends.
Penalty/Coercive is always wrong: Fear-based power creates compliance but destroys engagement, psychological safety, and team trust. Avoid it as a PM approach.
Situational leadership: Match your style to the team member's development level. New team members need more direction (Forming/Storming); experienced self-starters need delegation (Performing).
EI is a core PM competency: Emotional Intelligence — especially Empathy and Self-Regulation — is tested in scenarios involving difficult stakeholders, team conflict, and high-pressure decisions.

Team Development

Know all 5 stages AND their PM actions: Forming = direct/guide. Storming = coach/facilitate. Norming = support. Performing = delegate/empower. Adjourning = celebrate/close.
New member = back to Forming: This is the most commonly tested Tuckman exam trap. Any change in team composition typically triggers regression — even for high-performing teams.
Storming is not failure: Conflict in the Storming stage is normal and healthy — it surfaces different perspectives. The PM's job is to help the team work through it constructively, not suppress it.
Team Charter reduces Storming: Co-creating a Team Charter at project start — covering values, ground rules, communication norms — shortens the Storming phase by making expectations explicit.
Virtual teams need extra structure: Without informal interaction, virtual teams lose the natural relationship-building that accelerates Norming. Deliberate team-building and structured communication fill this gap.
Psychological safety enables performance: Teams that feel safe to raise issues, admit mistakes, and disagree constructively outperform those managed by fear or silence.
Adjourning = both closing and emotional transition: Team members may experience grief, loss, or anxiety when high-performing teams disband. Recognize contributions and provide transition support.

Motivation Theories

Maslow — lower needs block higher needs: If a team member is worried about job security (Level 2), recognition (Level 4) won't motivate them. Address the blocking need first.
Herzberg's hygiene trap: Salary raises NEVER motivate — they only remove dissatisfaction. The PMP will test this with "why isn't the team motivated after getting raises?" Answer: raises are hygiene, not motivators.
McGregor Theory Y = PMI preferred: Assuming people are self-motivated (Theory Y) aligns with servant leadership, agile self-organizing teams, and empowerment culture. Theory X (control-heavy) is misaligned with modern project management.
McClelland's high-nAch profile: Sets stretch goals, wants personal feedback, takes moderate risks, prefers personal responsibility over shared credit. High-achievers can be demotivated by trivial or group-only assignments.
Vroom's zero factor problem: If a team member doesn't believe they can do the task (low Expectancy), doesn't trust rewards will follow performance (low Instrumentality), or doesn't value the reward (zero Valence) — motivation collapses. Fix the specific broken link.
Theory Z (Ouchi): Sometimes tested — blends Japanese collective management with American individual autonomy. Focuses on long-term employment, consensus decision-making, and holistic employee care.

Conflict Resolution

Collaborating is almost always the correct first answer: When conflict appears in a PMP scenario, scan for the option that involves open discussion and a mutually acceptable solution. That's your answer.
Compromising ≠ Collaborating: Compromising means both parties give something up (lose-lose). Collaborating finds a solution where both parties' needs are genuinely met (win-win). They are different techniques.
Smoothing is temporary: It makes things feel better without resolving anything. The exam will present a scenario where the PM smoothed a conflict earlier and it reappears — indicating the wrong technique was used.
Forcing is NOT always wrong: It IS appropriate for safety violations, ethical breaches, or genuine emergencies. But it must be the exception, not the routine. Overuse destroys trust.
Avoiding = almost always wrong: Withdrawal buys time at best and allows the conflict to grow. If an exam option says "the PM decided not to address the conflict," that is almost never correct.
Top conflict sources on projects: In order: Schedules (most common), Priorities, Resources, Technical approach, Administrative procedures, Costs, Personality. Scheduling conflicts top the list — know this for exam scenarios.
Conflict escalation path: PM attempts to resolve → PM facilitates discussion between parties → Escalate to functional manager → Escalate to sponsor → Formal governance body. Always try lower levels first.

Project Closing

Closing applies to phases AND projects: The close phase/project process runs at the end of every project phase, not just the final one. Phase gates require formal closure before the next phase begins.
Formal acceptance before everything else: The first step in closing is always obtaining documented customer/sponsor acceptance of all deliverables. Everything else follows from this.
Cancelled projects still require closing: Budget cuts, strategic pivots, or external events may terminate a project early — but closing is still required. Document lessons, close contracts, release resources, archive records.
Lessons learned = OPA for future projects: Lessons learned are stored in the organizational process assets repository and become inputs for future project planning. They are one of the most valuable outputs of closing.
Close procurements before releasing resources: Vendor contracts must be formally closed (final payment, acceptance of deliverables, claim resolution) before the PM can release resources and archive documents.
Final project report captures performance vs. baselines: Documents actual vs. planned schedule, cost, scope, quality, risk outcomes. It is a historical record and performance audit — not just a summary.
Celebrate the team: Recognition of team contributions during adjourning is a genuine best practice — not just nice-to-have. It supports team morale, strengthens organizational culture, and reinforces high-performance behaviors for future projects.

Complete the Full PMP Series on FlashGenius

You've covered all 5 PMP topics. Reinforce everything with full-length timed practice exams — scored and mapped to all three PMP exam domains.

Unlock Full Practice Tests on FlashGenius →