In the context of business analysis, elicitation is the practice of collecting information from stakeholders and other sources. Observation is a key elicitation technique where the business analyst (BA) actively watches how users interact with a system or how processes are carried out. This technique allows the BA to gather insights that might not be captured through direct inquiries, as people may not be aware of their own work habits or may not communicate them effectively. Observation can be particularly useful for identifying discrepancies between what people say they do and what they actually do, leading to a more accurate understanding of the current state and requirements.

Create: solution components are assembled, constructed, or developed by experts as a direct response to a set of requirements.

A business analyst (BA) aims to improve the efficiency and effectiveness of business operations. Simplifying the work people perform can lead to streamlined processes, reduced errors, and increased productivity. This approach aligns with the core objectives of business analysis, which include understanding and defining requirements, analyzing business processes, and recommending solutions that deliver value to stakeholders. Simplification often involves removing unnecessary steps, automating tasks, and optimizing workflows, which are key activities in business process improvement. Reference: The BABOK Guide outlines the importance of simplifying processes as part of the requirements analysis and design definition. It emphasizes the role of the BA in identifying areas where complexity can be reduced to improve business operations. Additionally, the Business Analysis Learning documents highlight the significance of process simplification in achieving operational excellence and delivering business value.