How Do Common Project Manager Phrases Hold Up in The Real World?

Project management is full of timeless sayings – some helpful, some overused, and some that even make you want to roll your eyes. In this blog, I’m breaking down 10 of the most classic project management saying and sharing what I really think about them. We’ll look at how they hold up in the real world, whether they’re useful for modern projects, or if they’re just no more than corporate jargon.

Whether you’re a new project manager or you’ve been managing projects for years, you’ll appreciate my practical take on the 10 project management sayings we’ve all heard a thousand times, because like me, I’m sure some of these sayings drive you a little nuts!

Why Can’t You Fit in This One Small Change?

Oh boy. If you’re a project manager, you know the feeling you get in your gut when someone says this. It’s almost like an internal alarm that starts blaring. Because let’s be honest – there is no such thing as “just a small change,” not until you properly evaluate it that is.

Even a change that SEEMS minor can have ripple effects – on scope, budget, timeline, resourcing, dependencies, or stakeholder expectations. It’s like tugging one thread on a sweater. It might unravel more than you think.

That’s why change control is your friend on every project – not to slow things down, but to keep the project on track to get to the finish line on time. You can adjust with confidence instead of chaos when changes are:

• Assessed
• Documented
• Approved
• Tracked

This is where new project managers sometimes get tripped up though. They wait too long to introduce a change control process. Make sure you don’t make that mistake. Even before the first change request comes in, get clear on your project scope and make sure it’s documented, approved, and shared.

Then – introduce a change control form early. Walk all your stakeholders through it during kickoff. Let them know that any requested change – big or small – needs to go through that process. When people understand that structure from the start, you’ll deal with far less pushback later on.

This one phrase, “It’s just a small change,” has derailed countless projects. But if you’ve done the groundwork upfront, you’ll be ready to say: “Thanks for your request. Let’s run it through our change control process and take a look at where it will impact things and then we can go from there.” You’d be surprised how many requests for small changes just seem to disappear when someone has to fill out a form that makes their request official.

Scope Creep is Inevitable

I don’t agree that scope CREEP is inevitable – not if you’re doing your job properly it isn’t. Here’s what I mean – yes, scope CHANGE is inevitable, because in the real world of business and projects, priorities shift, stakeholders have new ideas, and business needs evolve. But scope CREEP is entirely different. Scope creep is unmanaged change. It’s what happens when we skip steps in the project management process and say yes without asking the right questions. It’s what happens when things aren’t set up properly, or when we don’t stick with the systems we’ve put in place.

This saying gets thrown around a lot, but honestly, I think it kind of normalizes bad habits. It sends the message that projects are destined to veer off course, but that’s not exactly true. When you are crystal clear on project scope and priorities, and you build a solid, flexible, and controlled process for dealing with change requests, you can accommodate change without chaos.

Let’s talk about what that looks like in practice – because I’m all about what’s practical – I structured my entire SLAY Project Management program around the practical information you need to manage projects well. Yes, project management theory is a good baseline, but where I see projects go sideways is when project managers don’t have the practical information they need to deal with real world situations.

Practical ways to avoid scope creep

1. Start with a clear, signed-off scope statement because vague scope equals vague outcomes. Get specific, write it down, and get agreement before kickoff.
2. Introduce your change control process early. Don’t wait until the first “tiny” request. Show stakeholders how change requests will be handled – how they’ll get evaluated, documented, and approved or declined.
3. Use the priority matrix. When scope changes are requested, refer back to what was agreed on: what’s fixed (like budget or timeline) and what’s flexible. This is such a great practical tool because it helps you have productive, neutral conversations about trade-offs.

The bottom line is that when you run projects with structure, change doesn’t have to lead to scope creep. Don’t let the saying “scope creep is inevitable” become an excuse for skipping steps. Instead, show your team what controlled, transparent change really looks like.

Fast, Cheap, or Good? Pick Two

This is the project management priority triangle reimagined as a catchphrase. Fast, cheap, and good equates to time, scope, and budget. My take on“fast, cheap, or good – pick two”is that I would never say this – because you need to have all three in your project. They’re ALL important. What’s key is, we have to negotiate their LEVEL of importance. The problem is when senior executives want ALL three to be TOP priority.

