Back to Details

product-manager

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Product Manager

产品经理

Strategic product management expertise for building the right things, in the right order, with the right people.
为产品打造提供战略性产品管理专业知识——做正确的事，按正确的顺序，和正确的人一起。

Philosophy

理念

Great product management isn't about features. It's about outcomes — solving real problems for real users in ways that drive business results.
The best product managers:
  1. Obsess over problems, not solutions — Understand deeply before building
  2. Say no more than yes — Focus is a feature
  3. Bridge all worlds — Connect customers, engineering, design, and business
  4. Make decisions reversible — Ship fast, learn faster
  5. Own outcomes, not outputs — Features shipped means nothing without impact
优秀的产品管理不在于功能，而在于成果——以推动业务成果的方式为真实用户解决真实问题。
最优秀的产品经理：
  1. 痴迷于问题而非解决方案——在构建前深入理解
  2. 说“不”多于说“是”——专注本身就是一种优势
  3. 连接所有领域——衔接客户、工程、设计和业务
  4. 做可逆的决策——快速发布，更快学习
  5. 对成果负责，而非产出——没有影响力的功能发布毫无意义

How This Skill Works

此技能的工作方式

When invoked, apply the guidelines in 
rules/
organized by:
  • roadmap-*
    — Roadmap creation, maintenance, and communication
  • prioritization-*
    — RICE, ICE, MoSCoW, and prioritization frameworks
  • stakeholder-*
    — Managing up, down, and across the organization
  • sprint-*
    — Sprint planning, backlog grooming, ceremonies
  • scoping-*
    — Feature scoping, trade-offs, MVP definition
  • release-*
    — Release planning, coordination, communication
  • metrics-*
    — Product metrics, OKRs, success measurement
  • debt-*
    — Technical debt management and balancing
调用时，应用
rules/
中按以下类别组织的准则：
  • roadmap-*
    — 路线图创建、维护与沟通
  • prioritization-*
    — RICE、ICE、MoSCoW及其他优先级排序框架
  • stakeholder-*
    — 向上、向下及跨组织的利益相关者管理
  • sprint-*
    — 冲刺规划、待办事项梳理、仪式活动
  • scoping-*
    — 功能范围界定、权衡取舍、MVP定义
  • release-*
    — 发布规划、协调与沟通
  • metrics-*
    — 产品指标、OKRs、成功衡量
  • debt-*
    — 技术债务管理与平衡

Core Frameworks

核心框架

The Product Trio

产品三人组

         ┌─────────────────┐
         │     Product     │
         │     Manager     │
         └────────┬────────┘
                  │
    ┌─────────────┼─────────────┐
    │             │             │
    ▼             ▼             ▼
┌────────┐  ┌──────────┐  ┌──────────┐
│  UX    │  │Engineering│  │  Data    │
│Designer│  │   Lead    │  │ Analyst  │
└────────┘  └──────────┘  └──────────┘
         ┌─────────────────┐
         │     Product     │
         │     Manager     │
         └────────┬────────┘
                  │
    ┌─────────────┼─────────────┐
    │             │             │
    ▼             ▼             ▼
┌────────┐  ┌──────────┐  ┌──────────┐
│  UX    │  │Engineering│  │  Data    │
│Designer│  │   Lead    │  │  Analyst  │
└────────┘  └──────────┘  └──────────┘

Prioritization Framework Comparison

优先级排序框架对比

FrameworkBest ForScoringComplexity
RICEFeature prioritizationReach × Impact × Confidence / EffortMedium
ICEQuick decisionsImpact × Confidence × EaseLow
MoSCoWRelease scopingMust/Should/Could/Won'tLow
KanoCustomer satisfactionDelight/Performance/BasicHigh
Value vs EffortQuick 2x2 plottingQualitative quadrantsLow
框架最佳适用场景评分方式复杂度
RICE功能优先级排序覆盖范围 × 影响力 × 置信度 / 投入中等
ICE快速决策影响力 × 置信度 × 易用性低
MoSCoW发布范围界定必须/应该/可以/不会做（Must/Should/Could/Won't）低
Kano客户满意度愉悦型/绩效型/基础型高
价值 vs 投入快速二维象限绘图定性象限低

The Product Development Loop

产品开发循环

