“Just checking in.” “Sorry to bother you.” “Hopefully by Friday.”
If you have said any of those at work this week, this article is for you. Every one of them tells the people above you that you are new. Not because the work is bad. It is the words.
There are seven phrases like this, and each one has a replacement you can use in your very next meeting.
I have been a project manager for over 10 years, and I have sat in a lot of status meetings and steering committee updates. I have also helped dozens of people break into project management, and I have listened to a lot of them present their first projects. These seven phrases come up again and again. Most of the people who say them are good at the work. That is what makes it so frustrating.
The people who decide your next promotion, or your next project, mostly hear you in meetings and read you in email. In those moments, your words are all they have to go on.
You get judged on the work and on how the work sounds
When you move into project management, you get judged on two things: the work, and how the work sounds.
The work is the plan, the schedule and the risks. The sound is every email, every update, and every time you speak up or present in a meeting. And the people above you see a lot more of the sound than the work. A director might read your plan once. They hear you every week in a status update.
A lot of people come into project management from support roles: coordinator, analyst, admin, operations. In those jobs, being polite and not bothering anyone is part of the job. So you pick up a way of talking that is soft on purpose.
That is not a flaw. It is a habit. But in a project seat, it costs you. The habits that made you a great coordinator are the same habits that make you sound like a coordinator when you are trying to be the project manager.
The one rule that fixes all seven
Here is what all seven phrases have in common. A project manager’s job is to take uncertainty off other people’s plates. Phrases like “just checking in” and “hopefully” hand it right back. They make the other person do the worrying for you.
The sponsor does not want to wonder whether the date will hold. The director does not want to wonder what you need from them. That is what they have a project manager for.
One rule fixes all seven: swap the feeling for a fact, a date or a decision.
- “Hopefully” becomes a condition and a date.
- “Just checking in” becomes a deadline.
- “What do you want me to do?” becomes a recommendation.
You are not trying to sound tougher or more confident. You are trying to give the other person something they can act on.
The seven below run in order, starting with the ones you will probably say this week and ending with the ones that matter most in front of executives. They all use one running example: a system rollout with a vendor, a test phase, a finance dependency and a go-live date on the 15th.
1. “Just checking in”
The first one is in almost every inbox. You send it when you need something from someone: an approval, a document, a test result.
Here is what they hear: this is not urgent, and I am not sure I am allowed to ask. The word “just” makes the request smaller. And “checking in” does not actually ask for anything, so it goes to the bottom of the pile.
Say this instead:
“I need your sign-off on the test results by Thursday at 3 p.m. That keeps go-live on the 15th.”
Now they know what you need, when you need it, and what happens if they do not deliver it. People are busy, and busy people act on deadlines. They do not act on check-ins.
The same goes for “just following up” and “just circling back.” Different words, same problem.
2. “Sorry to bother you”
This is the one people bring with them from support roles, where not bothering anyone is part of the job.
When you open with an apology, you have told the other person your request matters less than whatever they were doing. And you have told them before they even know what the request is.
Say this instead:
“Do you have five minutes? It affects the go-live date.”
You are not interrupting them. You are bringing them something they need to know. Lead with why it matters, and you will not feel the need to apologize.
3. “I’ll try”
Someone asks if you can deliver something by Friday, and you say, “I’ll try.”
It feels honest, because you really do not know yet. But what they hear is: probably not. And when it does slip, they are surprised.
Stakeholders can handle a delay. What damages trust is being surprised by one.
Say this instead:
“I can have it Friday if I get the data from finance by Wednesday. If that’s late, I’ll tell you on Wednesday.”
That is a real commitment, with the condition out in the open. And you have given them an early warning point, so nothing about Friday will surprise them.
Just do not overcorrect into “yes, definitely” when you do not know for sure. A promise you cannot keep is worse than “I’ll try.”
Trying to break into project management? Start here: How to become a project manager, the full step-by-step breakdown of the path.
4. “Hopefully”
As in: “Hopefully we’ll be able to deliver by Friday.”
What the listener hears is that you do not have a plan. You have a wish. “Hopefully” means the date depends on luck, or on something you have not named yet.
This one hides in other words too: “it should be fine,” “fingers crossed,” “we’re aiming for Friday.”
Say this instead:
“It will be done by Friday if the vendor delivers the configuration by Wednesday. I’ll confirm by noon on Wednesday.”
You have not removed the uncertainty. You cannot. But you have shown exactly what the date depends on, and when they will get an answer. That is the difference between hoping and managing the project.
5. “We’re a little behind, but”
This is how most people deliver bad news. They shrink it, and then they rush to the excuse.
The problem is that executives hear softened bad news all the time. So when you say “a little behind,” they assume it is worse than you are telling them.
Say this instead:
“Testing is five days behind, because the vendor delivered late. We can win back three of those days by running a second test shift. For the other two, I need a decision from you.”
The number comes first. Then the cause, then the plan, then the ask.
Bad news delivered straight builds trust. Softened bad news costs you trust.
6. “What do you want me to do?”
You hit a problem you cannot solve alone, so you take it to your manager or your sponsor. That part is right. Escalating is part of the job.
But when you ask what they want you to do, you have handed them the problem and the thinking. Now they have to do your job.
Say this instead:
“We have two options. We can move the go-live date by two days, or we can cut the reporting module from the release. I recommend moving the date, because the reporting is what finance signed up for. I need your decision by Thursday.”
Never take a problem to your boss and ask what they want you to do. Take two options and a recommendation. Then all they have to do is decide. And even if they pick the other option, you still look like the person running the project.
If you genuinely do not know which option is better, say what would decide it, and when you will know. That still counts as doing the thinking.
7. “Does that make sense?”
You finish your update, and you ask, “Does that make sense?”
It sounds considerate. But it tells the room you are not sure you explained it well, or you are not sure they followed it. And the meeting ends without a decision.
Say this instead:
“So the decision I need from you today is whether we move the date or not.”
Every update should end with the one thing you need from the people in that room. If you do not ask for it, you will walk out without it.
If you really do want to check that they followed you, ask “What questions do you have?” instead. That invites real questions, not a polite nod.
The same update, said two ways
Here is what this sounds like when it all comes together. Same project. Same facts. Two project managers giving the same update to a director.
The first one says:
“Sorry to bother you. Just checking on testing. We’re a little behind, but hopefully we can catch up by Friday. I’ll try to get the vendor moving. What do you want me to do about the go-live date? Does that make sense?”
The second one says:
“Testing is five days behind, because the vendor delivered the configuration late. We can win back three days with a second test shift. For the other two, we can move go-live or cut the reporting module from the first release. I recommend moving the date. I need your decision by Thursday.”
Same problem. Same five days. One sounds like the project is running them. The other sounds like they are running the project.
You already know which one gets handed the next project.
How to start changing this week
- Pick one. Do not try to fix all seven at once. Pick the phrase you catch yourself saying most, and fix that one this week. If your meetings get recorded, listen back to five minutes of yourself giving an update. You will hear your phrase straight away.
- Check your email before you send it. Search the draft for “just,” “hopefully,” “sorry” and “I’ll try.” Every time you find one, ask what fact, date or decision belongs there instead.
- Before any update, write down three things: where it stands, the date that matters, and the one thing you need from the people in the room.
And expect this: the first few times you say it the new way, it will feel blunt. It is not. To the person listening, it sounds like someone who has it handled.
Swap the feeling for a fact, a date or a decision
Do that, and you will sound like a project manager before you even have the title.
If you want to see what this looks like at the executive level, read how senior PMs push back on executives.
And if you want somewhere to practice this out loud before it counts, that is what the phase gates in my Live PMO are for. In Live PMO mode, you run a simulated project, present it at each of the four phase gates, and answer questions from the person playing your stakeholder.
Keep reading
- 11 words that instantly make you sound like a project manager in your next interview
- How to talk to executives as a project manager
- How to run a project status meeting without looking like a rookie
- How to translate coordinator work into PM experience (without lying)
Ready to gain real PM experience?
Sounding like a project manager takes practice out loud. Inside The Eddie System you work through governed projects across many industries in a live PMO environment, and in Live PMO mode you present your project at each of the four phase gates and answer questions from the person playing your stakeholder.