SAP cloud implementations introduce significant people-related challenges that change management must mitigate. Option A is correct because the "not-invented-here" syndrome-where users reject external standards (e.g., SAP best practices) in favor of legacy processes-leads to resistance and lack of buy-in, a common barrier in cloud projects due to reduced customization. Option B is correct as users often face stress and frustration when unlearning old habits to adopt new workflows, especially with cloud solutions' standardized processes, which differ from familiar systems. This emotional response requires targeted enablement and support.
Option C is incorrect-users don't typically adapt the cloud solution technically (that's an IT role); their resistance is more about adoption, not technical customization skills. Option D is incorrect; cloud implementations aim to streamline tasks, not add repetitive ones, so boredom isn't a typical challenge- resistance stems from change, not monotony. SAP OCM focuses on overcomingattitudinal and behavioral hurdles to ensure adoption.
"People challenges include resistance from a 'not-invented-here' attitude and stress from unlearning old habits, requiring change management to foster acceptance and adaptation" (SAP OCM Framework, People- Related Challenges).

Effective change communication in SAP projects balances reach and clarity. Option A is correct because a mix of channels (e.g., emails, workshops, videos) ensures broad coverage and suits different preferences.
Option D is correct as a compelling change story articulates the "why" and "what" of the project, fostering buy-in. Option B is incorrect-while overcommunication can overwhelm, the advice to "not overcommunicate" lacks specificity and isn't a proactive strategy. Option C is also incorrect; over-reliance on digital channels may exclude non-digital users and isn't universally effective.
Extract from SAP OCM Concepts: SAP OCM emphasizes a varied communication approach and a strong narrative to drive engagement (SAP OCM Framework).

Preparing for a detailed change impact analysis (CIA) workshop, typically conducted in the SAP Activate Explore or Realize phase, requires careful planning to ensure actionable outcomes. Option A is correct because inviting the right participants-process owners (who understand current workflows), subject matter experts (SMEs, who provide technical/process depth), and key users (who represent end-user perspectives)- ensures a comprehensive assessment of impacts across affected areas. Their diverse insights are critical for identifying specific changes at a granular level, such as how a process shift affects daily tasks or system usage. Without these stakeholders, the workshop risks missing critical details or buy-in, undermining its effectiveness.
Option B is correct because creating a template with relevant business processes broken down to a suitable level (e.g., subprocesses like "order entry" within "order-to-cash") provides a structured framework for discussion. This template might include columns for as-is vs. to-be states, impact severity, and affected roles, enabling participants to systematically evaluate changes. It ensures focus and consistency, preventing the workshop from becoming a free-for-all discussion, and aligns with SAP's methodical approach to CIA.
Option C is incorrect because scheduling individual upfront meetings with all participants is impractical and time-consuming for a detailed CIA, which builds on prior high-level analysis. While some pre-workshop input might be gathered, the workshop itself is the collaborative forum for insights, not pre-meetings. Option D is incorrect because limiting the analysis to one dimension (e.g., only "process") contradicts the holistic nature of a detailed CIA, which assesses multiple dimensions (process, technology, organization, people) to capture the full scope of change. SAP OCM emphasizes stakeholder inclusion and structured tools for detailed CIA preparation.
"Preparation for a detailed change impact analysis workshop involves inviting key stakeholders such as process owners, SMEs, and key users, and providing a structured template of business processes to guide the assessment of impacts across all dimensions" (SAP Activate Methodology, OCM Workstream, Detailed CIA Preparation).

During the Explore phase, fit-to-standard workshops focus on aligning business processes with SAP's best practices, often revealing changes to current ways of working. Option C is correct because managers may resist the cloud standard if it reduces customization or control, a common challenge in this phase. Option A is incorrect-lack of OCM awareness is more typical in the Discover or Prepare phase. Option B is incorrect; user adoption issues emerge post-go-live (Run phase), not in Explore. Option D is also incorrect; go-live readiness concerns arise in the Deploy phase, not Explore.
Extract from SAP OCM Concepts: Resistance to standardization is a key challenge in the Explore phase, requiring targeted stakeholder engagement (SAP Activate, OCM Workstream).