Positioning brief
Translate product capability into a specific reason for a defined buyer to act.
Use when buyers understand features but cannot explain why they should choose the product now.
Before the working session
- Collect recent buyer language from interviews, loss notes, reviews, and public alternatives. Separate direct quotes from internal interpretation.
- List the real alternatives: an incumbent, a spreadsheet, a service provider, an internal build, or doing nothing.
Run the process
Pick one buying context
Describe the role, workflow, trigger, and current constraint. A statement written for every buyer rarely survives a real comparison.
Map alternatives honestly
For each alternative, note what it does well, where it fails in this context, switching cost, and why a buyer might still prefer it.
Make a narrow claim
Link one capability to an outcome the buyer values. Name the mechanism and the proof available today. Keep unproven claims out of headline copy.
Test without coaching
Show a one-page message to five target buyers individually. Ask whom it serves, what it replaces, why it differs, and what they doubt. Record their words before explaining. Revise the misunderstood claim.
Fictional example: “Automate operations with AI” becomes “For operations teams reconciling weekly site reports, consolidate exceptions into one review queue.” The team tests whether buyers recognize the workflow and whether the queue is meaningfully better than their spreadsheet.
Failure checks
- A competitor list is not a positioning strategy.
- “Faster and easier” needs a specific task and measured proof.
- Comprehension is distinct from purchase intent.
Editable workbook and filled example
Choose a message that connects a specific buyer problem to supported differences. Preserve the alternative the buyer would actually use.
Download editable Word workbook ↓
What you will complete
- Audience and situation
- Problem and consequence
- Actual alternative including doing nothing
- Proposed category and promise
- Message owner and version
- Validation audience and review date
Write one defensible claim per row. Avoid turning a feature into an unsupported outcome. Compare messages using the same audience and task; record objections as evidence rather than editing them away.
Fictional filled evidence record
| Claim and buyer relevance | Proof source and scope | Limit or unsupported inference |
|---|---|---|
| Reduce duplicate reconciliation work | Fictional workflow test removes one manual copy step | Does not establish time savings for other teams |
Fictional action record
| Message variant | Audience and context | Observable response | Owner and decision rule |
|---|---|---|---|
| Reconcile reports without copying totals | Operations reviewers comparing spreadsheet workflow | Can explain the difference without prompting | Marketing lead; revise if misunderstood |
Decision and next review
Use the workflow-specific message in a bounded test. Remove the claim that it saves ten hours because the available test only demonstrates one eliminated copy step.
Marketing lead tests comprehension with eligible reviewers and records interpretations, objections and alternatives before choosing the final message.
The Word file includes editable response fields and blank tables. These examples are invented and do not represent a real buyer or employer.