A pulse check in SAP OCM is a quick, targeted survey to gauge stakeholder sentiment (e.g., readiness, adoption) at key project points, often in Deploy or Run phases. After agreeing on objectives (e.g., assess go-live confidence), focus topics (e.g., training effectiveness), target groups (e.g., key users), and principles (e.g., anonymity), the next steps operationalize it. Option B is correct because involving employee representatives (e.g., works council) is mandatory in some regions (e.g., Germany) due to legal requirements around employee data collection. This ensures compliance—e.g., if surveying a warehouse team, the works council might need to approve questions to protect worker rights, avoiding legal risks that could halt the process. Option C iscorrect as developing questions (e.g., “Do you feel prepared for the new system?”) and preparing the questionnaire in a survey platform (e.g., Qualtrics) translates objectives into actionable data collection. This step is critical—without questions, there’s no pulse check; a poorly designed survey (e.g., vague queries) yields useless results, while a platform ensures efficient distribution and analysis.

Option A is incorrect—planning survey waves for the entire project assumes multiple checks, but a pulse check is a single, focused snapshot; ongoing planning happens later if needed. Option D is incorrect; informing the steering committee about the schedule is a courtesy, not a “must” step—execution precedes reporting. SAP OCM stresses compliance and question design as immediate priorities post-agreement.

“After defining pulse check parameters, involve employee representatives for legal compliance where required, and develop questions with a survey platform to enable effective execution” (SAP Activate Methodology, OCM Workstream, Pulse Check Setup).