Follow the transformation
Name the stakeholder and decision.
Define the unit of analysis (customer, order, day, device, etc.).
Define each measure with numerator, denominator, time window and inclusion/exclusion rules where relevant.
Analytics Thinking & Problem Framing · Lesson 3
Questions Stakeholders and Decisions
Questions Stakeholders and Decisions is about connecting analysis to a decision.
What Questions Stakeholders and Decisions actually means
Questions Stakeholders and Decisions is about connecting analysis to a decision. Measures quantify something, dimensions describe how observations are grouped, and KPIs select a small set of measures that reflect progress toward an objective.
Questions Stakeholders and Decisions matters because analytics is valuable only when evidence changes or informs a decision. Clear questions, units, metrics and stakeholders prevent technically correct calculations from answering the wrong business problem.
Deeper walkthrough
Read Questions Stakeholders and Decisions as a mechanism, not a recipe
Treat this as a sequence of observable decisions rather than one opaque command. Stage 1: Name the stakeholder and decision. Stage 2: Define the unit of analysis (customer, order, day, device, etc.). Stage 3: Define each measure with numerator, denominator, time window and inclusion/exclusion rules where relevant. Final checkpoint: Check whether the metric can move because of data collection changes rather than real-world change.
Know what would convince you
- Write the decision question, unit of analysis and metric formula in plain language before computing it.
- Reconcile KPI numerators/denominators or grouped totals to source counts for a small slice.
Useful distinctionMeasure: A numeric quantity such as revenue or response time.
Trace the mechanism step by step
- Name the stakeholder and decision.
- Define the unit of analysis (customer, order, day, device, etc.).
- Define each measure with numerator, denominator, time window and inclusion/exclusion rules where relevant.
- Choose dimensions that support meaningful segmentation.
- Check whether the metric can move because of data collection changes rather than real-world change.
Make the concept concrete
Demonstration
Text example
Stakeholder: operations manager.
Decision: where to add staffing next week.
Question: which stores have sustained queue times above target?
Metric: median and 90th-percentile wait time by store/day.
Action threshold: review stores above 8 minutes for 3 consecutive days.Expected / illustrative result
The analysis is anchored to who acts, what decision they make and what evidence changes that action.
Interpret the result.
For Questions Stakeholders and Decisions, connect the displayed result to the specific input and mechanism above; independently verify one value/state change rather than treating successful execution as proof.
Know what this is — and what it is not
MeasureA numeric quantity such as revenue or response time.DimensionA grouping/category such as region, product or channel.KPIA measure deliberately tied to an objective and decision cadence.TargetA desired value or threshold against which a KPI is evaluated.When it is appropriate
Use Questions Stakeholders and Decisions when it connects a clearly framed stakeholder question to measurable evidence and an action or decision.
When to stop or reconsider
Reframe the analysis if the decision, unit of analysis, metric definition, comparison group or time window is still ambiguous; more computation will not repair an undefined question.
Failure modes to recognise
- Starting with a favourite chart/tool before defining the decision and unit of analysis.
- Using an undefined KPI, denominator, cohort or time window and then comparing incomparable numbers.
- Turning association or a descriptive pattern into a causal recommendation without supporting design/evidence.
How to check the result
- Write the decision question, unit of analysis and metric formula in plain language before computing it.
- Reconcile KPI numerators/denominators or grouped totals to source counts for a small slice.
- Test whether the conclusion changes under one reasonable alternative definition or comparison window.
Demonstrate understanding
Try this:
Build a tiny, inspectable example of Questions Stakeholders and Decisions. First name the stakeholder and decision. Then define the unit of analysis (customer, order, day, device, etc.). Write the expected result before running it, and explain one condition that would make the result misleading or invalid.
Write the decision, unit and metric definition first. Use a tiny slice where you can recompute the KPI/table manually and explain what would change the recommendation.
Check reasoning, not memorisation
Before trusting a result from Questions Stakeholders and Decisions, which check provides the strongest evidence that you understand and applied it correctly?
Keep the important distinctions visible
Step 1Name the stakeholder and decision.Step 2Define the unit of analysis (customer, order, day, device, etc.).Step 3Define each measure with numerator, denominator, time window and inclusion/exclusion rules where relevant.Step 4Choose dimensions that support meaningful segmentation.What to remember
- Questions Stakeholders and Decisions is about connecting analysis to a decision. Measures quantify something, dimensions describe how observations are grouped, and KPIs select a small set of measures that reflect progress toward an objective.
- Name the stakeholder and decision.
- Starting with a favourite chart/tool before defining the decision and unit of analysis.
- Write the decision question, unit of analysis and metric formula in plain language before computing it.