change-management

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Change Management Playbook

变革管理手册

Most changes fail at implementation, not design. The ADKAR model tells you why and how to fix it.

大多数变革的失败发生在执行阶段，而非设计阶段。ADKAR模型会告诉你原因以及解决方法。

Keywords

关键词

change management, ADKAR, organizational change, reorg, process change, tool migration, strategy pivot, change resistance, change fatigue, change communication, stakeholder management, adoption, compliance, change rollout, transition

变革管理, ADKAR, 组织变革, 重组, 流程变更, 工具迁移, 战略转型, 变革阻力, 变革疲劳, 变革沟通, 利益相关者管理, 采用, 合规, 变革推行, 过渡

Core Model: ADKAR Adapted for Startups

核心模型：适配初创企业的ADKAR

ADKAR is a change management model by Prosci. Original version is for enterprises. This is the startup-speed adaptation.

ADKAR是Prosci提出的变革管理模型。原版适用于企业，本版本是适配初创企业节奏的调整版。

A — Awareness

A — 认知（Awareness）

What it is: People understand WHY the change is happening — the business reason, not just the announcement.

The mistake: Communicating the WHAT before the WHY. "We're moving to a new CRM" before "here's why our current process is killing us."

What people need to hear:

What is the problem we're solving? (Be honest. If it's "we need to cut costs," say that.)
Why now? What would happen if we didn't change?
Who made this decision and how?

Startup shortcut: A 5-minute video from the CEO or decision-maker explaining the "why" in plain language beats a formal change announcement document every time.

定义： 人们理解变革发生的原因——即业务层面的理由，而非仅仅是通知内容。

常见误区： 先沟通“是什么”再沟通“为什么”。比如先说“我们要切换到新的CRM”，却不解释“当前流程为何拖垮我们”。

人们需要听到的内容：

我们要解决什么问题？（务必坦诚。如果是“我们需要削减成本”，就直接说出来。）
为什么是现在？如果不变革会发生什么？
谁做出的这个决定，决策过程是怎样的？

初创企业捷径： CEO或决策者用5分钟视频用直白语言解释“为什么”，效果远胜于正式的变革通知文档。

D — Desire

D — 意愿（Desire）

What it is: People want to make the change happen — or at least don't actively resist it.

The mistake: Assuming communication creates desire. Awareness ≠ desire. People can understand a change and still hate it.

What creates desire:

"What's in it for me?" — answer this for each stakeholder group, honestly
Involving people in the "how" even if the "what" is decided
Addressing fears directly: "Some people are worried this means their role is changing. Here's the truth: [honest answer]"

What destroys desire:

Pretending the change is better for everyone than it is
Ignoring the legitimate losses people will experience
Making announcements without any consultation

Startup shortcut: Run a short "concerns and questions" session within 48 hours of announcement. Not to reverse the decision — to address the fears and show you're listening.

定义： 人们希望推动变革发生——或者至少不会主动抵制。

常见误区： 认为沟通就能产生意愿。认知≠意愿。人们可能理解变革，但依然反感它。

能产生意愿的做法：

“这对我有什么好处？”——针对每个利益相关群体坦诚回答
即便“是什么”已确定，也要让人们参与到“如何做”的讨论中
直接回应担忧：“有些人担心这意味着他们的角色会变化。事实是：[坦诚回答]”

会摧毁意愿的做法：

假装变革对所有人都比现状更好
忽视人们将遭受的合理损失
未经任何咨询就发布通知

初创企业捷径： 在通知发布后的48小时内开展一场简短的“顾虑与问答”会议。不是为了推翻决策——而是为了回应担忧，表明你们在倾听。

K — Knowledge

K — 知识（Knowledge）

What it is: People know HOW to operate in the new world — the specific skills, behaviors, and processes.

The mistake: Announcing the change and assuming people will figure it out.

What people need:

Step-by-step documentation of new processes
Training or practice sessions before go-live
Clear answers to "what do I do when [common scenario]?"
Who to ask when they're stuck

Types of knowledge transfer:

Method	Best for	When
Live training	Skill-based changes, complex tools	Before go-live
Documentation	Process changes, reference material	Always
Video walkthroughs	Tool migrations	Available 24/7, self-paced
Shadowing / peer learning	Behavior changes	Weeks 2–4 after launch
Office hours	Any change with many edge cases	First 4–6 weeks

定义： 人们知道如何在新环境下开展工作——具体的技能、行为和流程。

常见误区： 发布变革通知后就假设人们能自行摸索。

