Capturing lessons learned in SAP OCM (typically Run phase) improves future projects, and the

process design is key. Option B is correct because a predefined structure (e.g., categories like

planning, execution, adoption) and scope (e.g., OCM-specific issues) ensure all aspects—successes

and failures—are covered systematically. Without this, discussions might miss critical insights, like

overlooked stakeholder engagement flaws. Option E is correct as clear rules (e.g., “no blame”) create

a safe environment, encouraging honest input—e.g., a team member might hesitate to admit a

communication delay if fearing criticism, stunting learning.

Option A is incorrect—confidentiality may limit sharing valuable lessons with the organization,

contradicting SAP’s goal of building capability; transparency (with discretion) is preferred. Option C is

incorrect; focusing only on negatives ignores successes (e.g., effective training), skewing the process

and wasting potential insights, not saving time. Option D is incorrect—a workshop isn’t always best;

surveys or interviews might suit smaller teams or remote setups. SAP OCM advocates flexibility and

constructive design.

“Design lessons learned with a structured scope and clear rules like ‘avoid finger-pointing’ to ensure

comprehensive and open feedback” (SAP Activate, Lessons Learned Process).