writing-pr-faqs
Writing PR/FAQs
What is a PR/FAQ?
A document that starts with the end in mind:
- Press Release: Announcement of the finished product
- FAQ: Questions stakeholders would ask
Structure
1. Press Release
Headline
Attention-grabbing summary of the benefit.
Subheadline
Target customer and key benefit.
Problem Statement
What problem does this solve?
Solution
How does this product solve it?
Quote from Leader
Why this matters to the company.
How It Works
Brief explanation of the product.
Quote from Customer
Testimonial about the benefit.
Call to Action
How to get started.
2. Internal FAQ
Business-focused questions:
- Why should we build this?
- What's the market size?
- Who are competitors?
- What are the risks?
- What does success look like?
3. External FAQ
Customer-focused questions:
- What is this product?
- Who is it for?
- How much does it cost?
- How do I get started?
Example Headline
[Company] Launches [Product] to Help [Customer] [Benefit]
[City, State] - [Date] - [Company] today announced [Product],
a new [category] that [key benefit] for [target customer].
Tips
- Write like it's real (present tense)
- Focus on customer benefit
- Be specific with metrics
- Address hard questions in FAQ
- Iterate based on feedback
Resources
More from nguyenhuuca/assessment
compliance
Ensure regulatory compliance. Use when implementing GDPR, HIPAA, PCI-DSS, or SOC2 requirements. Covers compliance frameworks and controls.
17requirements-analysis
Analyze and refine product requirements. Use when clarifying scope, identifying gaps, or validating requirements. Covers requirement types and analysis techniques.
16security-review
Conduct security code reviews. Use when reviewing code for vulnerabilities, assessing security posture, or auditing applications. Covers security review checklist.
13identity-access
Implement identity and access management. Use when designing authentication, authorization, or user management. Covers OAuth2, OIDC, and RBAC.
12execution-roadmaps
Create execution roadmaps for projects. Use when planning multi-phase projects or feature rollouts. Covers phased delivery and milestone planning.
12cloud-native-patterns
Apply cloud-native architecture patterns. Use when designing for scalability, resilience, or cloud deployment. Covers microservices, containers, and distributed systems.
12