To capture the right quantity and quality of information during requirement gathering, which starting question is essential about data?

• A. Who will work on a particular feature?
• B. When does a particular feature need to be ready?
• C. How will the application handle user errors?
• D. Where is the data used in the application coming from?

Answer: (D)

Starting with where the data used by the application comes from anchors the entire data requirement conversation. Knowing data origins reveals what information actually exists, in what format, and how it will flow through the system. It helps you define which data elements are needed, their data types, validation rules, and any transformations or mappings that must occur. It also points to data quality, ownership, governance, security, and compliance considerations, since different sources bring different constraints and reliability. Once you know the sources, you can determine update frequency, latency, and integration points, which shape the data model and acceptance criteria.

The other questions touch on who works on a feature, timing, or how errors are handled—these are important for project management and user experience, but they don’t establish the actual data requirements and constraints the system must satisfy. Without clarifying data origins first, you risk building around assumptions about data that may not exist or won’t meet quality standards.