The Conversation Product Marketing Keeps Avoiding

Product marketing has an influence problem inside most enterprise B2B SaaS organizations. Not a visibility problem. Not a budget problem. A conversation problem. The function produces positioning frameworks, enablement content, and launch briefs at a pace that has no shortage of output, and still finds itself sidelined when the decisions that matter actually get made.

The standard diagnosis blames structure. PMM doesn't have the right reporting line. Leadership hasn't invested in the function. The org hasn't committed to product-led thinking. There's enough truth in each of these to make them feel satisfying as explanations. But they're wrong as diagnoses, which means the interventions that follow, reorganizations, new dashboards, more executive touchpoints, rarely fix anything. The problem isn't structural. It's conversational.

I came to this reading Jefferson Fisher's The Next Conversation — a book ostensibly about communication skills that turns out to be an unexpectedly sharp lens on why PMM loses internal influence. Fisher's central observation is this: the conversations you avoid don't disappear. They keep happening without you. I've been thinking about that sentence across a range of client engagements, at a large-scale privacy tech company, at a real estate data platform, and at a handful of others at very different stages of scale, because it names something that shows up consistently regardless of team size or ARR. The function has stopped having the hard internal conversations the role requires, and replaced them with more content. More decks. Better briefs. Tighter messaging guides. Output as a substitute for the exchange that would actually move things.

This post names the three conversations that come up most consistently, explains why avoidance compounds over time, and describes what it actually looks like to show up differently. The discomfort of having these conversations is real and short-term. The consequences of avoiding them are also real, and they compound.

Communication Is Not the Same as Conversation

Most PMM alignment work is a broadcasting operation. A launch brief goes out. An enablement deck gets built. A positioning framework gets Slacked to the sales team with a note that it's ready to use. Information moves from PMM to the rest of the organization. The assumption underneath all of it is that if the content is clear and the coverage is wide enough, alignment will follow.

It won't. Not reliably. And the failure isn't that people don't read the brief or skip the enablement session, though that happens constantly. The deeper failure is that alignment isn't a cognitive state produced by receiving information. It's a relational state produced by exchange. People align when they've had the chance to push back, ask the question they were embarrassed to ask in a group setting, express the doubt they've been carrying since the last launch, and hear a response that actually addresses it.

Fisher frames this precisely: most people in a conversation are preparing what they're going to say rather than actually listening to what's being said. That's true of sales reps in enablement sessions. It's true of product managers in positioning reviews. And it's also true of the PMM delivering the content, often so focused on presenting clearly that they miss the signals telling them the room isn't actually with them.

The shift from communication to conversation is a shift from delivery to exchange. Most PMMs have never been trained for it. The internal relationships that determine their influence are shaped by whether that shift has happened, regardless of how good the content is.

| The conversations PMM avoids don't disappear. They keep happening without PMM in them.

The Three Conversations PMM Keeps Not Having

The alignment failures I see most often cluster around three recurring conversations the function systematically avoids. The reason isn't laziness. It's a reasonable instinct to protect relationships in a cross-functional role where political capital is finite and takes real time to rebuild.

The conversation with product about what the market actually needs. PMM sits at the intersection of market signal and product roadmap, which means they frequently know things the product team doesn't want to hear: that the differentiator the engineering team is proudest of isn't the one buyers care about, that the roadmap priority doesn't map to the buying criteria in the segment you're trying to win, that the messaging the CPO loves internally isn't landing externally. These are hard conversations. They require pushing back on people with more organizational authority, in a domain the product team considers its own. So instead of having them, PMM shapes the message around the roadmap rather than challenging the roadmap itself. The positioning ends up orphaned from the market reality it was supposed to reflect, and nobody says it out loud.

A security compliance company I've worked with had built a strong product for the North American market, then ran into this problem when it began selling internationally. Their positioning was built around a US-centric compliance framework. The enterprise buying group they were targeting in EMEA operated under an entirely different regulatory context and simply didn't recognize the value proposition as written. The PMM team knew the messaging wasn't resonating. The product team was confident the framework was the right anchor. The conversation about re-framing for the international context never happened at the level it needed to. The result was a prolonged period of underperformance in a market that should have been winnable.

