Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/change-management-and-training

change-management-and-training

Verified

Use 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.

references/well-architected.md

View on GitHub
# Well-Architected Notes — Change Management and Training

## Relevant Pillars

- **Operational Excellence** — The primary pillar. Change management and training directly determine whether a Salesforce implementation delivers operational value or sits unused. The Well-Architected Framework's Operational Excellence pillar covers adoption, sustainable operations, and continuous improvement — all of which require structured human change processes alongside technical delivery.

- **User Experience** — Training and in-app guidance directly shape the end-user experience of the platform. Poorly communicated changes degrade UX even when the technical implementation is sound. Role-specific training and Path coaching text are UX decisions, not just operational tasks.

- **Reliability** — Untrained users entering low-quality data, bypassing validation rules, or creating duplicate records degrades org reliability. Change management reduces reliability failures caused by human behavior, not platform faults.

## Architectural Tradeoffs

**In-App Guidance vs. External Training Material**
In-app guidance (walkthroughs, prompts) is delivered at the moment of need inside Salesforce. It scales without scheduling and degrades gracefully when users ignore it. External training (documents, videos, live sessions) is richer and allows practice in a safe environment but requires user initiative to consume. For simple behavioral changes (new required field, new stage), in-app guidance is sufficient. For complex workflow changes affecting multiple objects and steps, both are required — external training first, in-app guidance as reinforcement.

**Centralized Training Org vs. Sandbox for Practice**
A dedicated training org allows persistent, realistic data for exercises without risking sandbox refresh cycles. However, it requires ongoing maintenance to keep configuration in sync with production. Sandboxes are easier to maintain but get refreshed, wiping training scenarios. Choose a dedicated training org when training is repeated (e.g., onboarding new hires), use a full sandbox for one-time project rollouts.

The maintenance cost of the dedicated org is not only configuration drift. The Metadata API's `SandboxSettings` type exposes `disableSandboxExpirationEmails`, which suppresses notifications about deletion of sandboxes that have been inactive for 180 days or longer — a training org that sits idle between cohorts is precisely that profile. Budget an owner and a touch cadence for it, or accept that it will one day be gone when the next cohort arrives.

## Anti-Patterns

1. **Big-Bang Training on Go-Live Day** — Delivering all training on the morning of go-live combines the highest cognitive load (new system) with the highest stress (live work). Users retain almost nothing. The correct approach is training 1–2 weeks before go-live in a sandbox with realistic scenarios, followed by a brief reminder communication on launch day.

2. **One-Size-Fits-All Training** — Presenting a tour of all Salesforce features to a mixed audience of Sales Reps, Service Agents, and Managers simultaneously. Each role gets confused by features they will never use and misses depth on what they will. Training must be segmented by role and anchored to the specific tasks that role performs, not to the platform's feature inventory.

3. **No Adoption Baseline Before Go-Live** — Measuring adoption improvement requires a baseline. If no data is captured before go-live on current login patterns or task completion rates, there is nothing to compare against. Define and start capturing the baseline metric at least 2 weeks before go-live even if the system being replaced is not Salesforce.

## Official Sources Used

Each bullet names the section of this skill it supports.

### Platform behaviour (Summer '26 / v62 PDF guides)

