The Best Project Managers Don't Have One Leadership Style. They Know When to Change It.

Key Summary

• The biggest mistake project managers make isn't choosing the wrong leadership style, it's refusing to change it. This article explains why leadership effectiveness depends on uncertainty, not personality.

  
  

• From Waterfall to Agile, different projects demand fundamentally different behaviours. Drawing on Situational Leadership, Tuckman's team development model, and Robert Greenleaf's servant leadership, it shows why directive leadership creates clarity in high-risk environments while coaching and facilitation unlock performance in adaptive teams.

  
  

• Google's Project Aristotle reinforces the same principle: high-performing teams thrive on psychological safety, but safety doesn't replace accountability. Great project leaders know when to direct, when to coach, and when to step back.

  
  

• As AI automates scheduling, reporting, and administration, project managers will be valued less for managing tasks and more for adapting their leadership to changing circumstances. The future belongs to leaders who can change styles as quickly as projects change.

One of the most persistent myths in project management is that great leaders have a consistent leadership style.

Organizations often celebrate decisive leaders, collaborative leaders or servant leaders as though one philosophy consistently outperforms the others. Certification programs reinforce the idea by categorizing leadership into neat frameworks, while books encourage managers to discover "their" style.

Projects rarely work that way.

A project beginning with ambiguous requirements, cross-functional dependencies and constant customer feedback demands a fundamentally different approach from one delivering a nuclear power plant, a pharmaceutical manufacturing facility or an ERP implementation subject to strict regulatory controls. Yet many project managers continue applying the same leadership behaviours regardless of the environment.

The result is predictable.

Leaders who thrive in one project often struggle in another, not because they lack competence, but because they mistake consistency for effectiveness.

The strongest project managers understand something different.

Leadership is not a personality.

It is a response to uncertainty.

This idea appears repeatedly across decades of leadership research. Hersey and Blanchard's Situational Leadership Theory argued that effective leadership depends on the readiness and capability of followers rather than the leader's preferred behaviour. Bruce Tuckman's model of team development reached a similar conclusion from another direction. Teams in the forming stage require significantly more direction than teams that have reached the performing stage, where excessive supervision often becomes an obstacle rather than a benefit. Neither framework asks, "What kind of leader are you?" Instead, they ask, "What does this team need right now?"

Project management follows the same principle.

Traditional predictive projects, often referred to as Waterfall, are designed to reduce uncertainty before execution begins. Scope is defined upfront, dependencies are carefully planned and changes are intentionally controlled because late modifications can become extremely expensive. Leadership in these environments naturally becomes more directive. Decisions must be made clearly, responsibilities allocated precisely and governance maintained consistently. This is particularly evident in industries such as aerospace, construction, defence and pharmaceuticals, where regulatory compliance and safety leave little room for improvisation.

Directive leadership, however, is frequently misunderstood.

It is not authoritarian leadership.

It is leadership that provides clarity when ambiguity creates unnecessary risk.

A project manager overseeing the construction of a hospital cannot facilitate endless debate over engineering specifications or regulatory approvals. Teams need clear decisions, disciplined execution and predictable coordination because mistakes carry significant financial, and sometimes human, consequences.

Agile environments reverse many of those assumptions.

Rather than eliminating uncertainty before work begins, Agile accepts uncertainty as an inevitable feature of complex work. Customer needs evolve, technology changes and teams learn continuously throughout delivery. The project manager, or Scrum Master, Agile Coach or Product Leader, therefore creates value less by directing work than by enabling better decisions within the team.

This explains why servant leadership, first articulated by Robert Greenleaf in 1970, has become so closely associated with Agile methodologies.

Greenleaf challenged the traditional image of leadership as authority exercised from the top of an organizational hierarchy. Instead, he argued that leaders create better outcomes by removing obstacles, developing people and enabling others to perform at their highest level. The servant leader succeeds not because they control every decision, but because the team becomes increasingly capable of making good decisions independently.

That distinction matters because Agile teams are expected to become progressively more autonomous over time. Micromanagement slows adaptation, reduces ownership and discourages experimentation, the very capabilities Agile intends to cultivate.

Yet treating servant leadership as universally superior creates another misunderstanding.

The best project managers do not become servant leaders because Agile says they should.

They become servant leaders because mature teams require less direction.

Research on team effectiveness consistently supports this idea. Google's Project Aristotle, which examined more than 180 teams, found that the strongest predictor of team performance was not technical expertise but psychological safety, the confidence that team members could raise concerns, challenge assumptions and admit mistakes without fear of punishment. Servant leadership creates precisely those conditions by encouraging participation rather than compliance.

At the same time, psychological safety should never be confused with the absence of accountability.

High-performing Agile teams remain disciplined about delivery, commitments and customer value. The leader simply shifts from controlling work to creating an environment where good work becomes more likely.

Perhaps the most useful way to think about project leadership is through a continuum rather than competing philosophies.

When, 

• uncertainty about direction is high, leaders provide vision.

• uncertainty about execution is high, leaders provide structure.

• uncertainty about capability is high, leaders coach.

But when uncertainty about ownership is low, leaders step back.

In other words, leadership becomes progressively less directive as capability becomes progressively more distributed.

This is why experienced project managers often appear inconsistent to outside observers.

The same leader who makes rapid, non-negotiable decisions during a cybersecurity incident may facilitate collaborative workshops when defining product requirements six weeks later. Neither behaviour contradicts the other. Both respond to different forms of uncertainty.

Unfortunately, organizations often promote project managers because they consistently deliver projects, then expect the same behaviours to work as complexity increases.

Leading a five-person implementation team differs fundamentally from leading a global transformation involving multiple business units, competing stakeholders and ambiguous strategic priorities. As projects become more complex, leadership shifts away from task coordination toward communication, influence, stakeholder alignment and decision-making under uncertainty.

Increasingly, AI is changing this equation as well.

Routine project reporting, scheduling, documentation and risk tracking are becoming increasingly automated, allowing project managers to spend less time administering projects and more time leading them. Ironically, the rise of AI makes distinctly human leadership capabilities even more valuable. Negotiating competing priorities, building trust across stakeholders, coaching struggling teams and making difficult trade-offs remain responsibilities technology cannot meaningfully automate.

The future project manager will therefore be judged less by how well they manage Gantt charts and more by how effectively they adapt their leadership to the situation in front of them.

The most successful project managers have never been defined by a single leadership style.

They are defined by their ability to recognize when yesterday's leadership approach has stopped serving today's project.

Because in project management, as in leadership itself, adaptability is not the alternative to consistency.

It is what consistency actually looks like.

Great project managers don't commit to one leadership style. They commit to the situation.

At Oraton Executive Communication Coach, we help leaders practice the conversations that demand clarity, influence, and adaptability before the stakes are real.