Operations
A product positioning checklist built around release gates, not vibes
A positioning checklist that names the market frame, the difference you can defend, and the proof each release gate demands before you ship.
What to take away
- Run this product positioning checklist before the launch plan: market frame, who it is for, the one difference you can defend, and the proof behind it.
- April Dunford's "Obviously Awesome" order works as the spine: competitive alternatives, unique attributes, value, best-fit customers, then market category.
- A slogan is a phrase; a position is a claim a competitor cannot copy without changing their product.
- Every release gate below has a pass, fail, or accepted exception, with a named reviewer and a date. Log each one in Jira, Linear or a Notion table your engineers already open.
- Message comprehension by segment is the test that matters. Recall of a tagline is not.
The release-gate checklist
Work the items in order. Each one is a release gate: it passes, fails, or is accepted as an exception with a name and a date attached. One tracker holds every result, so product, marketing and sales read the same record.
Release-Gate Positioning Checklist
- Market framecategory with a budget line
- Segment and jobbuyer, user, job
- Difference you can defendnot a slogan
- Prooftest, record, spec, benchmark
- Alternatives consideredcompare against them
- Market frame.Name the category a buyer already has a budget line for. Dunford calls this the market category choice, and it decides which alternatives customers compare you against. "We are a scheduling tool for dental clinics" frames the purchase. "We are a productivity platform" does not.
- Segment and job.Name the buyer, the user, and the job the product does. One segment per position; a second segment gets its own position. Geoffrey Moore's "Crossing the Chasm" template still works: for a target customer who needs something, name the category and the benefit.
- Difference you can defend.Write the claim a competitor cannot match without rebuilding. Test it against the competitive alternatives you listed first. If they can match it with a copy edit, it is a slogan. Architectures, data sets and contracts are defensible; adjectives are not.
- Proof.Attach the evidence: a test result, a customer record, a specification, a dated benchmark. Named examples include a SOC 2 Type II report, an ISO/IEC 27001 certificate, a published Lighthouse score, or uptime measured against a public status page. No proof, no claim.
- Alternatives considered.Record the two or three positions you rejected and why. A Confluence page or a Notion doc with dated decision entries does the job. This is the positioning record, and it stops the team relitigating the same argument in month three.
- Message test by segment.Put the draft in front of five to ten people per segment, then ask them to say back what the product is, who it is for, and how it differs. Jakob Nielsen found that five users surface about 85 percent of usability problems, and message tests follow the same math. Comprehension, not enthusiasm.
- Claim strength.Rank each claim by how much evidence sits under it. Weak claims ship as qualified statements, or they do not ship. The FTC's reasonable basis has to exist before publication, not after a complaint.
- Sales and support alignment.The deck, the site, the demo script and the support macros carry the same position. Check all four side by side before the launch review. Mismatch here is where positioning collapses after launch day.
Pass
- Market frame
- Buyer names the budget line
- Segment and job
- One buyer, one user, one job
- Difference
- Competitor needs a rebuild to match
- Proof
- Dated source on file
- Alternatives
- Record shows rejected options
- Message test
- Segment restates the position unprompted
- Paid panel
- Ten completed responses per segment at $75 to $200 each
- Claim strength
- Every shipped claim has a dated source
- Sales alignment
- Deck, site, demo and macros match
Fail
- Market frame
- Buyer asks what category this is
- Segment and job
- Two segments sharing a sentence
- Difference
- Competitor matches it in a release note
- Proof
- "Everyone knows this"
- Alternatives
- No record exists
- Message test
- Segment repeats your tagline back
- Paid panel
- Three friendly customers asked at lunch
- Claim strength
- The top claim rests on one anecdote
- Sales alignment
- Sales rewrites the pitch on calls
Time the gates. Market frame, segment and difference belong at release planning, when changing course is still cheap. Proof, alternatives and the message test run two to three weeks before launch, because panels need booking. Claim strength and alignment close in the final week.
Slogan versus defensible position
A slogan is a phrase the marketing team owns. A position is a claim the product team has to keep true. "The fastest onboarding in the category" is a slogan until you publish the measured time, the cohort, and the date.
Slogan vs Defensible Position
Slogan
- Owner
- Marketing team
- Truth test
- Phrase only
- Evidence
- None required
- Tool
- Copy edit
- Survives review
- No
Position
- Owner
- Product team
- Truth test
- Must stay true
- Evidence
- Measured time, cohort, date
- Tool
- Amplitude or Mixpanel funnel
- Survives review
- Yes, with sample size
Measure it with a defined funnel in Amplitude or Mixpanel, starting at account creation and ending at the first successful run, and publish the sample size. Twelve accounts timed by hand on a spreadsheet will not survive a procurement review.
The product positioning work sits upstream of the launch plan. Get it wrong and every downstream asset inherits the error.
Evidence and the substantiation standard
The FTC advertising substantiation policy requires a reasonable basis for objective claims before you publish them. That standard applies to the exact promise, audience and qualification you put in market.
Substantiation Standard Checklist
- FTCreasonable basis before you publish
- Match exact promise, audience, qualification
- Safety claims need stronger support
- Reviewsno fake, conditioned, hidden incentives
- AI claimsscope statement, not certification
- Open standardscheck the GOV.UK guidance
The FTC weighs the claim type and the harm a false one could cause, so a safety claim needs stronger support than a preference claim. Canadian teams should confirm the equivalent expectation with counsel; the Competition Act governs deceptive marketing claims here.
Reviews and endorsements carry their own rules. The FTC guidance for marketers using reviews covers fake feedback, selective solicitation, conditioned incentives, hidden relationships and paid ranking. If a testimonial sits under your position, check it against that list first.
Where AI changes a workflow the position depends on, the NIST AI RMF Playbook sets out voluntary actions under govern, map, measure and manage. It is a reference, not a certification and not a ranking. A vendor claiming alignment without a scope statement owes you the evidence.
Open standards matter when the position rests on interoperability or portability. The GOV.UK open standards guidance links open standards to reuse and reduced supplier dependence. It governs UK public-service work, so treat it as a portability prompt for your own market rather than a rule.
Worked example: a failed gate
A team positions a warehouse scanner as "works with any WMS." The difference claim is integration. The proof is one customer's setup. Gate four fails.
Failed Gate Four: Fix or Fund
Claim 'works with any WMS' backed by one customer?
Narrow claim, name tested systems
Fund integration work, hold position
The fix is not a longer sentence. Either the claim narrows to the systems actually tested, and those get named on the page, or the integration work gets funded and the position holds until the evidence catches up. Shipping the broad claim and correcting it later costs the segment's trust, which is the asset the position was built on.
Common questions
What is the first decision in a positioning checklist?
Name the owner and the market frame, then write the difference claim you intend to defend. Everything else on the list tests whether that claim survives contact with evidence and with buyers.
How do you test a position before launch?
Run the message test by segment and record what people say back. If they restate your position in their own words, it landed. If they repeat your tagline, they heard a slogan.
What should a team avoid?
Confusing a slogan with a defensible position, and letting a claim outrun its proof. Keep the positioning record with the rejected alternatives so the decision does not get reopened without new evidence.
