Reviews
Straight answers to the product positioning questions
Straight answers to the product positioning questions teams ask most, with the evidence behind each and the market test that decides the right choice.
What to take away
Straight answers to the product positioning questions, written as decisions rather than definitions.
- A position is the market frame plus the difference you can defend with evidence, not a slogan.
- Write the position in one sentence, then write the claim your competitor would use to kill it.
- The market test that decides between two frames is comprehension, not preference: buyers in each segment restate the claim in their own words. Wynter runs these tests with panels of B2B buyers.
- Keep the evidence file dated, because a position that was true last year may not be true now.
- Escalate anything touching certification, tax treatment or procurement rules to the body that sets it.
- Start with competitive alternatives. April Dunford's "Obviously Awesome" (2019) puts that step first, ahead of attributes and benefits.
What a positioning question actually asks
A vague positioning question usually hides a comparison the team has not made. Ask which comparison, and the vague answers stop.
Moore's "Crossing the Chasm" (1991) template squeezes the comparison into one sentence: for [target buyer] who [need], our [product] is a [category] that [benefit], unlike [named competitor].
A frame is the category a buyer already shops in. Slack launched in 2013 selling team messaging, and its early pitch contrasted with email rather than with rival chat apps. Pick a frame buyers do not use and you pay to teach the category before you sell the product.
The difference is the claim you can prove. A slogan is a claim you cannot. That gap is where most launches fail.
Al Ries and Jack Trout argued in "Positioning: The Battle for Your Mind" (1981) that the mind files a new product into a category it already holds. A frame the buyer does not recognize gets no shelf.
The five questions teams ask, and the answer to each
1. Which market frame do we compete in? Name the category the buyer searches, budgets and compares inside. Check it against how your last ten won deals were described by the buyer, not by your sales team. Dunford's method lists competitive alternatives first, including "do nothing" and the spreadsheet.
If buyers search "warehouse onboarding software" and your page says "workforce platform", you hold the wrong frame.
Five positioning questions to answer
- Which market frame do we compete in?
- What difference can we defend?
- Will each segment understand the message?
- Which proof do we show, and to whom?
- When do we revisit the position?
2. What difference can we defend?
3. Will each segment understand the message?
Wynter tests messages with panels of B2B buyers, and studies typically run a few hundred to a few thousand dollars. Lyssna and Maze run cheaper comprehension and first-click tests.
4. Which proof do we show, and to whom?
5. When do we revisit the position?
"Play Bigger" (2016), by Al Ramadan, Dave Peterson, Christopher Lochhead and Kevin Maney, treats the frame choice as the first thing to revisit.
Where a position breaks after launch day
The common failure is a position that survives the deck and dies in the first sales call. The buyer asks what makes it different, and the rep reaches for the slogan.
The second failure is a claim that outruns its proof. A message written before the pilot data arrived tends to describe the product you hoped to ship.
The third is segment drift. One message aimed at everyone gets parsed differently by each group, and the group with the most money hears it last.
Frames also move for reasons outside the product. Adobe agreed to buy Figma for $20 billion in 2022 and abandoned the deal in December 2023 after antitrust reviews in the UK and EU.
A worked review for one positioning claim
Take the claim "cuts onboarding time for warehouse crews." Fill the record below before you publish it anywhere.
| Field | Test to apply | What goes in the record |
|---|---|---|
| Market frame | Ask ten buyers in the segment which budget line paid for the tool | Example entry: onboarding software for warehouse crews, the term buyers use in budget requests |
| Difference claim | Write the strongest counterclaim a named competitor could publish | Example entry: cuts the steps in shift-start onboarding, measured against the customer's current checklist |
| Proof | Name the test, the site, the sample and the date | Example entry: pilot at one site, three crews, time to first productive pick, dated this quarter |
| Segment comprehension | Ask buyers in each segment to restate the claim in their own words | Example entry: each restatement keeps both the frame and the difference |
| Counterclaim drill | Have a rep play the competitor and attack the claim | Example entry: the pilot covered one site and one shift |
| Review trigger | Set the trigger and name an owner before publication | Example entry: revisit when the pilot data expires or a competitor answers the claim |
Positioning record fields and tests
- Framecategory buyers already budget in
- Differencecan a named competitor rebut it?
- Evidencesource, date, sample, limits
- Segmentdoes each restate it correctly?
- Triggerevent, owner, review date
Borrowing the public-sector habits that hold up
Public buying rules are stricter than most commercial ones, so they make a useful stress test for a claim.
Habit one is portability. The GOV.UK technology selection guidance asks buyers to weigh adaptability, data control, security review and ownership cost rather than headline features. The GOV.UK open standards guidance ties open standards to interoperability, reuse and reduced supplier dependence. Apply it to your own claim: can a customer move off you without rebuilding everything?
Habit two is supply chain. For software bought into critical operations, the CISA software acquisition fact sheet points buyers at development practice, supply-chain exposure, deployment and vulnerability management. A position that ignores those four invites a security reviewer to end the deal.
Habit three is data quality. Where a claim rests on data you collected, the GAO data reliability guide treats quality as a function of intended use and asks for a documented assessment. Apply the same standard to your own pilot numbers before a buyer does.
Common questions
What is the first decision in a positioning question?
Treat it as a decision with a date and an owner, not a discussion. Write the one sentence above, then test it with buyers in each segment.
How do we know a position is working?
Buyers in each segment restate it correctly without prompting, and the sales team stops reaching for the slogan. Comprehension first, then preference, then revenue.
What should a team avoid?
Avoid shipping a claim before the proof exists, and avoid one message stretched across segments that read it differently. Both are cheap to fix before launch and expensive after. A named counterclaim you cannot answer is the clearest warning sign.
When should the position be rewritten?
When a competitor publishes a claim you cannot answer, when a segment keeps misreading you, or when the proof behind the claim goes stale. Set the trigger and the review date in advance.
