The Conversation Product Marketing Keeps Avoiding
Product marketing has an internal influence problem. Most people in the function know it. They’ve felt it in the room when a product VP dismisses a positioning recommendation, or when a sales leader nods through an enablement session and then goes completely off-message the moment they’re with a buyer. The frustration is real. But the diagnosis is almost always wrong.
The standard explanation blames visibility. PMM doesn’t have a seat at the table. Leadership doesn’t understand what the function does. The org hasn’t fully committed to product-led thinking. These explanations aren’t false exactly, but they’re surface-level. They treat a conversation problem as a structural problem, which means the interventions that follow—more reporting lines, more executive check-ins, more battle cards—don’t actually fix anything.
Jefferson Fisher’s The Next Conversation makes an observation that lands differently when you read it through a PMM lens: the conversations you avoid don’t disappear. They keep happening without you. The product VP forms a view of PMM’s strategic value based on every interaction you’ve had with them, including the ones where you deferred instead of pushed back. The sales leader who goes off-message does so in part because no one has had a direct, specific conversation with them about why it matters. The conversation happened. PMM just wasn’t in it.
The distinction between communication and conversation isn’t semantic. For PMM, it determines whether internal alignment actually holds.
Communication Is Not the Same as Conversation
Most PMM alignment efforts are broadcasting operations. A launch brief goes out. An enablement deck gets built. A Slack message announces the new positioning framework. Information moves from PMM to the rest of the org. 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 reason isn’t that people don’t read the brief or skip the enablement session, though that happens too. The deeper reason 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 the group session, express the doubt they’ve been carrying since the last launch, and hear something in response that actually addresses it.
Fisher frames this precisely: most people 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 PMMs delivering the content, often so focused on presenting clearly that they miss the signals in the room that tell 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 that shift. And the internal relationships that determine their influence are shaped by it regardless.
| The conversations PMM avoids don’t disappear. They keep happening without PMM in them.
The Three Conversations PMM Keeps Not Having
There’s a pattern across the PMM alignment failures that show up most often. They tend to cluster around three recurring conversations that the function systematically avoids. The reason isn’t laziness. It’s a reasonable desire to preserve relationships and avoid conflict in a cross-functional role where political capital matters.
The conversation with product about what the market actually needs. PMM sits at the intersection of market signal and product roadmap, which means they often know things the product team doesn’t want to hear: that the differentiator the team is most proud of isn’t the one buyers care about, that the roadmap priority doesn’t map to the buying criteria in the segment they’re trying to win, that the messaging the product leader loves internally isn’t landing externally. These are hard conversations. They require PMM to push back on people with more organizational authority, in a domain the product team considers its own. So instead, PMM shapes the message around the roadmap rather than challenging the roadmap itself, and the positioning ends up orphaned from the market reality it was supposed to reflect.
The conversation with sales about why off-message selling is costing deals. Most PMMs know their sales org goes off-message. They know which reps lead with discounting instead of value. They know which teams are still pitching last year’s narrative in a competitive landscape that has shifted. But calling it out 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 battle card lands where the last three didn’t. The root problem, which is a conversation problem, stays untouched.
The conversation with leadership about what PMM is actually being held accountable for. This is the most avoided conversation of the three, and the most consequential. PMM operates in a measurement vacuum at many companies, contributing to things that are hard to attribute and evaluated on outputs that don’t fully capture 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.
Why PMM Avoids Them and What That Costs
The avoidance isn’t irrational. PMM is a cross-functional role that depends on relationships across the org with product, sales, CS, and leadership to get anything done. Pushing back on a product VP or calling out a sales leader’s off-message behavior carries real risk. The political cost of a conversation that goes badly can outlast the launch it was supposed to support.
Fisher’s point about this kind of 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 cost compounds over time. PMMs who avoid hard internal conversations tend to develop a style of influence that relies on content quality and process compliance: better decks, clearer briefs, tighter frameworks. These things matter. But they can’t substitute for the relational credibility that comes from being someone who will say the hard thing, directly and without drama, when it needs to be said. That credibility is built one avoided conversation at a time. Or lost that way.
This is the core argument behind Customer Zero: PMM’s first customer is internal. The sales team, the product team, 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.
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 they show up in specific moments that recur constantly.
In product reviews, it means raising the market signal that contradicts the roadmap priority, not as a challenge to product’s judgment, but as the input product needs to make a well-informed call. Fisher’s framework here is useful: 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 a specific, evidence-based argument about a buyer behavior that the roadmap doesn’t account for is doing something fundamentally different from a PMM who presents positioning options and waits for feedback.
In sales enablement, it means designing for conversation rather than coverage. The instinct is to build comprehensive content and distribute it widely. But the 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, found the version of it 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 an operating system for GTM scale: not just infrastructure and process, but the internal credibility to influence how that infrastructure gets built and measured.
Conversation Is a Skill, Not a Personality Trait
One of Fisher’s core arguments is that communication in high-stakes situations is a skill, not a personality trait. The PMM who avoids hard internal conversations isn’t necessarily conflict-averse by nature. They’re often operating without a clear model for how to have those conversations in a way that advances the work rather than damaging the relationship. That’s a skill gap, and skill gaps are closable.
The specific skills matter here. Raising a contradiction without making it personal is different from raising it as a critique. Naming a pattern of off-message behavior in a way that invites a sales leader into the problem rather than putting them on defense requires preparation, not just courage. Holding a position under pressure in a leadership conversation without becoming rigid is something that can be rehearsed. These are techniques. They respond to practice in ways that personality traits don’t.
The underlying principle Fisher returns to is worth stating plainly: you are not responsible for how someone receives a hard truth, but you are responsible for how you deliver it. PMMs who internalize that shift stop using relationship preservation as a reason to avoid necessary conversations. The quality of their internal conversations becomes a performance variable, not an afterthought.
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.
Changing that doesn’t require a new framework or a reorganization. It requires PMM to show up differently in the conversations that are 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.
