T04: Org Change Management | Domain 3

📖 Organizational Change Management (OCM)

🇺🇸 English

Organizational Change Management is the structured approach to transitioning individuals, teams, and organizations from current state to a desired future state.

Projects deliver outputs; OCM ensures those outputs are adopted and the intended benefits are realized. Without OCM, technically successful projects often fail because people don't change their behavior.

ADKAR Model (Prosci): The most widely used OCM framework in PMP context:

Awareness — People understand why the change is necessary
Desire — People want to participate and support the change
Knowledge — People know how to change (training, guidance)
Ability — People can demonstrate the new behavior/skill
Reinforcement — Changes are sustained (recognition, consequence management)

Kotter's 8-Step Model: (1) Create urgency → (2) Build coalition → (3) Form vision → (4) Communicate vision → (5) Remove obstacles → (6) Short-term wins → (7) Build on wins → (8) Anchor change in culture

Reference: PMI — Change Management in Projects

🇻🇳 Tiếng Việt

Organizational Change Management (OCM) là phương pháp có cấu trúc để chuyển đổi cá nhân, nhóm và tổ chức từ trạng thái hiện tại sang trạng thái mong muốn.

Dự án deliver outputs; OCM đảm bảo những outputs đó được chấp nhận và sử dụng, và lợi ích dự định được hiện thực hóa.

ADKAR Model:

Awareness — Hiểu tại sao thay đổi cần thiết
Desire — Muốn tham gia và ủng hộ thay đổi
Knowledge — Biết cách thay đổi (training, hướng dẫn)
Ability — Có thể thực hiện hành vi/kỹ năng mới
Reinforcement — Duy trì thay đổi (ghi nhận, quản lý hậu quả)

📊 Change Readiness Assessment

Stakeholder Group	Current State	Change Required	Readiness Level	OCM Strategy
Loan Officers (users)	Manual process, Excel-based	Adopt new digital platform	Low — fear of job change	Early user testing, involve in design, training, champions program
Credit Risk Team	Manual credit review	Work with automated credit engine	Medium — skeptical of AI accuracy	Pilot program, explainability training, confidence-building workshops
IT Operations	On-premise systems	Support cloud-native platform	Medium — new technology skills needed	Training on new stack, pair with dev team during hypercare
Branch Managers	Approve exceptions manually	Review digital exception queue	High — they see efficiency gains	Leverage as champions, give early access, gather their feedback

OCM Plan — ADKAR Application

TARGET GROUP: Loan Officers (200 people, high resistance) AWARENESS (Months -2 to -1 before launch) • Townhall: Why this change? What problem does it solve? • Success stories from pilot branch users • FAQ document addressing "will this replace my job?" directly DESIRE (Month -1 to launch) • Involve loan officers in UAT — they shape the final product • Pilot program: 10 volunteer "early adopters" test system • Share early adopter wins with wider group KNOWLEDGE (Month -1 to launch) • 4-hour training program (role-based, not generic) • Quick reference guide (pocket-sized) + short video tutorials • Sandbox environment for practice ABILITY (Launch + 30 days) • On-floor coaching during first 2 weeks post-launch • Dedicated help desk for platform questions • Weekly Q&A sessions with product team REINFORCEMENT (Month +1 to +6) • Recognition for early adopters and power users • Track adoption metrics → celebrate milestones • Manager coaching guide for sustained adoption • Monthly productivity metrics shared with team

🎯

Exam Tips — Organizational Change Management

OCM is PM's responsibility — even if there's a dedicated change manager, PM ensures it's planned and executed
ADKAR: if someone is "stuck" at K (no training), don't push to A (ability) — address the gap first
Resistance to change is normal and expected. PM's role = understand root cause, not force compliance
Organizational readiness must be assessed before go-live, not after problems emerge
Champions/early adopters: identify and leverage them to accelerate adoption
Kotter's 8 steps: know them in order — "short-term wins" (step 6) come before "anchoring in culture" (step 8)

💼 Thực chiến / Scenario

🏢

FinTech Company X — Managing Loan Officer Resistance

Context: Project Alpha is launching a digital lending platform that will replace the current manual loan processing workflow used by 200 loan officers. Initial surveys show 60% of loan officers are worried about job security. 20% are actively resistant.

