writing-prds

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Writing PRDs

撰写PRD

Help the user write effective product requirements documents using frameworks and insights from 11 product leaders.

帮助用户运用11位产品负责人的框架和见解，撰写有效的产品需求文档。

How to Help

如何提供帮助

When the user asks for help with PRDs:

Start with the why - Ask about the problem being solved and why it matters now, before features
Define success upfront - Help them articulate how they'll know the feature succeeded
Choose the right format - Discuss whether they need a traditional doc, a prototype, or executable evals
Keep it actionable - Ensure the document leads to clear team action, not just documentation

当用户请求PRD相关帮助时：

从“为什么”入手 - 在讨论功能之前，先询问要解决的问题以及它为何在当下至关重要
提前定义成功标准 - 帮助他们明确如何判断功能是否成功
选择合适的格式 - 讨论他们需要的是传统文档、原型还是可执行评估方案
确保文档具备可操作性 - 确保文档能引导团队采取明确行动，而非仅停留在记录层面

Core Principles

核心原则

Lead with problem and context

以问题和背景为核心

Maggie Crowley: "The most important section is the first part - what is the background and context? What is the problem, why does it matter, and why does it matter now?" Center the team on the 'why' and the urgency before discussing solutions.

Maggie Crowley：“最重要的部分是开头——背景信息是什么？要解决的问题是什么？它为何重要，又为何在当下至关重要？”在讨论解决方案之前，先让团队聚焦于“为什么”和紧迫性。

The PR/FAQ forces clarity

PR/FAQ框架倒逼清晰度

Bill Carr: "Whenever we're devising a new product, we start by writing a press release describing it in a way that speaks to the customer. The idea better jump off the page." Use the PR to describe customer, problem, and solution in factual, data-rich language.

Bill Carr：“每当我们开发新产品时，都会先撰写一份面向客户的新闻稿。这个想法必须足够有吸引力。”用新闻稿以事实详实的语言描述客户、问题和解决方案。

Demos before memos in AI age

AI时代，先做演示再写备忘录

Aparna Chennapragada: "If you're not prototyping and building to see what you want to build, you're doing it wrong. Prompt sets are the new PRDs." For AI features, include functional prototypes and prompt sets as core requirements.

Aparna Chennapragada：“如果你不通过原型开发来明确要构建的内容，那你就做错了。提示词集就是新的PRD。”对于AI功能，要将功能原型和提示词集作为核心需求纳入。

Evals as living PRDs

可执行评估作为动态PRD

Hamel Husain & Shreya Shankar: "This is the purest sense of what a product requirements document should be - this eval judge that's telling you exactly what it should be, and it's automatic and running constantly." Translate product requirements into executable evaluations for AI products.

Hamel Husain & Shreya Shankar：“这是产品需求文档最纯粹的形式——这个评估判断标准会明确告诉你产品应该是什么样的，而且它是自动化、持续运行的。”将产品需求转化为适用于AI产品的可执行评估方案。

Keep it lightweight for action

保持轻量化以聚焦行动

Eric Simons: "We tend to keep them pretty light. I like to have the minimal amount of context that ensures everyone's on the same page and that key outcomes will be present when we get there." Focus on key outcomes rather than exhaustive details that developers ignore.

Eric Simons：“我们倾向于让PRD保持轻量化。我只保留能确保所有人达成共识、且能保证最终实现关键成果的最少背景信息。”聚焦于关键成果，而非开发人员会忽略的详尽细节。

PRDs demonstrate craft

PRD体现专业能力

Vikrama Dhiman: "Is your PRD quality good enough? Are you writing drafts that go to care teams, marketing teams? You must have impact through the artifacts you work on." High-quality PRDs demonstrate professional craft and create clarity at scale.

Vikrama Dhiman：“你的PRD质量是否足够高？你撰写的草稿是否会同步给客服团队、营销团队？你必须通过产出的文档发挥影响力。”高质量的PRD体现专业素养，并能在团队范围内创造清晰的共识。

AI can scaffold the basics

AI可搭建基础内容

Claire Vo: "I had used ChatGPT to come up with a very serviceable PRD spec for this very technical product." Use AI to scaffold basics like user stories and out-of-scope items, then focus on high-level strategy and narrative.

Claire Vo：“我曾使用ChatGPT为这款技术型产品生成了一份相当实用的PRD规格说明。”利用AI搭建用户故事、范围外事项等基础内容，然后专注于高层战略和叙事。

Live PRDs reduce ambiguity

动态PRD减少歧义

Guillermo Rauch: "The product management team is now actually building the product. We've specced out in v0, think of it as a live PRD. The amount of detail - we're all saying 'just ship it.'" Interactive, animated prototypes reduce ambiguity and speed up approval.

Guillermo Rauch：“产品管理团队现在实际上也在参与产品构建。我们在v0版本中完成了规格定义，可以把它看作一份动态PRD。关于细节程度，我们的共识是‘直接发布’。”交互式、带动画的原型能减少歧义并加快审批流程。

Include the 'Why Now'

纳入“为何是现在”

Justify the timing of this investment against other opportunities. If you can't explain why this matters now versus later, the priority is questionable.

对比其他机会，证明这项投入的时机合理性。如果你无法解释为何这个需求在当下而非未来更重要，那么它的优先级就值得商榷。

Questions to Help Users

用于引导用户的问题

"What problem is this solving, and why does it matter now?"
"How will you know if this feature was successful - what metric moves?"
"Who is the customer, and what does their life look like after this ships?"
"What is explicitly out of scope to prevent scope creep?"
"Could you build a quick prototype instead of writing more documentation?"
"What are the key decisions that still need to be made?"

“这要解决的是什么问题，它为何在当下至关重要？”
“你将如何判断这个功能是否成功——会有哪些指标发生变化？”
“目标客户是谁，功能上线后他们的工作/生活状态会有什么变化？”
“明确排除在范围外的内容有哪些，以防止范围蔓延？”
“你能否快速搭建一个原型，而非撰写更多文档？”
“还有哪些关键决策尚未确定？”

Common Mistakes to Flag

需要指出的常见错误

Starting with the solution - The document should lead with the problem and context
No success criteria - Every PRD needs a clear definition of how you'll measure success
Exhaustive detail - Lightweight PRDs focused on outcomes are more likely to be read and used
Static when prototypes work better - For AI and UI work, live prototypes communicate more than prose
Missing the 'Why Now' - Without urgency justification, priorities will be questioned

从解决方案入手 - 文档应先呈现问题和背景
缺乏成功标准 - 每一份PRD都需要明确的成功衡量标准
细节过于详尽 - 聚焦成果的轻量化PRD更可能被阅读和使用
在原型更适用时仍使用静态文档 - 对于AI和UI相关工作，动态原型比文字更能清晰传达信息
缺失“为何是现在”部分 - 没有紧迫性的理由，需求的优先级会受到质疑

Deep Dive

深入了解

For all 14 insights from 11 guests, see

references/guest-insights.md

如需查看11位嘉宾分享的全部14条见解，请参阅

references/guest-insights.md