Tense aftermath of an executive committee presentation with supply chain consolidation model on the monitor and executives departing in side discussion

The Case That Should Have Won (And The Unspoken Questions That Stopped It)

Dana left the meeting thinking she had won.

She had spent three weeks on the business case before presenting it to the executive committee.

She’s a VP of Operations at a national logistics company, and the initiative she was pushing, consolidating two regional distribution systems into one, was the kind of project that only moves if the right people say yes.

So she did what she’s always done.

She built the model herself. She stress-tested the numbers against three different demand scenarios. She anticipated the objections she could think of and built the answers into the deck before anyone asked the question.

By the time she presented, the logic was airtight. Anyone on that committee who wanted to poke a hole in it was going to have to work for it.

And the meeting seemed to go fine.

People nodded. Someone asked a smart question about implementation timing, and Dana had an answer ready. The CFO said the modeling was some of the clearest he’d seen on a proposal like this.

But then came the follow-up email:

“Let’s revisit this next quarter, once we’ve had time to socialize it more broadly.”

Not a no. Worse, in a way. A “no” would have told Dana something was wrong with the business case. This told her nothing, except that the case, however strong, hadn’t been enough.

Read closely, “socialize it more broadly” is a polite way of saying that the people on that committee had never been part of shaping the idea.

So the question worth sitting with isn’t whether Dana’s case was good. It was. The question is why a financially compelling business case still didn’t move the committee.

Why a strong business case feels like the answer (even though it isn’t)

Most senior leaders got where they are, in part, because this approach has worked for them. Gather the data. Test the logic. Reach the clearest conclusion the evidence supports. Explain it well, back it up, and let the merit of the idea do the rest.

For technical problems, financial models, and operational fixes, it often works. If the analysis is sound, sound decisions tend to follow. It’s the approach that made Dana good at her job.

The trouble is that a group of decision makers isn’t a technical problem. It’s a group of people, and each of them is carrying concerns into the meeting that never made it onto the slides.

What decision makers are really asking

Chris Argyris spent much of his career studying why smart, well-meaning people keep having conversations that fail to produce results.

One of his central findings was that most of us are far better at advocating for our own position than at finding out what’s true for the other person. We build the strongest possible case and treat presenting it clearly as the main job.

But the people on Dana’s committee weren’t only asking whether the model was correct.

Each of them was also asking some unspoken questions:

  • What does this mean for me and what I’m accountable for?
  • What does it do to my budget, my targets, my team, my timeline?
  • What does it do to my standing with the people I answer to?

Every decision maker is weighing these questions while you present. A flawless business case doesn’t answer them. It tells people whether the idea is right. It says nothing about what the idea will cost each of them or what it will ask of them, and we tend to treat those concerns as secondary to the analysis. For the people deciding, they’re often what matters most.

They weren’t being difficult. They were being rational, from where they sit, about things Dana’s case never addressed.

What was missing

What was missing wasn’t more rigor.

Dana had rigor to spare. What she was missing was information that only the people on the committee could give her: what each of them was most concerned about, what they were trying to protect, and what they would need to see before they could say yes.

The only way to get that information is to ask for it, and it works best when you ask before the meeting. I call those one-on-one conversations discovery conversations.

The leaders who consistently get important work approved aren’t the ones with the tightest decks. They’re the ones who have already had the real conversations by the time they present, so nothing in the meeting surprises anyone, including them.

That’s the difference between presenting to people you have to win over and presenting to people who have already helped shape what’s on the table.

Where the Stakeholder Map comes in

The conversations are the real work.

But when a decision involves many people, you can’t just start talking to whoever is closest. You need to know who to talk to, what each of them is likely weighing, and who to talk to first.

That’s what a Stakeholder Map is for.

A Stakeholder Map is a strategic game plan that shows who has a say in your initiative, what they (sometimes secretly) care about or fear, and who influences whom so you know exactly who to talk to and in what order to get everyone on board.

Here’s a rough sketch of what part of Dana’s might have looked like:

  • The CFO. Cares about when the capital goes out and how the savings will show up in the numbers.
  • The two regional heads. Each runs a system the consolidation would retire. They may be wondering what happens to their teams, their standing, and who takes the blame if the transition goes badly.
  • The head of IT. Concerned about the integration workload and the risk of disruption while the two systems are merged.
  • Who influences whom. The CFO listens closely to the regional heads on operational risk, so Dana would talk to them before she talked to him.

The map tells you where to start the conversations and in what order, so that the concerns that could sink your proposal surface while you can still do something about them. In Stakeholder Breakthrough, the workshop I teach, you build a map for your own initiative and plan the conversations that come out of it.

“I don’t want to play politics”

It’s a fair reaction, especially from leaders who are good at their jobs and a little offended by the idea that being good at the work isn’t enough. I understand it. Nobody wants to spend their energy managing perception instead of doing real work.

But finding out what’s true for the people who will decide on your initiative isn’t politics.

It’s curiosity. Done well, it’s one of the most useful things a leader can do, because it’s how people come to commit to a change instead of just agreeing to it. It’s the same instinct that makes Dana a strong analyst, aimed at people instead of numbers.

Opting out of these conversations isn’t staying neutral. Ignoring politics does not make you more powerful, just the opposite.

It means presenting to a room with too many unknowns and hoping the case is strong enough to cover for what you didn’t ask.

Dana’s business case was never the problem. What she lacked was knowing, before she walked in, what the CFO needed to hear to say yes that day instead of pushing it to next quarter. No amount of modeling could have told her that.

A conversation beforehand could have.

Next Time

If you’re about to make a proposal, you now know to find out what each decision maker is thinking about before you present.

What you may not know yet is that holding those conversations isn’t enough. There are three mistakes that lead people to tell you everything except the one thing that would have saved your proposal.

That’s what the next article is about.

P.S. If you missed the last article in this series, you can read it here: Accurate But Partial: Why Being Right About What You Can See Is Never Enough.

Transform Your Leadership.
Transform Your Team.
Achieve Your Vision.

Join senior leaders receiving practical strategies on stakeholder buy-in, culture change, and organizational momentum. Delivered straight to your inbox.

Short reads. Immediate application. Unsubscribe in one click.

Author Bio:

Michael Papanek – A Leadership Coach, Executive Advisor, OD Consultant, Author, and Team Facilitator

Michael Papanek, a professional leadership coach and expert team consultant, has an interesting backstory. Brought up in a family of leadership and teamwork experts, he has followed in the footsteps of the “family business”. Over 30 years of practice, Michael has developed a uniquely satisfying ability to describe interpersonal and cultural principles blending creative flair with extensive experience, which leads to sustained performance improvement when applied by his clients in real life.

Contact E-mail: michael@michaelpapanek.com

Transform Your Leadership - Transform Your Team - Achieve Your Vision

Subscribe to receive insights on achieving breakthrough results through cultural intelligence, strategic leadership and agile innovation—practical ideas you can use in your next meeting to lead your organization through transformation and change.

Join our community of change-makers, culture leaders and creators to build the team and the career you deserve.

Make your pivotal business relationships unbreakable

From Breakdown to Breakthrough is your playbook to build resilient business relationships that stand up to the heat of change.

“Ultimate decoder ring for rising professionals”
“Well-written, thoughtful account of how to develop and lead teams.”
”A game changer for business relationships”