CAPM Practice: Determine how to conduct stakeholder communication

End users understand how work actually gets done — including informal practices, workarounds, and nuances that managers often don't know. Excluding them leads to systems that don't fit real workflows, driving poor adoption and low user satisfaction.

**Why not A:** End users are absolutely stakeholders in a project. They are the people who will interact with the solution daily, and their input is critical for understanding usability needs, workflow requirements, and acceptance criteria. Excluding them because they are "not stakeholders" reflects a fundamental misunderstanding of stakeholder identification.

**Why not B:** While gathering input from many end users can introduce diverse opinions, this is a benefit rather than a risk. Managing multiple perspectives is a core BA competency, and techniques like surveys, focus groups, and user representatives help synthesize input effectively. The risk of too many opinions is far less severe than the risk of building a solution that users cannot or will not adopt.

**Why not C:** The concern that end users will leak information to competitors is not a legitimate reason to exclude them from requirements activities. Confidentiality concerns can be managed through appropriate agreements and by controlling what information is shared. Excluding end users to prevent leaks sacrifices solution quality for a risk that can be mitigated through other means.