OCM challenge: A technically perfect system with 30% adoption rate = project failure. Benefits (processing speed, volume) are only realized if loan officers actually use the system.

PM's OCM approach:

Address fear directly: Town hall with HR and branch leadership. Clear statement: "This platform augments loan officers — it doesn't replace them. Volume growth creates MORE positions, not fewer." Commitment in writing.
Early involvement: 15 loan officers participate in UAT (Sprint 10). Their feedback shapes the UI. They become system advocates because they owned part of it.
Champions network: 10 "Digital Champions" identified (enthusiastic early adopters) in 10 branches. They receive advanced training and a small performance bonus for supporting peers post-launch.
Phased rollout: Branches 1-5 launch first (highest readiness). Lessons learned feed into branches 6-20 rollout.
30-day adoption tracking: Daily active users, transaction volume per user, helpdesk tickets. Tracked by PM + HR. Branches below 60% adoption at Day 30 get extra coaching.

Result: Day 30 adoption = 78%. Day 60 = 92%. Loan processing time reduced from 45 minutes to 4 minutes. 3 loan officers promoted to "Digital Process Leads." Zero involuntary separations.

PMP lesson: OCM isn't a soft skill sidebar — it's the difference between a delivered project and a realized benefit. Budget and plan for it like any other workstream.

✏️ Practice Questions

Question 1

A project will significantly change how customer-facing staff perform their daily work. The team has delivered the software on time, but users refuse to adopt the new system, using workarounds instead. This is BEST described as a failure of:

A. Quality management — the system must not work correctly
B. Organizational change management — people adoption was not planned and managed
C. Stakeholder engagement — the stakeholders should have been informed more
D. Project communications — better reports would have prevented this

