In short
A PR/FAQ and a PRD answer different questions. The PR/FAQ comes first and answers 'should we build this?' in the form of a press release and FAQ. The PRD comes after and answers 'how do we build it?' as structured requirements. The strongest PRDs are built directly on an approved PR/FAQ.
Side by side
| Dimension | PR/FAQ | PRD |
|---|---|---|
| Question it answers | Should we build this? | How do we build it? |
| When it's written | Before committing | After committing |
| Format | Press release + FAQ | Structured requirements |
| Primary reader | Decision-makers | The build team |
| Main risk it kills | Building the wrong thing | Building it wrong |
When to use PR/FAQ
- You're deciding whether an idea is worth pursuing at all.
- You need to align leadership on the customer and the value.
- The idea is still fuzzy and needs a so-what test.
When to use PRD
- The decision to build is already made.
- Engineering and design need concrete requirements.
- You're scoping milestones and success metrics.
The verdict
They're sequential, not competing. Write the PR/FAQ to decide; write the PRD to deliver. Skipping the PR/FAQ is how teams end up with a beautifully specified product nobody wanted.
Write the press release before you write the code
Turn your idea into an Amazon-style PR/FAQ, a scored verdict, and a PRD - free to start.
Start your PR/FAQ
Design by The Resonance | Powered by GPC – The AI Transformation Company
