Short version: stakeholder management is done before the meeting, and executive presence is what the room concludes about your judgment during it. Before the room, map who decides and what they are protecting, pre-wire the decision in one-to-ones, lead with the outcome and the decision you need, and keep a no-surprises cadence. In the room, make the point first and stop, hold your number when it is challenged, speak at the altitude of the business, and answer the hard question in one sentence. Both are skills rather than traits, and both are built against real rooms, not in the abstract.
I held the product seat. At New Relic I was the EVP running product, presented product strategy to a board with partners from Benchmark, Trinity Ventures and Madrona and former executives of Twitter, Informatica and SAP, gave the global keynote at our customer conference and led the customer advisory boards. I now coach Chief Product Officers and the leaders one level below them, and the two pieces of feedback that bring them to me most are the two in the title. This is what I tell them.
Why product leaders get this feedback
The product seat holds responsibility for outcomes without authority over most of the people who deliver them. Sales, engineering, finance and the CEO each read your roadmap through a different lens, and none of them reports to you. Influence is the job. So a product leader can be the best product thinker in the company and still be read as the person who manages the roadmap rather than the executive who shapes the business.
The seat is judged in a handful of rooms: the executive meeting, the board, the customer advisory board, the all-hands after a slipped date. The feedback usually arrives as "needs more presence" or "work on stakeholder management", which tells you the room has formed a view and not what to change. The first move is to make it specific: which room, which behaviour, and who noticed. If the answer is "everywhere", no one has looked closely yet, and the work starts with one real meeting on your calendar.
Stakeholder management: manage the landscape, not the relationships
The common mistake is to treat stakeholder management as being liked by the people around the table. It is closer to a map and a sequence. The map says who matters for this decision; the sequence says what happens before the meeting so the meeting can end in a decision.
Map who decides, who can stop it, and who the CEO listens to
For each initiative that matters, write down, from the real power landscape rather than the org chart: who decides; who is measured on its success or failure; who can kill it; who has informal influence, which usually means the person the CEO listens to; and who is under-informed now but high-impact when they surface late. Then, for each name, what they care about this quarter (revenue, predictability, risk, growth), what would make them look successful, what they will resist and why. A simple power and interest grid is enough. Update it quarterly, because the map goes stale faster than the roadmap.
Pre-wire the decision
Do not present a consequential recommendation to a full room for the first time. Meet the people who can decide or block it one-to-one beforehand, find the objections they would not raise in a group, and fold the valid ones in. By the time the meeting happens, the people who matter should already agree, and the meeting confirms it. Treat these conversations like customer discovery: "What does success look like for you this quarter?" and "Where do you see the biggest risk?" Listen more than you pitch. People support what they helped shape.
Lead with the outcome and the decision you need
Executives care about risk, time to value, the trade-offs and the competitive position, not the feature list. Frame the update in that order: the business problem and the cost of doing nothing; the options considered and why this one; the trade-offs and the residual risk; and what you need from them, which is a decision, air cover, resources or just visibility. "We are building X" is a status report. "We are de-risking Y by Z date, and here is the decision I need" is an executive update. Translate product metrics into business ones on the way: adoption into retention, velocity into time to revenue, latency into churn risk.
No surprises: the cadence
Executive friction peaks when a leader feels caught off guard. A predictable rhythm removes most of it: a short written update weekly and a deeper review monthly, in the same shape each time, status against the outcome first, then risks and blockers, then asks, with the detail in an appendix. Silence creates anxiety and invites intervention; a dull, reliable update earns you the room's attention for the moments that need it.
Conflict is information
When sales and engineering disagree about your roadmap, surface the goals underneath instead of debating the solution: "You are optimising for bookings this quarter and we are optimising for retention next year. Which constraint is binding right now?" That moves the conversation from opinion to priorities. Then decision hygiene: who decides, who inputs, who is informed, and a written record of the decision and the reason, so it is not relitigated in the corridor.
At New Relic, when I arrived, our largest customers told us there had been little innovation for nearly three years, and sales had no confidence that product and engineering could deliver. We made three structural changes rather than relationship ones: a general manager to align product and engineering on business metrics and end the finger-pointing; a quarterly planning session that set a fixed share of engineering capacity for the roadmap, bugs and sales requests; and a cross-company escalation meeting where any change to the roadmap had to be agreed by the leaders of the company. At the next customer advisory board, the CTO of Disney and an SVP at Capital One said we had delivered more of what they wanted in six months than in the previous three years. That is stakeholder management as structure: the arguments moved into one room with the people who could decide, and the new products that followed added $50M-plus in incremental ARR.
Executive presence: what the room concludes about your judgment
Executive presence is not charisma, and it is not the suit or the slide template. It is what a room of people with power decides about you in the first minute and the hard minute: whether you are prepared, whether you believe your own number, whether you will say the inconvenient thing, and whether you can hold a position calmly when it is challenged. It is tested under pressure, not in rehearsal, which is why it breaks in the executive meeting for leaders who were fine in the prep session.
The point first, then stop
Executives are context-switching and short on time. Open with the decision, the risk or the ask, then the evidence when they want it. Instead of five minutes of background on API latency: "We need to move the launch two weeks to prevent churn on enterprise accounts. Here are the two paths." Then stop. Cut the qualifiers and the filler; in a senior room a hedge reads as doubt, and the sentence the room came for is usually buried under the background you prepared.
Hold the number when the CFO frowns
This is where presence breaks most often. A director says the plan does not look realistic, the tone sharpens, and the reflex fires before reasoning catches up: you over-explain, concede a point you did not need to concede, or trim the number you spent three weeks building. Have something short to do in that window. Acknowledge the concern in one sentence, name the trade-off, state the action and the date. Do not defend to the death, and do not retreat. A number that moves when pressed teaches the room to press harder next time.
Speak at the altitude of the business
The expert speaks in features, sprints and velocity. The executive speaks in revenue, retention, risk and the decision. Most of the gap between "seen as tactical" and "seen as strategic" is this translation, done out loud, in the language of the company rather than the function. The question to ask of your own sentence before you say it is "so what", and the answer is what the room hears.
The hard question in one sentence
Write down the ten hardest questions your room will ask this quarter. Answer each in one clear sentence, with the assumption it rests on, and rehearse the answers out loud until the short version is the one that comes out under pressure. Then stop talking. The long defence, the early concession and the flurry of data that buries the point are the three ways a good answer goes wrong.
Be read as the executive, not the expert
At the executive level, presence is often less rather than more. The leader who has to add to each conversation, who proves the point with a fifth slide, who argues each position, reads as the smartest person in the function. The executive asks the question instead of proving the answer, pauses instead of filling the silence, and speaks less so that when they do speak the room pays attention. Owning a miss plainly belongs here too: a dropped metric presented as a clear reason to change course earns more trust than a sugar-coated one.
The board: where both skills are tested at once
A board presentation of product strategy is stakeholder management and executive presence in one hour. Before it: the pre-read three days ahead; the one-to-ones with the directors who care most about the decision; the deck built as a decision document, with the recommendation on the first slide, the trade-off stated, and the risks named before a director names them. In it: revenue, retention and risk first, features second; the point first; the number held; the hard question answered short. The questions I was asked when I presented product strategy to the New Relic board were about the number and the risk, almost never about the roadmap itself.
A thirty-day practice
- Week one. Pick the next real room on your calendar. Map the stakeholders for the decision in it. Write the ten hardest questions the room will ask.
- Week two. Pre-wire: the one-to-ones, the objections surfaced, the valid ones folded in. Rewrite your update to open with the decision and translate the product metrics into business ones.
- Week three. Rehearse out loud, on camera if you can stand it: the opening sentence, the number held while someone pushes, the one-sentence answers.
- Week four. The room. Then a debrief the same day: what held, what moved, what the room now believes about you. Ask two people whose read of you matters how you came across, so "needs more presence" becomes a specific behaviour you can work on next.
Repeat on the next room. The behaviour changes in weeks; the room's view of you changes more slowly, because people who have read you one way for two years need to see the new behaviour several times before they update. That lag is normal and is not evidence the work failed.
When a coach helps, and when one does not
If the gap is polish, voice and slides, a presentation coach is the right call. If you know what to say and still fold at the moment of pushback, that is coaching work on the reaction itself, done against real rooms with direct feedback; it is what my executive presence coaching is built for, as an eight-week bootcamp for the role or a project for one room. If the organisation's definition of "executive" excludes the way you lead, no amount of coaching fixes the environment, and the honest conversation is about fit. For the product seat specifically, the CPO coaching page and the guide to finding a Chief Product Officer coach cover the rest of the job.
What product leaders ask about presence and stakeholders
What does "needs more executive presence" mean for a product leader?
Usually that in a senior room you are read as the expert rather than the executive: over-explaining when challenged, speaking in features rather than business outcomes, trimming the number under pressure, or going quiet when you disagree. It is feedback about a perception, so the first step is to find the moment it formed: which room, which behaviour, who noticed.
Is stakeholder management just politics?
No. Politics is managing what people think of you. Stakeholder management is knowing who decides, what they are protecting and what they need from you, then getting the decision made before the meeting rather than in it. It is a map and a sequence, and it works for people who dislike politics.
How do I present product strategy to the board?
Revenue, retention and risk first, features second. Send the pre-read three days ahead, pre-wire the directors who care most, put the recommendation on the first slide with the trade-off and the risks named, and rehearse the hardest questions in one sentence each. Expect the questions to be about the number and the risk, not the roadmap.
How long does it take to build executive presence?
The behaviour changes within weeks when you work it against real rooms: most leaders see the first meeting go differently inside the first month. The room's perception lags, often by a quarter or more, because people need repeated evidence before they update a view they have held for years.
What is the difference between stakeholder management and executive presence?
Stakeholder management is what you do before and between meetings: the map, the one-to-ones, the cadence, the decision hygiene. Executive presence is what the room concludes about your judgment while you are in it: the point first, the number held, the hard question answered short. Product leaders need both, and the board is where they are tested together.
Should I hire an executive presence coach?
When you know what to say and still fold under pressure, or when the feedback keeps coming and you cannot turn it into a behaviour on your own. A coach who has sat on the other side of the table, as the director asking the question, can rehearse the real rooms with you. If the gap is delivery and slides, a presentation coach is cheaper and faster.