Most positioning exercises start the same way. Someone pulls up a whiteboard. The team debates terminology. Someone advocates for a capabilities frame. Someone else wants to lead with the problem. A compromise gets reached. The output is a messaging hierarchy that everyone signs off on and nobody uses in the field.
The failure isn't in the execution. It's in the starting question.
The wrong question
Most positioning work starts with: "What does this product do?"
From there, teams work outward. They enumerate features. They translate features into benefits. They try to find the right combination of problem + solution + differentiation that will land. And they end up with messaging that describes the product accurately and compels no one.
The reason this approach fails isn't that the team is bad. It's that the question creates the wrong constraint. When you start with "what does this product do," you're starting from the inside out. You're describing your world and hoping the buyer's world matches up. It usually doesn't.
The right question doesn't start with your product. It starts with the buyer's actual decision process, and it has to be specific enough that the answer reveals the positioning, not just confirms it.
The right question
"What would have to be true for a buyer to choose this product over what they're doing today?"
Not "what's the problem we're solving." Not "who is our buyer." The specific gap between the current state and the chosen alternative. What has to be true about the problem, the stakes, the solution, and the proof for a buyer to move?
This question is harder to answer than "what does this product do." It requires knowing what buyers are actually doing today, which means real conversations, not assumptions. It requires understanding why they're doing it that way, which means digging past the stated rationale into the actual incentives. And it requires being honest about whether your product actually closes that gap or whether you're hoping it does.
Most teams can't answer it honestly, so they answer a version of it that sounds true: "buyers want to reduce risk," "buyers want to save time," "buyers want a single platform." These aren't wrong. They're also not positioning. They're categories. And categories don't close deals.
Why this matters for product launches
The difference between a product launch that gains traction and one that stalls often comes down to this: whether the go-to-market team can articulate exactly what the buyer had to believe to choose the product.
If sales can't explain the specific decision a buyer is making, and what evidence they'd need to make it, the messaging won't save it. The enablement materials won't save it. The proof points and battle cards won't save it. They'll paper over the gap temporarily, but the gap will show up in win rates, in the questions buyers ask, in the deals that go quiet.
I've watched teams ship launches with messaging that everyone agreed was good, and then spend six months wondering why the pipeline wasn't converting. The answer was usually sitting in the discovery calls they didn't run before the launch, not in the decks that got revised after.
How to use this question
You don't need to wait for a formal positioning exercise. Before any launch, any major message refresh, any competitive response: sit down with your most experienced sellers and ask them to describe the last three deals they won against a specific competitor. Not "what did you say" but "what did the buyer believe was true before they'd even take the meeting?"
The answer will tell you more about your real positioning than any messaging hierarchy ever written.
Then ask: does our current messaging make those beliefs legible? Does it address the actual gap or does it describe the product?
If you find the gap, you have your positioning. If you don't, that's the problem to solve before you write a single message.