PM Primer

Beginner-friendly project management courses to help you launch your PM career with confidence.
1 joined
Profile picture
@matthewvanceProfile pictureJul 20

How to Handle Stakeholders Who Keep Changing Their Mind

If you've run even one project, you've met this person: the stakeholder who approves a plan, then changes direction two weeks later — with no acknowledgment that anything's changed. Here's how to handle it without losing your schedule or your sanity.


1. Get alignment in writing, every time


Verbal "yeah that sounds good" in a meeting isn't approval — it's a maybe. The fix: follow every stakeholder conversation with a short written recap ("Confirming we're moving forward with X, unless I hear otherwise by Friday"). It takes 2 minutes and saves you from "that's not what I asked for" three weeks later.


2. Separate "urgent" from "important"


Stakeholders are great at making everything sound urgent. Not everything is. The fix: when a new request comes in, ask what happens if it waits until the next planning cycle. If the answer is "nothing bad," it's not urgent — it's a backlog item.


3. Make the trade-off visible, not just the ask


When a stakeholder asks for something new, don't just say yes or no — show the cost. "Sure, we can add that — it'll push the deadline by 4 days or we drop feature Y. Which do you prefer?" This turns you from an order-taker into a decision-partner.


---


Communication like this is exactly what we cover in the Execution & Leadership chapter of the course — check it out if you want frameworks you can use in your very next stakeholder meeting. 👇

Profile picture
@matthewvanceProfile pictureJul 7

3 Project Management Basics Every Beginner Gets Wrong

If you're brand new to project management, here are 3 things almost everyone gets wrong when they start — and how to fix them.


1. Confusing "busy" with "on track"


A team can be working hard every single day and still be way behind schedule. The fix: track progress against your schedule baseline, not against how much activity is happening. Ask "what % of the critical path is done?" not "how many hours did we log?"


2. Treating scope as fixed once and never revisiting it


New PMs write a scope doc, get it approved, and then let scope quietly drift as stakeholders ask for "just one more small thing." Six weeks later the project is unrecognizable from the original plan. The fix: put a lightweight change control process in place from day one — every new request gets assessed for its time/cost impact before it's approved, even if the answer is "yes, let's do it."


3. Waiting too long to surface bad news


The instinct is to try to fix a problem quietly before anyone notices. This almost always backfires — by the time you speak up, the problem is bigger and trust is lower. The fix: as soon as you spot a risk becoming real, communicate it immediately, along with 1-2 options for how to recover.


---


These are covered in more depth (with practical frameworks you can apply right away) inside our Introduction to Project Management course — built specifically for people with zero prior PM experience who want to break into the role. Check it out if you want the full foundation, not just the tips. 👇