The Stakeholder Who Smiled and Said No
When logic is the wrong tool for a political problem
“Great data,” he said. “This really makes a lot of sense.”
I walked out of that meeting feeling cautiously optimistic. The Head of Marketing had just sat through my full analysis: customer counts, revenue baseline, industry benchmarks, and top-of-funnel projections, all the way down to the revenue number I’d been hired to deliver. The logic was airtight, the numbers were clean, and he’d told me in his own words that it made sense. I figured we were close.
He did nothing. The next meeting, same reaction. “Great data.” Nothing again.
I was three months into a new VP role at a Fortune Global 500, hired mid-year into a product portfolio that had been planned without me. The top-of-funnel was entirely organic, and the product wasn’t anywhere close to a state where it could drive meaningful organic traffic. I had 90 days to show results and 120 days to show revenue, in a portfolio that had essentially zero demand generation infrastructure in place when I arrived.
The one thing I needed was a demand generation budget. The one person who controlled that budget kept telling me my data was great and doing nothing about it.
So I built a better deck. More benchmarks, tighter projections, cleaner visuals, and a more explicit line from top-of-funnel investment to bottom-of-funnel revenue. I kept sharpening the argument because I was convinced the problem was that I hadn’t made it clear enough yet. As a logical person, when I face a problem, I go to data first, because in most situations throughout my career, a well-reasoned, evidence-backed argument is what moves people. That’s the tool I know how to use, so that’s the tool I kept picking up.
The problem was that I was using a screwdriver on a nail.
What was actually happening in those meetings
The Head of Marketing had planned his entire year before I was hired. His budget was fully allocated. He was privately worried it wouldn’t be enough for the goals he’d already committed to, and every dollar he had was tied to products the C-suite was actively and visibly tracking. My products were showing up in monthly reviews, and anyone paying attention could reasonably infer they needed support. The Head of Marketing chose not to make that inference.
From where he sat, the calculus looked like this:
Reallocating budget to my portfolio meant pulling from initiatives tied to his existing commitments
My portfolio had no explicit executive mandate behind it, so supporting it was a discretionary risk
If the demand gen worked, the credit would flow to my products recovering, not to marketing
If it didn’t, he’d burned budget on something nobody had formally asked him to prioritize
“Great data” was not confusion, and it was not a request for more information. It was a professional way of saying: I see your logic, and it has nothing to do with my goals or incentives. He wasn’t going to say that out loud, of course, but it changed nothing for him. The logic was fine. The incentives pointed somewhere else entirely, and no amount of better analysis was going to change that.
What I needed to see earlier, and didn’t, was that I was asking someone to take on personal risk for a portfolio that had no explicit cost attached to ignoring it. Until that changed, his rational move was to stay exactly where he was.
The part that’s genuinely hard for logical people
When we’ve spent years building the skill of making a tight case, when being the clearest thinker in the room has historically been what moved things forward, it becomes almost automatic to reach for data when we hit resistance. We assume the resistance is informational. We assume that if we just find the right angle, the right benchmark, the right framing, the other person will see what we see and act. I am guilty of this. That’s how I know.
But there’s a category of problems where data is genuinely irrelevant to the outcome. It’s the category where the person you’re trying to move has incentives pointing in a different direction than your ask, not because they’re irrational, but because they’re rational about a completely different set of constraints than the ones you’re reasoning from. Their budget, their performance review, their existing commitments, their relationships upward: all of that is a system they’re optimizing for, and your ask either fits into that system or it doesn’t. Better data doesn’t change the system. It just gives them more to politely acknowledge before they don’t move.
The diagnosis that actually matters is not “do they understand my argument?” Before you build the next deck, ask yourself:
Does saying yes cost them something?
Does saying no cost them anything?
What are they being measured on, and does my ask connect to that or compete with it?
Who above them has explicitly said my work matters, not implied it, not included it in a slide, but said it out loud in a way that created accountability?
If the answers to those questions are uncomfortable, you are not in a logical conversation. You are in a political one, and the sooner you know that, the sooner you can stop building decks and start thinking about what actually needs to change.
How it ended
I escalated. Got my boss involved, got time in front of the CEO, and watched how fast things shifted once the CEO made it unambiguous that my products needed attention. Budget appeared almost immediately after that conversation, which told me everything I needed to know about where the real blockage had been all along.
What I felt in that moment was not relief. It was frustration, and honestly, some embarrassment. I was a VP at a Fortune Global 500 company, as was he, and we both reported directly to the C-suite. Needing my manager to intervene to get a peer to act on something that was clearly in the company’s interest made me look like I couldn’t operate independently, which, at that level, is not a reputation you want. The budget I finally got was the bare minimum for a pilot. I wasn’t allowed meaningful input into how it was spent, and the money got directed in ways that didn’t move the needle. The products didn’t recover.
The story doesn’t have a good ending. I’m telling it anyway, because the lesson inside it is about what I should have done months earlier, before any of this became necessary.
What I do differently now
That experience rewired how I walk into any conversation where I need something from someone who has no obvious reason to give it to me.
I don’t start with my ask anymore. I start with their world.
Before I walk in, I try to understand what they’re measured on, what they’re worried about, and what goals they’re actively trying to hit. Sometimes I can figure that out from context, from how their team talks, from what gets mentioned in all-hands, from what their manager cares about. Sometimes I don’t have enough access and I have to ask directly, which is a conversation in itself and usually a useful one. It depends on the relationship and how much visibility I have into their situation.
Once I have a picture of their incentives, I work through four questions in order:
What do they actually care about right now?
Is there a way to reframe what I need so it connects to something on their list?
If there isn’t a natural connection, is there a way to get my goal onto their list, not through pressure, but by making it genuinely worth their while?
Only then: how do I state my ask in a way that lands in their world, not mine?
Step three is the one most people skip. It requires accepting that sometimes the problem isn't that your ask is poorly framed. It's that the other person has no structural reason to say yes, and until that changes, better framing won't help. In my case, that meant finding a way to change the budget situation entirely before I walked back into that room. I'll come back to what that looked like in a moment. It's not manipulation. It's the work of figuring out how to make the right outcome work for both people, which is what I should have been doing from the start.
The honest version of “influence without authority” is not a communication technique. It’s the work of understanding someone else’s constraints well enough to find an outcome they’d actually choose.
What I should have done instead
In hindsight, there were two moves I should have made at the very beginning, before I walked into a single meeting with the Head of Marketing.
The first was going to the CEO early and asking for an explicit budget earmarked specifically for demand gen tied to my new revenue goals. Not assuming that because my products were in the monthly review deck the resources would materialize. Actually asking, directly, for money to be allocated to make the goal achievable. That’s not an unreasonable ask when you’ve just been hired with a specific revenue target attached to your name. The deck I built wasn’t the mistake, by the way. What I should have done was use it differently, not to justify my ask to the Head of Marketing, but to build the demand gen number together with him, so that the goal and the resource request felt jointly owned rather than handed down.
The second was using part of that budget as an offer rather than a request. If I’d walked into his office and said: here is additional budget for your team to support my products, and I’d like your team to lead the demand gen strategy, that conversation looks completely different. His risk calculation changes. Instead of being asked to pull from existing commitments, he’s being handed new resources with a clear mandate attached. He might actually become an ally. What I had instead, for my entire tenure at that company, was a marketing team with every structural reason to deprioritize my portfolio and no reason not to.
I turned a solvable resource problem into an entrenched political one, mostly by arriving with logic when I should have arrived with a different kind of proposal entirely.
Where to go from here
Think about wherever you’re stuck right now. Think about the person who keeps nodding and not moving. Before you go back with more analysis, ask yourself honestly whether this is a comprehension problem or a consequence problem. Ask what they’re being measured on and whether your ask connects to that or competes with it. Ask who above them has explicitly said your work matters, not implied it, not included it in a slide deck, but actually said it out loud in a way that created accountability.
And then ask whether there is a version of this where you come in with resources rather than requests. Whether there is a way to make saying yes easier for them rather than just more logical for you.
The data was never the obstacle in my story. The incentive structure was, and the incentive structure was always going to stay exactly as it was until something changed the consequences of not acting. I kept trying to change minds when what I actually needed to change was the conditions under which saying yes became the easier choice.
I write about strategic product thinking for leaders in resource-constrained environments. If this resonated, subscribe below.