Your launch meeting is too late to get stakeholder buy-in

There's a particular kind of launch meeting that every product marketer gets to experience.

You walk in with your plan - the customer research, positioning, launch plan, timeline, and requirements for the responsible teams - all worked out. You anticipate a discussion on execution.

Instead, sales immediately questions the ICP. Product brings up a compliance feature that might not ship in time. Customer success points out that the message will alienate existing customers. Demand gen says there’s no budget and no resources to run the campaign. 

Now you're questioning the sequence of decisions that led you to prepare the launch plan in the first place. Oftentimes, the launch meeting itself is blamed. The deck was unclear. The audience wasn't prepared. There should have been a pre-read.

The root of many of these issues is treating stakeholder buy-in as implied, or as something to get after you’ve put together your perfect launch plan.

The best launches I've been part of have had one thing in common: by the time the full launch plan was presented, little about it was completely novel to the people that mattered most. They knew the target audience, had weighed in on the key strategic choices, and understood how the launch would impact their responsibilities because they’d had their say in the process.

This is the crux of stakeholder management in a product launch. It's not about keeping stakeholders informed, but rather managing when decisions happen, who needs to be involved in them, and where opposition is likely to occur in order for the launch to move swiftly through approvals at the right levels.

Stakeholder alignment is built through decision-making

Product marketers often speak of "buy-in" as a single binary outcome - presenting the strategy and having everyone agree.

Launches don't work that way.

There are dozens of decisions behind every launch:

• The target audience,
• Whether we're leading with a particular problem or solution,
• Positioning against competitors,
• Whether this is a Tier 1 or Tier 2 launch,
• Which markets to include,
• What sales needs,
• The promises we're making to customers, and
• The resources it will take us to deliver on them all have to be considered.

Each stakeholder has a say over what objectives their teams deliver on. 

Not one stakeholder having a say over everything. The executive who has a say over how much we invest in the launch wouldn't be expected to wordsmith the sales deck. Customer success has a say over the promises we're making to customers but not ultimate authority over positioning. Sales leaders have a say over sales enablement, but likely not the support process.

Good stakeholder management starts by recognizing that the first step is understanding which decisions require which stakeholders' input.

Then, as PMM, you need to influence the decisions that are designed for the best outcome of the launch. Formulate your recommendations and don’t be shy about talking them through with your stakeholders.

I care deeply about understanding three things for every major launch decision: who has information that could affect each decision, who has authority to make or break the decisions, and who has to implement the decisions once they’ve been made. These categories often overlap, but they're not always the same people.

This is also why it's often not useful to get everyone involved in the launch in a room for every launch meeting (I’ve personally made this mistake and learned a hard lesson from it). Visibility and involvement are different things. We want to involve people where their input has value and ensure that everyone else has the information they need to proceed.

Start with what each stakeholder cares about

One common way a stakeholder becomes disengaged from the launch is when you frame the conversation from the launch's perspective rather than the stakeholder's.

You care about getting the product to market successfully. They care about what the product launch means for the thing they care about. You need to understand what they care about!

Customer success may care deeply about who the audience is, what promises we're making, and whether we've anticipated the problems that an existing customer will run into. For a sales leader, it's about whether the product will give them a credible reason to engage or win a particular type of deal they're currently losing. Product has different concerns, as do marketing, finance, and leadership, who have to balance the launch against several other initiatives.

That leads us to one of the most valuable early questions for engaging stakeholders: what does this person need to believe in order to support this launch?

Your head of sales may need to believe that there's a viable selling opportunity. Your CMO may need to believe the market opportunity supports the investment. Product may need to believe the story is representative of what they've built. Customer success may need to believe the launch won't create a wave of unprepared customers.

Understanding this has value because it gets us out of the trap of asking everyone the same questions. You engage stakeholders based on the decisions they have a say in.

This sounds obvious, but I see teams falling into the trap all the time.

Find the arguments before the big meeting

Every launch has a few decisions that are more likely to be contentious. Often, we can expect them in advance.

The roadmap date is being treated as a launch date even though go-to-market teams will need more time. Marketing won’t have the appropriate amount of budget to do a full-scale launch. Or maybe sales already has too many things competing for their attention.

These are the conversations I want to have early, preferably with a small number of people.

I call it pre-wiring if I want to be cute about it, but really, I want to avoid situations where the first meaningful conversation about an important decision is happening in front of fifteen uninformed people. It’s embarrassing.

If I'm leaning towards a specific ICP, I want to stress test it with the people who understand the market before building the entire strategy around it. If there's a value proposition that I think is preferable to the one product has embraced, I want to walk through the supporting information with them before they see the final message. If a launch date looks dangerous, I want to have the dependencies on display while there's still time to change something.

