Problem definition turns a received business question into a precise statement of the real issue an analysis should address. A simple request may describe only a symptom: Tuesday patient waiting times could point to planning, budgeting, or resource-allocation concerns. section 1.2.1
Build a stronger starting point by:
- Asking what real problem sits behind the requested metric. section 1.2.1
- Keeping the final decision maker responsible for defining the analysis scope. section 1.2.1
- Using generative AI to suggest business contexts without replacing stakeholder judgment. section 1.2.1
From metric to problem
“What is the average waiting time for patients on Tuesdays?” may be a symptom rather than the true problem. Investigate whether the underlying concern involves planning, budgeting, or resource allocation before choosing the analysis. section 1.2.1
Figure 1.1 Recommended generative AI–supported data analysis flow
Use the analysis flow to move from an initial question toward decision-enabling conclusions while combining human judgment with generative AI. section 1.2.1





