Promoted on Friday, managing on Monday: the first 90 days
Your best engineer now runs the team and nobody told them how. What the first ninety days should actually contain, and what the business owes them.
Read the articleGanesh HS ·
A manager prepared a forty-slide deck for a leadership review. Eight minutes were allocated, which she knew was tight, so she had rehearsed a brisk version. On slide three the managing director asked what she was recommending. She said she would come to that, and carried on. He asked again on slide five. The remaining thirty-five slides were never shown, the decision was deferred, and she left believing she had been treated unfairly.
She had prepared thoroughly for a presentation that was never going to happen. The deck was built to be delivered in sequence to an audience that would wait for the conclusion, and no senior audience does that.
It helps to understand the behaviour rather than resent it. Someone in a review meeting has usually read nothing in advance, has four other items that morning, and is trying to establish one thing quickly: what is being asked of them and whether they can say yes.
Until they have that, every slide is noise. The interruption is not rudeness; it is an attempt to get to the point so that the rest of the material becomes interpretable. A presenter who defers the answer is, from that seat, withholding the only thing that would make the presentation useful.
The practical consequence is that the build-up structure — context, analysis, options, recommendation — fails reliably upward, however well it is constructed. It is the structure most people were taught, which is why this goes wrong so consistently and feels so unfair when it does.
1 THE ASK
"I need a decision on X" or "this is for
information, no decision needed today."
2 THE RECOMMENDATION
"I recommend option B."
3 THE THREE REASONS
One line each. Not the analysis - the reasons.
4 THE MAIN RISK, NAMED BY YOU
"The risk is that delivery slips a month."
THEN STOP AND LET THEM DRIVE.
Everything else is backup you turn to when asked.Two things happen when you open this way. The interruption arrives at a useful moment rather than a damaging one, because by then they have the shape and their question is about substance. And naming the risk yourself changes your position in the room entirely — a presenter who has identified the weakness is treated as someone who has thought it through, whereas one whose weakness is found by the audience spends the rest of the meeting defending.
The forty slides do not go to waste. They become the appendix you navigate to when someone asks about the assumptions behind the third reason. Material held in reserve and produced on demand is far more persuasive than the same material delivered in sequence. Reordering a deck this way is a mechanical change that takes twenty minutes, and it is the first thing worth trying before anybody books presentation and public speaking training, because for a proportion of people it turns out to be the entire problem.
Most preparation time goes into the delivery of the planned content. Most of the meeting will be the questions. The allocation is backwards.
Everyone has them and most people avoid writing them down, because doing so makes them feel less prepared. They are precisely the questions a competent senior audience will ask, because they are the weak points and that is what experienced people notice.
Not a deflection. If the honest answer is that you do not know, the prepared version is what you would need in order to find out and how long that would take, which is a perfectly good answer delivered calmly.
There is almost always one — a cost, a date, a headcount, a comparison to last year. Not having it is the single most common way credibility is lost, and it is entirely avoidable.
Knowing in advance which objections you will accept keeps you from defending everything reflexively, which is what makes presenters look brittle rather than confident.
The instinct when asked something unexpected is to produce an answer, because silence feels like failure. Senior audiences are unusually good at detecting a constructed answer, and one detected costs more than the question would have.
"I don't have that with me. I'll send it by Thursday" is a complete and entirely acceptable answer, provided it is followed by sending it on Thursday. The presenters who lose credibility in review meetings are rarely the ones who did not know something; they are the ones who appeared to be improvising and were caught.
Most people asking for presentation training describe the problem as nerves. Nerves are usually the symptom of a structural issue rather than the issue, and they subside considerably once it is fixed.
A presenter who knows their opening ninety seconds precisely, has written answers to the three hard questions, and has accepted that they will be interrupted is far less anxious than one who has rehearsed forty slides and is privately aware the plan will not survive. The anxiety was rational; it was a correct assessment of a fragile plan.
What remains after that is ordinary performance nerves, which improve with repetition and do not particularly need managing. Audiences also notice them far less than presenters believe — the internal experience of nervousness is considerably more vivid than its external signal, which is worth knowing because much of the discomfort comes from imagining it is obvious. Where the anxiety is genuinely about the audience rather than the plan — a room that has historically been hostile, or a presenter who has been publicly corrected before — that is a different matter, and it usually sits alongside how disagreement is handled in the business generally, which conflict management capability addresses more directly than presentation coaching will.
In many Indian workplaces there is an additional constraint that no generic presentation advice addresses: a strong norm against contradicting seniority in public. A manager who has been asked for a recommendation, and whose recommendation differs from what the room expects, faces a real judgement rather than just a stylistic choice.
Two things help. State the recommendation as your analysis rather than as an assertion about what the business must do — "on these three criteria, option B comes out ahead" invites disagreement with the criteria rather than with you. And name the option they are expecting, with its merits, before explaining why you landed elsewhere. It demonstrates you considered it, which is usually what the senior person is actually testing.
This is the point where presentation and public speaking work overlaps with something broader — being able to hold a position under pressure from someone more senior is a communication skill and a confidence one, and the second is not developed by rehearsing slides. It is developed by doing it several times in a setting where the stakes are lower, which is what practice-based training provides and what the actual review meeting does not.
Brief, because the deck matters less than presenters think. One message per slide, stated in the title line rather than as a topic label. Numbers large enough to read from the end of the table. No slide you would need to talk over for more than ninety seconds.
And send the substance in advance, in the email body rather than as an attachment nobody opens — the ask, the recommendation, the three reasons. Some of the audience will read it, and those who do arrive ready to discuss rather than to catch up, which changes the meeting more than any improvement to the slides would. Where the harder problem is that the written version does not land either, that is a business writing and email etiquette issue and it is worth fixing first, since the email reaches more people than the meeting does.
Shorter than the slot. If you have eight minutes, build for four and expect the remainder to be questions. A presenter who finishes early with time for discussion is read as prepared, not as underprepared.
Some senior people do prefer the build-up, and it is worth asking beforehand which they want. Absent that information, leading with the recommendation is the safer default because it fails less badly.
Send the substance in advance in the email body — the ask, the recommendation, the reasons. Attachments are opened inconsistently, and a deck read without you presenting it is often understood differently from what you intended.
Answer the question asked, briefly, then say where you were going. Fighting to return to the sequence is what turns an engaged audience into an adversarial one, and the sequence was your convenience rather than theirs.
It is often worth more for them, because the rare presentations tend to be the high-stakes ones. What transfers is the preparation method rather than the delivery polish, and that is useful regardless of frequency.
Workplace behaviour and the management capability a growing business runs on.
Discuss a Custom Training ProgrammeYour best engineer now runs the team and nobody told them how. What the first ninety days should actually contain, and what the business owes them.
Read the articleGood trainer, engaged room, excellent feedback forms — and no observable difference six weeks later. What went wrong, and what a training day needs around it.
Read the articleFour people were copied, everyone read it, nobody moved. What separates an email that produces action from one that produces a thread.
Read the articleIdentify critical compliance gaps, payroll leaks, and hiring bottlenecks with a free 360-degree HR audit. Get a clear roadmap for your business.
Prefer the full picture? Request a free 360-degree HR audit.