This also gives stakeholders an opportunity to disagree with one another without having to do it in front of the whole team, slowing down the meetings and risking looking out of the loop. A stakeholder is often more likely to share what they think you're not considering in a working conversation than a meeting where everyone has already taken a position.

And sometimes, they'll spot something that you didn't. That's a win and a chance to correct it early.

The importance of stakeholder management isn't to get people to agree with you; it's to get the right questions answered early enough that it improves the launch.

Bring evidence with your recommendations

There's a moment in many cross-functional discussions where evidence disappears, and everyone starts arguing from personal experience.

Sales had a prospect who said X, product had a beta customer who said Y, an executive saw a competitor doing Z. Suddenly, everyone's strategy is being informed by the anecdotes that seem to have the most seniority.

Product marketing's job is to help filter these pieces of information. We see the launch from dozens of angles and perspectives. Our value is in connecting these inputs and turning them into a recommendation.

Show that work.

If you believe the launch should be focused on a particular pain point, explain what led you there. Choosing one audience over another? Show the evidence behind the choice. If you believe a competitor isn't as important as the sales team thinks, bring the win/loss or customer research that supports the argument.

You don't need to share every piece of research you have, but you need enough evidence to support your recommendations.

It changes the conversation dynamics. You want stakeholders to challenge your interpretation, bring additional evidence, or point out a gap in your knowledge. All three are useful.

Be specific about the feedback you need

There's a product marketing sin that involves sending a deck to ten people and asking for thoughts.

You will get all the thoughts. They just may have nothing to do with the decision you want them to make.

When I'm asking stakeholders for feedback, you want to frame it as specifically as possible.

For example, asking sales what they think about the GTM strategy isn't as valuable as whether the proposed buyer fits the people involved in the deals they're winning. Asking product if they like the messaging isn't as valuable as whether any of the claims create a gap between what we're promising and what the product delivers.

This does two things. It gets you better feedback, and it gets the stakeholder's role in the decision clearer.

Both matter when you have a lot of people involved.

Clarify who makes the final decision

Buy-in gets particularly messy when no one knows who has the ultimate say.

Input turns into veto power. Decisions get reopened. A stakeholder who missed an earlier conversation comes in late and changes everything. PMM gets stuck trying to harmonize six different opinions because nobody has established who actually gets to decide.

Make your RACI visible to everyone and manage your risks and decisions log like it’s evidence for a trial. 

For the major strategic decisions, everyone involved should understand who is providing input and who has the final say. It may be product, product marketing, a functional leader, or an executive sponsor depending on the company and the decision.

Once a decision has been made, capture it somewhere. A simple decision log with the decision, rationale, owner, date, and conditions under which you'll revisit it can save a ton of time later on.

The last part is particularly important. Decisions can change when the facts change. The scope of the product moves. A competitor launches something unexpected. Customer research reveals a faulty assumption. The company's priorities change.

That's not the same thing as reopening a decision because someone has just arrived late in the conversation.

Good stakeholder management still requires saying no

There's another side to stakeholder management that is less discussed. Sometimes you listen to the feedback, and you keep your original recommendation.

PMMs work cross-functionally, which means we spend a lot of time listening to input. That can create an expectation to find a version that everyone is comfortable with.

Comfort isn't always a virtue.

It’s how messaging gets watered down and why every company in your industry starts sounding the same.

Your job is to hear the concern, determine whether it changes the strategy, and explain the decision.

Sometimes, that's "I understand why sales wants this audience included, but based on the research and opportunity we're prioritizing, we're still going to focus the launch here."

Buy-in doesn't require universal agreement. It requires enough trust in the process and enough clarity around the decision that people can move forward together.

By the launch meeting, the strategy should feel familiar

The big, cross-functional launch meeting still matters. It just shouldn't bear the weight of creating alignment.

By that point, each team should be aligned on the launch direction, why it’s happening now, and what part they play.

There will still be questions. There will still be changes. Launches are living things right up until the launch date (and sometimes beyond that).

What you want to avoid is discovering a fundamental disagreement about the strategy when the machine is already moving.

A good launch meeting should feel like an extension of what’s already happened and bring it all together in one place. The major decisions have context behind them, owners know what they own, risks are visible, and the conversation is about getting the launch into market on time.

That is what effective stakeholder management gets you.

Real buy-in comes from involving the right people in the right decisions, understanding what matters to them, dealing with dissent early, grounding recommendations in evidence, and being clear about who has ultimate authority. 

Do that, and you'll spend a lot less time trying to get everyone aligned at the end, and you’ll build trust with people you’ll be working with on other projects in the future.