Low readiness in a business unit (assessed pre-go-live, likely in Deploy) requires targeted intervention.
Option B is correct because a workshop with project management (for alignment), local management (for context), and change agents (for execution) enables a deep dive into root causes and collaborative mitigation planning (e.g., extra training). This multi-stakeholder approach ensures comprehensive understanding and action. Option A is too narrow-change agents alone lack the authority or full perspective. Option C excludes local input, limiting effectiveness. Option D involves the sponsor, which is overkill for an operational issue, and users may not strategize solutions. SAP OCM favors inclusive, practical responses.
"Address low readiness through workshops with project management, local leaders, and change agents to analyze results and plan targeted mitigation" (SAP Activate, Business Readiness Assessment Follow-Up).

A high-level change impact analysis (CIA) in SAP OCM gathers broad insights early on. Option C is correct because interviews and workshops with stakeholders (e.g., business leads) provide a comprehensive view of impacts across units. Option A is incorrect-surveys are too narrow and project-team focused. Option B is part of detailed CIA, not high-level. Option D is a follow-up, not the method itself. SAP emphasizes stakeholder engagement for high-level CIA.
"Conduct high-level change impact analysis through stakeholder interviews and workshops to assess broad impacts" (SAP Activate, OCM Workstream, Prepare Phase).

The initial change plan, developed in the SAP Activate Prepare phase, sets the OCM roadmap. Option C is correct because considering interdependencies with project milestones (e.g., aligning training with system testing in Realize) ensures synchronization-e.g., if go-live shifts, communication must adjust, preventing misaligned efforts. This integration is vital in SAP Activate, where OCM supports technical delivery. For instance, stakeholder workshops might be timed before fit-to-standard sessions to prepare users, showing how OCM tasks hinge on project progress.
Option A is incorrect-using a different tool (e.g., separate software) risks silos and confusion, not visibility; alignment with the project plan (e.g., same Gantt chart) is standard. Option B is incorrect-waiting for full details contradicts agile principles; the initial plan is high-level and refined later (Explore/Realize), as early info is often incomplete. Option D is incorrect; while stakeholder alignment is valuable, it's a follow-up to ensure execution, not the development process, which focuses on planning first. SAP OCM prioritizes integration over isolation.
"Develop the initial change plan by considering interdependencies with project milestones, ensuring OCM activities synchronize with the overall implementation" (SAP Activate, Change Plan Development).

Skipping the detailed CIA (Explore/Realize phases) in SAP OCM has significant consequences. Option C is correct because underestimating impacts (e.g., process changes, user resistance) leads to inadequate preparation, risking adoption failure. Option D is correct as missing detailed insights (e.g., specific process or role changes) hampers transition planning, leaving gaps in training or communication.
Option A is incorrect-team motivation isn't directly tied to CIA; it's more about leadership and recognition.
Option B is incorrect; the change story relies on high-level insights, not detailed CIA, though it might be refined later. SAP OCM stresses detailed CIA for precise transition management.
"Omitting detailed CIA risks underestimating impacts and missing critical transition planning data, jeopardizing project success" (SAP Activate, OCM Workstream, CIA Importance).

A reluctant change agent at a kick-off meeting poses a challenge, and the change manager must respond constructively. Option B is correct because a bilateral discussion post-meeting-e.g., asking "What's your concern?"-allows the change manager to understand the reluctance (e.g., workload, disinterest) privately, avoiding public confrontation and tailoring a solution (e.g., support, reassignment). This respects the agent's feelings while maintaining network morale.
Option A is incorrect-asking for a substitute shifts responsibility to the agent, potentially alienating him and disrupting the meeting. Option C is incorrect; convincing him on the spot risks resistance or resentment, undermining his effectiveness. Option D is incorrect-ejecting him is harsh, damages trust, and weakens the network's start. SAP OCM favors discreet, empathetic handling of such issues.
"Address a reluctant change agent's concerns bilaterally after the meeting to resolve issues constructively and preserve network cohesion" (SAP Activate, Change Network Management).