人们需要的内容：

新流程的分步文档
上线前的培训或实操环节
针对“当[常见场景]发生时我该怎么做？”的明确答案
遇到问题时可以求助的人

知识传递的类型：

方法	适用场景	时机
现场培训	基于技能的变革、复杂工具	上线前
文档资料	流程变更、参考材料	始终适用
视频演示	工具迁移	全天候可用、自主进度
跟岗学习/同伴学习	行为变革	上线后第2-4周
办公时间答疑	存在大量边缘情况的任何变革	前4-6周

A — Ability

A — 能力（Ability）

What it is: People have the time, tools, and support to actually do things differently.

The mistake: "We've trained everyone" ≠ "everyone can now do it." Training is knowledge. Ability is practice.

What creates ability:

Time to practice before being evaluated
A safe environment to make mistakes (no public shaming for early struggles)
Reduced load during transition (if you're asking people to learn new skills, don't simultaneously pile on new work)
Access to help (a Slack channel, a point person, documentation)

Signs of ability gap:

People revert to old behavior under pressure
Workarounds emerge (people invent their own way around the new system)
Training scores are high but actual behavior hasn't changed

定义： 人们拥有时间、工具和支持来真正做出改变。

常见误区： “我们已经完成全员培训”≠“所有人现在都能做到”。培训是知识层面，能力是实操层面。

能培养能力的做法：

在评估前留出练习时间
提供允许犯错的安全环境（不对早期的困难进行公开指责）
过渡期间减轻工作负担（如果要求人们学习新技能，就不要同时增加新工作）
提供求助渠道（Slack频道、专人对接、文档资料）

能力缺口的迹象：

人们在压力下恢复旧行为
出现变通方法（人们自行发明绕过新系统的方式）
培训分数很高，但实际行为未改变

R — Reinforcement

R — 巩固（Reinforcement）

What it is: The change sticks. The new behavior becomes the default.

The mistake: Declaring victory at go-live. Changes fail because they're never reinforced.

What creates reinforcement:

Visible measurement (are we tracking adoption?)
Recognition of early adopters ("Sarah fully migrated to the new workflow in week 2 — ask her how")
Leader modeling (if the CEO uses the old way, everyone will)
Removing the old option (when possible — eliminate the path of least resistance)
Consequences for non-adoption (stated clearly, applied consistently)

Adoption vs. compliance:

Compliance: People do it when watched, revert when not
Adoption: People do it because they believe it's better

Only reinforcement creates adoption. Compliance is the result of enforcement. Aim for adoption.

定义： 变革得以持续。新行为成为默认选项。

常见误区： 在上线时就宣告胜利。变革失败往往是因为从未得到巩固。

能实现巩固的做法：

可见的衡量指标（我们是否在跟踪采用情况？）
认可早期采用者（“Sarah在第2周就完全切换到新工作流程了——问问她是怎么做的”）
领导者以身作则（如果CEO仍使用旧方法，所有人都会效仿）
移除旧选项（如果可行——消除阻力最小的路径）
对不采用的后果（明确说明，一致执行）

采用vs.合规：

合规： 有人监督时才做，没人监督就恢复原状
采用： 人们因为相信它更好而主动去做

只有巩固才能实现采用。合规是强制的结果。我们的目标是采用。

Change Types and ADKAR Application

变革类型与ADKAR的应用

Process Change (new tools, new workflows)

流程变更（新工具、新工作流程）

