PR FAQs for Product Documents — Everything Product Managers Need to Know - Deepstash
PR FAQs for Product Documents — Everything Product Managers Need to Know

PR FAQs for Product Documents — Everything Product Managers Need to Know

Curated from: medium.com

Ideas, facts & insights covering these topics:

5 ideas

·

3 reads

1

Explore the World's Best Ideas

Join today and uncover 100+ curated journeys from 50+ topics. Unlock access to our mobile app with extensive features.

Basic PR FAQ Format

Basic PR FAQ Format

The PR FAQ should be the starting point for all of your other product documents: 

  • Engineering team should be able to use PR FAQ as starting point for Scoping. Design team should be able to use PR FAQ as starting point for design documents.
  • The sales team should be able to use your PR FAQ to design the sales playbook for the new product 
  • Marketing should be able to use the PR FAQ to create actual press releases 
  • Your executive sponsors should be able to use your PR FAQ to understand the resource allocation needed to build the product, etc. 

2

1 read

FAQs

FAQs

A set of public frequently-asked questions and their answers. This should be a comprehensive list of everything that a customer might want to know about the product. 

It should include any reasonable question that comes up when discussing the new product/feature with customers and customer-facing teams during the development of the product/feature. 

2

0 reads

Internal FAQs

Internal FAQs

A set of private, internal frequently-asked questions and their answers in a format that can be understood by every other stakeholder. 

An FAQ might include wireframes of a product with a strong UX component, or a link to separate wireframe documents, but the PR should rely on text alone. This will allow all internal stakeholders to get clarity on the product/feature. 

2

1 read

Why does the PR FAQ format work?

Why does the PR FAQ format work?

The PR/FAQ format works because it is: 

  1. Customer-centric 
  2. Forcing your assumptions to be explicit 
  3. Interpretable by any stakeholder 
  4. Increases the ownership of stakeholders 
  5. Simple enough to be created by any stakeholder 

2

0 reads

How does this PR FAQ format differ from Amazon?

There are three main ways that my PR FAQ documents differ from Amazon’s: 

  • Allow some design elements 
  • Allow more details about potential solutions 
  • Elicit feedback in multiple different ways 

2

1 read

IDEAS CURATED BY

evelynlopez

Television/film/video developer

Evelyn Lopez's ideas are part of this journey:

Product Management Essentials

Learn more about product with this collection

Essential product management skills

How to work effectively with cross-functional teams

How to identify and prioritize customer needs

Related collections

Read & Learn

20x Faster

without
deepstash

with
deepstash

with

deepstash

Personalized microlearning

100+ Learning Journeys

Access to 200,000+ ideas

Access to the mobile app

Unlimited idea saving

Unlimited history

Unlimited listening to ideas

Downloading & offline access

Supercharge your mind with one idea per day

Enter your email and spend 1 minute every day to learn something new.

Email

I agree to receive email updates