If the customer constantly changes priorities, it is important for the systems analyst to officially record all changes, clarify the reasons for adjustments, and identify the true business goals. It is recommended to use transparent requirements management mechanisms (for example, a requirements register with a change history) and to initiate regular meetings for alignment and validation of priorities. If necessary, stakeholders should be involved to assess the impact of changes on project timelines and costs, as well as to document risks. This approach helps minimize chaos and maintain process manageability.