I've seen smaller-scale versions of the same dynamic at a $20M ARR workflow automation company with a solo PMM. She had strong buyer insight from sales calls showing that mid-market operations teams cared almost entirely about implementation speed, not feature depth. The product roadmap was heading in the opposite direction. She brought it up once in a planning meeting, was overruled quickly, and let it go. The conversation she didn't push for cost the company six months of positioning that didn't convert.

The conversation with sales about why off-message selling is costing deals. Most PMMs know exactly which reps go off-message. They know who leads with discounting instead of value, who pitches last year's narrative in a competitive landscape that has shifted, who hasn't internalized the ICP definition well enough to disqualify the wrong opportunities. But naming it directly feels like a turf war: marketing criticizing sales, the classic dysfunction. So the conversation doesn't happen. PMM builds more content instead, hoping the next battlecard lands where the last three didn't. The root problem, a conversation problem, stays untouched.

At a $75M ARR HR tech company, the PMM team had built a solid competitive narrative following a major platform update. Win rates in the mid-market had improved. But the enterprise segment was still losing deals to a competitor with an older product and a sharper story. The problem wasn't the narrative. It was that the enterprise reps were reverting to a feature-comparison pitch under pressure from procurement. PMM had identified this pattern in win/loss data. They'd updated the battlecard three times. The direct conversation with enterprise sales leadership about what was actually happening in those late-stage deals never took place. The pattern continued for two more quarters.

The conversation with leadership about what PMM is actually accountable for. This is the most avoided of the three, and the most expensive. PMM operates in a measurement vacuum at most companies, contributing to things that are hard to attribute and evaluated on outputs that don't capture real impact. The ambiguity isn't accidental. It's the residue of a conversation that never happened. PMM didn't push leadership to define what success looks like. Leadership didn't push PMM to name it. Both parties avoided the discomfort. The result is a function that can't make the case for its own value because it never agreed on what that value was supposed to be.

At a data provider platform I worked with, the PMM function had real influence on product direction and messaging, but the accountability conversation was always murky. What PMM owned versus what demand gen or product owned in terms of pipeline contribution was never cleanly defined. That ambiguity made it harder to demonstrate impact, and easier for leadership to underinvest in the function when budget pressure arrived. The conversation that would have fixed it kept getting deferred in favor of executing the next launch.

Why PMM Avoids Them and What That Costs

The avoidance isn't irrational. PMM depends on relationships across the organization to get anything done. Pushing back on a product VP or naming a sales leader's off-message behavior carries real political risk. A conversation that goes badly can outlast the launch it was supposed to support.

Fisher's point about avoidance is worth sitting with: when you avoid a hard conversation, you don't avoid the outcome. You just lose the chance to shape it. The product VP still forms a view of PMM's strategic credibility based on every interaction that has happened, including the ones where PMM deferred when it should have pushed. The sales leader still draws conclusions about whether PMM's frameworks are worth following. The conversation happens in their heads, without PMM's input, and the verdict is rarely favorable.

The long-term cost is more serious than most PMMs recognize while it's accumulating. Short-term discomfort from a hard conversation is recoverable. A function that has spent two years building a reputation for deferring, for producing good content and never pressing when it matters, has a credibility problem that content quality alone will never fix.

This is the core argument behind Customer Zero: PMM's first customer is internal. The sales team, the product team, and the leadership team all need to believe in the story before the market can. But belief isn't produced by exposure to good content. It's produced by the experience of being genuinely heard and directly engaged. That's a conversation, not a broadcast.

The Silencing Pattern: Why PMM Stops Speaking Up

There's a specific mechanism behind the avoidance that rarely gets named directly, and it's worth naming here because understanding it is the first step to breaking it.

