13.1 Leadership Styles and Influencing Team Performance

13.1 Leadership Styles and Influencing Team Performance

Definition (APM BoK7 glossary): Leadership is the ability to establish vision and direction, to influence and align others towards a common purpose, and to empower and inspire people to achieve success.

Three verbs carry the definition — establish, influence and align, empower and inspire. A paraphrase that stops at "motivating people" loses the first and third. BoK7 also defines influencing as "the act of affecting the behaviours and actions of others", which is exactly what assessment criterion 10.2 asks about when it requires you to explain how a project team leader can influence team performance.

Projects are temporary endeavors delivered through human effort. While project management methodologies provide essential structural frameworks—such as work breakdown structures, risk registers, and critical path schedules—these technical tools do not execute work on their own. Projects succeed or fail based on the dedication, competence, collaboration, and morale of the people executing them. Within the APM Body of Knowledge (BoK7), leadership is recognized not as an innate, unteachable trait or a luxury reserved for senior executives, but as an indispensable core competence required of every project professional.

A project manager must exercise leadership across complex, shifting organizational landscapes. Unlike permanent line managers who rely primarily on formal hierarchy, departmental authority, and static job descriptions, project managers routinely lead temporary, multidisciplinary teams over whom they may have little or no direct functional authority. In this environment, the ability to influence, inspire, and align people around a shared purpose is the true currency of delivery success.

---

The Fundamental Distinction: Management vs. Leadership

A central theme within the APM PFQ curriculum is the vital distinction—and operational interdependence—between management and leadership. While frequently used interchangeably in common parlance, they represent two fundamentally different behavioral systems.

• Management is primarily concerned with order, predictability, and control. It focuses on administering processes, establishing governance structures, defining work packages, estimating budgets, scheduling activities, mitigating variances, and ensuring that project deliverables conform strictly to approved baseline parameters.
• Leadership is primarily concerned with vision, alignment, inspiration, and change. It focuses on articulating the strategic "why" behind the project, motivating people through intrinsic purpose, fostering psychological safety, navigating ambiguity, building interpersonal trust, and empowering teams to overcome unforeseen obstacles.

As the renowned leadership scholar John Kotter observed, management provides the operational scaffolding that prevents chaos, while leadership generates the vision, emotional connection, and momentum necessary to navigate complex transformations. A project that is rigorously managed but poorly led may produce deliverables on time and on budget, yet suffer from severe team burnout, toxic disengagement, and a lack of innovative problem-solving. Conversely, a project that is passionately led without disciplined management inevitably collapses into operational chaos, unmanaged scope creep, missed milestones, and budget overruns.

Master Comparison: Management vs. Leadership across Six Dimensions

The following table provides a comprehensive APM BoK7 comparative evaluation across the six defining dimensions of project delivery.

---

The Situational Leadership Model

A critical tenet of modern project management is that there is no single "best" leadership style. The most effective project leaders exhibit behavioral flexibility, diagnosing the needs of their team and adapting their leadership approach to match the specific context. The APM framework adopts the principles of the Situational Leadership Model (originally formulated by Paul Hersey and Ken Blanchard).

The Situational Leadership model posits that leadership style must be calibrated according to two underlying leader behaviors:

1. Directive Behavior (Task Focus): The extent to which the leader spells out the duties and responsibilities of an individual or group. This includes telling people what to do, how to do it, when to do it, where to do it, and closely supervising performance.
2. Supportive Behavior (Relationship Focus): The extent to which the leader engages in two-way communication, listens actively, provides encouragement, facilitates collaborative problem-solving, and offers socio-emotional support.

The Four Development Levels of Team Members (D1 to D4)

To apply the model, the project leader must assess the team member's development level (or maturity) in relation to a specific project task. Development level is a combination of two variables: competence (knowledge, technical capability, and transferable skills) and commitment (confidence, enthusiasm, and motivation):

• D1: Low Competence, High Commitment ("Enthusiastic Beginner"): The individual lacks the specific technical skills or domain experience required for the project task, but approaches the work with high enthusiasm, energy, and a strong desire to learn.
• D2: Some Competence, Low/Variable Commitment ("Disillusioned Learner"): The individual has acquired basic competence through initial exposure, but has encountered unforeseen difficulties, roadblocks, or tedious tasks, leading to plummeting motivation, frustration, or self-doubt.
• D3: High Competence, Variable/Low Confidence or Commitment ("Capable but Cautious Contributor"): The individual possesses the technical ability and proven competence to execute the task, but lacks self-confidence, feels insecure about taking full responsibility, or suffers from temporary motivational fatigue.
• D4: High Competence, High Commitment ("Self-Reliant Achiever"): The individual has demonstrated mastery of the task, operates with high self-confidence, takes proactive ownership, and is deeply dedicated to project objectives.

