How to Talk to Executives as a Project Manager (What Gets You Trusted, What Gets You Ignored)

Executives do not care about your project. At least, not the way you do.

You know every task, every dependency and every person on the team. They do not want to know any of that. They are listening for exactly three things. Give them those three things fast, and they trust you. Make them dig for them, and they stop listening.

I have been an IT project manager for over 10 years, and a big part of that job is standing in front of directors, VPs and sponsors and telling them where things stand. I have done that in a lot of steering committees. I have also spent a lot of time on the other side of the table. In my Live PMO, when members present their projects at a phase gate, I play the executive sponsor and ask the questions an executive would ask. So I have seen what gets a project manager trusted from both chairs, and it is rarely what people expect.

The trap most project managers fall into

You get time with an executive. Maybe ten minutes in a steering committee. You want to show you are on top of everything, so you prepare the way you would prepare for your own team.

You bring the full history. Every task. The technical detail of what went wrong, and what everyone has been working on. It feels thorough. It feels like the professional thing to do.

But think about that executive’s day. They might hear about five or six projects before lunch. They are not trying to understand your project. They are trying to work out where their attention needs to go.

So when you hand them everything, you are making them do the sorting. And to them, that looks like you cannot tell what matters. The work can be excellent and the update still makes the executive dig. That is how good project managers get tuned out.

The three questions every executive is listening for

Every update you give an executive is really an answer to three questions:

1. Do I need to worry about this?
2. Do I need to decide something?
3. Can I trust this person to handle the rest?

Answer those fast, and you get trusted. Make them dig for the answers, and you get ignored. That is what they are scanning for while you talk. Not your schedule. Not the history of the vendor relationship.

The third question is the one that shapes your career. If an executive feels they can leave a project with you, you get room to run it, and you get the next, bigger one. If they feel they have to watch you, you get more check-ins, more status requests, and less room to do your job.

Here are the six habits that decide which way that goes. For each one: what gets you ignored, and what gets you trusted.

Habit 1: Answer first

The first habit is the order you say things in.

Most people tell an update the way it happened. On Monday we started testing. On Tuesday the vendor sent the wrong file. On Wednesday we found the problem. By the time you get to where things actually stand, the executive has stopped listening. That is what gets you ignored.

What gets you trusted is the opposite order. The answer first. Then the reason. Then the detail, only if they ask. Like this:

“We are two days behind on testing, and we will still make the launch date. The vendor sent the wrong file on Tuesday, and that has been fixed. I will have the full test results on Friday.”

Here is a test for any update to an executive. If they stopped listening after your first sentence, would they know where things stand? If not, your first sentence is in the wrong place.

And when an executive asks you a yes or no question, start with yes or no. Then explain.

Habit 2: Report outcomes, not effort

The second habit is what you choose to report.

When people are nervous in front of executives, they report effort. “We had eleven meetings with the vendor.” “The team worked through the weekend.” “We have been really busy on the data migration.”

It comes from a good place. You want them to know the team is working hard. But effort does not answer any of the three questions. It does not tell them whether to worry, it does not ask for a decision, and it leaves them wondering why you are telling them.

Effort matters to your team. In front of an executive, what matters is what changed, what is at risk, and what happens next. So instead of the weekend, tell them what the weekend bought: “The data migration is finished, two days early. That gives testing the buffer it needed.”

If the team went above and beyond, absolutely say so. Just attach it to the result. “The team worked the weekend, and that is why we are two days early.” Now the effort means something.

Habit 3: Use their language, not yours

The third habit is the language you use.

Project managers spend all day with the people doing the work, so they pick up that language. Then they carry it straight into the executive room. “The API is failing authentication in the staging environment.” Every word of that is accurate, and most executives cannot do anything with it. They cannot tell if it is a five-minute fix or a disaster.

Executives think in four things: customers, money, dates and risk. If an issue does not connect to one of those, they cannot tell whether to care.

