Instruction: Explain how you would unpack a dashboard request before turning it into reporting or system work.
Context: Assesses whether the candidate can avoid treating dashboard requests as self-explanatory requirements.
I do not assume a dashboard request is really about visualizations. Usually it is about a decision someone wants to make faster or with more confidence. So I start by asking what question they are trying to answer, what action they expect to take from the dashboard, how often they need it, and what is not working with the information they have now.
Then I clarify audience, grain, and definitions. Is this for executives, managers, or operational users? Do they need trend visibility, case-level detail, alerts, or simple status reporting? I also ask what existing reports already exist, because sometimes the problem is not lack of data. It is low trust, poor design, or unclear metric definitions.
Only after that do I talk about dashboard content. A strong BA should help the stakeholder move from "I need a dashboard" to a clearer statement of the decision, audience, and metrics that matter. Otherwise the team may build a dashboard that looks useful but changes nothing.
"I would ask which charts they want and what fields they want displayed."
easy
easy
easy
easy
easy
easy