Answer extracted from the Beyond The Plan podcast — listen to the full episode below.
What is the core difference between managing under pressure and leading under pressure in project management?
Managing under pressure means you are handling your own performance adequately, but leading under pressure means you are actively helping your team navigate difficult phases as well. As a project manager, staying calm and providing clarity and direction to your team remains essential even when facing severe financial, time, personnel, or third-party pressures.
The distinction matters because many project managers conflate coping with crisis with actually leading their team through it. You might be meeting your own deadlines and maintaining your composure, yet if your team is confused, demoralised, or left without clear direction, you're only managing yourself—not leading.
Nick Jagger, whose 45 years of project management experience spans major infrastructure projects including work as a risk manager on the $8 billion Northwest Ruralink (later Sydney Metro), emphasises that this shift from managing to leading is fundamental. The technical aspects of the role—schedules, budgets, scope—pale in comparison to how you hold the space for your people during crisis.
Real leadership under pressure involves communicating with transparency. Your team needs to understand what constraints exist, what options remain on the table, and what you expect from them. Without that clarity, pressure cascades downward as anxiety rather than focus.
"It is not necessarily what the project manager knows that makes the difference. It is how they can work with the team."
Nick Jagger — Technical Director of Project Management, Elemental Projects. A project management veteran with 45 years of experience, Jagger studied a Masters of Project Management at UTS and worked on major infrastructure projects including the Northwest Ruralink as a risk manager. After approximately 10 years with risk management firm ACOM, he moved to smaller consultancy Ontwit focusing on social infrastructure, then to Mark McDonald as technical director, before joining Elemental Projects 18 months ago.
The emotional labour of this distinction is significant. As explored in this episode, managing pressure is a solo task; leading under pressure requires you to monitor how your team is absorbing the stress, stepping in to reset expectations when needed, and sometimes simply reassuring people that the situation, however difficult, is being stewarded responsibly.
This is why experience alone is not the strongest predictor of successful project delivery. A project manager with ten years of technical know-how but who isolates during crisis will fail to hold the team together. Conversely, a less experienced manager who focuses on keeping people aligned and motivated can often navigate pressure more effectively.
The pressure itself doesn't change—financial constraints, tight timelines, and competing stakeholder demands are real. What changes is your approach: are you surviving the pressure, or are you helping your team survive it together? That pivot from personal management to collective leadership is what separates the project managers who retain their teams from those who watch talented people leave during crisis.
Why This Matters in Practice
When a team senses that their project manager is merely holding on—barely coping, reactive, or worse, deflecting blame—morale collapses. People start protecting themselves rather than collaborating on solutions. Productivity drops, mistakes multiply, and the crisis deepens.
Leading under pressure reverses this pattern. When your team sees you present, thoughtful, and focused on helping them succeed within the constraints, they stay engaged. Jagger discusses how genuine culture—not just a launch event but sustained, authentic support—becomes the bedrock of how teams perform when everything is on the line.
The people skill of managing conflict and encouraging healthy dialogue becomes indispensable. Under pressure, tensions surface. If your team trusts you to handle disagreement fairly and to keep the conversation focused on solving the problem rather than blaming individuals, they will bring their concerns to you early. That transparency gives you a chance to course-correct before small issues become catastrophic.
See also
What role did confusion between governance and policing play in RoboDebt's punitive outcomes?
The program team and stakeholders believed in the governance structures, but the way governance was executed from a technology and process perspective created systemic harm.
How does poor governance experience transfer across organizations and impact future project outcomes?
Negative governance experiences are deeply memorable and transferable. When people move to a new organization years after a poor experience, those cautionary patterns follow them.
Why does good governance often have a poor reputation while bad governance is highly memorable?
Good governance is invisible because it works seamlessly—processes flow together, decisions are made, and teams feel supported. Bad governance, by contrast, creates visible friction and memorable pain.