Timeline: 4–8 weeks for full adoption Hardest phase: Ability (people know what to do but haven't built the habit) Critical reinforcement: Remove or deprecate the old tool/process

Communication sequence:

Week -2: Announce the why + go-live date
Week -1: Training sessions available
Week 0 (go-live): Launch + point person available
Week 2: Adoption check-in (who's using it? Who isn't?)
Week 4: Feedback collection + public wins
Week 8: Old system deprecated

时间线： 完全采用需4-8周 最困难阶段： 能力（人们知道该做什么，但还没养成习惯） 关键巩固措施： 移除或弃用旧工具/流程

沟通顺序：

上线前2周：宣布变革原因+上线日期
上线前1周：开放培训课程
第0周（上线日）：启动+专人对接支持
第2周：采用情况检查（谁在使用？谁没使用？）
第4周：收集反馈+公开表彰成功案例
第8周：弃用旧系统

Org Change (reorg, new leader, team splits/merges)

组织变革（重组、新领导者、团队拆分/合并）

Timeline: 3–6 months for full stabilization Hardest phase: Desire (people fear for their roles and relationships) Critical reinforcement: Consistent behavior from new leadership

Communication sequence:

Day 0: Announce the change with the "why" — in person or synchronous video
Day 1: 1:1s with most affected team members by their manager
Week 1: FAQ published with honest answers to the 10 most common concerns
Week 2–4: New structure is operating (don't delay implementation)
Month 2: First retrospective — what's working, what needs adjustment
Month 3–6: Regular check-ins on team health and morale

What to say when a leader is leaving or being replaced: Be honest about what you can share. Never: "We can't share the reasons." Always: either a truthful explanation or "we're not able to share the specifics, but I can tell you [what this means for you]."

时间线： 完全稳定需3-6个月 最困难阶段： 意愿（人们担心自己的角色和人际关系） 关键巩固措施： 新领导层的一致行为

沟通顺序：

第0天：通过面对面或同步视频宣布变革，并说明“为什么”
第1天：由经理与受影响最大的团队成员进行一对一沟通
第1周：发布FAQ，坦诚回答10个最常见的顾虑
第2-4周：新结构开始运作（不要推迟实施）
第2个月：首次回顾——哪些有效，哪些需要调整
第3-6个月：定期检查团队健康状况和士气

当领导者离职或被替换时该说什么： 坦诚分享你能透露的信息。绝对不要说：“我们无法分享原因。”应该说：要么给出真实解释，要么说“我们无法分享具体细节，但我可以告诉你[这对你意味着什么]。”

Strategy Pivot (new direction, killed products)

战略转型（新方向、终止产品）

Timeline: 3–12 months for full alignment Hardest phase: Awareness (people don't believe the pivot is real) Critical reinforcement: Resource reallocation that visibly proves the pivot is happening

Communication sequence:

Internal first, always. Employees should never hear about a pivot from a press release.
All-hands with full context: what changed in the market, what you're doing, what it means for teams
Each team leader runs a "what does this mean for us?" conversation with their team
Resource reallocation announced within 2 weeks (if the money doesn't move, people won't believe the pivot)
First milestone of the new direction celebrated publicly

What kills pivots: Announcing a new direction while still funding the old one at the same level.

时间线： 完全对齐需3-12个月 最困难阶段： 认知（人们不相信转型是真的） 关键巩固措施： 资源重新分配，以明确证明转型正在进行

沟通顺序：

永远先对内沟通。员工绝不能从新闻稿中得知转型消息。
全员会议提供完整背景：市场发生了什么变化，我们要做什么，这对各团队意味着什么
每个团队负责人与团队开展“这对我们意味着什么？”的讨论
2周内宣布资源重新分配（如果资金没有转移，人们不会相信转型是真的）
公开庆祝新方向的首个里程碑

导致转型失败的原因： 宣布新方向的同时，仍以相同水平为旧方向提供资金。

Culture Change (values refresh, behavior expectations)

文化变革（价值观更新、行为期望）

Timeline: 12–24 months for genuine behavior change Hardest phase: Reinforcement (behavior doesn't change just because values were announced) Critical reinforcement: Visible decisions that reflect the new values

Communication sequence:

Build with input: involve a representative sample of the company in defining the change
Announce with story: "Here's what we observed, here's what we're changing and why"
Behavior anchors: for each culture change, state the specific behavior in observable terms
Leader behavior: leadership team must visibly model the new behavior first
Performance integration: new expected behaviors appear in reviews within one cycle
Celebrate the right behaviors: when someone exemplifies the new culture, name it publicly

时间线： 真正实现行为改变需12-24个月 最困难阶段： 巩固（仅仅宣布价值观不会改变行为） 关键巩固措施： 体现新价值观的可见决策

沟通顺序：

集思广益：让公司内具有代表性的员工参与定义变革
用故事宣布：“这是我们观察到的情况，这是我们要改变的内容及原因”
行为锚点：针对每项文化变革，用可观察的术语明确具体行为
领导者行为：领导层必须首先以身作则，展现新行为
绩效整合：新的期望行为在一个周期内纳入绩效评估
表彰正确行为：当有人体现新文化时，公开点名表扬

Resistance Patterns

阻力模式

Resistance is information, not defiance. Diagnose before responding.

Resistance pattern	What it signals	Response
"This won't work"	Awareness gap or credibility gap	Explain the evidence base for the change
"Why now?"	Awareness gap	Explain urgency — what happens if we don't change
"I wasn't consulted"	Desire gap	Acknowledge the gap; involve them in the "how" now
"I don't have time for this"	Ability gap	Reduce their load or push the timeline
"We tried this before"	Trust gap	Acknowledge what's different this time. Be specific.
Silent non-compliance	Could be any gap	1:1 conversation to diagnose

The worst response to resistance: Dismissing it. "Some people are resistant to change" as if resistance is a personality flaw rather than a signal.

阻力是信息，而非对抗。先诊断再回应。

阻力模式	信号含义	应对方法
“这行不通”	认知缺口或可信度缺口	解释变革的依据
“为什么是现在？”	认知缺口	解释紧迫性——如果不变革会发生什么
“没人征求我的意见”	意愿缺口	承认缺口；现在让他们参与“如何做”的讨论
“我没时间做这个”	能力缺口	减轻他们的工作负担或推迟时间线
“我们之前试过这个”	信任缺口	承认本次与以往的不同之处，给出具体说明
沉默的不配合	可能是任何缺口	一对一沟通进行诊断

对阻力最糟糕的回应： 无视它。比如将“有些人抵制变革”视为性格缺陷，而非信号。

Change Fatigue

变革疲劳

When organizations change too fast, people stop believing any change will stick.

当组织变革过快时，人们会不再相信任何变革能持续。

Signals

迹象

Eye-rolls during change announcements ("here we go again")
Low attendance at change-related sessions
Fast compliance on paper, slow adoption in practice
"Last month we were doing X, now we're doing Y" comments

变革通知时翻白眼（“又来了”）
变革相关会议出席率低
书面上快速合规，但实际采用缓慢
“上个月我们还在做X，现在又要做Y”的言论

Prevention

预防措施

Finish what you start. Don't announce a new change while the last one is still being absorbed.
Space changes. One significant change at a time. Give 2–3 months of stability between major changes.
Announce what's NOT changing. People in change-fatigue need to know what's stable.
Show results. Publish what the previous change achieved before launching the next.

善始善终：不要在上一次变革还未被完全接受时就宣布新变革。
间隔变革：一次只推进一项重大变革。在重大变革之间留出2-3个月的稳定期。
宣布不变的内容：处于变革疲劳中的人们需要知道什么是稳定的。
展示成果：在推出下一项变革前，公布上一次变革取得的成果。

When you're already in change fatigue

当已陷入变革疲劳时

Pause non-critical changes
Run a "change inventory": how many changes are in progress simultaneously?
Prioritize ruthlessly: which changes are essential now? Which can wait?
Communicate stability: "Here's what is NOT changing this quarter"

暂停非关键变革
开展“变革盘点”：同时有多少项变革在推进？
无情地优先排序：哪些变革现在是必需的？哪些可以推迟？
沟通稳定性：“以下是本季度不会发生的变化”

Key Questions for Change Management

变革管理的关键问题

"Who are the most skeptical people about this change? Have we talked to them directly?"
"Do people understand why we're doing this, or just what we're doing?"
"Have we given people time to practice before we measure performance on the new way?"
"Is the old way still available? If so, people will use it."
"Are leaders modeling the new behavior themselves?"
"How many changes are we running simultaneously right now?"

“谁是对这项变革最持怀疑态度的人？我们是否直接与他们沟通过？”
“人们理解我们为什么要做这件事，还是只知道我们要做什么？”
“在我们用新方式衡量绩效之前，是否给了人们练习的时间？”
“旧方式是否仍可用？如果是，人们会继续使用它。”
“领导者是否在以身作则，践行新行为？”
“我们目前同时在推进多少项变革？”

Red Flags

危险信号

Change announced on Friday afternoon (people stew over the weekend)
"This is final, questions are not welcome" framing
No published FAQ or way to ask questions safely
Old system/process still running 6 weeks after "go-live"
Leaders exempted from the change they're asking everyone else to make
No measurement of adoption — assuming go-live = success

在周五下午宣布变革（人们会在周末反复琢磨）
采用“这是最终决定，不接受提问”的措辞
没有发布FAQ或安全提问的渠道
“上线”6周后旧系统/流程仍在运行
领导者豁免于他们要求其他人执行的变革
不衡量采用情况——假设上线=成功

Detailed References

详细参考资料

```
references/change-playbook.md
```
— ADKAR deep dive, resistance counter-strategies, communication templates, change fatigue management

```
references/change-playbook.md
```
— ADKAR深度解析、阻力应对策略、沟通模板、变革疲劳管理