'change-management' 검색 결과

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.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when planning or executing the human side of an Agentforce or Einstein AI feature rollout — user trust-building, AI-specific training, structured feedback collection via the Feedback API, and adoption measurement via Agentforce Analytics. NOT for turning the Einstein for Sales features on — use agentforce/agentforce-sales-ai-setup. NOT for rollout training with no AI in scope — use admin/change-management-and-training.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare employee communications for organizational changes, tool rollouts, and policy updates. Create announcements, audience-specific FAQs, manager talking points, and a communication calendar, while checking tone, channel choices, and sequencing against the change's impact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing an internal reorganization announcement
• Planning communications for a new tool rollout
• Writing audience-specific FAQs for policy changes

Manage change for AI adoption in organizations. TRIGGERS - Use when user needs help with ai-change-management related tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when building, reviewing, or refreshing a RACI (Responsible / Accountable / Consulted / Informed) matrix for a Salesforce project so that every Salesforce-specific decision — data model change, automation tier choice, security model, integration boundary, deployment, license/edition — has exactly one accountable owner and a documented escalation path that downstream agents can route to. Trigger keywords: RACI matrix salesforce project, stakeholder authority salesforce, escalation path salesforce decisions, who approves data model change, salesforce decision rights, REFUSAL_NEEDS_HUMAN_REVIEW routing. NOT for the change advisory board operating model itself (use admin/change-management-and-deployment). NOT for end-user training rollout plans (use admin/change-management-and-training). NOT for the technical mechanics of permission set assignment authority (use admin/permission-set-architecture). NOT for pure stakeholder requirements elicitation (use admin/requirements-gathering-for-sf). More trigger keywords: who approves a sandbox refresh, who signs off a data load, release update activation owner, delegated admin authority vs RACI, multi-org decision rights, escalation time-box.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when a practitioner needs to classify the risk level of an upcoming Salesforce deployment, define rollback trigger conditions, or assign decision authority before the release window opens. Triggers: 'how risky is this release', 'what needs rollback planning', 'classify deployment risk', 'pre-deployment risk checklist', 'rollback decision authority', 'high risk metadata types'. NOT for executing the deployment itself, writing CI/CD pipeline code, or troubleshooting failures after a deployment has already run — use admin/change-management-and-deployment for execution planning and devops/deployment-error-troubleshooting for post-failure diagnosis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, implement, or audit a Change Advisory Board (CAB) process for Salesforce deployments: change classification (standard, normal, emergency), required approvals, deployment gate sequencing, and integration with external ITSM tooling. NOT for scoring how risky one release is - use admin/deployment-risk-assessment. NOT for executing or troubleshooting the deployment itself - use admin/change-management-and-deployment. Also covers: the CAB charter (membership, quorum, decision rights), the CAB decision record artefact and its linter, the change classification matrix, the deployOptions a CAB decision pins (checkOnly, testLevel, rollbackOnError, ignoreWarnings, runTests), the 10-day quick-deploy validity window, the deploy-window vs freeze-register check, and the emergency (ECAB) path with its mandatory retrospective.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Expert en gestion du changement avancé (ADKAR, Kotter, stakeholder analysis, communication plans)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage change for AI adoption in organizations. TRIGGERS - Use when user needs help with ai-change-management related tasks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan organizational changes such as tool migrations, restructures, and strategy shifts using ADKAR, a five-stage model for adopting change. Structure communication, training, and follow-up while addressing employee concerns, resistance, and fatigue from overlapping changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Plan communication and training for a tool migration
• Prepare reorganization announcements and employee FAQs
• Explain a strategy shift and its impact on teams

