🎮 Can You Survive This Project as a PM?

You’re the PM on a high-stakes digital rollout. The budget is tight, the exec sponsor is impatient, and your team is stressed.

Your mission: Deliver the project without losing your credibility, your team’s trust, or your sanity.

Let’s play 👇


Scene 1: The Angry Exec

In a steering committee, your sponsor slams the table:
“Why are we already two weeks behind?”

Do you…
• Option A: Stay calm, acknowledge the frustration and issues, and propose two recovery options tied to business outcomes.
• Option B: Pull up your Gantt chart, walking them through every blocker  educate them. This way it is clear there are issues but it's not your fault.

👉 If you chose B: The logic makes sense because clarity protects you. But the sponsor doesn’t care whose fault it is; they care how to fix it. You lose the room. 

GAME OVER!

👉 If you chose A: The sponsor exhales, reassured that you’re steering toward solutions.


Smiling at having calmed the storm, you leave the room — only to get pulled into a tense meeting with your dev team.

⸻

Scene 2: The Exhausted Team

Your dev lead says, “We can’t keep doing late nights. Morale is shot.”

Do you…
• Option A: Calmly remind them of the deadline and say, “We all need to push through.” Sounds tough, but it’s critical to get to the finish line - and the reality is there are some stakeholders that cannot be said no to. 

• Option B: Listen, validate their concern, then negotiate with leadership to review scope and/or delivery cadence instead of burning people out.

👉 If you chose A: The team disengages. Attrition risk. Project limps. You can’t write the code yourself and neither will executives.

GAME OVER!

👉 If you chose B: The dev lead nods, relieved that you see them as humans, not machines. Negotiation means you can deliver at a pace that is sustainable, and with chances of better quality - even when some of the stakeholders are powerful or scary. 

⸻

Scene 3: The Scope Creep Trap

With the team back on your side, you walk into the next stakeholder sync —only to face a VP that has a really “brilliant idea” of some additional features that will make for an amazing user experience. 
The VP says: “Can’t we also add these new features? Customers will love it.”

Do you…
• Option A: With an understanding that in the business world, "the customer is king", you agree to implementing the new features. From an understanding of stakeholders, it is also best to keep an influential VP happy now, and figure out the impact later.

• Option B: You thank the VP, and then tell them you will review the impact of the changes. Basically, you want to run the request through change controls to check if there is an impact to cost, quality and timelines. As you speak, the VP is looking increasingly uncomfortable. 

👉 If you chose A: Smart political instinct — but this will backfire. There is always hidden work, it will likely snowball. Your team burns out and delivery implodes. 

GAME OVER!

👉 If you chose B: The VP sighs but respects the data-driven stance. Scope creep neutralized. You keep delivery intact and head into the final review with confidence.

⸻

The Delivery Review

You’ve managed the sponsor, kept the team alive, and blocked scope creep.

The product launches — slightly leaner — but on time and aligned with business value.

The CIO says:
“This was a great delivery - and you displayed real leadership during the process!”

🎯 You win!


⸻

Notice what actually saved the project.

Not the tools.
Not the plan.
Not the pressure.

Judgment did.

That’s the part of project management no framework can automate — and why great PMs are still rare.

It's 2026 and if you're still thinking about if getting started with Tech Project Management, AI and automation, here is a good place to start. 

John Nova

Rooting for your success!