This core concept refers to how stakeholders relate to the requirements and designs produced by business analysts.

Let's look at an example to bring this concept around stakeholders into the real world:

Let's now consider an example of two different types of stakeholder groups. The first stakeholder group is a group of product managers who have been closely involved in the requirements elicitation workshops you recently conducted. The second stakeholder group consists of the internal sales team, who have not been closely involved with the requirements and design work at all. It is important that you present the requirements and designs in a different way for each of these two groups. The product managers would be interested in the detailed requirements they have provided and, therefore, you could provide them with comprehensive requirements documentation using models and designs that they can understand and relate to. 

With the sales managers' group, it is more suitable to present the main new features of the planned products in a summary. It might also work well to use a prototype-based format to ensure the sales managers can relate to the new products because they may not have been involved in the detailed requirements elicitation. 

Therefore, it is important to realize during the Requirements Analysis and Design Definition that stakeholders relate to business analysis information in different ways.