Change agents in SAP OCM are key employees who support adoption within their units, and motivation is critical to their effectiveness in a cloud project’s change network. Option A is correct because fostering visibility—e.g., being recognized by leadership during a townhall—boosts their professional profile, making their role rewarding. Imagine an agent praised for rallying their team; this public acknowledgment drives engagement. Option B is correct as peer exchange across units (e.g., in network meetings) offers collaboration and learning—e.g., a sales agent sharing tips with a finance agent—building a sense of community and value. Option E is correct because looking behind the scenes of a transformation (e.g., understanding why cloud standardization was chosen) satisfies curiosity and gives agents a privileged perspective, enhancing their investment in the project.

Option C is incorrect—designing business processes is typically a task for process owners or consultants during fit-to-standard workshops (Explore phase), not change agents, who focus on communication and support, not process creation. Option D is also incorrect; while skill development (e.g., project management) might occur incidentally, it’s not a primary motivator or structured outcome for agents, who are selected for influence, not training. SAP OCM emphasizes intrinsic and social motivators like visibility, connection, and insight to sustain agent enthusiasm, aligning with their role as grassroots advocates.

“Motivate change agents with opportunities for visibility, peer exchange, and insight into the transformation to maintain their active engagement in the change network” (SAP Activate Methodology, Change Network Motivation Strategies).

Assessing communication needs ensures effective messaging in SAP OCM. Option C is correct because it prevents under- or over-communication, maintaining engagement without overwhelming stakeholders. Option D is correct as tailoring information (e.g., by role or impact) increases relevance and adoption. Option A is incorrect—stakeholder identification precedes communication planning, not vice versa. Option B is also incorrect; change impacts are assessed separately, not primarily through communication needs.

Extract from SAP OCM Concepts: SAP OCM stresses tailored communication to avoid deficits or overload (SAP OCM Framework, Communication Dimension).

Resistance in SAP cloud projects often stems from perceived risks. Option A is correct—data privacy/security concerns are common due to cloud hosting. Option B is correct; users resist if standard processes seem inadequate compared to legacy systems. Option C is correct as cloud solutions reduce local control, sparking resistance. Option D is incorrect—cloud typically lowers maintenance costs, not increases them. Option E is incorrect; works council doubts are situational, not a typical cause. SAP OCM identifies these as key resistance drivers to address.

“Resistance often arises from concerns over data security, process fit, and loss of control in cloud transitions” (SAP OCM Framework, Resistance Management).