create-a-messaging-framework

name	create-a-messaging-framework
category	write
description	Create a reusable message system linking audience, value, proof, objections, and channel choices. Use when teams describe the same offering inconsistently or need evidence-backed language across content and conversations.

create-a-messaging-framework

Align on claims and proof while allowing each channel to sound natural.

Procedure

1. Gather positioning, audience evidence, product facts, research, objections, alternatives, and approved claims.
2. Define the primary audience situation and the decision the framework supports.
3. Write a message hierarchy: organizing value, three to five supporting ideas, and the proof for each.
4. Separate outcomes, capabilities, mechanisms, and evidence so features do not masquerade as benefits.
5. Build an objection map with truthful responses, qualification questions, and cases where the offering is not a fit.
6. Record approved terms, prohibited shorthand, sensitive claims, and legal or technical review needs.
7. Add audience and channel adaptations without changing the underlying facts.
8. Create examples for homepage, email, sales conversation, announcement, support, and short description.
9. Test comprehension, credibility, distinctiveness, and recall with representative readers.
10. Publish an owner, version, source links, expiry dates, and review triggers.

Guardrails

• Never invent customer outcomes, market demand, comparative superiority, or product capability.
• Do not erase important limitations in shorter variants.
• Preserve audience language without appropriating private or stigmatizing terms.
• Treat the framework as guidance, not a script that overrides context.

Done

• A messaging framework document links every major claim to proof
• Objections, non-fit cases, limitations, and review needs are explicit
• Channel examples remain factually consistent
• Reader tests and revision evidence are recorded