There's a moment in most growing companies where product and marketing stop talking to each other. It happens quietly. Product ships a feature; marketing figures out how to explain it. Marketing learns something about customers; product files it away for later. The handoff feels clean. It is not clean.
What's actually happening is that the company has split its brain. One half knows what it's building. The other half knows why people care. And neither half is telling the full story to anyone, including itself.
I've spent my career at the seam between those two functions — sometimes by design, more often because that's where the interesting problems lived. What I've learned is that treating product and marketing as separate disciplines is a choice, and it's usually the wrong one.
Positioning is a product decision
Most people think of positioning as a marketing artifact — the thing you write in a deck, the headline on the website, the one-liner you use at conferences. And it does live there. But it starts somewhere else.
Positioning is really an answer to the question: what is this for, and for whom? That question has to be answered before you write a word of copy. And the people best equipped to answer it are the ones who understand what the product actually does — which is usually the product team, not the marketing team.
When positioning is treated as a marketing problem, you end up with messaging that describes a product the product team doesn't recognize. When it's treated as a shared problem, you end up with products that are easier to explain because they were designed to be explainable. The difference in outcome is significant.
The best positioning I've seen wasn't written in a conference room. It was discovered by watching someone use the product and finally understand it.
The product surfaces the message
It works the other way too. Marketing isn't just downstream of product — it's a feedback loop that, when it's working, actively sharpens what gets built.
Every time marketing tries to explain something and struggles, that's a product signal. If the feature is hard to describe in a sentence, it's probably trying to do too many things. If customers keep asking the same question about how it works, the product hasn't answered that question yet. Good marketers, the ones who are paying attention, are sitting on a pile of product insights that the product team never hears.
At Frame.io, some of the clearest signals I got about what was working — and what wasn't — came from watching how people talked about the product when they didn't know I was listening. That's a marketing function, not a product function. But it shaped product decisions constantly.
What sharing a brain actually looks like
It doesn't require a reorganization. It requires a few deliberate habits. The marketing team is in the room when product decisions are made — not to approve messaging, but because they know things about customers that matter. The product team is part of positioning conversations — not to sign off on copy, but because they understand the product's actual edges and limits.
More than anything, it requires both teams to agree on what they're trying to do. Not "ship the feature" and "launch the campaign." The actual goal: help a specific kind of person solve a specific kind of problem better than they could before.
When both teams are working toward that, the handoff disappears. There's nothing to hand off. You're just building the same thing from different angles.