What Marketing Taught Me About Users That Most PMs Miss

Marketing works with real behavior. PM often works with stated preferences.

One of the first things you learn in marketing is that what users say and what users do are almost always different. You run a survey and 70% of respondents say they'd pay for a feature. You build it and three people use it.

Marketers learn early to be deeply skeptical of stated preferences. They watch conversion rates, not survey responses. They test subject lines on real inboxes, not in focus groups. They measure what users actually click, not what users say they value.

A lot of PM discovery work, in my observation, over-indexes on what users say — in interviews, in NPS comments, in support tickets. These are useful signals, but they're filtered through the user's own model of their behavior, which is often wrong. The best discovery insight I've had has almost always come from watching someone use a product, not from asking them about it.

Positioning shapes perception before the product does

Every PM I know thinks about onboarding. Fewer think about pre-boarding — the set of expectations a user arrives with before they touch the product for the first time. Those expectations were set by marketing copy, by the salesperson's pitch, by what a colleague told them, by the product's positioning in the market.

When users churn or resist adoption, it's often because the product didn't meet expectations they formed before they ever logged in. That's a positioning problem as much as a product problem.

PMs who have never done marketing often treat messaging as someone else's responsibility. I think that's a mistake. The narrative around your product shapes what users try to do with it, how much patience they have when something breaks, and whether they bother to explore features they didn't know they needed.

Adoption barriers are usually emotional, not functional

Marketers spend a lot of time thinking about the gap between a potential customer and a purchase. Why doesn't this person buy, even when the product solves their problem? The answers are rarely about features. They're about trust, risk perception, social proof, and switching cost anxiety.

The same dynamic plays out inside products, but PM teams often reach for functional explanations: the flow is confusing, the UI is unclear, the onboarding is too long. Sometimes that's true. But often, the real barrier is that the user doesn't believe the product will actually work for them — and no amount of UI polish fixes a trust problem.

Marketing teaches you to ask: what story does this user need to hear before they'll take the next step? That question is just as relevant on a checkout page as it is in a product onboarding flow or an AI assistant prompt.

The transition I'd recommend

If you're a PM who's never done any marketing work — even a few months in GTM or content — I'd genuinely suggest finding a way to get that exposure. Not because the tactics matter, but because the mental model shifts. You stop thinking of users as people who need features and start thinking of them as people who have beliefs, habits, and reasons to be skeptical of new things.

That's a useful PM to be. Especially when you're building AI products where user trust is the most important variable of all.