Auto-sync: 2026-04-21 00:02
This commit is contained in:
37
wiki/concepts/Discovery-Process.md
Normal file
37
wiki/concepts/Discovery-Process.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
title: "Discovery Process"
|
||||
type: concept
|
||||
tags: [product-management, discovery, user-research]
|
||||
sources: [product-manager.md]
|
||||
last_updated: 2026-04-20
|
||||
---
|
||||
|
||||
## Definition
|
||||
发现阶段是产品开发周期的第一阶段,通过系统化用户研究、行为数据分析和 Support 信号挖掘来定义要解决的问题。
|
||||
|
||||
## Activities
|
||||
1. **Structured Problem Interviews**:最少 5-10 次结构化问题访谈
|
||||
2. **Behavioral Analytics Mining**:挖掘摩擦模式、drop-off 点和意外使用
|
||||
3. **Support Tickets Audit**:审计 Support 票据和 NPS 评语发现重复主题
|
||||
4. **User Journey Mapping**:映射当前端到端用户旅程,找出挣扎、放弃或绕过产品的节点
|
||||
5. **Synthesis**:将发现合成清晰、证据-backed 的问题陈述
|
||||
|
||||
## Output
|
||||
- 清晰的问题陈述(Problem Statement)
|
||||
- 用户痛点的优先级列表
|
||||
- 支持每个问题的证据(访谈引用、数据指标、Support 信号)
|
||||
|
||||
## Key Principle
|
||||
- 分享原始信号,不只是结论——设计、工程和领导层都应看到原始数据
|
||||
- 在验证问题前不讨论解决方案
|
||||
- Discovery 质量决定后续所有工作的方向
|
||||
|
||||
## Minimum Evidence Threshold
|
||||
每个 >2 周工作量的 initiative 必须至少有:
|
||||
- 5 次用户访谈,或
|
||||
- 等效的行为证据
|
||||
|
||||
## Connection
|
||||
- [[Discovery Process]] ← conducted_by ← [[Product Manager Agent]]
|
||||
- [[Discovery Process]] ← outputs ← [[Product Requirements Document (PRD)]]
|
||||
- [[Opportunity Assessment]] ← follows ← [[Discovery Process]]
|
||||
Reference in New Issue
Block a user