PranavNagrecha/AwesomeSalesforceSkills / skills/admin/change-management-and-training
change-management-and-training
VerifiedUse this skill when planning user adoption, structuring Salesforce training materials, drafting release communications, or running a change impact assessment for a Salesforce rollout or update. Triggers: user adoption plan, training materials, release announcement, change impact, go-live communication, communication plan, training plan by persona, adoption metrics, LoginHistory adoption report, PromptAction, training sandbox, go-live checklist, post-go-live feedback, super user program, pilot group. NOT for org deployment mechanics or sandbox promotion — use admin/change-management-and-deployment. NOT for adoption of an Agentforce or Einstein AI feature — use admin/ai-adoption-change-management. NOT for configuring the in-app prompts themselves — use admin/in-app-guidance-and-walkthroughs.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 20.7 KB |
| references/examples.md | markdown | 6.7 KB |
| references/gotchas.md | markdown | 15.5 KB |
| references/llm-anti-patterns.md | markdown | 6.7 KB |
| references/well-architected.md | markdown | 10.4 KB |
| references/worked-examples.md | markdown | 21.4 KB |
| scripts/check_change_management_and_training.pyexecutable | script | 15.5 KB |
| templates/change-management-and-training-template.md | markdown | 6.8 KB |
references/examples.md
View on GitHub# Examples — Change Management and Training
## Example 1: Service Cloud Go-Live with 200 Agents
**Context:** A company is rolling out Salesforce Service Cloud to 200 customer service agents across three contact centers. The agents currently use a legacy ticketing system. This is not a Salesforce-to-Salesforce migration — most agents have never used Salesforce before.
**Problem:** Without structured change management, agents will receive a login URL, attend a 2-hour generic demo, and then be expected to handle live cases. Within the first week, handle time spikes, agents revert to email, and management loses confidence in the project.
**Solution:**
1. Run change impact assessment 6 weeks before go-live. Output:
- Agents: entirely new UI, new case workflow, required Reason field
- Supervisors: new dashboards, omni-channel queue management
- QA team: new case scoring in Salesforce vs. legacy system export
2. Build role-specific training:
- Agents: 4-hour hands-on session in sandbox with realistic case scenarios; Trailhead trail "Service Cloud for Agents" as pre-work
- Supervisors: 2-hour session on queue management and dashboards
3. Configure In-App Guidance walkthroughs for the top 3 case-handling steps (create case, set status, add resolution note)
4. Run a 2-week pilot with 15 volunteer agents from one contact center
5. Use pilot feedback to rewrite 3 training modules that were unclear
6. Send go-live announcement 5 business days before, including Chatter group link and named floor support contacts
7. Install Salesforce Adoption Dashboards; set target: 95% of agents logging in within 5 business days of go-live
**Why it works:** Role-specific training anchored to real scenarios reduces cognitive load. The pilot catches gaps before they affect 200 people. In-app guidance provides just-in-time help without agents needing to remember the training session.
---
## Example 2: Sales Process Change — New Required Stage Fields
**Context:** The Revenue Operations team is adding 3 required fields to the Opportunity object for the Proposal stage: Competitor, Decision Criteria, and Budget Confirmed. This affects 50 Sales Reps and 10 Sales Managers globally.
**Problem:** The admin deploys the required fields without communication. Sales Reps encounter validation errors when saving Opportunities at stage Proposal. They call IT, frustrated that "Salesforce is broken." Handle time on IT support spikes for 3 days.
**Solution:**
1. Change impact assessment identifies:
- Sales Reps: 3 new required fields at Proposal stage (medium disruption)
- Sales Managers: no UI change; downstream impact on forecast quality (low disruption)
- Integration team: field mapping for CRM-to-ERP sync needs update (separate technical track)
2. Draft a What Changed Guide for Sales Reps:
- "When you move an Opportunity to Proposal, you will now need to fill in Competitor, Decision Criteria, and Budget Confirmed before saving."
- "These fields help Revenue Ops forecast accurately. If you are unsure, enter your best estimate — you can update it later."
3. Update Path coaching text at the Proposal stage to remind reps of the 3 fields and why they matter
4. Send announcement to Sales Reps and Managers 5 business days before deployment:
- Subject: "Salesforce Update on [Date]: 3 New Fields for Proposal Stage"
- Body: what changes, why, who to contact with questions
5. Deploy the validation rules and Path coaching text together
6. Monitor Chatter group for questions in the first week
**The artefact that goes out — a What Changed Guide short enough to be read on a phone:**
```markdown
## Opportunity Proposal stage — what changes on 14 March
**Who:** Sales Reps (50), Sales Managers (10) **When:** Friday 14 March, 06:00 UTC
**Who to ask:** #salesforce-help on Slack, or Priya (RevOps)
### If you are a Sales Rep
Moving an Opportunity to **Proposal** now asks for three fields before it saves:
| Field | What to put in it | If you do not know yet |
|---|---|---|
| Competitor | Who else is in the deal | "Unknown" is fine — update it later |
| Decision Criteria | What the customer says will decide it | One line is enough |
| Budget Confirmed | Yes / No / Not discussed | "Not discussed" is a real answer |
You will see the same three fields in the Path panel at the top of the record,
with a reminder of why each one matters.
**Why:** RevOps forecasts from these three fields. Today they guess.
### If you are a Sales Manager
Nothing changes on your screen. From week two, your pipeline review will show
Competitor and Budget Confirmed, so ask about them in your one-to-ones.
### Nothing changes for you if
You work Renewals, Service, or Marketing. This affects the Opportunity
Proposal stage only.
```
**The go/no-go check the morning of the deploy** — verify that what the guide promises is true before anyone reads it:
```bash
# 1. Did the Path deploy for BOTH Opportunity record types?
# PathAssistant allows only one path per record type per object, so expect one
# file per record type. One file back means a record type was missed.
sf project retrieve start -m "PathAssistant" -o prod
ls force-app/main/default/pathAssistants/
grep -h "<recordTypeName>" force-app/main/default/pathAssistants/*.pathAssistant-meta.xml
```
```sql
-- 2. Does everyone the email is addressed to already have the field?
-- Must equal 60 (50 reps + 10 managers) BEFORE the announcement sends.
-- Reading this object needs View Setup and Configuration, Assign Permission
-- Sets, or Manage User — an enablement lead often has none of them.
SELECT COUNT(Id)
FROM PermissionSetAssignment
WHERE PermissionSet.Name = 'Opportunity_Proposal_Fields'
AND IsActive = true
```
**Why it works:** Communicating before deployment turns a surprise error into an expected behavior. Path coaching text provides persistent guidance without requiring IT support. Framing the change around business benefit ("help Revenue Ops forecast") gives reps a reason to comply.
---
## Anti-Pattern: Training Delivered on Go-Live Day
**What practitioners do:** Schedule a "training session" as a 30-minute Zoom call on the morning of go-live. The demo covers every feature rather than what specific roles actually do.
**What goes wrong:** Users are overwhelmed with platform features they will not use for months. They have no time to practice before live cases or opportunities arrive. The first live interaction is stressful. Adoption drops. Management blames the tool, not the training approach.
**Correct approach:** Deliver hands-on, role-specific training in a sandbox at least one week before go-live. Use the go-live day for a brief reminder communication (5 minutes, not 30), not for primary training. Reserve the launch day for excitement and support — not instruction.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |