A communication needs analysis in SAP OCM identifies what information stakeholders require, when, and how. Option B is correct because interviewing selected business users (e.g., key users from different units) allows the change manager to explore individual needs—such as preferred channels (email vs. meetings) or content (updates vs. training)—and aggregate these into a comprehensive plan. For instance, a finance user might need detailed process updates, while a warehouse user wants quick system tips. This targeted, qualitative approach uncovers nuances that broad methods miss, ensuring tailored communication that drives adoption.

Option A is incorrect—relying only on managers/experts is efficient but risks missing end-user perspectives, leading to top-down assumptions and unmet needs. Option C is vague; “project activity” isn’t a method, and speed/team spirit aren’t primary goals—accuracy is. Option D is impractical—workshops across all units are resource-intensive and may raise expectations without delivering actionable insights, diluting focus. SAP OCM favors user-centric, data-driven methods like interviews for communication planning.

“Conduct a communication needs analysis by interviewing selected business users to gather and aggregate insights, ensuring messages meet specific stakeholder requirements” (SAP OCM Framework, Communication Needs Analysis).