42 lines
1.9 KiB
Markdown
42 lines
1.9 KiB
Markdown
---
|
||
title: "Outcome vs. Output"
|
||
type: concept
|
||
tags: ["product-management", "mindset", "strategy"]
|
||
last_updated: 2026-04-30
|
||
---
|
||
|
||
## Aliases
|
||
- Outcome over Output
|
||
- 结果导向 vs. 产出导向
|
||
- 以结果为中心
|
||
|
||
## Definition
|
||
Outcome vs. Output（结果 vs. 产出）—— 产品管理的核心思维模式：**结果（Outcome）** 是用户行为的实际改变和业务价值达成；**产出（Output）** 是交付的功能数量、特性或里程碑。
|
||
|
||
## Core Distinction
|
||
|
||
| 维度 | Output（产出） | Outcome（结果） |
|
||
|------|--------------|----------------|
|
||
| 关注点 | 做了什么 | 用户改变了什么 |
|
||
| 度量 | 功能数量、上线时间 | 指标改善、用户行为变化 |
|
||
| 陷阱 | 功能上线即成功 | 以活动代替进步 |
|
||
| 典型错误 | "我们交付了 X 功能" | 没人用的功能 |
|
||
|
||
## Key Quotes
|
||
> "A feature shipped that nobody uses is not a win — it's waste with a deploy timestamp." — [[Product Manager Agent]]（Alex）
|
||
|
||
> "Features are hypotheses. Shipped features are experiments. Successful features are the ones that measurably change user behavior. Everything else is a learning." — [[Product Manager Agent]]
|
||
|
||
## Why It Matters
|
||
- **防止虚荣指标**：团队交付了很多功能，但用户留存没有改善
|
||
- **保护资源**：避免在无人使用的功能上浪费工程资源
|
||
- **对齐业务**：确保团队努力直接转化为商业价值
|
||
|
||
## Application
|
||
[[Product Manager Agent]] 在所有产品文档（PRD、Opportunity Assessment、Launch Retrospective）中坚持使用 Outcome 思维，并在成功指标定义中要求可量化的用户行为指标（如 30 天留存率、功能激活率）而非功能完成状态。
|
||
|
||
## Related
|
||
- [[Product Requirements Document (PRD)]] — 要求明确的结果指标（Goals & Success Metrics）
|
||
- [[Product Manager Agent]] — 坚持结果导向的核心理念
|
||
- [[Product Roadmap (Now/Next/Later)]] — 路线图按结果而非交付物组织
|