Personas in SAP OCM personalize communication, and their development requires balance and input. Option A is correct because the right detail level—e.g., “Finance User, 35, cautious, needs process clarity”—avoids being too specific (e.g., daily tasks) or too vague (e.g., “employee”), ensuring usability without losing focus. Option B is correct as involving target group reps (e.g., a key user) ensures accuracy—e.g., they might note “we need system tips,” shaping a persona’s needs realistically.

Option C is incorrect—employee reps (e.g., works council) focus on rights, not persona details; alignment isn’t needed. Option D is incorrect; using a real person risks bias or privacy issues—personas are composites, not copies. SAP OCM stresses relevance and collaboration in persona creation.

“Develop personas with balanced detail and target group input to ensure they reflect stakeholder needs accurately” (SAP OCM Framework, Persona Creation Guidelines).