This core concept refers to how change is explored with business stakeholders by utilizing elicitation techniques to identify change characteristics and any concerns that a stakeholder may have about the change. 

Let's look at an example to bring this concept around change to life:

Let's say you have been assigned as a business analyst on a project where the goal is to merge two different general ledger software systems utilized by the company you are currently working for. The project is the result of a merger that happened two years ago, and since then the company has been running two general ledger systems with two different finance teams. This is causing a lot of duplication of effort and finance-related reporting errors. 

In a real-life business analysis scenario, your role is to elicit the requirements for a single general ledger solution by running requirements elicitation workshops with the key stakeholders from both finance teams. You capture not only the main requirements, which must be met by the new general ledger solution but also the host of concerns raised by these stakeholders as a result of this change.

This example illustrates how the core concept of change is implemented in the Elicitation and Collaboration Knowledge Area.