The Four Situational Leadership Styles (S1 to S4)

The project manager maps their leadership behavior to the diagnosed development level of the individual or team:

+-----------------------------------------------------------------------------------+
|                         THE SITUATIONAL LEADERSHIP MATRIX                         |
+-----------------------------------------------------------------------------------+
|  SUPPORTIVE BEHAVIOR (Relationship Focus)                                         |
|  HIGH  |                                        |                                 |
|        |  S3: SUPPORTING / PARTICIPATING       |  S2: COACHING / SELLING         |
|        |  • Low Directive, High Supportive     |  • High Directive, High Support |
|        |  • Facilitates collaborative decisions|  • Explains "why", invites ideas|
|        |  • Builds confidence & self-reliance  |  • Restores flagging enthusiasm |
|        |  • Matched to: D3 Contributors        |  • Matched to: D2 Learners      |
|        |----------------------------------------+---------------------------------|
|        |  S4: DELEGATING                       |  S1: DIRECTING / TELLING        |
|        |  • Low Directive, Low Supportive      |  • High Directive, Low Support  |
|        |  • Passes operational control         |  • Specific instructions & rules|
|        |  • Monitors from a distance           |  • Close supervision of work    |
|   LOW  |  • Matched to: D4 Achievers           |  • Matched to: D1 Beginners     |
|        +--------------------------------------------------------------------------|
|                    LOW  <----------------------------------->  HIGH               |
|                              DIRECTIVE BEHAVIOR (Task Focus)                      |
+-----------------------------------------------------------------------------------+

1. S1: Directing / Telling (High Directive, Low Supportive): The leader provides explicit, step-by-step instructions, establishes rigid guidelines, clarifies roles, and closely monitors execution. The focus is entirely on task completion. This style is essential for D1 team members who need clear operational direction to avoid costly errors.
2. S2: Coaching / Selling (High Directive, High Supportive): The leader still defines what needs to be done and maintains ultimate decision-making authority, but engages in extensive two-way dialogue. The leader explains the rationale behind directives, solicits suggestions, praises small wins, and actively works to rebuild the team member's bruised confidence. This style is designed for D2 team members.
3. S3: Supporting / Participating (Low Directive, High Supportive): The leader steps back from day-to-day instruction, as the individual already knows how to perform the work. Instead, the leader acts as a facilitator and sounding board, sharing decision-making, offering reassurance, and helping the D3 individual overcome anxiety or reluctance.
4. S4: Delegating (Low Directive, Low Supportive): The leader entrusts day-to-day operational execution and decision-making to the individual. The leader provides high-level objectives, ensures resources are available, and removes organizational impediments, allowing D4 achievers the freedom to excel autonomously.

---

Emotional Intelligence (EQ) in Project Leadership

Historically, organizational management placed disproportionate emphasis on cognitive intelligence (IQ) and technical expertise. However, the APM Body of Knowledge recognizes that while technical competence is a baseline requirement, Emotional Intelligence (EQ) is what truly distinguishes exemplary project leaders. Projects are high-pressure environments fraught with shifting deadlines, competing priorities, commercial friction, and ambiguity. A project manager who cannot govern their own emotions or read the social dynamics of others will struggle to maintain team cohesion.

Formulated prominently by Daniel Goleman, Emotional Intelligence comprises four foundational domains:

1. Self-Awareness

Self-awareness is the ability to recognize and understand one's own emotions, mood states, behavioral triggers, strengths, weaknesses, and values, as well as their ripple effect on others. A self-aware project manager recognizes when personal fatigue, stakeholder criticism, or milestone pressure is causing them to become irritable, enabling them to pause and recalibrate before responding destructively to a colleague.

2. Self-Regulation (Self-Management)

Self-regulation involves the capacity to control, channel, or redirect disruptive emotional impulses and moods. In project environments, crises are inevitable: servers crash, suppliers default, or sponsors demand emergency scope reductions. A project manager with high self-regulation remains composed, objective, and resilient under duress, projecting calm confidence that prevents panic from spreading across the team.

3. Social Awareness (Empathy)

Social awareness is the ability to accurately sense, understand, and appreciate the emotional makeup, unvoiced concerns, and perspectives of other people. Empathy does not mean agreeing with every complaint or compromising project standards; rather, it means demonstrating genuine understanding of the pressures facing team members, contractors, and client stakeholders. Empathy allows a project manager to detect early signs of team burnout or subterranean resistance to change.

