Positioning is a decision, messaging is its expression
A positioning statement is short and internal. It names the target segment, the category the product competes in, the point of difference and the reason to believe it, and it is written to be agreed rather than read by customers. Messaging is what customers read, and the gap between the two is where most inconsistency creeps in. If each writer works from the positioning directly, each will express it differently, and the website, the deck and the adverts drift apart. A messaging hierarchy closes the gap by expressing the positioning once, in a structured form, so that writers draw from the expression rather than reinterpreting the decision.
The method for arriving at the positioning itself, from segmentation and targeting to the choice of competitive frame, belongs to the positioning guide in the strategy section; the positioning hub explains how positioning feeds the rest of product marketing. This guide starts with a positioning decision that exists and asks how to turn it into messaging that can be used. The voice the messages are written in, the brand's tone, vocabulary and personality, is a separate decision owned by the branding root and covered in the brand identity and voice guide; messaging decides what is said, voice decides how it sounds. A brand tagline sits inside the same hierarchy rather than outside it, and the guide to writing a brand tagline covers deriving one from the position and checking any claim it makes.
The distinction matters when things go wrong. If buyers misunderstand what the product is, the positioning is unclear or the messaging has not expressed it. If buyers understand it but the copy sounds like every competitor, the voice is the problem. Diagnosing which is which saves a great deal of rewriting.
The messaging house
The common structure is a house: a roof, which is the core message that states the positioning in one line a buyer would recognise; pillars, which are the three or four reasons the core message is true; and foundations, which are the proof points under each pillar. Writers take the roof for headlines, a pillar for each section or slide, and the foundations for the body copy and the objection-handling.
| Level | What it is | Example for an invented scheduling product | Proof beneath it |
|---|---|---|---|
| Core message | The positioning in one line a buyer would say back | Rota planning that staff accept without argument | The pillars together |
| Pillar: fairness | The reason buyers in the segment care most about | Shifts allocated by rules the team agreed, not by whoever asks first | Visible rules engine; customer story from a care provider |
| Pillar: speed | The time saving relative to the current alternative | A month's rota in an afternoon, not a week | Timed demo; documented import from the usual spreadsheet formats |
| Pillar: compliance | The risk the product removes | Working-time rules checked before the rota is published | Rule library maintained against published regulations; audit log |
| Foundations | Proof points under each pillar | Demo flows, named customers, certifications, documented capabilities | The evidence a sceptic would accept |
The table's job is to force a proof column. A pillar with nothing beneath it is a hope, and the discipline of the house is that hopes are either substantiated or removed. Each pillar also gets a short list of the features that support it, so that the product team can see which features carry the message and the content team knows which to show. The value proposition canvas is useful before the house is built: it maps what customers are trying to do and what pains and gains they have against what the product does, and the pillars usually fall out of the strongest fits.
Keep the whole house on one page. If it needs more, it is a feature list wearing a messaging framework's clothes. The messaging house template gives the full version to copy, adding a proof register with sources, segment variants, channel cuts and an owner to the roof and pillars. At the level of a single feature, the FAB framework of features, advantages and benefits turns the features listed under each pillar into copy.
Proof points and substantiating claims
A proof point is the evidence a sceptical buyer would accept for a pillar. Capability proof is the product doing the thing, in a demo, a screenshot or a free trial. Customer proof is a named organisation describing its experience, with permission and in its own words. Third-party proof is an independent certification, audit, award or review. Process proof is a documented way of working that explains why a claim holds, such as how a rule library is kept current. Each pillar needs at least one proof point of a kind the segment finds credible; enterprise buyers weight certifications and references, small-business buyers weight the demo and the trial. Customers' own words matter beyond proof as well: the tutorial on turning customer language into page copy codes reviews, support tickets and sales notes into jobs, objections and exact phrases that give each pillar its wording on the page.
Substantiation is also a regulatory question, and the direction of the rules is consistent across markets even where the detail differs. In the UK the Advertising Standards Authority administers codes that require objective claims to be capable of substantiation before they are made, and treats comparative claims and claims about efficacy, performance and testing with particular care. In the US the Federal Trade Commission's business guidance sets out a similar expectation that advertisers hold a reasonable basis for objective claims before publishing them. The practical consequence for a messaging hierarchy is that every objective claim in it should have its evidence recorded next to it, with a date, so that the person writing an advert can check rather than hope. Superlatives, implied comparisons and claims about what a product will achieve for a buyer are the usual trouble spots. None of this is legal advice; when a claim matters commercially, the compliance or legal team reviews it before it ships.
Proof decays like positioning. A customer story from a company that has since churned, a certification that has lapsed, or a capability that was removed in a release are all common, and the hierarchy's review should check the foundations as well as the pillars. When a capability is deliberately removed, the guide to retiring a feature or product lists the pages, decks and comparisons that keep claiming it until someone changes them.
Messaging by segment, persona and stage
One hierarchy serves the product, but not every buyer reads it the same way. Three dimensions of variation cover most needs, and the rule is to vary the emphasis and the proof rather than the pillars.
By segment, the pillars keep their order of importance from the positioning, but the lead pillar and the examples change. A product sold to both agencies and in-house teams might lead with speed for agencies, whose economics depend on it, and with fairness for in-house teams, who live with the result. The core message stays the same.
By persona, the proof changes. The economic buyer wants the cost case and the risk removed; the user wants to see the product doing their job; the technical evaluator wants integrations, security and administration. The hierarchy should list, for each pillar, the proof that each personaA research-based profile of a typical customer type: goals, problems and buying behaviour. finds persuasive, so that a deck for a finance director and a demo for a team lead draw on the same pillars with different foundations.
By stage of the FunnelModel of the customer journey stages., the message's job changes. Early, the problem and the category matter more than the product; the message explains that a better way exists. Mid-stage, the pillars and the comparison to the alternatives carry the weight. Late, the proof carries it: references, trials, contract terms, the specifics an evaluator needs to say yes. A messaging hierarchy that only works at one stage leaves the others to improvise, and the improvisation is where contradictions appear.
Write the variants into the same document, as a matrix of pillar against segment or persona, rather than as separate documents that will diverge.
Adapting messages by channel
A channel changes the length, the format and the attention available, and the hierarchy has to survive the change. The roof becomes a headline in search advertising, a subject line in email, a hook in video and the first line of a sales call. A pillar becomes a section on a landing page, a slide in a deck, an advert in a sequence, a paragraph in a proposal. The foundations become the body copy, the demo script, the case study and the objection-handling notes. The adaptation is legitimate so long as the meaning holds; the failure is when a channel team rewrites the message to fit a format and changes what it claims. A press interview is a channel too, and the tutorial on preparing a spokesperson for a media interview shows how a few pillars and their proof points become spoken answers that hold their meaning under questioning.
Two checks keep channel adaptations honest. The first is message match: the message a person saw in the advert or the email should be the message they find on the page they land on, in the same words where possible, because a mismatch reads as a different offer. The message match guide in the conversion root covers the mechanics. The second is a review of click-through (CTRShare of impressions that result in a click.) alongside conversion rate (CVRShare of visits or clicks that convert.) by message, since a channel adaptation that raises clicks and lowers conversion has usually promised something the page does not deliver. Agencies and channel specialists should receive the hierarchy with the variants, not a brief that paraphrases it, so that what they produce can be checked against the source.
Testing messages
A message that reads well internally still needs evidence that buyers understand it and that it moves them. Testing has qualitative and quantitative forms, and most launches use both.
Qualitative tests put candidate messages in front of a small number of target buyers, in interviews or at the end of sales calls, and ask three things: what did you understand this to mean, what did you doubt, and what would you want to know next. Comprehension comes first; a message buyers like but misread will produce the wrong leads. Doubt reveals where proof is missing. The next-question reveals what the page or the deck should answer immediately after. Three or four rounds of a handful of conversations each are usually enough to choose between candidates and to fix the wording of the winner.
Quantitative tests run candidate messages as variants and read the results. A search or social advert A/B TestControlled comparison of two variants. compares headlines on click-through and, if the landing page is held constant, on conversion. A landing page test compares the lead message with the proof held constant. An email test compares subject lines, which is really a test of the roof. The discipline in every case is to change one thing, hold the rest, run long enough for the difference to be real, and read the metric that matters for the stage rather than the one that moves fastest. A message that wins on clicks and loses on qualified conversions has not won.
Sales tests are the cheapest form: give two representatives different framings for a fortnight and listen to the recordings. The result is not statistically clean, but it reveals which framing buyers pick up and repeat back, which is the strongest sign that a message has landed. Record every test, the variants, the result and the decision, in the hierarchy's change log, so that the next revision starts from what is known.
A compliance software company tests two core messages
Brightwater Compliance sells policy-management software to regulated firms. Its messaging hierarchy had led with "compliance without the admin", and the product marketer wanted to test it against "audit-ready every day". Fourteen interviews with compliance officers found that 9 of them read the first message as a claim about automation they did not believe, while 12 understood the second and 8 asked, unprompted, how the audit trail worked. A paid search test ran both as headlines on the same landing page for three weeks: the first produced a click-through rate of 3.1% and a demo-request rate of 1.4%, the second 2.6% and 2.3%. Sales reported that prospects who arrived under the second message asked about the audit log in the first call. The hierarchy was revised with "audit-ready every day" as the roof, the audit trail promoted to a pillar with a timed demo and a customer story as proof, and the test recorded in the change log.
For a product with no customers to quote yet, positioning statement decisions for a launch shows how provisional proof points are chosen, tested before launch day and replaced on a dated review.
When a product launches before any customer proof exists, the guide to running STP for a new product launch shows how to mark proof points as provisional and replace them later.
Common mistakes
- Pillars that are features. "Real-time dashboard" is a feature; the pillar is what the dashboard lets a buyer do that they could not do before.
- Pillars without proof. A claim with nothing beneath it will be removed by the first sceptical buyer or the first regulator; better to remove it yourself or substantiate it.
- Too many pillars. More than four and the hierarchy stops guiding anyone; merge the ones that overlap.
- Separate documents per segment. Variants in separate files diverge within a quarter; keep them as a matrix in one document.
- Channel teams rewriting the claim. Adaptation changes the form, not the meaning; a brief that paraphrases the hierarchy invites both.
- Testing preference instead of comprehension. Buyers choosing the message they like tells you less than buyers explaining what it means.
- Letting proof lapse. Customer stories, certifications and capabilities change; review the foundations with the pillars.
- Confusing messaging with voice. If the meaning is clear but the copy sounds generic, the fix is in brand voice, not in the hierarchy.
The pricing and packaging guide covers the other deliverable that follows from positioning, and the two should be built from the same decision so that the pricing page reads as a continuation of the messaging rather than a surprise at the end of it.
