What This Template Is For
Most process and tool changes fail not because the new tool is bad, but because the rollout was. People resist change when they do not understand why it is happening, when they are not given time to learn, and when nobody measures whether the transition actually worked. The result is shadow processes, low adoption, and a worse outcome than the system you replaced.
This template structures a change rollout across four phases: assess the impact, communicate the change, execute the rollout, and track adoption. It works for tool migrations (e.g., moving from Jira to Linear), process changes (e.g., new sprint cadence), workflow redesigns (e.g., new approval process), and organizational restructures that affect how teams work.
The product operations handbook covers how to build operational rhythms that stick. For communicating the rationale behind the change to leadership, the Stakeholder Alignment Meeting Template provides the decision-making structure. For proposing the change in the first place, the Internal Tool Proposal Template is the right starting point. Understanding stakeholder management principles will help you navigate resistance.
How to Use This Template
- Start with the Impact Assessment. You cannot plan a rollout without understanding who is affected, how their work changes, and what the risks are.
- Build the Communication Plan before you touch any tooling. People need to know what is changing, why, and what they need to do, in that order.
- Plan the rollout in phases. Never switch everyone at once unless the change is trivial. Start with a pilot group, iterate, then expand.
- Define adoption metrics before the rollout begins. If you wait until after launch to figure out what "success" means, you will rationalize whatever happened.
- Assign a change owner for each affected team. This person is not the PM; they are a champion within the team who answers questions and models the new behavior.
- Plan for the transition period. There will be a dip in productivity. Acknowledge it and budget time for it.
The Template
Change Summary
| Field | Details |
|---|---|
| Change description | [One sentence: what is changing] |
| Reason for change | [Why: the problem this change solves, with data if available] |
| Change owner | [Name and role] |
| Sponsor | [Executive or leader who approved the change] |
| Affected teams | [List of teams] |
| Number of people affected | [Count] |
| Target completion date | [Date when the old process/tool is fully retired] |
Impact Assessment
For each affected team, assess the change impact.
| Team | Current Process | New Process | What Changes for Them | Impact Level | Change Champion |
|---|---|---|---|---|---|
| [Team A] | [How they work today] | [How they will work after] | [Specific differences] | [High/Med/Low] | [Name] |
| [Team B] | [Current] | [New] | [Changes] | [Impact] | [Champion] |
| [Team C] | [Current] | [New] | [Changes] | [Impact] | [Champion] |
Risks.
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk 1: e.g. team resists adoption] | [High/Med/Low] | [Impact] | [Mitigation plan] |
| [Risk 2: e.g. data loss during migration] | [Likelihood] | [Impact] | [Mitigation] |
| [Risk 3: e.g. productivity dip] | [Likelihood] | [Impact] | [Mitigation] |
Dependencies.
- ☐ [Dependency 1: e.g. IT needs to provision accounts by DATE]
- ☐ [Dependency 2: e.g. data migration must complete before training]
- ☐ [Dependency 3: e.g. integration with existing tool X]
Communication Plan
Who needs to know, what they need to know, and when.
| Audience | Message | Channel | When | Owner |
|---|---|---|---|---|
| Leadership | Why we are making this change, timeline, expected ROI | Meeting / Email | [T-30 days] | [Change owner] |
| Affected teams | What is changing, why, what they need to do, training dates | Team meeting + Slack | [T-21 days] | [Change champion] |
| All company | Brief announcement: what is changing and when | All-hands / Email | [T-14 days] | [Change owner] |
| Affected teams | Training sessions scheduled, resources shared | Slack / Calendar invite | [T-7 days] | [Change champion] |
| All company | Go-live announcement with support channels | Slack / Email | [Launch day] | [Change owner] |
Key messages to include in every communication.
- ☐ Why we are making this change (the problem, with data)
- ☐ What is changing (specific, concrete differences)
- ☐ When it is happening (dates and phases)
- ☐ What they need to do (training, migration steps)
- ☐ Where to get help (support channel, change champion name)
Rollout Plan
Phase 1: Pilot (Weeks 1-2)
- ☐ Select pilot group: [Team name, 5-15 people, ideally early adopters]
- ☐ Migrate pilot group data/access
- ☐ Run training session (30-60 min)
- ☐ Provide 1:1 support for the first week
- ☐ Collect feedback daily via [channel]
- ☐ Document issues and FAQs for broader rollout
Pilot success criteria.
| Metric | Target | Actual |
|---|---|---|
| [Adoption rate in pilot group] | [e.g. 90% daily use by end of week 2] | ☐ |
| [Task completion time] | [Same or better than old process] | ☐ |
| [User satisfaction (survey)] | [4+ out of 5] | ☐ |
Phase 2: Expand (Weeks 3-4)
- ☐ Address issues discovered in pilot
- ☐ Migrate next batch: [Teams, number of people]
- ☐ Run training sessions (use pilot learnings to improve)
- ☐ Change champions provide team-level support
- ☐ Retire old tool/process access for pilot group (or set read-only)
Phase 3: Full Rollout (Weeks 5-6)
- ☐ Migrate remaining teams: [List]
- ☐ Final training sessions
- ☐ Set hard cutover date for old tool/process: [Date]
- ☐ Communicate cutover date with 2-week notice
Phase 4: Stabilize (Weeks 7-8)
- ☐ Retire old tool/process completely
- ☐ Archive old data (ensure backup)
- ☐ Close temporary support channels
- ☐ Conduct adoption review (see metrics below)
- ☐ Document the new process as the standard operating procedure
Adoption Tracking
Measure weekly during rollout, monthly after stabilization.
| Metric | Week 1 | Week 2 | Week 3 | Week 4 | Target |
|---|---|---|---|---|---|
| % of affected users active in new system | ☐ | ☐ | ☐ | ☐ | [Target, e.g. 95%] |
| % of affected users still using old system | ☐ | ☐ | ☐ | ☐ | [Target, e.g. 0%] |
| Support tickets related to change | ☐ | ☐ | ☐ | ☐ | [Declining trend] |
| Task completion time (new vs old) | ☐ | ☐ | ☐ | ☐ | [Same or better] |
| User satisfaction score | ☐ | ☐ | ☐ | ☐ | [4+ out of 5] |
Filled Example: CRM Migration (Salesforce to HubSpot)
Change Summary (Filled)
| Field | Details |
|---|---|
| Change | Migrate from Salesforce to HubSpot as primary CRM |
| Reason | Salesforce license costs are $340K/year. HubSpot is $120K/year with equivalent functionality for our use case. Sales team satisfaction with Salesforce is 2.8/5 (complexity complaints). |
| Change owner | Marcus Chen, Sales Operations Manager |
| Sponsor | VP Sales |
| Affected teams | Sales (42 people), CS (18 people), Marketing (12 people), Finance (4 people) |
| Total affected | 76 people |
| Target completion | May 15, 2026 |
Impact Assessment (Filled)
| Team | Current | New | Changes | Impact | Champion |
|---|---|---|---|---|---|
| Sales | Salesforce for pipeline, forecasting, activity logging | HubSpot CRM for all sales workflows | New UI, different reporting, simpler but different automation | High | Sarah, Senior AE |
| CS | Salesforce for account health, renewal tracking | HubSpot Service Hub | New ticketing interface, different dashboard builder | High | Devon, CS Manager |
| Marketing | Salesforce for lead status, campaign attribution | HubSpot Marketing Hub (already using) | Integration improves. No new tool to learn. | Low | Already on HubSpot |
| Finance | Salesforce reports for revenue recognition | HubSpot custom reports | New report templates needed | Med | Jamie, Rev Ops |
Rollout Plan (Filled)
Phase 1: Pilot (March 10-21). West Coast sales team (8 reps). Data migrated March 7-9. Training March 10 (90 min). Sarah (change champion) available for daily office hours.
Phase 2: Expand (March 24 - April 4). East Coast sales (18 reps) + CS team (18 people). Incorporate pilot feedback: add 15-minute "tips" Slack posts daily.
Phase 3: Full Rollout (April 7-18). Remaining sales (16 reps) + Finance (4). Salesforce set to read-only April 14.
Phase 4: Stabilize (April 21 - May 15). Salesforce decommissioned May 1. Data archived. Final adoption review May 15.
Adoption Tracking (Filled)
| Metric | W1 | W2 | W3 | W4 | Target |
|---|---|---|---|---|---|
| % active in HubSpot | 100% (pilot) | 100% (pilot) | 88% | 94% | 95% |
| % still using Salesforce | 38% (pilot checking old data) | 12% | 8% | 2% | 0% |
| Support tickets | 23 | 14 | 31 (expansion) | 18 | Declining |
| Deal logging time | +2 min avg | +0.5 min | Same | Same | Same or better |
| Satisfaction (1-5) | 3.4 | 3.8 | 3.6 | 4.1 | 4.0+ |
Common Mistakes to Avoid
- Switching everyone at once. Big-bang rollouts create big-bang failures. A phased approach with a pilot group catches problems when they affect 10 people, not 100.
- Underestimating the productivity dip. People will be slower with the new tool for 1-2 weeks. Acknowledge it, budget for it, and do not schedule the migration during a critical business period.
- No change champion. The PM cannot be the help desk for every affected team. Identify one person per team who learns the new system early and provides local support.
- Keeping the old system available indefinitely. If people can fall back to the old tool, they will. Set a hard cutover date and communicate it repeatedly.
- Not measuring adoption. "We migrated" is not success. Track daily active use, old system usage, and satisfaction weekly.
Key Takeaways
- Assess impact per team before planning the rollout. Different teams are affected differently
- Communicate the "why" before the "what." People accept change when they understand the reason
- Use a phased rollout with a pilot group first. Catch problems early when they are cheap to fix
- Assign change champions in each affected team. The PM cannot be everyone's help desk
- Track adoption weekly with specific metrics. "We migrated" is not success; daily active use is
About This Template
Created by: Tim Adair
Last Updated: 3/4/2026
Version: 1.0.0
License: Free for personal and commercial use