How can you keep project priorities straight?

That’s where your priority matrix comes in. Early in your project, sit down with your sponsor or steering committee and define which of the three constraints – scope, time, or budget – is fixed, and which ones have some flexibility. Then get it in writing – that part is important, because when the scope of your project begins to creep, or deadlines don’t fall in line, your priority matrix becomes your north star.

I’ve used the priority matrix as a visual anchor during kickoffs, risk reviews, and I use it especially when dealing with change requests. It reminds everyone about what they’ve agreed to, and makes it way easier to say, “Sure, we can do that, but here’s what has to shift.”

So, while this saying is catchy – it would be detrimental to your project and your career if you spouted this off to a senior executive. Instead, set the priorities, communicate them clearly, document them and get sign-off, and don’t be afraid to pull out that document to remind everyone what’s been agreed on when things start pulling in all directions.

Let’s Circle Back

This saying is the corporate equivalent of “I don’t want to deal with this right now.” And to be fair, sometimes that CAN be a valid response, where we put a pin in something, or we put it in the ‘parking lot’ for the time being. Sometimes we do need space to think, check facts, or gather input before making a decision. I agree that not everything can or should be decided in the moment on our projects.

But the problem is this phrase gets used all the time as a polite way to dodge a tough topic – or worse yet, to bury it entirely. It becomes code for “Let’s ignore this until it becomes a full-blown crisis.” As a project manager, part of your job is to protect your project from delays that come from indecision. When you hear “Let’s circle back,” don’t let that be the end of the conversation.

How can you respond when project stakeholders stall?

Keep this one word in your back pocket: WHEN? It might be a little abrupt to just say it exactly that way, but you get the idea! In practice, it might sound more like you asking:

• Great – should I add this to our check-in next Thursday?
• Do you want me to block 15 minutes in our calendars so we can revisit this tomorrow morning?”
• Is this something I should escalate now, or should we give it a week?

And if you’re the one saying, “let’s circle back”, that’s okay – just don’t leave it vague. Set a date, set a reminder, and make sure someone owns the follow-up. Even better? Capture it in your meeting notes or put it in your WBS and assign it an owner and a deadline. Do whatever you need to do so it doesn’t get lost in the shuffle.

Because “Let’s circle back” without a follow-up plan isn’t deferring – it’s stalling. And stalled decisions create bottlenecks, delays, and confusion for your team – all of which you want to avoid at all costs.

Project Management is Not a Popularity Contest

Truer words were never spoken. Project management is about leading people, not pleasing them, and that means sometimes you’ll have to make tough calls, deliver hard messages, or hold people accountable – even when it’s uncomfortable.

What does that mean in practice? Well, if you’re doing a good job well, there are going to be moments when someone’s unhappy with you, or with a decision you’ve made. Maybe a stakeholder won’t like it when you ask them to fill out a change request form, or when you remind them of the project priorities they agreed to. Or, maybe a team member won’t love it when you call them out on missing a deadline they were assigned weeks ago. Either way, that doesn’t mean you’re failing – it means you’re leading.

The truth is you need to develop a bit of a thick skin as a project manager. You need to be okay when people are unhappy with you. Now, that doesn’t mean you bulldoze your way through people or act like you’re above feedback, because it is still your job to listen, collaborate, and show respect. But your focus has to stay on delivering the project, not protecting your popularity. Sometimes that’s easier said than done, because we all have feelings, after all.

How should you handle discontented project team members?

1. Stick to the facts when you’re communicating about contentious things on your project. Ground your decisions in data, plans, and what’s already been agreed to.
2. Overcommunicate your “why.” Even if they don’t love the outcome of a decision, people are much more likely to get on board if they understand the reasoning behind it.
3. Be consistent. If you bend the rules for one person, that’s the expectation you’ll create for others, and then you put the whole project at risk.

Overall, keep in mind that your role isn’t to keep everyone smiling – it’s to guide the team toward a successful outcome. And trust me, nothing earns LONG TERM respect like a project manager who does what’s right, NOT what makes them more popular.

Projects Always Take Longer Than You Think