4. Relationship Management (Social Skills)

Relationship management encompasses the adept management of interpersonal interactions, collaborative networks, and political currents. It involves using influence, persuasive communication, conflict negotiation, and inspirational leadership to guide diverse groups toward shared goals. Leaders high in social skills dismantle functional silos, build lasting alliances, and resolve interpersonal discord before it harms project momentum.

---

Influencing Team Performance and Motivation

Project managers cannot force high performance through contractual mandate or authoritarian command; sustainable high performance must be cultivated. APM BoK7 highlights several core leadership strategies through which project managers positively influence team productivity:

Establishing a Compelling Shared Vision

Individuals are rarely inspired by Gantt charts or cost-performance indices. Exceptional leaders connect daily, mundane tasks to a larger, meaningful purpose. When team members understand why the project matters—whether it is improving patient safety in a new hospital wing, eliminating carbon emissions in an energy grid, or transforming customer experience—they commit discretionary effort that goes far beyond minimum compliance.

Setting Clear Expectations and Accountabilities

Ambiguity is a primary source of project anxiety and conflict. Leaders ensure that every team member understands their specific responsibilities, reporting lines, quality standards, and decision-making boundaries. Utilizing tools like the RACI matrix (Responsible, Accountable, Consulted, Informed) eliminates duplicate efforts and finger-pointing.

Practicing Active Listening

Active listening requires giving undivided cognitive attention to the speaker, observing non-verbal body language, withholding premature evaluation, and paraphrasing core messages to confirm mutual comprehension. When team members feel genuinely heard and validated, their engagement and trust in leadership increase exponentially.

Cultivating Psychological Safety

Pioneered by Harvard Business School professor Amy Edmondson, psychological safety is a shared belief held by members of a team that the team is safe for interpersonal risk-taking. In a psychologically safe project culture:

• Team members admit technical errors and bugs immediately without fear of humiliation or retribution.
• Novice members feel comfortable asking clarifying questions and challenging flawed assumptions.
• Risks and "bad news" are escalated early, dismantling the dangerous "watermelon project" phenomenon (where a project appears green on the surface but is bright red underneath).

---

Motivation Theories in Project Delivery

Understanding human motivation enables project managers to create working environments that bring out the best in diverse teams. Two foundational motivation models are widely applied within the APM framework:

1. Maslow's Hierarchy of Needs in Project Settings

Abraham Maslow proposed that human beings are motivated by an escalating hierarchy of needs, ranging from physiological survival to self-actualization. A project manager must recognize which tier of need is primary for their team members:

• Physiological & Safety Needs: In a project context, this translates to fair financial compensation, reasonable working hours, ergonomic workstations, physical site safety, and clear job security.
• Social / Belonging Needs: Projects are social systems. Leaders foster belonging by establishing inclusive team rituals, collaborative workshops, mutual support networks, and shared team identities.
• Esteem Needs: Team members seek recognition, status, and appreciation. Leaders fulfill esteem needs through public praise for milestone completions, recognizing specialized expertise, and granting greater autonomy.
• Self-Actualization Needs: The highest level of motivation occurs when individuals are given challenging, complex problems that stretch their creative abilities, allowing them to realize their full professional potential.

2. Herzberg's Motivation-Hygiene Theory (Dual-Factor Model)

Frederick Herzberg's research demonstrated that job satisfaction and job dissatisfaction do not exist on a single continuum; they are driven by two distinct sets of factors:

1. Hygiene Factors (Extrinsic / Maintenance Factors): These relate to the project working environment, including company policies, physical working conditions, base salary, job security, administrative procedures, and interpersonal relationships with supervisors.
   • Critical Rule: If hygiene factors are deficient or unfair, they cause intense dissatisfaction. However, improving hygiene factors (e.g., upgrading office chairs or providing free coffee) merely removes dissatisfaction—it does NOT generate sustained positive motivation or discretionary effort.
2. Motivator Factors (Intrinsic / Growth Factors): These relate directly to the content of the work itself, including personal achievement, meaningful recognition, challenging tasks, increased responsibility, autonomy, and professional growth.
   • Critical Rule: Only motivator factors have the power to create genuine job satisfaction and drive individuals to deliver superior, high-discretionary performance.

Managerial Takeaway: A project manager cannot motivate a struggling development team simply by fixing administrative hygiene issues. While fair pay and decent working conditions must be established as a necessary baseline, true project motivation requires designing work packages that provide intellectual challenge, granting team members real ownership, and celebrating tangible project achievements.