GTMGO TO MARKETPLAYBOOKS
← All playbooksPositioning · Field guide

Positioning brief

Translate product capability into a specific reason for a defined buyer to act.

When to use this

Use when buyers understand features but cannot explain why they should choose the product now.

Before the working session

Run the process

01

Pick one buying context

Describe the role, workflow, trigger, and current constraint. A statement written for every buyer rarely survives a real comparison.

02

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.

03

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.

04

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 worked example

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

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 relevanceProof source and scopeLimit or unsupported inference
Reduce duplicate reconciliation workFictional workflow test removes one manual copy stepDoes not establish time savings for other teams

Fictional action record

Message variantAudience and contextObservable responseOwner and decision rule
Reconcile reports without copying totalsOperations reviewers comparing spreadsheet workflowCan explain the difference without promptingMarketing 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.

See more fictional examples → · Open planning tools →