Back to Details

organizational-transformation

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Organizational Transformation

组织转型

Scope

适用范围

Covers
  • Designing and leading a practical transformation plan to move a company toward a modern product operating model
  • “Nudging” legacy orgs: sequencing change so it’s adopted, not rejected
  • Avoiding the trap of treating framework adoption (Spotify, SAFe, etc.) as the end goal
  • Coordinating structure + process + culture changes (teams, decision rights, discovery/delivery, incentives, rituals)
When to use
  • “Help me move us from feature teams to empowered product teams.”
  • “We keep adopting frameworks but nothing changes—build a real transformation plan.”
  • “Create a 90-day pilot plan plus a roadmap for rolling out a product operating model.”
  • “Our leaders want transformation; teams are skeptical. Build a change + comms plan that reduces rejection.”
When NOT to use
  • You need strategy/vision first (use 
    defining-product-vision
    or 
    working-backwards
    ).
  • You only need an org chart / team topology change (use 
    organizational-design
    ).
  • You need project management for a known plan (use 
    managing-timelines
    ).
  • You need HR/legal guidance on comp, layoffs, labor law, or sensitive people actions (involve HR/legal).
涵盖内容
  • 设计并落地一套务实的转型计划，推动企业向现代产品运营模型迈进
  • “温和推动”传统组织：合理规划变革节奏，确保变革被接纳而非抵制
  • 避免陷入将框架落地（如Spotify、SAFe等）视为最终目标的误区
  • 统筹协调结构+流程+文化层面的变革（包括团队架构、决策权、探索/交付流程、激励机制、团队仪式）
适用场景
  • “帮助我们从Feature Teams转型为Empowered Product Teams。”
  • “我们一直在尝试落地各种框架，但毫无改变——帮我们制定一套真正的转型计划。”
  • “制定一份90天试点计划，以及推广产品运营模型的路线图。”
  • “管理层希望推进转型，但团队持怀疑态度。制定一套变革+沟通方案以减少抵制情绪。”
不适用场景
  • 你需要先明确战略/愿景（请使用
    defining-product-vision
    或
    working-backwards
    工具）。
  • 你仅需要调整组织架构图/团队拓扑（请使用
    organizational-design
    工具）。
  • 你需要为已知计划提供项目管理支持（请使用
    managing-timelines
    工具）。
  • 你需要关于薪酬、裁员、劳动法或敏感人事行动的HR/法务指导（请咨询HR/法务团队）。

Inputs

输入要求

Minimum required
  • Org context: industry, size/stage, geography, regulated constraints (if any)
  • Executive sponsor + decision maker(s) and the transformation “why now”
  • Current operating model symptoms (with examples): decision bottlenecks, output-vs-outcome mismatch, discovery gaps, dependency chains
  • Current team model (feature teams vs product teams), and where product decisions currently live
  • Constraints: timelines, budget/headcount, must-keep processes, critical launches
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If answers aren’t available, proceed with explicit assumptions and label unknowns.
最低必填信息
  • 组织背景：行业、规模/发展阶段、地域、监管约束（如有）
  • 高管发起人+决策人，以及“为何此时启动转型”的原因
  • 当前运营模型的问题症状（需附实例）：决策瓶颈、产出与成果不匹配、探索环节缺失、依赖链冗长
  • 当前团队模式（Feature Teams还是Product Teams），以及产品决策的当前归属方
  • 约束条件：时间线、预算/人员编制、必须保留的流程、关键发布计划
缺失信息处理策略
  • 可从[references/INTAKE.md]中选取最多5个问题进行询问。
  • 若无法获取答案，基于明确假设推进，并标注未知信息。

Outputs (deliverables)

输出成果（交付物）

Produce an Organizational Transformation Pack (Markdown in-chat, or files if requested) in this order:
  1. Transformation Charter (why now, goals/non-goals, principles, success metrics, constraints)
  2. Current-State Diagnostic (how work flows today; capability gaps; resistance map; failure modes)
  3. Target Product Operating Model Blueprint (team types, roles, decision rights, cadences, core artifacts)
  4. Pilot / Nudge Plan (90 days) (2–4 safe-to-try pilots, training/coaching, learning loop, adoption strategy)
  5. Transformation Roadmap (6–12 months) (phases, big rocks, dependencies, sequencing, resourcing)
  6. Change + Comms Plan (stakeholders, messages, rituals, enablement, resistance handling)
  7. Governance + Metrics (leading indicators, review cadence, escalation, “framework hygiene” guardrails)
  8. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
