How do you categorize your messaging, and what format do you apply for each category? Say release notes, feedback requests, beta testers requests

Interesting way to phrase this, but I like to use those as INPUTS for my messaging. Then I look at what am I trying to create messaging for? A solution/platform, new product pillar, or a launch? I like to have a "single source of truth" messaging docs both for the overall platform and each (seasonal) launch to start.

From there, I build a messaging pyramid:

• Overview: What is the overarching solution and what it does

  • For example: "MetaRouter is an enterprise-grade customer data collection and integration solution that ensures quality, compliance, and control."

• Messaging Pillars: 3-5 pillars that capture the essence of the product and its differentiation.

  • Each pillar should have:

    • A clear statement of the message - I like to call this an "impact statement." For example: "Create a reliable, centralized point of collection that can feed your ecosystem with confidence in real time."

    • Supporting evidence or data to back it up

    • How it relates to the target audience’s needs

• Value Props - HOW a product or service solves a problem, delivers specific benefits, and addresses the needs of a target audience

• Differentiation Points - talk about the unique features, qualities, or aspects of a product that set it apart from competitors in the market (and which competitors).

  • NOTE: This does not need to be a feature by feature comparison imo.

• Use Cases (with examples) - describes a specific scenario in which a product or service is used to achieve a particular goal or solve a problem. It often includes details about the user, the context, and the desired outcome.

• Features and capabilities (HOW your product supports these use cases)

• Customer and industry stats

Happy to share a template for this!