Plan and control a staged Abridge rollout across clinical cohorts and EHR workflows without pretending to deploy vendor infrastructure. Use when preparing an Abridge pilot or expansion. Trigger with "plan the Abridge rollout".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create a structured change management plan for any organisational change. Use when asked to write a change management plan, manage a change initiative, plan a system rollout, or lead an organisational transformation. Produces a plan covering stakeholder analysis, impact assessment, communication strategy, and resistance management.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement change management processes. Configure CAB reviews, change windows, and rollback procedures. Use when managing production changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Framework for rolling out organizational changes without chaos, using ADKAR adapted for startups. Use when announcing a reorg, switching tools, pivoting strategy, killing a product, or managing change resistance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan, sequence, and pressure-test internal announcements before they send. Use when announcing a reorg, policy, or product change, drafting an all-hands or exec update, or deciding who hears what and in which order.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guides privacy law change monitoring and impact assessment for multi-jurisdiction organisations. Covers regulatory tracking sources, change classification, impact scoring methodology, and implementation prioritisation. Keywords: law monitoring, regulatory tracking, change management, impact assessment, implementation priority.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Establishes ongoing RoPA maintenance processes including update triggers, change management integration, version control, stakeholder review cycles, and completeness verification procedures. Activate for RoPA updates, record maintenance, change management, version history, review scheduling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan and execute organizational or technical changes. Trigger with "we're changing", "rolling out", "migration plan", "how do we communicate this change", "change management plan", or when the user is planning a change that affects people, processes, or systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use whenever the user wants to find, shortlist, vet, or enrich US management consultancies — strategy, operations, executive coaching, leadership development, org-development/change management, PMO/program management, sales/revenue operations consulting. Triggers on "find me three top strategy consultancies in California", "shortlist boutique ops-consulting firms with healthcare experience", "we need an executive coach for our new CEO", or "pull contact info for these 10 consulting firm domains", even when described indirectly (post-merger integration help, change-management partner, fractional COO). Drives the ServiceGraph API (api.servicegraph.co) — a 100k+ US firm catalog filterable by industry, services, location, size, ratings. Skip in-house strategy hires, "help me build a strategy" do-the-work asks, framework comparisons (Lean vs Agile, BCG matrix, etc.), academic/MBA-program questions, life/career coaching for individuals, non-US firms, individual freelancers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build change management plans using ADKAR and Kotter's 8-Step framework. Covers stakeholder readiness, communication plans, training schedules, resistance management, and adoption metrics. Use when rolling out new systems, reorganizations, or process changes that affect people.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when preparing for a Salesforce seasonal release — triaging release notes, reviewing Release Updates, opting into Sandbox Preview, and communicating change impact to stakeholders. Triggers: 'upcoming Salesforce release', 'release notes triage', 'Release Updates', 'sandbox preview opt-in', 'release readiness checklist', 'production upgrade date', 'feature impact', 'critical update', 'roll out the Spring release safely', 'is our org ready for the Spring release', 'release update settings metadata', 'FlowSettings release update field', 'release run sheet', 'preview sandbox refresh freeze', 'settings deploy flipped a release update'. Also covers: which Release Updates are deployable as Settings metadata, the release run sheet artefact, and the preview opt-in refresh-date rule. NOT for planning your own release train — use devops/release-management. NOT for user training and go-live comms — use admin/change-management-and-training.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configuring Salesforce In-App Guidance: floating, docked, and targeted prompts, multi-step walkthroughs, audience targeting, scheduling, and adoption analytics. Use when designing user onboarding or feature adoption programs in Lightning Experience. Covers the Prompt metadata type, promptVersions, displayType, uiFormulaRule, stepNumber, isPublished, PromptAction and PromptError. NOT for guidance on a record's Path — use admin/path-and-guidance. NOT for adoption and training — use admin/change-management-and-training.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when planning, sequencing, or troubleshooting an org-wide migration from Salesforce Classic to Lightning Experience. Covers the LEX Transition Assistant Readiness Check, asset triage matrix (Visualforce, JavaScript buttons, page layouts, Knowledge, email templates, list views, AppExchange), pilot/wave rollout sequencing, end-user adoption telemetry, and cutover criteria. Triggers: 'lightning experience transition', 'classic to lightning migration plan', 'LEX readiness check', 'why are some users still on Classic', 'turning on Lightning for everyone'. NOT for individual asset migrations like a single VF page (use lwc/visualforce-to-lwc-migration), a single JavaScript button (use admin/custom-button-to-action-migration), or Knowledge article migration (use admin/knowledge-classic-to-lightning) — this skill orchestrates the program. NOT for Lightning App Builder page design (use admin/lightning-app-builder-advanced).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.