产出组织转型工具包（支持聊天内Markdown格式，或按需生成文件），内容顺序如下：
  1. 转型章程（转型动因、目标/非目标、原则、成功指标、约束条件）
  2. 现状诊断报告（当前工作流转路径、能力缺口、抵制情绪地图、失败模式分析）
  3. 目标产品运营模型蓝图（团队类型、角色定位、决策权、节奏周期、核心交付物）
  4. 试点/温和推动计划（90天）（2-4个低风险试点项目、培训/辅导方案、学习反馈闭环、落地策略）
  5. 转型路线图（6-12个月）（阶段划分、核心任务、依赖关系、推进节奏、资源配置）
  6. 变革+沟通方案（利益相关方、核心信息、团队仪式、赋能计划、抵制情绪应对机制）
  7. 治理与指标体系（领先指标、评审节奏、升级路径、“框架健康度”管控规则）
  8. 风险/待解决问题/下一步行动（必含模块）
模板参考：[references/TEMPLATES.md]

Workflow (8 steps)

工作流程（8步）

1) Align on outcomes (not frameworks)

1) 对齐转型成果（而非框架）

  • Inputs: Why now; goals; symptoms; constraints; prior attempts.
  • Actions: Convert “adopt X framework” into outcomes + behaviors. Define non-goals (what you will not change yet). Set 3–5 transformation principles.
  • Outputs: Transformation Charter (draft) + assumptions.
  • Checks: Sponsors can state success as outcomes/behaviors, not “we implemented X.”
  • 输入：转型动因、目标、问题症状、约束条件、过往尝试经验。
  • 行动：将“落地X框架”转化为具体成果+行为要求。明确非目标（暂不调整的内容）。设定3-5条转型原则。
  • 输出：转型章程（草案）+ 假设条件。
  • 验收标准：发起人能够以成果/行为而非“我们落地了X框架”来定义成功。

2) Diagnose the current operating model as a system

2) 系统性诊断当前运营模型

  • Inputs: Team types; planning cadence; decision rights; delivery flow; examples of delays/rework.
  • Actions: Map how work moves from idea → shipped; identify bottlenecks (dependencies, approvals, incentives, missing discovery). Capture where a feature-team model is reinforced.
  • Outputs: Current-State Diagnostic (system map + top issues).
  • Checks: Diagnostic explains the symptoms with concrete mechanisms (not vibes).
  • 输入：团队类型、规划节奏、决策权、交付流程、延迟/返工实例。
  • 行动：绘制从想法到上线的工作流转图；识别瓶颈（依赖关系、审批流程、激励机制、探索环节缺失）。记录功能型团队模式的固化表现。
  • 输出：现状诊断报告（系统地图+核心问题）。
  • 验收标准：诊断报告能够通过具体机制解释问题症状（而非主观感受）。

3) Pick a transformation thesis + guardrails (framework hygiene)

3) 确定转型核心方向+管控规则（框架健康度）

  • Inputs: Diagnostic; constraints; change capacity; leadership alignment.
  • Actions: Define the smallest set of operating model changes that would create leverage (e.g., empowered teams, dual-track discovery/delivery, outcome-oriented planning). Add “framework hygiene” rules: what you’ll borrow, what you won’t, and why.
  • Outputs: Transformation thesis + guardrails section in the Charter.
  • Checks: The plan is tailored to context; it avoids copying a model wholesale.
  • 输入：诊断报告、约束条件、变革承接能力、管理层对齐情况。
  • 行动：定义能够产生杠杆效应的最小运营模型调整集合（如自主团队、双轨探索/交付、成果导向规划）。添加“框架健康度”规则：明确借鉴框架的哪些部分、舍弃哪些部分，以及原因。
  • 输出：转型核心方向+章程中的管控规则章节。
  • 验收标准：计划贴合组织实际，避免全盘照搬现有模型。

4) Design the target product operating model (concrete, observable)

4) 设计具象可落地的目标产品运营模型

  • Inputs: Transformation thesis; product shape (integrated vs modular); talent maturity.
  • Actions: Specify: team types (product/platform/enabling), roles, decision rights, intake, discovery expectations, planning cadence, and required artifacts.
  • Outputs: Target Product Operating Model Blueprint.
  • Checks: A leader can answer “who decides what” and “what ‘good’ looks like” on Day 1.
  • 输入：转型核心方向、产品形态（集成式 vs 模块化）、人才成熟度。
  • 行动：明确：团队类型（产品/平台/赋能型）、角色、决策权、需求接入流程、探索要求、规划节奏、核心交付物。
  • 输出：目标产品运营模型蓝图。
  • 验收标准：管理层能够在转型首日明确“谁做什么决策”以及“合格标准是什么”。

5) Create a nudge-first pilot plan (90 days)