It usually starts with a PMM who does speak up: raises a market insight that contradicts the roadmap, flags a pattern of off-message selling, challenges an assumption the leadership team has held for a long time. And gets railroaded. Not necessarily with malice. Often it's an executive who is confident, vocal, and moves quickly past the input without genuinely engaging it. Sometimes it's more direct: the idea gets dismissed, the concern gets labeled as out of scope, the PMM gets managed back into their lane.

If this happens once, it's a bad meeting. If it happens consistently, if the PMM learns through repeated experience that speaking up leads to being talked over, corrected by people with more authority, or quietly excluded from the next conversation, the behavior changes. The PMM stops raising the uncomfortable insight. They start presenting options instead of taking positions. They learn to shape their input around what the room is already likely to accept, rather than what the market is actually telling them. They become very good at producing content no one pushes back on, because it doesn't challenge anything.

The organizational cost of this pattern is significant and often invisible. The PMM who has learned not to speak up is still in the room for every product review and leadership meeting. They still have the buyer data, the win/loss patterns, the competitive intelligence. They're just not sharing it in a way that changes anything. The most vocal and confident executives continue to drive the direction, sometimes correctly, sometimes not, while the people most connected to market reality have quietly stopped putting up a fight. The business can travel a long way down the wrong path before anyone realizes the signal was there all along and simply wasn't heard.

Breaking this pattern requires something from both sides. The PMM has to be willing to re-engage, to recognize that past dismissal doesn't make current input wrong, and that staying silent carries a cost that eventually lands on the business, not just on their own influence. But the organization has to create the conditions where PMM input is genuinely invited and seriously considered, not tolerated and then overridden. Both things have to be true for the conversation to be worth having.

What Changes When PMM Treats This as Conversation Work

The operational shift isn't dramatic. It doesn't require restructuring the team or redesigning the planning process. It requires PMM to make a different choice about how to show up in specific moments that recur constantly, and to prepare for those moments instead of arriving empty-handed.

In product reviews, it means arriving with a specific, evidence-based argument about buyer behavior the roadmap doesn't account for, not as a challenge to product's judgment, but as the input product needs to make a well-informed call. Fisher's framework is useful here: the goal isn't to win the conversation, it's to change what's possible in it. A PMM who enters a product review with buyer quotes and a pipeline analysis connecting deal losses to a specific capability gap is doing something categorically different from one who presents positioning options and waits for feedback.

In sales enablement, it means designing for conversation rather than coverage. Reps who go off-message aren't doing it because they lack information. They're doing it because they haven't had a conversation in which the narrative became their own, where they argued with it, tested it against real objections, and found the version that fits how they sell. Enablement built around that kind of exchange looks different from a slide deck and a recording. It looks like structured practice, direct feedback, and a PMM who is willing to say 'that framing doesn't match what we're trying to accomplish' when it doesn't.

In leadership conversations, it means naming the accountability question before leadership raises it, or stops raising it and quietly concludes the answer. PMMs who proactively define what they're accountable for, and what evidence will confirm or challenge their impact, operate from a fundamentally different position than those who wait to be evaluated on criteria they didn't set. This is part of what it means to build the operational infrastructure for GTM scale: not just process and rhythm, but the internal credibility to shape how that infrastructure gets measured.

The Conversation Is Already Happening

If PMM's influence within a GTM org feels lower than it should, the most honest diagnosis is usually this: the conversations that shape that influence have been happening without PMM's active participation. Every deferred pushback, every enablement session that didn't address the real objection, every accountability conversation that never got scheduled — those are moments where the story of PMM's value was being written by someone else.

The short-term discomfort of having these conversations is real. So is the long-term consequence of avoiding them. A function that consistently defers the hard exchange in favor of producing more content eventually loses the credibility to have the conversation at all. Changing that doesn't require a new framework or a reorganization. It requires PMM to show up differently in the conversations already on the calendar, and to schedule the ones that aren't.

BlindSpot works with PMM leaders and GTM teams at growth-stage B2B SaaS companies to close exactly this kind of gap: the space between what the function produces and the influence it actually carries. If your team is doing the work but struggling to make it land internally, that's a conversation worth having. Contact BlindSpot to talk through what's getting in the way.