Mengapa ERP Gagal? Bukan Teknologi—Manusia
Studi Prosci: Proyek dengan change management excellent 6x lebih likely mencapai objektif dibanding yang poor. ERP mengubah cara kerja semua orang—resistensi alami, tapi manageable.
Framework Change Management ERP (ADKAR + Kotter Hybrid)
Phase 1: Prepare (Awareness & Desire) – Pre-Project
- Executive Sponsorship: Visible, active, consistent. C-level kommunikasikan “Why ERP, Why Now, What’s In It For Me”
- Change Vision & Narrative: Story telling: Current pain → Future state → Benefit per role
- Stakeholder Analysis: Mapping (Power/Interest), identifikasi Champion, Resistor, Neutral. Strategi per kelompok
- Impact Assessment: Role mapping: Proses apa berubah? Skill gap apa? Training butuh berapa jam?
- Communication Plan: Multi-channel (townhall, email, video, poster, chat), cadence (mingguan/bulanan), two-way (Q&A, feedback)
Phase 2: Design & Build (Knowledge & Ability) – During Implementation
- Super User Network: 1 per 10-15 user per modul/dept. Diberi akses early, training mendalam, jadi “go-to person” & feedback channel
- Role-Based Training Curriculum:
- End User: Task-based (simulasi sandbox), 2-3 hari, job aid/cheat sheet
- Super User: Deep dive config, troubleshooting, train-the-trainer, 5-10 hari
- Manager: Dashboard, approval, exception handling, coaching skill
- IT/Technical: Admin, integration, security, upgrade, 10+ hari
- Training Delivery: Blended (ILT + VILT + e-learning + sandbox practice + job shadowing). Microlearning (5-10 menit) untuk just-in-time
- Training Environment: Sandbox dengan data production-like, reset harian, scenario lengkap (end-to-end)
- Certification & Assessment: Pre/post test, practical exam, minimum passing score untuk go-live access
Phase 3: Deploy (Reinforcement) – Go-Live & Hypercare
- Go-Live Support Model:
- Command Center (War Room): PM, Functional Lead, Technical Lead, Vendor Support – 24/7 minggu pertama
- Floor Walker: Super User di lantai/dept – bantuan langsung, escalate ke Command Center
- Help Desk: Ticketing (SLA 15 menit critical, 2 jam high, 8 jam medium), knowledge base
- Daily Standup: Issue triage, priority, owner, ETA, communication ke stakeholder
- Quick Wins Communication: Daily “Win of the Day” (contoh: “PO approval dari 2 jam jadi 5 menit”), share di channel komunikasi
- Resistance Management: Listen → Empathize → Clarify → Support → Escalate (kalau blocker kritis). Jangan abaikan resistensi—ia sinyal butuh bantuan
- Performance Dip Management: Expect 20-30% productivity drop 2-4 minggu. Communicate upfront. Temporary staffing/overtime budget siapkan
Phase 4: Sustain (Continuous Improvement) – Post Hypercare
- Adoption Metrics Dashboard: Login rate, transaction volume, feature adoption, task completion time, error rate, help desk ticket trend
- Continuous Learning: Monthly tips & tricks, advanced feature webinar, new hire onboarding ERP module, certification renewal
- Optimization Backlog: User feedback → enhancement request → prioritization → Phase 2/3 implementation
- Change Champion Community: Bulanan meeting, share best practice, recognize top contributor, gamification
- Annual Change Health Check: Survey adopsi, satisfaction, skill gap, process compliance, benchmark
Tools & Template Change Management
| Tool | Fungsi | Contoh |
|---|---|---|
| Stakeholder Map | Visualisasi power/interest, strategi engagement | Miro, PowerPoint, Excel |
| Impact Assessment Matrix | Role vs Process change (High/Med/Low), training hours | Excel template |
| Communication Calendar | Jadwal komunikasi: apa, ke siapa, channel, kapan, PIC | Shared calendar, Notion |
| Training Tracker | User, modul, status (not started/in progress/complete/certified) | LMS, Excel |
| Resistance Log | Resistensi, root cause, action, status, owner | Jira, Azure DevOps, Excel |
| Adoption Dashboard | Real-time metrics: login, transaksi, fitur, error, ticket | Power BI, Tableau, ERP native |

Leave a Reply