This core concept really refers to how change is managed in response to when a need is identified. Specifically, in the knowledge area of Business Analysis Planning and Monitoring, the concept of "change" is applied in terms of how the changes that arise from business analysis results will be requested and approved within a specific project or initiative’s context and environment.

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

Let’s say you have just finished completing requirements documentation for a new sales solution and all the stakeholders have signed off your requirements documents. The project is now ready for the design and implementation of the solution. You then receive a phone call from one of the stakeholders, who is asking you to please change the requirements for deleting old customer records. Now, you already have signed off the requirements that state that old customer records must be deleted after two years of accounts being closed. However, the stakeholder wants you to make a change that allows these old customer records to be archived and stored for 10 years. In a real-life business analysis scenario, you will have defined a procedure or approach around how a stakeholder can request changes to requirements and what authorization steps would be involved as part of the Business Analysis Planning and Monitoring activities. So, you can now simply refer to the stakeholder, who is waiting for you to respond on the phone, to the agreed procedure or change request form. Or even better, you can offer to complete the change request for the stakeholder to review and then submit it for approval!

This example illustrates how the core concept of "change" is implemented within the Business Analysis Planning and Monitoring knowledge area.