The decisions you make under pressure define your project

Most projects don’t fail because of poor planning. 

They fail because of what happens next. 

Because no matter how detailed the plan is, no project unfolds exactly as expected. Timelines shift. Stakeholders change their minds. Risks emerge. Dependencies don’t land the way you thought they would. 

In those moments often messy, ambiguous, and time-pressured, decisions need to be made. 

This is where the real work of leadership begins. 

The quality of your project’s delivery is not defined by how good your plan looked at the start. It’s defined by the decisions made when things don’t go to plan. 

Pressure changes how we decide

When pressure builds, even experienced leaders can find themselves responding differently. 

You might recognise some of these patterns: 

• waiting for more certainty before making the call, 
• bringing in more voices to “get alignment”, 
• making a quick decision just to relieve the pressure, or 
• quietly hoping the issue resolves itself. 

None of this comes from a lack of capability. 

It comes from the weight of responsibility… and the discomfort of not having a clear answer. 

But here’s the reality. 

In project delivery environments, indecision isn’t neutral.
It shapes the outcome just as much as a decision does because while you’re waiting: 

• the timeline continues,  
• dependencies keep moving, and 
• the rest of the team starts interpreting the silence. 

It’s not the big decisions, it’s the accumulation

When people look back on a project that’s gone off track, they often search for a single moment where it all turned. 

A missed milestone.
A major issue.
A dependency that didn’t land. 

But in reality, that moment is rarely the cause. 

What I see more often is a slow drift. 

A series of small decisions that sounded reasonable at the time: 

• “Let’s revisit this next week”  
• “We’ll keep both options open for now”  
• “We don’t want to escalate this yet”  
• “Let’s get one more perspective before we decide”  

Individually, they make sense. 

Collectively, they create: 

• delay, 
• ambiguity, and 
• a lack of forward momentum  

And over time, that becomes the project outcome. 

Strong projects feel different

In projects that are performing well, the pressure is still there but the response to it is different. 

Decisions tend to be: 

• made at the right level,  
• made in a timely way, 
• made with clear trade-offs, and 
• communicated with confidence. 

Not because everything is easier but because the team has already done the work to prepare for pressure. 

They’ve created clarity around: 

• who makes which decisions,  
• how and when to escalate, and  
• what matters most when trade-offs are required. 

So when the moment comes… they’re not starting from scratch. 

Decision quality is a leadership capability

One of the biggest myths I see is that decision-making under pressure is a personality trait. 

It’s not. It’s a capability and it can be developed. 

It looks like: 

• pausing long enough to understand what’s really being asked,  
• separating the signal from the noise,  
• being willing to make a call without perfect information,  
• thinking through the downstream impact, and  
• bringing others with you through clear communication  

It also means getting comfortable with a level of discomfort because the “right” decision isn’t always the easy one. 

The cost of waiting

Waiting can feel responsible. 

Measured. Considered. Safe. 

But in many projects, waiting is where momentum quietly disappears. 

You’ll often hear: 

• “We just need a bit more data”  
• “Let’s hold off until we’re clearer”  
• “We’ll come back to this next week”  

And sometimes, that’s exactly the right call. 

But often, it’s not about needing more information rather avoiding the tension that comes with making the decision. 

Because while you’re waiting: 

• teams start to hesitate,  
• priorities become less clear, and  
• confidence begins to drop.  

The window to act doesn’t stay open indefinitely. 

A better way to lead under pressure

What I’ve seen consistently, especially in project recovery, is this: 

When leaders shift how they make decisions under pressure, everything else starts to move. 

Not overnight but noticeably. 

You start to see: 

• clearer conversations,  
• faster movement,  
• stronger alignment, and  
• renewed energy in the team.  

The most effective leaders don’t avoid pressure; they design for it. 

They create: 

• clear decision frameworks,  
• simple escalation pathways,  
• open conversations about trade-offs, and  
• a shared understanding of what success looks like  

So when pressure shows up and it always does, the team is ready. 

If you paused for a moment and looked at your current project… 

What decisions are sitting there… waiting? 

What conversations are being softened? 

What trade-offs haven’t been made explicit? 

Because somewhere in those moments, your project outcome is already taking shape. 

Not later. 

Now.