Back to Your Feed

What types of messaging documents or frameworks are typically shared with stakeholders from different teams (i.e. product, marketing, execs, etc.)?

5 Answers
Diana Smith
Diana Smith
Hashi Senior Director of Product MarketingJuly 17

We find it helpful to have a single messaging document that everyone in the company can access. It goes through our mission/vision/description all of the way down to messaging segmented product, customer type, and industry vertical. A shared document enables all of the teams to be on the same page and tell the same story to the market.

Before we’re ready to share messaging broadly (and put it in the master document), we collaborate with different teams to have the highest confidence that the messaging is going to land. 


Executives — Collaborate on mission and vision, consulted on product naming and packaging
Marketing team — Collaborate on key value propositions, category decisions, and boilerplate, test different headlines and messages via campaigns and our site
Product team — Collaborate on quarterly themes we align to for product development and product launches, co-own the customer-facing product roadmap, work closely on product-level messaging for new products refining the audience, positioning, and key use cases with the PM
Sales team — Test messaging, value propositions, and pricing in market, finalize the sales deck and talk tracks together, identify common objections to create messaging for

3746 Views
Sarah Din
Sarah Din
Quickbase VP of Product MarketingSeptember 25

We are in the process of creating an internal messaging hub, where all of our messaging will live. This hub will be on our Confluence site (which is what we use as our internal Wiki for the org). Our goal is to host all of our messaging docs on that hub, and give everyone access to it as a "Single Source of Truth" (SSOT). For the rollout, we also did a focus group with leads from different functions to get feedback on what formats work best for them.

Some teams, such as marketing or product teams, will likely want to review messaging in detail, but for a lot of other teams, you likely need “snackable” versions of your messaging. The most important thing to keep in mind is that you need to deliver this information in a variety of ways, and you need to deliver it over time so you are reinforcing it again and again to make it land.

Here are some ways we have tailored this content to different stakeholders:

  • Executives: we have created an executive pitch that our leadership team can use for anything from internal presentations to analysts briefings or executive customer meetings, based on our updated messaging - this is our corporate messaging at the highest level
  • Marketing/Product: We have our core value proposition, elevator pitches in different word counts, use cases mapped to product features and functionality, buyer persona overviews, ICPs, and a doc on proof points and customer testimonials. We also link to our competitive intel from our messaging docs, but that is an entirely separate initiative.
  • Sales: Sales pitch decks, talk track, training videos, documentation on objection handling and any competitive positioning docs.
2408 Views
Scott Schwarzhoff
Scott Schwarzhoff
Unusual Ventures Operating PartnerFebruary 7

I've always been in the product team, so that's the most natural interaction for me. For PM, we'd collaborate on how to position new products. We built a spreadsheet that had product pillars>concepts>key features>'feature rank'>feature flags, price.

You may be asking, 'what's a feature rank' and that's where I LOVED using this handy three-point rating scale that was drilled into me at Citrix:

* Table-stakes: required capabilities that everyone and where there’s no clear uniqueness.
* Competitive differentiators: everyone has the capability, but your company does it better
* Purple cows: your company provides this capability and no one else has it

So in practice, here’s how that netted out for our entry into the mobility market:

* Mobile Device Management: table stakes. Everyone has it, no one had a big advantage
* Mobile App Management: differentiated. We put a security ‘wrapper’ around applications that protected them from security breaches. Not unique to us but the easy wrapping capabilities were novel.
* Mobile Data Management: purple cow. No mobility vendor offered a secure Dropbox-like capability. We generated 70% of our mobility sales based on this unique capability.

Ok, enough geeking out over product-level messaging. Here's a messaging doc template that nets out all the core messaging that a marketing/demand-gen team will need. Beyond product and marketing, I don't think sharing messaging frameworks is very helpful. The other teams are more interested in outputs / deliverables from using the core messaging framework.  

Hope this helps!

2118 Views
Francisco M. T. Bram
Francisco M. T. Bram
Albertsons Companies Vice President of MarketingFebruary 14

I believe in promoting a very collaborative environment where the best information is always shared and used to inform the different workstreams. At Uber we create one source of truth document, called the Marketing Brief. This brief can be shared with every stakeholder in the organization but is mostly used to inform the cross-functional work needed to launch a product or campaign. This Marketing Brief is used by our creative teams to help design the campaign, by our Growth marketing teams to plan for performance marketing, by our sales enablement teams to help develop a sales education plan, by product management, etc. 

The Marketing Brief contains the following sections:

1. Background context on the project 

2. Business opportunity

3. Business KPIs

4. Marketing KPIs

5. Key research or user insights

6. Product Messaging/Narrative

7. Value proposition (Reasons to Believe)

8. Comms and Channel strategy

9. Measurement plan

10. Deliverables

11. Timeline

12. Budget

13. Cross-functional team members

14. Useful resources or links

15. Review and signoffs 

2337 Views
Grace Kuo
Grace Kuo
Chan Zuckerberg Initiative Product MarketingMarch 6

The key thing for messaging frameworks that are shared with your org is know your audience.

As PMMs, we are often creating different messages for different audiences. When you share your framework, be clear on how to use the messaging, and for whom the messaging is created for. 

i.e. Whenever I prepare a launch, I always label the messaging the SALES team should use in talking to prospects, messaging Customer Success should be using for customers, key value props for Marketing, etc.

For Leadership, it's really important to give them Executive Summaries..again just to show that your team is on top of the launch and that they get visibility on what's happening with the GTM/product, etc. 

A quick summary of key elements:

- Audience

- Key Value Props

- Launch Timeline

- Pricing/Packaging (if applicable)

- Outcomes desired

- Competitive advantages/comparison, etc.

1798 Views
Developing Better Messaging
Thursday, April 18 • 12PM PT
Developing Better Messaging
Virtual Event
Alex Lopes
Arpana (Arpita) Neelmegh
Jeff Rezabek
+2
attendees
Top Product Marketing Mentors
Christy Roach
Christy Roach
AssemblyAI VP of Marketing
Tanya Khakbaz
Tanya Khakbaz
Stripe Head of Product Marketing
Sarah Din
Sarah Din
Quickbase VP of Product Marketing
Sherry Wu
Sherry Wu
Gong Director of Product Marketing
Jeffrey Vocell
Jeffrey Vocell
Panorama Education Head of Product Marketing
Mary Sheehan
Mary Sheehan
Adobe Head of Lightroom Product Marketing
Jenna Crane
Jenna Crane
Klaviyo Head of Product Marketing
Abdul Rastagar
Abdul Rastagar
GTM Leader | Marketing Author | Career Coach
Amanda Groves
Amanda Groves
Crossbeam Senior Director Product Marketing
Amanda Groves
Amanda Groves
Crossbeam Senior Director Product Marketing