Presenting to leadership
Give a VP the bottom line first, or, as the leader, ask sharp questions that are still fair.
Case study: Suresh's slide fifteen
Suresh, an engineering manager in Chennai, got ten minutes with a New York VP to explain a delayed migration. He had fifteen slides. He started with the project history, then the architecture, then the team's challenges. At minute seven, the VP interrupted: "Sorry, are we late, and what do you need from me?" The answer was on slide fifteen. The next quarter, Suresh opened with one sentence: "We're two weeks late, the cause is a vendor API, and I need you to escalate with the vendor." The VP made the call that afternoon. The other fourteen slides became the appendix.
Takeaway: Leaders read the last page first. Put your conclusion and your ask in the first thirty seconds.
We're trained to build up to the conclusion and show all our hard work first. Senior global leaders want the bottom line up front and will ask for detail if they need it.
Presenting the update
Goal: Make the status, the risk and your ask clear in the first minute, then handle questions calmly.
Step by step
- Bottom line. Status in one sentence: on track, at risk or late.
- Why. One or two reasons, with numbers.
- The ask. Say exactly what decision or help you need.
- Details on demand. Offer the backup slides, don't force them.
Say this, not that
| The bottom line: we're two weeks behind, and I need your help with one decision. | First let me give some background about the project. | Leaders decide whether to listen in the first thirty seconds. |
| The main cause is the vendor's API. It's failing about one call in ten. | ||
| What I need from you is an escalation with the vendor this week. | Just for your information. | If you don't name an ask, you won't get help. |
| I have the details in the appendix if you'd like to go deeper. | Offering detail shows you have it without wasting their time. | |
| That's a fair question. The honest answer is we'll know by Friday. | Everything is under control. | Leaders trust honesty about uncertainty more than blanket reassurance. |
Model conversation
- You
- Thanks, Jennifer. Bottom line: the migration is two weeks behind, and I need one thing from you.
- Jennifer
- Okay. What's causing the delay?
- You
- The vendor's API. About one call in ten is failing, and they haven't responded to our tickets in nine days.
- Jennifer
- And what do you need from me?
- You
- An escalation with their account lead this week. If they fix it by the fifteenth, we land on the new date.
- Jennifer
- What's your confidence in that new date?
- You
- About seventy percent. The rest depends on the vendor. I'll update you every Monday until it's done.
- Jennifer
- Clear. I'll call their VP today. Send me the ticket numbers.
Asking tough questions
Goal: Get to the real status, risk and ask quickly, while leaving the presenter respected, not humiliated.
Step by step
- Set the frame. Tell them what you need: status, risk, ask.
- Ask one at a time. One clear question, then let them answer fully.
- Probe the evidence. Ask how they know, and what would change the picture.
- Close with support. Say what you'll do and thank them for the honesty.
Say this, not that
| I've got ten minutes. Give me the status, the biggest risk, and what you need from me. | A clear frame helps the presenter give you what you need. | |
| What's your confidence in that date, as a percentage? | Are you sure? Really sure? | A number is easier to answer honestly than pressure. |
| What would have to go wrong for us to miss it? | ||
| Thanks for being straight with me. That's exactly what I need. | Why didn't anyone tell me this before? | If bad news gets punished, you'll stop hearing it. |
| Let's take the detail offline. For now, what's the one decision you need from me? | Skip all this, just tell me. | Redirect firmly without making them feel small. |
Model conversation
- You
- Thanks, Karthik. I've got ten minutes, so start with the status, the risk, and what you need from me.
- Karthik
- Sure. We're on track for the March launch, but there's a risk on performance testing.
- You
- Okay. What's your confidence in March, as a percentage?
- Karthik
- Honestly, about sixty percent.
- You
- Thanks for being straight. What would have to go wrong for us to miss it?
- Karthik
- If the load tests fail at ten thousand users, we'd need two more weeks to tune the database.
- You
- Got it. What do you need from me to raise that sixty percent?
- Karthik
- Approval for a second performance engineer for one month.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.