Read Achilles markRead Achilles

Marketing

Positioning Statements Die in the Wild

Every brand team has written the sentence. For a defined audience, we are the category that delivers the defining difference — the frame is taught in every marketing programme, mine included, and it produces a small…

♥ 0 Sign in to like 1 comment

This post’s retention & record terms are stated in full in the colophon below.

Every brand team has written the sentence. For a defined audience, we are the category that delivers the defining difference — the frame is taught in every marketing programme, mine included, and it produces a small, polished paragraph that everyone in the room can recite. Then the brand goes out into the wild, and the wild edits it. I have come to believe that positioning statements rarely fail because they are badly written. They fail because they are not the thing they claim to describe. [author assertion]

A positioning statement is a promise drafted by a committee. A brand, as customers actually encounter it, is something else: it is what the firm's behaviour teaches them to expect. Customers do not read statements. They read the product that shipped late, the support reply that took four days, the price that contradicted the premium story, the update that removed the feature they loved. Each of these acts is a copy edit performed on the brand by the only editors whose revisions count. [author assertion]

The wild kills statements in predictable ways. The difference the statement names turns out to be one the operations cannot deliver at scale. The audience the statement targets turns out to buy for reasons the research politely concealed. The competitor the statement defines itself against simply ignores the frame and competes on another axis entirely. None of these is a communications failure. All of them arrive dressed as one, because the statement is the artefact the organisation knows how to revise. [author assertion]

Where statements genuinely earn their keep is inside the firm. A good positioning statement is a coordination device — a decision rule that a product manager, a service agent and a pricing analyst can each apply, alone, at midnight, and arrive at roughly the same answer. Judged as advertising, most statements are fiction. Judged as internal law, the best of them are excellent. The tragedy is that firms keep score on the wrong function: they polish the sentence for the customer who will never read it, instead of testing whether the employee can use it. [author assertion]

So here is the exercise I now assign, in place of the traditional one. Take the last hundred customer-facing decisions your organisation actually made — the shipments, the refusals, the prices, the apologies — and write the positioning statement they imply. Then place it beside the official one. The distance between the two documents is your brand strategy problem, stated honestly, and closing that distance is almost never a writing task. [author assertion]

Brands as promises are liabilities, because promises are graded on delivery by people who did not attend the workshop. Brands as behaviour are assets, because behaviour is what compounds. Manage the behaviour. Let the statement follow, cap in hand, and be pleasantly surprised when it turns out to be true. [author assertion]

Tony Liang

All posts by Tony Liang → · Follow Tony Liang by RSS

The Board 20 essays 0 corrections Agent citations: —— — citation attached ≠ claim validated As of 16 November 2026 Full board →

Provenance

About this version

How this post was verified, labelled and shared — in plain language first. The complete machine-readable record is kept below, word for word, for anyone who wants to check it.

Version
1 · in good standing
Author
Tony Liang · verified at publication
Published
6 Nov 2026
Claims
6 labelled — 6 author assertion
Citations
No external citations
Distribution
Shared with the author’s consent — including to agents acting for readers, under the author’s per-post opt-in
Content fingerprint
a391cd80…6d3ab7
Full verification record

The verbatim graded record of this version: identifiers, claim classes, citation targets, hashes and standing, exactly as issued.

This record is also published in structured text for agents and tools — the same fields, word for word. View structured text

House editorial — Read AchillesAuthor verification: verifiedStanding: governingHash: a391cd8057bc9fd2d254bd2c7946e0e2500495b7f08e23e019171a9aa86d3ab7

Version & standing

Post post-positioning-statements-die-in-the-wild-ef9abf · version 1 (post-positioning-statements-die-in-the-wild-ef9abf-v1)

@tony-liang · verified state at publish: verified

Published: 2026-11-06T23:54:22.926Z · Standing: governing

Claims & citations

  • c-1: author_assertion
  • c-2: author_assertion
  • c-3: author_assertion
  • c-4: author_assertion
  • c-5: author_assertion
  • c-6: author_assertion

    Disclosure & trust

    When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule.

    When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule.

    Integrity & distribution

    Content hash: a391cd8057bc9fd2d254bd2c7946e0e2500495b7f08e23e019171a9aa86d3ab7

    Distribution: opted_in

    Canonical presentation: https://blog.readachilles.com/post-positioning-statements-die-in-the-wild-ef9abf/

    What we retain, and why — the retention disclosure

    The retention disclosure for this version is the disclosure line of record, stated in full in the colophon fields above.