5) 制定以温和推动为核心的90天试点计划

  • Inputs: Blueprint; candidate teams/areas; risk constraints.
  • Actions: Design 2–4 pilots with clear hypotheses, enablement (coaching/training), and adoption tactics (nudges, rituals, templates). Define what you’ll learn and how you’ll adapt.
  • Outputs: Pilot / Nudge Plan + pilot scorecard.
  • Checks: Pilots are safe-to-try, measurable, and don’t require perfect org-wide alignment.
  • 输入：模型蓝图、候选团队/业务领域、风险约束。
  • 行动：设计2-4个试点项目，明确假设验证目标、赋能方案（辅导/培训）、落地策略（温和推动、团队仪式、模板工具）。定义学习目标与迭代机制。
  • 输出：试点/温和推动计划+试点评分卡。
  • 验收标准：试点项目低风险、可衡量，无需全组织完美对齐即可启动。

6) Build the transformation roadmap (6–12 months)

6) 构建6-12个月转型路线图

  • Inputs: Pilot plan; resourcing; calendar constraints.
  • Actions: Sequence the big rocks (structure changes, capability building, tooling/process changes). Include decision points, dependencies, and rollback triggers.
  • Outputs: Transformation Roadmap (phases + milestones).
  • Checks: Roadmap is implementable; it protects business continuity and in-flight commitments.
  • 输入：试点计划、资源配置、日历约束。
  • 行动：规划核心任务的推进顺序（架构调整、能力建设、工具/流程优化）。包含决策节点、依赖关系、回退触发条件。
  • 输出：转型路线图（阶段+里程碑）。
  • 验收标准：路线图具备可执行性，能够保障业务连续性与在途项目交付。

7) Plan change + comms (reduce rejection)

7) 制定变革+沟通方案（降低抵制）

  • Inputs: Stakeholders; resistance map; incentives.
  • Actions: Draft a comms narrative, stakeholder-specific messages, enablement plan, and a system for handling objections. Connect the change to incentives and leadership behaviors.
  • Outputs: Change + Comms Plan.
  • Checks: Plan includes reinforcement mechanisms (rituals, metrics, leadership actions), not just announcements.
  • 输入：利益相关方、抵制情绪地图、激励机制。
  • 行动：起草沟通叙事、针对不同利益相关方的定制化信息、赋能计划，以及异议处理机制。将变革与激励机制、管理层行为绑定。
  • 输出：变革+沟通方案。
  • 验收标准：方案包含强化机制（团队仪式、指标、管理层行动），而非仅依赖公告。

8) Quality gate + finalize

8) 质量校验+最终定稿

  • Inputs: Draft pack.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Ensure Risks/Open questions/Next steps are present.
  • Outputs: Final Organizational Transformation Pack + rubric score.
  • Checks: If rubric score is low, do one more intake round (max 5 questions) and revise.
  • 输入：工具包草案。
  • 行动：对照[references/CHECKLISTS.md]检查，并使用[references/RUBRIC.md]评分。确保包含风险/待解决问题/下一步行动模块。
  • 输出：最终组织转型工具包+评分结果。
  • 验收标准：若评分较低，最多补充一轮信息收集（5个问题以内）并修订。

Quality gate (required)

质量校验（必做）

  • Run references/CHECKLISTS.md and score with references/RUBRIC.md before finalizing.
  • Always include: Risks, Open questions, Next steps.
  • 最终定稿前，必须对照[references/CHECKLISTS.md]检查，并使用[references/RUBRIC.md]评分。
  • 必须包含：风险、待解决问题、下一步行动模块。

Examples

示例

Example 1: “VP Product at a legacy enterprise: teams ship features but outcomes don’t improve. Create a transformation plan toward empowered product teams.”
Expected: diagnostic, target operating model blueprint, 90-day pilots, 6–12 month roadmap, governance metrics.
Example 2: “CEO: we tried SAFe/Spotify-style changes and got backlash. Build a nudge-first plan and comms to reduce rejection.”
Expected: framework hygiene guardrails, small pilots, stakeholder messaging, reinforcement mechanisms.
Boundary example: “Write a plan to ‘implement the Spotify model’ verbatim.”
Response: this skill treats frameworks as tools; it will instead produce a context-fit operating model and specify what (if anything) to borrow and how to validate via pilots.
示例1：“传统企业产品副总裁：团队不断交付功能，但业务成果无提升。制定向自主产品团队转型的计划。”
预期产出：现状诊断、目标运营模型蓝图、90天试点计划、6-12个月路线图、治理指标。
示例2：“CEO：我们尝试过SAFe/Spotify风格的变革，但遭遇强烈抵制。制定一套以温和推动为核心的计划与沟通方案，减少抵制情绪。”
预期产出：框架健康度管控规则、小型试点项目、利益相关方沟通话术、强化机制。
边界示例：“制定一份‘完全照搬Spotify模型’的计划。”
回应：本工具将框架视为参考工具，会基于组织实际情况定制运营模型，并明确借鉴框架的哪些部分，以及如何通过试点验证效果。