Study guide
11.2 Changing Leadership Styles for the Situation
APM Project Management Qualification PMQ
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Exam Format & Question Types 1.3 How to Study for APM PMQ
2 Life Cycles
2.1 Linear Life Cycles and Why Work Is Phased 2.2 Iterative and Hybrid Life Cycles 2.3 Project Life Cycles and Extended Life Cycles 2.4 Choosing a Life Cycle: Context, Culture, Strengths and Limitations
3 Governance Arrangements
3.1 Functional, Matrix and Projectised Structures 3.2 Governance Frameworks, Policies and Delegated Responsibility 3.3 Life-Cycle Impact on Governance and Limits of Financial Authority 3.4 Project Roles and Responsibilities 3.5 Project Manager and Project Sponsor Through the Life Cycle 3.6 Linking Projects to Organisational Objectives
4 Sustainability
4.1 Sustainability Responsibilities, Principles and Impact 4.2 Monitoring and Reporting Sustainability Measures
5 Business Case
5.1 Business Case Fundamentals and Analysis Tools 5.2 The Business Case as Baseline and Reviewing Change
6 Procurement
6.1 Procurement Strategy: Purpose and Contents 6.2 Supplier Selection and Negotiation 6.3 Features of Different Contractual Relationships 6.4 Supplier Reimbursement Methods
7 Reviews & Assurance
7.1 Reviews, Decision Gates, Benefits Reviews and Audits 7.2 What Gets Reported and Informing Decisions 7.3 Why Activities Are Re-Planned After a Review 7.4 Project Assurance
8 Transition & Benefits Management
8.1 Transition Requirements and Business-as-Usual Readiness 8.2 Knowledge Transfer and Agreeing the Transition Plan 8.3 Benefits Management: Identification to Realisation 8.4 Aligning and Communicating Benefits
9 Stakeholder Engagement & Communication
9.1 Stakeholder Analysis, Influence and Engagement 9.2 The Communication Management Plan and Its Benefits 9.3 Managing Stakeholder Expectations 9.4 Communication Methods and Tailoring the Message 9.5 Factors That Help and Hinder Communication
10 Conflict Resolution
10.1 Sources and Impacts of Conflict 10.2 Addressing Conflict and the Thomas-Kilmann Model
11 Leadership
11.1 Leadership, Motivation and Team Performance 11.2 Changing Leadership Styles for the Situation 11.3 Coaching, Mentoring and Emotional Intelligence
12 Team Management
12.1 Team Development Stages and Models 12.2 Characteristics and Benefits of Effective Teams 12.3 Leading Virtual and Hybrid Teams
13 Diversity & Inclusion
13.1 Diversity Characteristics and the Equality Act 13.2 Incorporating Diversity and Diverse Thinking 13.3 Conscious and Unconscious Bias and Fair Treatment
14 Ethics, Compliance & Professionalism
14.1 Continuing Professional Development and Competence 14.2 Sources of Specialist Advice and Standards 14.3 The Legal and Regulatory Landscape
15 Requirements & Solutions
15.1 Establishing Scope Through Requirements Management 15.2 Managing Scope Through Configuration Management 15.3 Solutions Development and Prioritisation
16 Quality Management
16.1 Quality Planning, Indicators and the Business Case 16.2 Quality Control and Success Criteria
17 Integrated Planning
17.1 The Integrated Project Management Plan: Format and Contents 17.2 Why an Integrated Plan Matters
18 Schedule Management
18.1 Defining Scope and Breakdown Structures 18.2 Dependencies and What Drives the Schedule 18.3 Re-Estimating and Schedule Optimisation
19 Resource Management
19.1 Determining Resource Requirements and Availability 19.2 Organisational Breakdown Structure and RACI 19.3 Categorising and Allocating Resources 19.4 Resource Smoothing and Resource Levelling
20 Budgeting & Cost Control
20.1 Creating a Budget and Cost Types 20.2 Earned Value and Cost Forecasting 20.3 Monitoring and Reporting Financial Performance 20.4 Closing Down Project Finances
21 Risk & Issue Management
21.1 Benefits of Risk and Issue Management and Contingency Planning 21.2 The Risk and Issue Management Processes 21.3 Proactive and Reactive Risk Responses 21.4 Governance in Risk and Issue Management
22 Change Control
22.1 The Change Control Process and Its Stages 22.2 What a Change Request Must Capture 22.3 Assessing Options and the Impact of a Change 22.4 Recommending Decisions and Updating Plans
11.2 Changing Leadership Styles for the Situation
Key Takeaways Explain This Topic AI
Leadership style should be a deliberate response to team capability, urgency and risk, task clarity, and team motivation.
Capability and motivation move independently: a capable but demotivated specialist needs ownership, not instruction.
Style should shift across the life cycle — consultative in definition, directive in early deployment and crisis, delegating in steady delivery, coaching at transition.
A permanently directive default disengages capable people and makes the project manager a decision bottleneck.
A permanently hands-off default leaves inexperienced teams without structure and nobody to take unpopular decisions.
Last updated: August 2026
Outcome 12b is a single, high-yield line: understand why it may be necessary to change leadership styles depending upon the situation . The mark is never for naming a style. It is for explaining what about the situation makes one style appropriate and another counter-productive.
Changing leadership styles depending on situation
Effective project leadership is situational . Style should fit task urgency , team competence and confidence , stakeholder power , risk severity , and life-cycle moment . A single fixed style (always directive, or always laissez-faire) fails under varied project conditions.
Situation Often-effective emphasis Why
Crisis / safety incident Directive, clear single voice, short instructions Speed and clarity protect people and objectives
New team / low experience Directive to coaching — structure, standards, frequent feedback Competence and norms are still forming
Capable team, clear goals Delegating / supportive — autonomy with checkpoints Uses expertise; builds ownership
Conflict between peers Facilitative / collaborative leadership Parties need joint problem-solving, not imposed silence
Political stakeholder environment Visible, diplomatic, network-oriented leadership Influence beyond formal authority
- Iterative product work Servant / coaching with product focus Enables team flow and learning
- Assurance or audit finding Firm on standards, open on learning Compliance without fear culture
- Situational arc on one project
Start-up: more structure — roles, vision, ways of working (directive elements + coaching).
Storming (team development): active conflict facilitation and norm-setting.
Performing: more delegation; leader removes blockers and manages upwards.
Crisis mid-project: temporary return to directive control, then release once stable.
Transition/close: recognition, knowledge transfer, and support for people returning to BAU.
Exam trap: "The best leaders always empower and never direct." Situational leadership includes directive action when needed , then a return to developmental styles.
The variables that should move your style
Four situational variables do most of the work in exam scenarios. Read them off the stem before choosing a style.
Variable Pushes towards a directive style Pushes towards a supportive or delegating style
Team capability and experience New team, unfamiliar work, low competence in the task Experienced specialists who know the work better than you do
Urgency and risk Safety incident, live outage, imminent regulatory breach Routine delivery with time to explore options
Clarity of the task Well-defined work with a known right answer Ambiguous problems needing exploration and ideas
Team motivation and confidence Low confidence needing structure and reassurance High commitment needing autonomy and challenge
Note that capability and motivation move independently . A highly capable but demotivated specialist does not need instruction; they need to understand why the work matters and to be given ownership. A motivated but inexperienced apprentice needs structure without having their enthusiasm managed out of them. Diagnosing which of the two is missing is precisely the judgement that scenario questions test.
Style shifts across the life cycle
Leadership style should also move as a project progresses, and saying so lifts an answer:
Concept and definition — facilitative and consultative: the task is ambiguous, options must be explored, and stakeholders must be brought along.
Early deployment — more directive: baselines are set, the team is new, and clarity beats debate.
Steady delivery — supportive and delegating: the team is competent, and micromanagement now destroys ownership and slows decisions.
Crisis — directive, briefly: someone must decide quickly and take responsibility for it.
Transition and closure — coaching and appreciative: motivation dips as the team disperses, and knowledge transfer depends on goodwill.
Why a single style fails
Two failure patterns recur in scenarios and both are worth naming.
Permanently directive. Fast in a crisis, corrosive as a default. Capable people disengage, stop raising problems because they are not asked, and eventually the project manager becomes the only source of decisions — a bottleneck and a single point of failure. This also drifts towards McGregor's Theory X, where controlling behaviour produces the passivity that appears to justify it.
Permanently hands-off. Comfortable with strong teams, dangerous with new ones or in a crisis. Inexperienced members flounder without structure, ambiguity persists, and nobody takes the unpopular decision.
The professional position is that style is a deliberate response to circumstances , chosen consciously and changed openly. Telling a team why you are stepping in — "for the next two days while we resolve the outage I'm going to direct this closely, then we go back to how we normally work" — preserves trust while the style changes. In a long response, name the situational variables, state the style, justify the fit, and say what would make you change it.