Project managers tell us they wish they'd asked certain questions earlier. Questions they already knew to ask but were afraid to. Here’s what’s typically going through their head in the moment when they need to address these questions:
"If I push back on this, will they think I'm obstructing progress?"
"If I ask for clarification, will I look like I don't understand?"
"If I point out that two stakeholders want different things, will I just be creating problems?"
So they don't ask. And three months later, the project implodes.
Here are the questions that save projects. The ones PMs wish they'd asked on day one.
Not "what are we building" or "what are the deliverables." What problem does this solve? What's the actual goal?
You'd be surprised how many people on the same project have different answers to this question.
One stakeholder thinks the goal is "get to market fast." Another thinks it's "get it right, even if it takes longer." Nobody said this out loud, so the project ping-pongs between the two approaches.
Ask this question in the kickoff. Ask it again when direction shifts. Make people articulate what they're actually trying to achieve.
Success for the finance team might be "on budget." Success for the user team might be "all features work." Success for leadership might be "minimal disruption to current operations."
These aren't wrong. They're just different. And they lead to different decisions.
When you understand what each person cares about, you can design conversations that address the real tensions instead of pretending they don't exist.
This one feels obvious but PMs sometimes skip it because they don't want to sound negative.
But here's the thing: the problems exist whether you ask about them or not. The only difference is when you find out.
Ask this early, and you surface issues when you can still fix them. Ask it late (or never), and you're firefighting three months in.
Scope creep happens because nobody talks about boundaries. People assume different things about what's in and what's out.
Explicitly talk about what's out of scope. What won't happen. What you're saying no to.
This prevents the surprise halfway through the project where someone says "wait, I thought we were doing that too."
Not "how will we measure success" in the abstract. How will you know, week to week, if things are on track? What's the signal that you're heading in the right direction?
Without this, people interpret progress differently. You think you're on track. They think you're behind. Nobody knows until the end.
Don't ask "are you comfortable with this?" or "does this work for you?"
Ask: "Can you commit to this?" or “Can anyone NOT agree to this?” These questions will help you avoid the annoying head nodding when people aren’t really agreeing.
Most PMs don't ask these questions because they're afraid of the answers. Afraid someone will say "actually, I want something different." Afraid the conversation will be uncomfortable.
From what we’ve learned from training thousands of PMs: the uncomfortable conversation on day one is better than the project implosion on day 90.
These questions make you look strategic. They make you look like you care about getting it right. They make you sound like someone who prevents problems instead of just fixes them after the fact.
Download our PM Survival Toolkit. It includes a Stakeholder Map template that helps you prepare for these conversations before the kickoff.
Or if you want to go deeper: Join our Facilitation Tip Stream.