This saying is almost humorous, because it’s often true. But that doesn’t mean you should just shrug and accept it. If your projects always run long, it’s not just bad luck, it’s a sign your estimation process needs work.

Yes, there are unknowns, and surprises will always happen. But if your timeline is based on the best-case scenario, you’re setting yourself – and your team – up to fail before you even get started. To keep your project from taking longer than expected, you want to stop forecasting your project timelines based on optimistic guesses.

How can you accurately estimate project timelines?

1. Add buffer time where it actually counts – especially on tasks that sit on the critical path, the tasks that, if delayed, will delay the entire project. Instead of padding every task, focus your contingency on high-risk activities where even a small slip could create a ripple effect. On that note, you also want to make sure you,
2. Plan for risk by building risk planning into your schedule development – not as an afterthought. Identify high-probability, high-impact risks early, and develop mitigation strategies that include time-based contingencies. That way, if something does go sideways, you won’t be left scrambling.
3. Use past data by digging into similar projects that have already happened in your organization, or in your own history as a project manager, so you can understand what actually took longer than expected in the past, and then use that to build your current timeline.
4. Review your After Action Reviews. They are a goldmine for spotting where timelines slipped in the past – and why. They’ll help you see whether estimates were too aggressive, or if approvals lagged, or what resource bottlenecks caused delays. They key is to learn from it, so you don’t repeat it.

Planning isn’t about predicting the future perfectly – it’s about preparing for what’s likely, and giving yourself space to adapt when things don’t go exactly to plan. When you use history and risk management to guide you, your project timelines will actually stay on track.

On Projects You Should Under-promise and Over-deliver

This one sounds noble, and it definitely has its place – but if you live by it all the time, it can backfire. Here’s the thing, consistently under-promising can make it seem like you don’t fully understand your project. If your estimates are always padded, or you’re constantly “surprising” stakeholders with early wins, they may start to question whether you truly understand the scope and effort involved – or if you’re intentionally holding back to make the outcome look better than expected.

And over-delivering all the time? Well, that can end up setting a dangerous precedent where people start expecting miracles from you. When that happens, what you’ve done a few times to go “above and beyond” becomes the new baseline, which is a fast track to burnout for you and your team.

What should you do instead? You want to focus on setting CLEAR and REALISTIC expectations from the start, so that everyone understands what’s being delivered, when, and by whom. That removes the guesswork, builds trust with stakeholders, and gives you a solid foundation to manage risk and change without scrambling.

What do clear and realistic project estimations look like in practice?

1. Be honest. Base your estimates on actual data from your subject matter experts.
2. Be clear. Communicate scope, timing, and constraints early – and get sign-off on them.
3. Be consistent. Deliver WHAT you said you would, WHEN you said you would. THAT becomes your credibility.

Of course, if you find you can deliver early or squeeze in a bonus win without blowing up your team’s workload, do it! Just make sure those moments are intentional – and that they’re not the expectation, because clear expectations are your secret weapon as project manager. Set them early, communicate them often, and don’t be afraid to revisit them as the project evolves.

Failing to Plan is Planning to Fail

This one is a classic, and honestly, it’s 100% true. I’d like to take it one step further though and add that failing to plan properly is also planning to fail.

I’ve seen plenty of projects that technically had a plan – a 100-page Word document, a 47-tab spreadsheet, or a Gantt chart so detailed it could wallpaper a boardroom. But the problem was that none of it was useful, either because it lacked clarity, or the team wasn’t bought in, or because no one actually looked at the plan after the kickoff meeting.

It’s not the size of the plan that matters – it’s how well it sets the project, and your team, up for success.

The best project plans don’t try to predict the future perfectly right down to the minute. They create a shared understanding of what we’re doing, why it matters, and how we’ll get there together. They’re structured, realistic, and reviewed regularly – not created once and buried in a shared drive somewhere.

What does proper project planning look like?

1. A clear charter that gets sponsor sign-off before anything else.
2. A WBS that breaks deliverables into manageable chunks.
3. Roles, responsibilities, and timelines that are actually reviewed by the team.
4. Documented assumptions and risks that get revisited often, rather than being outlined at the start and then forgotten.

