## Tool 1: Stakeholder Communication Plan Template
Use this template to map every stakeholder group affected by your initiative, define their key WIIFM message, and plan how and when you will communicate with them throughout the change.
<table header-row="true">
<tr>
<td>Stakeholder Group</td>
<td>Key Message (WIIFM)</td>
<td>Channel</td>
<td>Timing</td>
<td>Owner</td>
<td>Status</td>
</tr>
<tr>
<td>GC/CLO</td>
<td>Clearer visibility into function performance; direct reports more engaged; strategic time freed from admin oversight</td>
<td>One-on-one briefing + monthly metrics report</td>
<td>Week 1 (pre-launch) + ongoing</td>
<td>Project Lead</td>
<td>Scheduled</td>
</tr>
<tr>
<td>Senior Counsel</td>
<td>Less administrative overhead; more time to focus on complex matters and team development</td>
<td>Team meeting + executive summary document</td>
<td>Week 1 (pre-launch)</td>
<td>Project Lead</td>
<td>Scheduled</td>
</tr>
<tr>
<td>Working-Level Lawyers</td>
<td>5–8 hours per week reclaimed from admin; faster turnaround on client requests; clearer career visibility</td>
<td>Hands-on workshop + peer champions</td>
<td>Weeks 3–4</td>
<td>Training Lead</td>
<td>Scheduled</td>
</tr>
<tr>
<td>Business Stakeholders</td>
<td>Faster contract turnaround; real-time visibility into status; reduced chase time</td>
<td>Business partner briefing + demonstration</td>
<td>Week 1 (pre-launch)</td>
<td>Project Lead</td>
<td>Scheduled</td>
</tr>
<tr>
<td>IT/Technology</td>
<td>Visibility into new systems; integration points clear; support model defined</td>
<td>Technical briefing</td>
<td>Week 1 (pre-launch)</td>
<td>IT Lead</td>
<td>Scheduled</td>
</tr>
</table>
---
## Tool 2: Adoption Tracker
Track adoption by stakeholder group across the launch timeline. Use RAG (Red/Amber/Green) status to identify groups falling behind target and trigger intervention.
<table header-row="true">
<tr>
<td>Stakeholder Group</td>
<td>Target Adoption %</td>
<td>Week 4 Actual</td>
<td>Week 8 Actual</td>
<td>Week 12 Actual</td>
<td>Status (RAG)</td>
<td>Intervention</td>
</tr>
<tr>
<td>Senior Counsel</td>
<td>85%</td>
<td>72%</td>
<td>81%</td>
<td>87%</td>
<td>Green</td>
<td>—</td>
</tr>
<tr>
<td>Working-Level Lawyers</td>
<td>80%</td>
<td>55%</td>
<td>68%</td>
<td>79%</td>
<td>Green</td>
<td>Peer coaching for laggards at week 6</td>
</tr>
<tr>
<td>Paralegals & Support</td>
<td>90%</td>
<td>65%</td>
<td>82%</td>
<td>91%</td>
<td>Green</td>
<td>—</td>
</tr>
<tr>
<td>Business Stakeholders</td>
<td>70%</td>
<td>40%</td>
<td>58%</td>
<td>72%</td>
<td>Green</td>
<td>Additional orientation session at week 5</td>
</tr>
<tr>
<td>Laggard Group (identify)</td>
<td>75%</td>
<td>25%</td>
<td>45%</td>
<td>62%</td>
<td>Amber</td>
<td>Individual coaching; identify specific blockers</td>
</tr>
</table>
**RAG Thresholds:**<br>- **Green:** Within 10% of target (e.g., target 80%, actual 72%–88%)<br>- **Amber:** 11–25% below target (e.g., target 80%, actual 60%–71%)<br>- **Red:** More than 25% below target or zero usage (e.g., target 80%, actual \< 60%)
**Action Protocol:**<br>- Green status: Continue standard support; celebrate progress<br>- Amber status: Schedule check-in with group lead; diagnose adoption barriers; intensify peer champion support<br>- Red status: Escalate to project leadership; investigate root cause; consider alternative interventions (additional training, tool configuration, workflow redesign)
---
## Tool 3: Training Plan Template
Map training delivery by role group, covering format, duration, content focus, facilitator, and completion tracking.
<table header-row="true">
<tr>
<td>Role Group</td>
<td>Training Format</td>
<td>Duration</td>
<td>Content Focus</td>
<td>Facilitator</td>
<td>Scheduled Date</td>
<td>Completion Rate</td>
</tr>
<tr>
<td>Executive/GC</td>
<td>Executive briefing</td>
<td>30 min</td>
<td>Strategic benefits; oversight and governance; adoption expectations</td>
<td>Project Lead</td>
<td>Week 1</td>
<td>100%</td>
</tr>
<tr>
<td>Senior Counsel</td>
<td>Executive briefing + Q&A</td>
<td>45 min</td>
<td>How the tool changes their day; team supervision; quality assurance role</td>
<td>Senior Champion</td>
<td>Week 1</td>
<td>95%</td>
</tr>
<tr>
<td>Mid-Level Lawyers</td>
<td>Hands-on workshop</td>
<td>2.5 hrs</td>
<td>Live workflow walk-through using their actual contracts; decision-making in the system; peer Q&A</td>
<td>Training Lead + Peer Champions</td>
<td>Weeks 3–4</td>
<td>85%</td>
</tr>
<tr>
<td>Junior Lawyers</td>
<td>Hands-on workshop</td>
<td>2 hrs</td>
<td>Core tasks; integration with research/precedent tools; how to escalate complex issues</td>
<td>Peer Champions</td>
<td>Week 4</td>
<td>92%</td>
</tr>
<tr>
<td>Paralegals & Support</td>
<td>Operational training</td>
<td>1.5 hrs</td>
<td>Specific operational tasks; data entry standards; reporting obligations</td>
<td>Operations Manager</td>
<td>Week 4</td>
<td>98%</td>
</tr>
<tr>
<td>Business Stakeholders</td>
<td>Demonstration + Q&A</td>
<td>60 min</td>
<td>Visibility features; status tracking; communication workflow</td>
<td>Project Lead</td>
<td>Week 1</td>
<td>75%</td>
</tr>
<tr>
<td>Remote/Geographic</td>
<td>Self-paced online module</td>
<td>1.5 hrs</td>
<td>Core content + recorded walkthrough; asynchronous Q&A via Slack</td>
<td>Training Lead</td>
<td>Available Week 2</td>
<td>70%</td>
</tr>
<tr>
<td>New hires (post-launch)</td>
<td>Peer coaching</td>
<td>2 hrs</td>
<td>One-on-one or small group with peer champion; embedded in onboarding</td>
<td>Peer Champions</td>
<td>Ongoing</td>
<td>TBD</td>
</tr>
</table>
**Format Guidance:**
- **Executive briefing (30 min):** High-level overview, business case, leadership role, minimal operational detail. Benefit-focused. For C-suite, senior leaders, or stakeholders without daily tool use.
- **Hands-on workshop (2–3 hrs):** Live demonstration using participant work examples; guided practice with real-world scenarios; peer Q&A. Best for regular tool users. Deliver in role-specific groups.
- **Self-paced module (online):** Recorded walkthrough, knowledge checks, downloadable reference guide. For geographically distributed teams, shift workers, or people who learn better alone.
- **Peer coaching (1–2 hrs):** One-on-one or small group with a champion or experienced user. Used for laggards, new hires, or complex use cases. Most personalised; highest coaching intensity.
---
## Tool 4: 30-Day Post-Launch Review Agenda
Schedule a structured review meeting at day 30 of launch to assess adoption progress, identify friction points, and plan interventions for the next phase.
**Meeting Duration:** 60 minutes<br>**Attendees:** Project lead, training lead, IT support, peer champions (1–2), legal function leadership<br>**Facilitator:** Project lead
### Agenda:
**(1) Adoption Metrics Dashboard (15 min)**<br>- Review key metrics: activation rate, active usage rate, task completion rate, user satisfaction (NPS)<br>- Compare actual vs target for each stakeholder group<br>- Identify groups on track vs groups falling behind<br>- Celebrate wins and progress
**(2) Friction Points and Barriers (20 min)**<br>- Peer champions share feedback from daily interactions: What questions are users asking? What is confusing? What is slower or more difficult than expected?<br>- IT support shares technical issues or performance problems<br>- Aggregate feedback into themes: workflow-related, tool-related, training-related, manager-related, etc.<br>- Prioritise by frequency and severity
**(3) Champion Feedback (10 min)**<br>- What are champions observing about user confidence and satisfaction?<br>- Where are champions spending most time answering questions?<br>- What improvements or features are users requesting?<br>- Are there specific laggard users or teams that need direct intervention?
**(4) Interventions for Amber/Red Groups (15 min)**<br>- For each group below target:<br>- Root cause: Why are they not adopting? (Knowledge gap? Ability gap? Desire gap? Tool issue? Workflow issue?)<br>- Planned intervention: What will be done? (Additional training? Configuration change? Manager conversation? One-on-one coaching?)<br>- Responsible party: Who will drive the intervention?<br>- Timeline: When will this be completed?
**(5) Actions and Owners (10 min)**<br>- Confirm accountability for each intervention identified above<br>- Confirm timeline for next check-in (typically day 60)<br>- Confirm schedule for next phase activities (e.g., launch communications 2.0 at day 45, expanded training for laggards at day 35)
**Output:** Intervention plan with owners, timelines, and success criteria for the next phase.
---
## Tool 5: Change Initiative Checklist — Pre-Launch
Use this checklist 2 weeks before launch to ensure all foundational work is in place.
**Awareness & Communication**<br>- \[ \] Urgency has been established through clear, credible business case communicated to leadership<br>- \[ \] Guiding coalition is assembled and aligned on change narrative<br>- \[ \] Launch communication plan is drafted and approved (channels, timing, messages for each group)<br>- \[ \] One-page “Why We Are Changing” document is drafted and ready for distribution<br>- \[ \] FAQs have been drafted addressing common concerns
**Training & Capability**<br>- \[ \] Training materials are complete for each role group<br>- \[ \] Facilitators are trained and confident delivering role-specific content<br>- \[ \] Training room/platform is booked and tested<br>- \[ \] Self-paced online modules are available for remote learners<br>- \[ \] Peer champions are identified, trained, and briefed on their role<br>- \[ \] Support channel (Slack, email, or helpdesk) is configured and monitored<br>- \[ \] Support team has escalation procedures and is trained on common issues
**Technology & Process**<br>- \[ \] System is fully configured and tested in production environment<br>- \[ \] Integrations with existing tools are tested end-to-end<br>- \[ \] Data migration (if applicable) is complete and validated<br>- \[ \] IT support has tested common troubleshooting scenarios<br>- \[ \] New process is documented (written, visual, or video) for reference
**Leadership & Accountability**<br>- \[ \] Sponsoring executive has conducted public buy-in communication<br>- \[ \] Managers have had individual briefings on their role in adoption<br>- \[ \] Adoption targets and timelines have been communicated to team<br>- \[ \] Success metrics have been defined and baseline data collected<br>- \[ \] Post-launch review meeting is scheduled (day 30)
**Contingency**<br>- \[ \] Rollback plan is in place if critical issues are identified at launch<br>- \[ \] Escalation procedure is defined (who to contact, when, for what severity)<br>- \[ \] 24-hour support coverage is arranged (on-call resource for critical issues)
---
## Tool 6: Change Initiative Checklist — Post-Launch
Use this checklist at key milestones (day 7, day 30, day 90) to ensure ongoing progress and sustained adoption.
**Day 7 Check-In**
- [ ] Activation rate is ≥ 50% of target users
- [ ] No critical technical issues preventing use
- [ ] Support team is handling volume of questions with \< 24-hour response time
- [ ] Peer champions are active and visible in support channels
- [ ] Team sentiment is neutral to positive (no widespread complaints)
- [ ] Course-correct any early issues (communication clarity, technical problems, training gaps)
**Day 30 Review**
- [ ] 30-day post-launch review meeting has been completed
- [ ] Adoption metrics have been calculated and compared to targets
- [ ] Friction points have been identified and prioritized
- [ ] Intervention plan is in place for groups falling behind
- [ ] User satisfaction survey has been distributed and initial results reviewed
- [ ] Celebration communication has been sent highlighting early wins
- [ ] Next phase support and reinforcement is scheduled
**Day 90 Check-In**
- [ ] Adoption rate is at or approaching end-of-phase targets (80%+ active usage expected)
- [ ] Tool utilization is increasing (not plateauing)
- [ ] User satisfaction is stable or improving (NPS \> 30)
- [ ] Interventions for laggard groups have been completed or are showing progress
- [ ] New team members are onboarding smoothly with peer coaching
- [ ] New process is becoming embedded in daily workflow
- [ ] Transition to sustained support model is underway
- [ ] Post-launch learning is being captured (what worked, what would we do differently?)
---