So translate it: “Customers cannot log in to the new portal yet. The team expects a fix this week. If it is not fixed by Friday, the March launch is at risk.” Same problem. Now they know whether to worry.

If they want the technical detail, they will ask. Have it ready. Just do not lead with it.

Habit 4: Never guess

The fourth habit is what you do when you do not know.

An executive asks you something you cannot answer. What does this do to the budget? When will the vendor deliver? The instinct is to answer anyway, because “I don’t know” feels like failing in front of someone important. So you guess. You give a number that sounds reasonable. And sometimes the guess is wrong.

The fastest way to lose an executive’s trust is to guess and be wrong. Because after that, they do not know which of your other answers were guesses too.

What gets you trusted is this: “I don’t have that number. I’ll get it to you by three o’clock today.” And then you do. That is not weakness. That is precision. When the number lands in their inbox at two forty-five, you have shown them you do what you say.

Habit 5: No surprises

The fifth habit is about timing, and it is the one that separates senior project managers from everyone else.

Picture it from the executive’s side. They are in a steering committee with the other leaders, and you announce their project is three weeks late. Now they are surprised in public, with no time to think about what to say. Even if the delay is not your fault, you have put them in a bad spot.

Never let an executive hear bad news for the first time in front of their peers. If they are going to be surprised, it should be in private, and it should be from you.

So talk to them first. A quick call the day before the meeting: “I want you to hear this from me before Thursday. Testing is going to slip by three weeks. Here is why, and here is what I am going to propose.”

Some people call this pre-wiring the meeting. By the time you are in the room, the executive already knows, already has a view, and might even back you up. It takes ten minutes, and it changes how they see you, because you just protected them.

Habit 6: Have the short version ready

The sixth habit is about time.

Executive meetings run over. The update before yours takes twice as long as planned, and the person running the meeting turns to you and says, “You’ve got two minutes.” If your update only works in ten minutes, you are stuck. You either rush it and lose the point, or you run over and lose the room.

What gets you trusted is having the short version ready before you walk in. Three sentences: where it stands, what is at risk, and what you need from them. Even in thirty seconds, that answers all three questions. And executives remember the project manager who gave them their time back.

What this looks like from the executive’s chair

Here is how this plays out over a few months, from the executive’s side of the table.

Picture a director with a new project manager on an important project. The first few updates are long. The history, every task, the technical detail. The director leaves each meeting not quite sure where things stand. So they ask for a written summary every Friday, and they ask someone from their own team to sit in on the project meetings.

Then the project manager changes how they report. The first sentence says where things stand. Issues come in customers, dates and money. Bad news reaches the director privately, the day before the meeting. And when the project manager does not know something, they say so, and the answer arrives that afternoon.

A few weeks later, the director stops asking for the Friday summary. A month after that, their team member stops coming to the meetings. And when the next big project comes up, the director asks for that project manager by name.

Nothing about the project changed. The work was good all along. What changed is that the director stopped feeling they had to watch it.

A five-minute checklist before any executive update

1. Write your first sentence. Where does the project stand, in one line?
2. Translate your biggest issue into customers, money, dates or risk.
3. Write down the decision you need from them. If you do not need one, say so. “No decision needed today” is one of the best things an executive can hear.
4. Check for surprises. Would anything in this update surprise them? If it would, call them before the meeting.
5. Prepare the thirty-second version: where it stands, what is at risk, and what you need.

And if they ask something you do not know, you already know what to say: “I’ll get that to you by three.”

Easy to trust beats impressive

Executives do not need you to be impressive. They need you to be easy to trust. Answer their three questions before they have to ask, and you will find yourself in more of those rooms.

If you want to practice this before it counts, that is what the phase gates in the Live PMO are for. In Live PMO mode, one of the four gates is a steering committee update: you present your project and a change request live to the person playing your executive sponsor, and you answer their questions on the spot.

Keep reading

• How senior PMs push back on executives (without getting fired)
• How to run a project status meeting without looking like a rookie
• How to run a project when you have no authority
• How project managers actually think