And if you’re using a framework like my SLAY Project Management program, all of this is built right in, step-by-step, so you’re not guessing what should come next, or wasting time recreating documents from scratch. So yes, this saying is correct – you do need a plan. But more importantly, you need a plan that’s dynamic, practical, and aligned with reality. Your goal isn’t just to check off the planning box – it’s to give your team a plan that gives them the clarity and confidence to deliver.

Meetings are Where Minutes are Taken and Hours are Wasted

Unfortunately, this one is sometimes painfully true. We’ve all been in those meetings that should’ve been an email, or worse – meetings where no decisions are made, no one knows why they’re there, and everyone leaves more confused than when they joined. That’s a waste of time and energy – especially on a fast-moving project.

But here’s the thing: meetings themselves aren’t the problem. Poorly run meetings are. The good news is, as the project manager, you have the power to make meetings focused, useful, and even enjoyable. Done right, your team won’t be repeating this catchphrase – they’ll be thanking you for keeping things on point,

How to ensure your meetings aren’t time wasters

1. Start with a purpose. Why are you calling the meeting? If you can’t answer that in one sentence, don’t send the invite.
2. Create a clear agenda – and share it ahead of time. Let people know what to expect, what to prepare, and how they’ll contribute.
3. Stick to time and stay on track. Be the person who respects everyone’s schedule by starting and ending on time.
4. Capture actions and assign owners. If there are no outcomes or next steps, was it really a meeting – or just a group complaint session?
5. Take minutes in real time, clean them up, and send them out right after the meeting. Don’t fall into the “I’ll do it later” trap – you won’t have time, and those notes lose value the longer they sit in your drafts. Minutes only matter if you use them. Otherwise, you’re just adding to the time you’ve already spent without driving anything forward.
6. If you’re dealing with standing meetings that no longer serve a purpose – cancel them or consolidate them. Your team will thank you.

The best meetings solve problems, align people, and drive momentum. Anything else is just a calendar block begging to be deleted.

That’s Not My Job

I hate this one. It’s a momentum killer, a collaboration killer – and honestly, a morale killer too. On projects, things move fast, overlap constantly, and don’t fall into neat little buckets, and we all end up wearing multiple hats. If everyone clings too tightly to their job description, problems slip through the cracks.

To be clear, I’m not saying everyone should be doing everything. People have roles for a reason, and burnout is real. But there’s a difference between protecting your workload and refusing to be helpful. When someone says, “That’s not my job,” and leaves it at that? It sends the message that they’re not invested in the outcome unless it benefits them directly. That’s a mindset that tanks project morale.

Helping the project team helps the project

As a project manager, your job isn’t to personally solve every issue – but it is your job to make sure every issue has a path to resolution. And if a team member flags a problem? That’s not an interruption – it’s an opportunity. Help them navigate it, even if it’s outside your official lane. That builds trust. That builds team strength.

I always say: People power projects. And the best project environments are the ones where people pitch in, step up, and stay solution-focused – even when the task isn’t written in black and white under their name. If something falls outside your scope, acknowledge it, but don’t ignore it. Redirect it, escalate it, or find the right person to help. Because what helps the project helps the whole team – and that IS your job.

What’s My Final Word on Classic Project Management Sayings?

Some of these sayings are timeless and others need a serious update. But what they all remind us is that project management isn’t just about tools and templates – it’s about how we think, how we communicate, and how we lead.

Whether you love these sayings or they drive you crazy, the fact that you’re taking the time to reflect on them says a lot about how invested you are in your own abilities as a project manager.

If you want to take your project leadership skills to the next level – whether you’re managing small initiatives or massive corporate programs – check out the links below to learn more about the ways I can help.

---

Which of these 4 ways can I help with your project needs?

1. Want to learn five things to do at the START of every project to bring it to success? Check out my free webinar.
2. Want a practical, step-by-step guide to managing projects? Check out my SLAY Project Management online course.
3. Looking for expert project coaching? Check out SLAY PRO.
4. Ready to start making organizational gains? My SLAY Corporate Project Management Program helps companies fix project-related issues.

Thanks For Sharing!