81 lines
4.9 KiB
Markdown
81 lines
4.9 KiB
Markdown
---
|
||
title: "Product Manager"
|
||
type: source
|
||
tags: [agent, product-management, the-agency]
|
||
date: 2026-04-20
|
||
---
|
||
|
||
## Source File
|
||
- [[raw/Agent/agency-agents/product/product-manager.md]]
|
||
|
||
## Summary
|
||
- 核心主题：The Agency 项目中的产品经理智能体（PM Agent）完整定义，涵盖身份设定、核心使命、技术交付物模板、工作流程和成功指标
|
||
- 问题域：产品管理中的需求发现、优先级排序、跨职能协调、交付管理和结果度量
|
||
- 方法/机制：PM Agent 通过 6 阶段工作流程（Discovery → Framing → Definition → Delivery → Launch → Measurement）驱动产品从想法到落地
|
||
- 结论/价值：提供标准化的 PM 智能体框架，包含 PRD、Opportunity Assessment、Roadmap、GTM Brief、Sprint Health Snapshot 等可复用模板
|
||
|
||
## Key Claims
|
||
- PM 智能体以 [[Outcome-Driven Development]] 为核心思维，交付成果而非产出物
|
||
- 需求发现阶段必须进行至少 5-10 次结构化用户访谈才能进入方案讨论
|
||
- RICE 评分 = (R × I × C) ÷ E 用于客观优先级排序
|
||
- Scope creep（范围蔓延）是产品失败的主要原因，必须严格控制
|
||
- GTM 发布需要 100% 完成发布清单，包括 CS/Support 培训和文档
|
||
|
||
## Key Quotes
|
||
> "Features are hypotheses. Shipped features are experiments. Successful features are the ones that measurably change user behavior." — PM 核心哲学
|
||
> "My job isn't to have all the answers. It's to make sure we're all asking the same questions in the same order — and that we stop building until we have the ones that matter." — PM 角色定位
|
||
> "Alignment is not agreement. You don't need unanimous consensus to move forward. You need everyone to understand the decision, the reasoning behind it, and their role in executing it." — 共识与对齐的区别
|
||
|
||
## Key Concepts
|
||
- [[Product Requirements Document (PRD)]]：产品规格文档，定义问题域、目标、解决方案、技术考量、发布计划
|
||
- [[Opportunity Assessment]]：机会评估，RICE 优先级评分框架，用于 build/explore/defer/kill 决策
|
||
- [[Roadmap (Now / Next / Later)]]：产品路线图，分三个时间维度管理产品组合
|
||
- [[RICE Prioritization Score]]：R × I × C ÷ E 优先级算法
|
||
- [[Go-to-Market Brief]]：GTM 发布计划，覆盖目标受众、价值主张、发布清单、成功标准
|
||
- [[Sprint Health Snapshot]]：冲刺健康快照，追踪交付率、阻塞和范围变更
|
||
- [[Outcome-Driven Development]]：结果驱动开发，以可衡量成果而非功能产出定义成功
|
||
- [[Discovery Process]]：发现问题阶段，用户访谈、行为分析、support 信号挖掘
|
||
|
||
## Key Entities
|
||
- [[Alex]]：The Agency PM Agent 的人格化身，10+ 年产品管理经验
|
||
- [[The Agency]]：开源 AI 智能体集合项目，PM Agent 是其中一员
|
||
- Engineering（工程团队）：负责技术实现和交付
|
||
- Design（设计团队）：负责用户体验和界面设计
|
||
- Marketing（市场团队）：负责 GTM 策略执行
|
||
- Sales（销售团队）：负责客户获取和收入
|
||
- Support/CS（客户支持）：负责发布后客户培训和问题处理
|
||
|
||
## Connections
|
||
- [[Product Requirements Document (PRD)]] ← produced_by ← [[Discovery Process]]
|
||
- [[Opportunity Assessment]] ← informs ← [[Roadmap (Now / Next / Later)]]
|
||
- [[Sprint Health Snapshot]] ← monitors ← [[Delivery Phase]]
|
||
- [[Go-to-Market Brief]] ← enables ← [[Launch Phase]]
|
||
- [[RICE Prioritization Score]] ← ranks ← [[Product Backlog]]
|
||
|
||
## Contradictions
|
||
- 无明显冲突
|
||
|
||
## Workflow Phases
|
||
1. **Discovery**：用户访谈、行为分析、support 审计、旅程映射
|
||
2. **Framing & Prioritization**：Opportunity Assessment、RICE 评分、build/defer/kill 决策
|
||
3. **Definition**：PRD 协作编写、PRFAQ 练习、设计kickoff、依赖识别
|
||
4. **Delivery**：Backlog 管理、冲刺仪式、 blocker 解决、周报同步
|
||
5. **Launch**：GTM 协调、发布策略定义、回滚预案、48h 监控
|
||
6. **Measurement & Learning**：30/60/90 天回顾、复盘文档、用户访谈、发现反馈
|
||
|
||
## Communication Principles
|
||
- **Written-first, async by default**：书面优先，异步为主
|
||
- **Direct with empathy**：清晰表达建议同时邀请真实反驳
|
||
- **Data-fluent, not data-dependent**：引用指标同时标注信心水平
|
||
- **Decisive under uncertainty**：不做完美主义者，在不确定下做最佳决策
|
||
- **Executive-ready at any moment**：面向 CEO 可以 3 句话总结，面向工程团队可以 3 页详细
|
||
|
||
## Success Metrics
|
||
- 75%+ 功能在发布后 90 天达到主要成功指标
|
||
- 80%+ 季度承诺按时交付或提前重新调整范围
|
||
- 零意外——领导层和跨职能合作伙伴在决策前就知情
|
||
- 每个 >2 周工作量的计划至少获得 5 次用户访谈支持
|
||
- 100% GA 发布配备培训完成的 CS/Support 团队
|
||
- 零未追踪的 sprint 中期范围增加
|
||
- 中等复杂度功能（2-4 工程师周）discovery-to-shipped < 8 周
|