✅ Answer: B — Organizational Change Management. The project delivered technically (system works) but the people transition was not managed. OCM failure means adoption didn't happen, so benefits can't be realized. This is a distinct discipline from stakeholder engagement (C — knowing what's coming) or communications (D — receiving information). OCM ensures people have the Awareness, Desire, Knowledge, Ability, and Reinforcement to actually change their behavior.

Question 2

According to the ADKAR model, a user has been trained (Knowledge) but still cannot perform the new process correctly. What should the PM address next?

A. Awareness — they don't understand why change is needed
B. Desire — they don't want to change
C. Ability — they need practice, coaching, or additional support to perform the skill
D. Reinforcement — add a reward system to motivate performance

✅ Answer: C — Ability. In ADKAR, having Knowledge (knowing how) is different from having Ability (being able to do it). Training gives knowledge, but ability requires practice, coaching, and real-world application support. The PM should provide hands-on coaching, a practice environment, and time on the job with support — not more training or re-explaining the "why" (those gaps are earlier in ADKAR).

Question 3

A project is implementing a new ERP system. 6 months post-go-live, 40% of users are still using the old system in parallel, creating data duplication. The BEST intervention is:

A. Force users to stop using the old system by disabling it immediately
B. Diagnose why users prefer the old system (missing functionality? usability? habits?), address root causes, provide targeted support, and set a definitive sunset date with communication — not just forcing compliance
C. Accept dual-system operation permanently
D. Roll back to the old system

✅ Answer: B — OCM principle: understand resistance root cause before forcing compliance. Users reverting to the old system is a signal, not just a behavior to eliminate. Root causes could include: missing critical features in the new system, poor usability compared to familiar tools, inadequate training, or simply change resistance from habit. Each root cause needs a different intervention. Abrupt shutdown (A) without addressing the underlying reasons creates backlash, workarounds, and shadow IT. Dual-system permanence (C) is unsustainable and perpetuates data integrity problems. At FinTech Company X, this mirrors ERP adoption challenges in finance teams after Project Alpha go-live.

🤖 AI Tools for PMs

🤖

How AI Augments This Process

AI helps PMs design organizational change management plans, assess change readiness, generate ADKAR-based interventions, and create adoption tracking frameworks.

Sample Claude Prompts

ADKAR-based change readiness assessment I need to assess organizational readiness for change using the ADKAR model. Change being introduced: [what the project will change for users] Target population: [who must change their behavior — role, size, location] Current state: [how they work today] Future state: [how they need to work after the project] Timeline to adoption required: [by what date must adoption be achieved] For each ADKAR element, assess the current state and gap: Awareness: Do people know WHY the change is happening? Current level: [1-5] | Evidence: [what do I observe] Gap: [what they don't understand yet] Desire: Do people WANT to change? Current level: [1-5] | Evidence: [attitudes / resistance signals observed] Root cause of resistance: [my hypothesis] Knowledge: Do people know HOW to change? Current level: [1-5] | Training plan in place: [yes/no] Ability: Can people PERFORM the new behavior? Current level: [1-5] | Practice opportunities: [what's available] Reinforcement: Is the change being SUSTAINED? Current level: [1-5] | Recognition/consequence system: [what exists] Output: ADKAR gap analysis with targeted intervention for each dimension.

Change resistance management strategy I'm facing resistance to organizational change. Help me develop a strategy. Change being resisted: [what the project is implementing] Resisting group: [role / department / location / size] Resistance type observed: [active opposition / passive non-compliance / vocal skepticism / silent withdrawal] Root cause assessment: [fear of job loss / loss of control / past bad experience / distrust of leadership / genuine concern about the change] Change history with this group: [have they been through failed changes before?] Their legitimate concerns: [what valid points do they raise?] Champions available: [are there supportive people in this group?] Develop a resistance management strategy: 1. Acknowledge what's legitimate in their concerns (don't dismiss) 2. Categorize resistors: Core resister / Fence-sitter / Passive follower 3. Intervention plan by segment: - Core resisters: targeted 1-on-1 engagement - Fence-sitters: champion peer influence + early wins - Passive followers: clear communication + easy wins 4. Messaging strategy: what to say and what NOT to say 5. Quick wins to demonstrate early success and convert fence-sitters 6. Escalation: when and how to involve senior leadership

Adoption metrics and tracking plan My project is launching. Help me design an adoption tracking plan. Change being adopted: [what users need to start doing] Target adoption rate: [% of users actively using the new system/process] Timeline: [when must adoption be achieved] User population: [size, roles, locations] Available data for tracking: [system login data / transaction volumes / manual surveys / helpdesk tickets] Definition of "adopted": [what does it mean for a user to have adopted? — specific behavior] Design an adoption tracking plan: 1. Adoption metrics (leading and lagging indicators): - Leading: [training completion %, early adopter usage rate, helpdesk ticket types] - Lagging: [% using new system, old system decommission readiness, productivity metrics] 2. Measurement cadence (daily/weekly/monthly) 3. Dashboard design: what to show PM vs. sponsor vs. operations 4. Intervention triggers: adoption < X% by day Y → escalate / provide support 5. Adoption milestone celebrations: when and how to recognize progress 6. Definition of "change complete" — when can we close the OCM workstream?

Jira / Confluence Template

Confluence — OCM Plan and Adoption Tracker

── CONFLUENCE: OCM PLAN — ADOPTION TRACKER ────────────── Project: [Project Alpha] | Target group: [Loan Officers — 200 people] Go-live: [YYYY-MM-DD] | Target adoption: 90% by Day 60 ── ADKAR STATUS ────────────────────────────────────────── A - Awareness: 🟢 Townhalls complete — 95% reached D - Desire: 🟡 Resistance in Branch 3 and 7 — coaching in progress K - Knowledge: 🟢 Training complete — 98% attendance A - Ability: 🟡 Day 14 post-launch — some users still need floor support R - Reinforcement: 🔴 Recognition program not yet launched — starting Week 3 ── ADOPTION METRICS ────────────────────────────────────── Day 7: DAU: [count] ([%] of target) | Tickets: [count] | Top issue: [type] Day 14: DAU: [count] ([%] of target) | Old system parallel use: [%] Day 30: DAU: [count] ([%] of target) | Productivity change: [+/-%] Day 60: DAU: [count] ([%] of target) | Target met: [ ] Yes [ ] No ── INTERVENTION LOG ────────────────────────────────────── [Date] Branch [X]: Low adoption → Action: Extra coaching → Result: [outcome] Champions activated: [count] | Branches at risk: [list]

🎓

Domain 3 Complete! All Three Domains Done!

Bạn đã hoàn thành toàn bộ nội dung học PMP: Domain 1 (42%) + Domain 2 (50%) + Domain 3 (8%) = 100% ECO coverage.

Next steps: Review Tools & Templates, practice exam questions, and use Exam Tips for final review strategy.

Support Organizational Change