Master executive influence and stakeholder management. Learn proven tactics from product leaders at Slack, Box, and Webflow to build trust, align incentives,...
How to Influence Executives: Master the Art of Stakeholder Management and Drive Results
Key Insights
- Executive influence is the highest-leverage skill for product leaders in the age of AI—more critical than ever as automation handles technical execution
- Understand executive calendars and incentives before pitching; they're running meeting-to-meeting with minimal context, not thinking about your problems
- Treat executives as your primary users by applying the same curiosity and empathy you use for customers to understand their goals, success metrics, and board pressures
- Build trust through small wins by demonstrating domain expertise, killing bad ideas, and consistently delivering results that align with their strategic objectives
- Context matters more than content; spend 30-60 seconds setting the stage before diving into your pitch to ensure executives can actually engage with your ideas
Understanding the Executive Mindset: Why Your Pitch Fails
When product managers struggle to secure executive buy-in, they often blame their leaders for "not getting it." But here's the uncomfortable truth: if executives aren't buying your idea, it's your job to change their minds. This isn't about politics or manipulation—it's about becoming genuinely curious about how the people making decisions actually think.
Most product managers fundamentally misunderstand executive decision-making. They assume their leaders have the luxury of focused attention on their projects. In reality, an executive's calendar is like a strobe light constantly flickering on and off. An executive wakes up at 8 AM facing an overwhelming list of urgent matters: budget meetings with finance, interviews for new hires, people problems, legal issues, and product reviews back-to-back. Between meetings, they might not have gone to the bathroom, let alone thought about your pitch since you last spoke three weeks ago.
This context deprivation is critical. Your executive hasn't had the time, energy, or mental space to focus on your problems. They're context-switching at an intensity most product managers never experience. Everything landing on their plate feels like an emergency. When you walk into their office or join their Zoom call, you can't assume they've prepared. You have to help them get into the right mindset in the first 30 seconds.
The key tactical move: spend exactly 30-60 seconds at the start of every executive meeting setting the stage. Say something like: "We're here to discuss X, Y, and Z. Last time we met, we left off here. Today's goals are A, B, and C. Here's how we'll run this meeting." Then stop talking. If you go over 60 seconds, you've already lost them. After setting the stage, ask: "Is there anything else you were hoping to cover today?" This signals respect for their time and opens the door for them to bring their real concerns to the table.
This simple framework acknowledges the harsh reality of executive life while also demonstrating that you understand and respect their constraints. It shows you're not there to waste their time.
Aligning Your Pitch with Executive Incentives: The Universal Lever
People vastly underestimate how powerful incentive alignment is when influencing leaders. Before you ever step into a room to pitch an idea, you need to know: What are their goals? What are they trying to achieve? How are they measured? What's success for them?
Only after answering these questions should you craft your pitch. Here's how to structure it: Connect your proposal directly to their success metrics. Don't talk about your product in isolation. Instead, explain how your idea helps them move the needle on what they care about. If your CEO is focused on enterprise expansion, show how your feature helps land bigger deals or increases customer retention. If your CFO is worried about burn rate, demonstrate how your initiative reduces engineering hours or improves operational efficiency.
This isn't about telling them what they want to hear—it's about genuinely understanding where they're optimizing and showing that your work serves that optimization. Many executives face board pressure, competitive threats, or specific quarterly objectives. Ask them directly: "What's the board pushing you on right now?" or "What's your biggest concern this quarter?" Everyone has a boss, even the CEO. Understanding their pressures gives you the information you need to position your work as part of their solution.
Consider a real example from Slack: The executive team believed the company had lost its edge on product craft. Engineers and designers felt the product experience wasn't delivering the 10x usability that defined Slack's identity. Instead of just complaining about it internally, the team framed a "Customer Love Sprint"—two weeks where engineers stopped all other work to "paint the inside of the cabinets," fixing rough edges and shipping quality-of-life improvements.
This initiative aligned perfectly with what executives cared about: rebuilding brand perception, differentiating from competitors, and showing up for users in a way that would drive retention and word-of-mouth growth. The result? Engineers shipped 65 improvements, executives were thrilled, and the company reinforced the values that made it special. The product work didn't change—the framing did. By connecting it to executive incentives, it became impossible to say no.
The Art of Being a Communication Chameleon
Executives are not monolithic. Some prefer data dashboards; others respond to customer stories. Some want a 50-page document to read quietly before discussion; others want a 10-minute verbal walk-through. Some think in terms of ROI; others care about mission impact.
Your job is to become a "communication chameleon." Study how your executive actually consumes information. Ask their executive assistant, their Chief of Staff, or colleagues who've successfully pitched to them: What medium works best? Do they prefer written memos or verbal discussions? Do they want dense data or high-level narratives? What sparks their genuine interest?
Then, deliver your message in that format, using that language. This isn't pandering—it's respect. You wouldn't present the same way to a customer without understanding their context and preferences. Your executive deserves the same thoughtfulness.
One powerful tactic: Ask more interesting questions than "What's top of mind?" That phrase has become so generic that it's lost all power. Instead, ask: "Tell me what the board is pushing you on," or "What's keeping you up at night about competitive threats?" or "How are you thinking about resource allocation between our two priorities?" These questions dig deeper and reveal the real tensions and pressures your executive is navigating.
Understanding communication style also means recognizing that executives want to be successful. They want to be good at their jobs. If you approach them with genuine curiosity about their worldview, their constraints, and their strategic vision—rather than just seeking approval for your plan—everything changes. You shift from a supplicant asking for resources to a partner invested in their success.
Building Trust: The Foundation of Influence
Trust doesn't happen overnight, especially if you're new to an organization or new to working with a particular executive. Building trust requires consistent demonstration that you respect their judgment, take their feedback seriously, and deliver results that matter.
One of the most powerful ways to build trust is knowing when to kill or deprioritize things. Everyone in a company is constantly trying to acquire more resources, more headcount, more investment. When your executive suggests an idea off-hand—"Oh, we should really explore that market segment" or "Have you thought about building X feature?"—they might not mean it as a mandate. But most product managers treat every executive comment as gospel, immediately reorganizing their roadmap.
Instead, ask clarifying questions: "That's a really interesting idea. How urgent do you think that is?" or "Do you think that trumps these three other priorities we're currently working on?" Often, the executive will say, "Oh no, that's just a random thought. Put it on the backlog." But if they do indicate it's truly important, listen. Do the thing they say should take priority.
This seemingly small habit—asking for context instead of assuming urgency—demonstrates that you're thinking strategically, not just reactive. It also gives executives permission to think out loud around you without you immediately running off to reorganize everything.
Another trust-builder: deliver on your domain expertise. You were hired because you're the deepest person in the room on your product. Your executive isn't looking for a "yes person" who executes every idea exactly as stated. They're looking for expert pushback when needed. If you disagree with something, say so—but do it thoughtfully. Bring a customer anecdote, research data, or strategic reasoning. Show that you're disagreeing from a place of expertise, not ego.
The best version of this: ask curious questions to understand where their idea comes from. "That's interesting—what led you to that belief?" or "Tell me more about what you're seeing in the market that suggests we should go that direction." Often, their insight will teach you something valuable. Sometimes, their concern is valid and forces you to strengthen your thinking. Either way, you're demonstrating respect for their expertise while also standing firm in your own.
Preparing for the Pitch: The Art of Strategic Incompleteness
Many product managers go into executive presentations over-prepared. They bring deck after deck of data, exhaustive research, and proof that they've done their homework. They're trying to be so convincing that the executive simply can't say no.
This approach backfires. Executives don't have the attention span or the mental energy for 47 slides of supporting data. Their eyes glaze over. They check their phone. You lose the room.
Instead, follow the "Minto Pyramid" structure: Start with your main recommendation at the top. Then outline the alternatives you considered. Finally, provide supporting evidence in an appendix. This inverted structure gets to the core message immediately while signaling that you've done thorough thinking.
More specifically, when presenting options, never present just one solution. Always present your recommendation plus at least two other viable alternatives you seriously considered. Why? Because it shows you've thought expansively and aren't wedded to one idea. It also creates space for productive debate. If an executive doesn't love your recommendation, they can see the alternatives instead of feeling like you're backed into a corner demanding they accept option A or nothing.
One tactic that works surprisingly well: create a "Themes for Discussion" section at the top of your document. After you've written your full proposal and the executive has commented (executives always comment—they mark documents with 100 red comments), bubble up only the truly important, controversial, or discussion-worthy pieces. For the rest—the clarifying questions about timeline or staffing—tell them you'll answer offline.
When you write something like, "Rachel, looking at your comments, here are the three themes I think we should discuss live: Theme 1, Theme 2, Theme 3. On the other questions about timeline and resources, I'll follow up with you offline. Did I get your concerns right?" you accomplish multiple things: You show you respect their time by being selective about what requires live discussion. You signal that you're actually reading their feedback and taking it seriously. You create psychological safety for them to be honest in the live discussion because you've already handled the administrative stuff. That's when the really good insights emerge.
The Power of Early, Informal Conversations
Many product managers only interact with executives during formal pitch meetings. This is a massive missed opportunity. The real leverage in influence comes from building trust and understanding before you need buy-in on something big.
One of the best practices: office hours or informal alignment conversations. At Webflow, they explicitly build this into the culture. At Slack, before you'd formally pitch a major initiative to the CEO, you could have a casual 30-minute conversation called "Hey Stewart, what do you think?" It was positioned as a user interview—you were downloading his expertise, his belief system, his past experiences. There was no formal agenda, no ask at the end. You were just learning.
These conversations serve multiple purposes. First, they give you information about how that executive thinks, what they care about, what concerns them. Second, they build relationship capital outside of high-stakes moments. Third, they often surface strategic context you never would have found in a formal pitch. An executive might mention a board conversation, a competitive threat, or a customer dynamic that completely changes how you should think about your work.
The barrier to this? Many product managers feel like they can't ask for time from busy executives. But if you don't seek this insight early, you might spend weeks building something that's completely misaligned with what the executive cares about. You'll learn about that misalignment only when you formally pitch—and then it's too late.
Ask for 30 minutes to chat about a strategic topic. Position it as you wanting to learn from their perspective. Most executives appreciate this, especially if you've clearly thought about what you want to understand from them. The investment in these early conversations pays massive dividends when you do eventually pitch something significant.
Understanding Executive Context and Constraints
Here's a fundamental tension that many product managers miss: executives operate with different constraints and capabilities than you do. You might feel limited by your team of four engineers, your current tooling budget, and your quarterly timeline. But your executive can reallocate people within the organization, approve unexpected expenses, shift priorities, or elevate projects to change their urgency.
This means you should approach resource constraints differently. Instead of saying, "This isn't possible with our current team," say: "With our current resourcing—X engineers, Y tooling, and Z investment—here's what we can deliver in the base case. But here's the 10x scenario I think matters. If that's aligned with your priorities, here's what I need to be successful: eight more engineers, closer alignment with marketing, or an hour of your time twice a week."
This frame accomplishes two things. First, it shows your executive the scope of what's possible if they invest. Second, it explicitly identifies the constraints holding you back—and many executives can help remove those constraints if they understand what matters. You're not asking them to magic away reality. You're saying, "Here's the wall I'm hitting. Can you help me get over it?"
Many product managers never do this. They accept their constraints as immovable and then struggle to convince executives that their vision matters. But executives are often uniquely positioned to move resource constraints if something truly matters to the company.
Building Momentum Through Cross-Functional Advocacy
When you're pitching something truly novel or ambitious—a new product category, a major pivot, a significant investment—the executive's decision often hinges on whether peers and other leaders also believe in it.
This is where cross-functional influence becomes critical. You need advocates who will say, "Yeah, I've talked to customers about this. I think it could drive significant expansion" (Customer Success perspective). Or: "Our team thinks this could drive a 10x increase in sign-ups" (Marketing perspective). Or: "We've explored this in a proof of concept and it's technically feasible" (Engineering perspective).
Building this coalition happens through socializing your idea widely before the executive pitch. Use prototypes, messy proof-of-concepts, user interviews, and small experiments to create a groundswell of belief across the organization. When your executive sees that multiple trusted leaders believe something matters, their bar to fund it drops dramatically.
This also aligns with how product leaders should operate in a world of AI and agents. The leverage isn't in being the sole decision-maker. It's in deciding what matters, building consensus around that decision, and then unleashing teams to execute at full speed. In a world where building is becoming easier and faster, deciding what to build and aligning everyone on that decision becomes the hardest and most valuable work.
The Bigger Picture: Influence in the Age of AI
As AI becomes better at writing, analyzing data, running experiments, and even writing code, the traditional product manager skills of execution and synthesis become less differentiating. The question becomes: What can humans do better than AI?
The answer is influence. AI cannot yet be an anthropologist. AI cannot derive truly novel insights through deep user empathy and understanding of market dynamics. AI cannot recognize industry trends that others are missing. And AI cannot persuade an organization that a particular direction matters.
This is the 10x skill for product leaders in 2024 and beyond: deciding what to build, building consensus around that decision, and maintaining clarity about strategy and beliefs while teams move at increasing speed. As execution gets easier, deciding what's worth executing becomes harder and more valuable.
For product managers concerned about AI replacing their roles, the answer is clear: Double down on influence. Become exceptional at understanding what users truly need. Become deeply knowledgeable about your market. Become skilled at building consensus across functions. Learn to ask better questions and listen more deeply. These are inherently human skills that AI complements but cannot replace.
Similarly, as organizations bring in AI agents and automation to accelerate work, you'll need to articulate your beliefs, codify your product philosophy, and teach agents (and humans) what matters. This requires even greater clarity of thinking and communication—the exact skills this entire conversation is about.
Authenticity in Influence
One final, crucial point: You don't have to be a particular personality type to be good at influence. You don't have to be extroverted, charismatic, or gregarious. You don't have to change who you are fundamentally.
Throughout a career, many talented product managers receive feedback to "show up more aggressively," "be more decisive," or "act more like a leader." Sometimes that feedback contains useful information. But often, it's just asking you to be someone you're not. The real superpower is learning to do these things—building trust, asking great questions, aligning stakeholders, moving people toward consensus—in a way that's authentically you.
Whether you're analytical and data-driven, creative and visionary, introverted and thoughtful, or outgoing and collaborative, you have tools to build influence. The specific tactics and approach will differ based on who you are. But the underlying principles—curiosity, empathy, respect for others' constraints and incentives, genuine learning, and clear communication—those are universal.
Find the version of influence that feels true to you. Then double down on it. Your authenticity is actually what makes you credible and trustworthy in the long run.
Conclusion
Influence isn't politics. Politics is about manipulating outcomes for personal gain. Influence is about increasing the odds that good ideas survive and get funded by aligning people around what matters. It's about respecting others' constraints and incentives. It's about being curious enough to truly understand how the people in power think. And it's about bringing your full self and expertise to these conversations.
In an age where execution is becoming easier and faster, influence becomes the differentiating skill. Learn it. Practice it. Get better at it. Your career—and your products—depend on it.
Original source: The art of influence: The single most important skill left that AI can’t replace | Jessica Fain
powered by osmu.app