# 为 PRD 建立产品研究知识库

这是三份研究笔记的虚构练习：从冲突请求中选出一个有限的 PRD 决策，再标出需要更多研究的部分。

## 任务

只根据三份研究笔记，选择最小且有依据的 PRD 决策，保留冲突和未知信息，并指出哪些选择需要更多产品负责人的判断。每个结论都用 [[filename]] 引用。

## 预期推理

提出带有来源链接的草稿，并在分享前要求人工审核。不要仅凭这组小型且相互冲突的资料承诺自动发布、导出、存储默认值、团队权限或完整路线图。

## 完整来源资料包

### Research note A — source-linked review — research-note-a.md

```markdown
# Research note A — source-linked review

Fictional moderated session note; no real participant or customer is represented.

The evaluator wanted an imported Markdown note to produce a draft answer with a link back to each source passage. They preferred to review the draft before it became a shared page. The note records one narrow workflow preference, not demand for automatic publishing, team permissions, or a mobile app.
```

### Research note B — local-only request — research-note-b.md

```markdown
# Research note B — local-only request

Fictional research note; no real participant or customer is represented.

The evaluator asked to keep source files and drafts in a local workspace and rejected an external export for this exercise. They said an explicit review step matters more than a polished final page. The note does not establish that every user wants local-only storage or that export is never useful.
```

### Research note C — conflicting product request — research-note-c.md

```markdown
# Research note C — conflicting product request

Fictional product-research note; no real participant or customer is represented.

A separate request asked for a CSV export of the source-linked draft and also asked for automatic publishing after import. The request conflicts with note B's local-only preference and note A's review-before-sharing preference. The sample is too small to resolve the conflict or justify a broad roadmap.
```

## Reference answer: choose a reviewable draft, keep the roadmap narrow

The three fictional notes support one limited PRD decision: imported Markdown may produce a source-linked draft that a person reviews before sharing. Export, automatic publishing, storage defaults, and broader permissions remain unresolved because the notes conflict and the sample is small.

# Product-research reference for a PRD

## Limited decision

Add one narrow requirement: an imported Markdown note can produce a draft answer with links to its source passages, and a person must review the draft before it becomes a shared page. This is supported by the source-linked review preference and the request for an explicit review step. [[research-note-a.md]] [[research-note-b.md]]

## Keep unresolved

Do not commit automatic publishing. Note A prefers review before sharing, note B prioritizes local-only drafts, and note C separately requests automatic publishing and CSV export. The notes conflict and are too small to decide a universal storage or export policy. [[research-note-b.md]] [[research-note-c.md]]

A product owner must decide whether to run more research before choosing export, storage defaults, team permissions, or a broader PRD. Those decisions are not established by this packet. [[research-note-a.md]] [[research-note-b.md]] [[research-note-c.md]]

## 变更后来源

### research-note-c.md

```markdown
# Research note C — conflicting product request, revision 2

Fictional product-research note; no real participant or customer is represented.

A separate request asked for a source-linked review report that can be saved in the local workspace. It did not request CSV export. The same request still asked for automatic publishing after import, which conflicts with note B's local-only preference and note A's review-before-sharing preference. The sample is too small to resolve the conflict or justify a broad roadmap.
```

## 变更预期

The reference's statement that note C requested CSV export becomes stale. Revision 2 clarifies that the request was for a locally saved source-linked review report, not CSV export. The automatic-publishing conflict, narrow review-before-sharing decision, and unresolved storage or permission questions remain; a human product owner still decides whether more research is needed.

## 审核边界

逐项对照笔记，特别检查分享前审核、只在本地保存、自动发布与导出之间的冲突；存储默认值、权限和更广泛需求仍待产品判断。

## 对比

三份笔记可以用普通文件比较。当修订、矛盾请求，以及证据与产品判断的边界需要在持续更新的 PRD 中保持可见时，来源链接的研究 wiki 才有帮助。

## 阅读本地化页面

https://wenlan.app/zh-CN/learn/build-product-research-knowledge-base-for-prd