The Short Answer
Change management is not a communication activity tacked on at the end of a project. It's a parallel workflow that begins with Discovery and concludes months after Go Live. The disparity between successful and failed projects almost always lies here, not in the code.
Four stages, each with a defined deliverable: impact mapping, stakeholder engagement, communication and training, and an ongoing management cycle.
Stage 1 — Impact Mapping by Role
Before designing a single screen, define for each affected role: what they do today, what will change, what will become easier, what will become harder, and what will be measured differently. The third and fourth lines are critical—projects fail when someone discovers only upon Go Live that they've lost control or gained additional work.
| Role | What Changes | Main Risk | Planned Response |
|---|---|---|---|
| Sales Rep | System entry instead of personal Excel | Entry burden, loss of control | Concise form, recurring daily value |
| Sales Manager | System-based forecast | Exposure to unflattering numbers | Prior preparation, private dashboard for transition period |
| Back Office | New approval process | Delays during transition period | Pre-practice, exceptions procedure |
| Management | Single source of truth for reporting | Discrepancies with old reports | Parallel comparison for one quarter |
The deliverable is a two-to-four-page document, serving as input for solution design.
Stage 2 — Stakeholders and Sponsorship
A genuine Sponsor is someone who can change a process, goal, or incentive. A Sponsor who only appears in an introductory message is not a Sponsor. Three minimum commitments worth getting in writing:
- Participation in monthly project reviews and open decision-making.
- An explicit declaration of the single source of truth and discontinuation of parallel reporting by a defined date.
- Support for process changes, even when inconvenient for a specific department.
Alongside the Sponsor, a network of field representatives is built, functioning as a two-way channel—details in Building a Salesforce Champions Network.
Stage 3 — Communication That's Understood Differently Than Usual
Effective communication answers one user question: what does this mean for me? Messages touting "digital transformation" are perceived as noise. Three principles:
- Role-Based Segmentation — One message for the entire organization doesn't work. Tell a representative what changes on their screen, tell a manager what changes in their review.
- Acknowledge the Cost — Explicitly state what will be harder. Denial erodes trust faster than any real drawback.
- Regular Cadence — A short bi-weekly update from Discovery until Hypercare, even when there's no dramatic news.
The training itself is built around work scenarios, not screens; the recommended structure is detailed in Role-Based Salesforce Training.
Stage 4 — The Management Cycle After Go Live
This is the most omitted and most crucial stage. Change is cemented only when it becomes part of the management routine:
- Weekly team review from a system dashboard, not a file.
- Monthly management report generated solely from the system.
- Open request channel with periodic releases and communication of what was fixed.
- Monthly adoption measurement based on Salesforce Adoption Metrics.
The significant target date is not Go Live but the day parallel reporting stops. As long as a legitimate shadow report exists, the system remains a secondary one.
Common Risks and Early Warning Signs
| Warning Sign | Meaning | Reaction |
|---|---|---|
| Sponsor skips two consecutive reviews | No business ownership | Escalate issue to management before UAT |
| "Just one more field" requests accumulate | Process not agreed upon | Freeze and re-evaluate the process |
| Training delayed due to schedule pressure | Project will launch unprepared | Postpone Go Live for relevant team only |
| Managers ask for "the old report too" | Lack of data trust | Correct data before expanding Scope |
Metrics for the Change Program
Four metrics are measured: the percentage of users who completed scenario training, the core action completion rate in the first two weeks, the number of active shadow files, and the average time to close a change request. The first three indicate adoption, the fourth indicates channel trust.
Summary
A good change management program begins with impact mapping during the planning phase, relies on a Sponsor with genuine authority, communicates by role, and continues as a management cycle months after Go Live. This is the least expensive part of the project and the most impactful on its ROI.