- Metadata API Developer Guide — `Prompt` and `PromptVersion`: file suffix `prompt` in the `prompts` folder, API 46.0+; `displayType` (`DockedComposer` / `FloatingPanel` / `Targeted`); `userProfileAccess` (`Everyone` / `SpecificProfiles`, API 48.0+); `userAccess` (`Everyone` / `SpecificPermissions`); `uiFormulaRule` with `{!$Permission.CustomPermission.<name>}`; `stepNumber` up to 10 consecutive steps; `timesToDisplay` maximum 30; `title` 36 chars, `actionButtonLabel` 25, `dismissButtonLabel` 15, `body` up to 4,000 chars in API 60.0+ (240 for floating and targeted prompts earlier). *(Supports gotcha 1, `worked-examples.md` §5.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/api_meta.pdf

- Metadata API Developer Guide — `PathAssistant` (API 34.0+): only one path per record type per object including `__Master__`; `recordTypeName` required and not updateable; a missing `pathAssistantSteps` entry means the step is unconfigured, not absent. *(Supports gotcha 2.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/api_meta.pdf

- Metadata API Developer Guide — `CustomApplication.profileActionOverrides` / `AppProfileActionOverride` (API 39.0+): a Lightning record page assignment is keyed on `pageOrSobjectType`, `recordType`, `profile` and `formFactor` (`Large` = Lightning Experience desktop). *(Supports gotcha 8, `worked-examples.md` §1.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/api_meta.pdf

- Object Reference — `LoginHistory` (API 21.0+): supported calls `describeSObjects()`, `query()`, `retrieve()`; access limited to Manage Users or Monitor Login History, except own records from API 37.0; `LoginType` values include `Application`, `Remote Access 2.0`, `SAML Sfdc Initiated SSO`, `Lightning Login`, `Help And Training`. *(Supports gotcha 3 and the AM-01 metric.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/object_reference.pdf

- Object Reference — `PromptAction` (API 46.0+): `TimesDisplayed`, `TimesActionTaken`, `TimesDismissed`, `TimesSnoozed`, `StepNumber`, `StepCount`, and `LastResult` (`CustomAction` / `Dismiss` / `Error` / `Finish` / `NoAction` / `NotSeen` / `Snooze`). *(Supports the AM-02 metric — the only platform record of whether guidance was consumed.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/object_reference.pdf

- Object Reference — `PermissionSetAssignment` (API 22.0+): supported calls include `create()` and `delete()`; `ExpirationDate` and `IsActive` from API 52.0; access requires View Setup and Configuration, Assign Permission Sets, or Manage User (Summer '20+). *(Supports gotcha 7 and the pre-send verification in `examples.md`.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/object_reference.pdf

- Object Reference — `ListView` (API 32.0+): the field list is `DeveloperName`, `IsSoqlCompatible`, `LastModifiedById`, `LastReferencedDate`, `LastViewedDate`, `Name`, `NamespacePrefix`, `SobjectType` — no user field and no usage counter. *(Supports the "what you cannot measure" note in `worked-examples.md` §6.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/object_reference.pdf

- Metadata API Developer Guide — `SandboxSettings` (API 56.0+): `disableSandboxExpirationEmails` suppresses notifications about deletion of sandboxes inactive for 180 days or longer. *(Supports the training-org maintenance tradeoff below — a dedicated training org that sits idle between cohorts is exactly the profile these notices target.)*
  URL: https://resources.docs.salesforce.com/262/latest/en-us/sfdc/pdf/api_meta.pdf

### Repo standards and neighbouring skills

- `skills/devops/sandbox-refresh-and-templates/SKILL.md` — "Refresh Intervals by Sandbox Type" and sandbox-template scope. *(Supports gotcha 5 and the training-environment sequencing in `worked-examples.md` §4; carries the UNVERIFIED marker there, since the interval is not in the extracted PDFs.)*

- `skills/admin/salesforce-release-preparation/SKILL.md` — seasonal upgrade cadence, Sandbox Preview opt-in irreversibility, Release Updates triage. *(Supports gotcha 9 and the `release_window_check` field of the plan artefact.)*

- `agents/_shared/AGENT_CONTRACT.md` — the Citations block and Process Observations requirements that any agent consuming this skill's artefacts must satisfy. *(Supports the "Where each artefact goes next" table in `worked-examples.md`.)*

### Salesforce Architects and Trailhead

- Salesforce Well-Architected Overview — Operational Excellence and Engaging pillar framing
  URL: https://architect.salesforce.com/docs/architect/well-architected/guide/overview.html

- Salesforce Well-Architected — Engaging sub-pillar (Easy pillar) — user adoption as an architecture quality dimension
  URL: https://architect.salesforce.com/well-architected/easy/engaging

- Trailhead: User Training and Motivation — four-step training plan workflow, super user program, training library structure
  URL: https://trailhead.salesforce.com/content/learn/modules/user-training-and-motivation

- Trailhead: Training Strategy and Communication Plan — role-specific communications, "What's in it for me?" framing
  URL: https://trailhead.salesforce.com/content/learn/modules/user-training-and-motivation/create-your-training-strategy-and-communication-plan

- Trailhead: Leveraging Change — Six Levers of Change model (Leadership, Ecosystem, Values, Enablement, Rewards, Structure)
  URL: https://trailhead.salesforce.com/content/learn/modules/levers-of-change-model/learn-the-levers-of-change

- Trailhead: Salesforce Adoption Strategies — adoption planning, go-live readiness, internal communication
  URL: https://trailhead.salesforce.com/content/learn/modules/salesforce-adoption-strategies

- Trailhead: Release Readiness Strategies — pre-release sandbox preview workflow, Release Notes triage, user communication timing
  URL: https://trailhead.salesforce.com/content/learn/modules/sf_releases/sf_releases_strategy

- Trailhead: Improve User Engagement with In-App Guidance — prompt types, targeting, walkthrough configuration
  URL: https://trailhead.salesforce.com/content/learn/modules/user-engagement

- Salesforce In-App Guidance Help — configuring walkthroughs and prompts in Lightning Experience
  URL: https://help.salesforce.com/s/articleView?id=sales.customhelp_lexguid.htm&type=5

- Salesforce Path documentation — Stage coaching text, record type scoping, Path setup
  URL: https://help.salesforce.com/s/articleView?id=sf.sales_path_overview.htm

- Trailhead: Enhance User Adoption Metrics — LoginHistory-based adoption measurement
  URL: https://trailhead.salesforce.com/content/learn/modules/user-adoption-metrics
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 119kUpdated Claude CodeCodexVerifiedInstall
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: 118kUpdated Claude CodeCodexVerifiedInstall