This element is about considering the level of detail that is required when you describe the requirements to stakeholders. In some types of projects, the requirements may well be understood conceptually and the business analyst doesn’t need to delve into a high level of detail when describing the requirements. However, it may also be that the stakeholder group really needs to review the requirements in a high level of detail to have comfort and confidence that the necessary complexities of the requirements have been documented and understood. Therefore, when planning the level of abstraction, the business analyst should consider the stakeholders' needs and plan for them accordingly. 

An example of planning for a level of abstraction could be when you as the business analyst are working on a high profile, high risk, and complex area of the business and the stakeholders are concerned that they must demonstrate in-depth analysis and an understanding of the specific subject area prior to proceeding to the next stage of the project. In this type of project or environment, the business analyst should plan to manage the business analysis information in a way that allows for detailed analysis and design activities to take place.