┌──────────────────────────────────────────────────┐
│                                                  │
│   ┌──────────┐    ┌──────────┐    ┌──────────┐  │
│   │ Discover │───▶│  Define  │───▶│  Develop │  │
│   └──────────┘    └──────────┘    └──────────┘  │
│         ▲                               │        │
│         │         ┌──────────┐          │        │
│         └─────────│  Measure │◀─────────┘        │
│                   └──────────┘                   │
│                                                  │
└──────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────┐
│                                                  │
│   ┌──────────┐    ┌──────────┐    ┌──────────┐  │
│   │ Discover │───▶│  Define  │───▶│  Develop │  │
│   └──────────┘    └──────────┘    └──────────┘  │
│         ▲                               │        │
│         │         ┌──────────┐          │        │
│         └─────────│  Measure │◀─────────┘        │
│                   └──────────┘                   │
│                                                  │
└──────────────────────────────────────────────────┘

Roadmap Types

路线图类型

TypeAudienceTime HorizonDetail Level
VisionBoard, investors2-5 yearsHigh-level themes
StrategicLeadership1 yearQuarterly goals
ReleaseStakeholdersQuarterFeatures/epics
SprintDev team2 weeksStories/tasks
类型受众时间范围详细程度
愿景型董事会、投资者2-5年高-level主题
战略型领导层1年季度目标
发布型利益相关者季度功能/史诗级需求
冲刺型开发团队2周用户故事/任务

The PM Decision Matrix

PM决策矩阵

                    High Confidence
                         │
         ┌───────────────┼───────────────┐
         │   VALIDATE    │     SHIP      │
         │  (test more)  │   (execute)   │
Low      │               │               │   High
Impact───┼───────────────┼───────────────┼───Impact
         │    IGNORE     │  INVESTIGATE  │
         │  (say no)     │  (research)   │
         └───────────────┼───────────────┘
                         │
                    Low Confidence
                    High Confidence
                         │
         ┌───────────────┼───────────────┐
         │   VALIDATE    │     SHIP      │
         │  (test more)  │   (execute)   │
Low      │               │               │   High
Impact───┼───────────────┼───────────────┼───Impact
         │    IGNORE     │  INVESTIGATE  │
         │  (say no)     │  (research)   │
         └───────────────┼───────────────┘
                         │
                    Low Confidence

Stakeholder Map

利益相关者图谱

StakeholderPrimary InterestCommunication Style
ExecutivesBusiness outcomes, strategyHigh-level, metrics-focused
EngineeringTechnical feasibility, qualityDetailed, collaborative
DesignUser experience, usabilityVisual, user-centric
SalesRevenue, competitive advantageCustomer stories, timelines
MarketingPositioning, launch timingMessaging, dates
SupportUser satisfaction, volumePain points, frequency
CustomersProblems solved, valueEmpathy, listening
利益相关者核心关注点沟通风格
高管业务成果、战略高-level、聚焦指标
工程团队技术可行性、质量详细、协作式
设计团队用户体验、可用性可视化、以用户为中心
销售团队收入、竞争优势客户案例、时间线
营销团队定位、发布时机信息传递、日期
支持团队用户满意度、工作量痛点、频率
客户问题解决、价值共情、倾听

Anti-Patterns

反模式

  • Feature factory — Shipping without measuring outcomes
  • Roadmap theater — Treating roadmaps as promises, not hypotheses
  • Stakeholder-driven development — Building what's loudest, not what matters
  • Scope creep acceptance — Never saying no to "just one more thing"
  • Velocity worship — Optimizing for speed over impact
  • Documentation paralysis — Perfect specs over shipping
  • The PM as order taker — Writing tickets instead of solving problems
  • Ignoring technical debt — Shipping features on a crumbling foundation
  • 功能工厂——只发布不衡量成果
  • 路线图表演——将路线图视为承诺而非假设
  • 利益相关者驱动开发——只做呼声最高的事，而非重要的事
  • 接受范围蔓延——永远不对“再多一件事”说不
  • 盲目追求速度——为速度优化而非影响力
  • 文档瘫痪——追求完美规格而非发布
  • PM沦为订单接收者——只写工单而非解决问题
  • 忽视技术债务——在摇摇欲坠的基础上发布功能