HumachLearnLearn · explore · apply
Start learning
Analytics Thinking & Problem Framing · Lesson 2

Descriptive Diagnostic Predictive and Prescriptive Analytics

Descriptive, diagnostic, predictive and prescriptive analytics describe four different analytical goals.

ConceptWorked examplePracticeKnowledge check
Textbook walkthrough

What Descriptive Diagnostic Predictive and Prescriptive Analytics actually means

Descriptive, diagnostic, predictive and prescriptive analytics describe four different analytical goals. They are not a maturity ladder that every project must climb; the correct type depends on the decision and on what evidence is available.

Descriptive Diagnostic Predictive and Prescriptive Analytics 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 Descriptive Diagnostic Predictive and Prescriptive Analytics as a mechanism, not a recipe

Treat this as a sequence of observable decisions rather than one opaque command. Stage 1: Descriptive: summarise observed data. Stage 2: Diagnostic: compare segments, time periods or explanatory factors to investigate possible drivers. Stage 3: Predictive: estimate an unknown or future outcome from patterns learned in historical data. Final checkpoint: Keep causal claims separate from predictive association unless the design supports causality.

Mechanism

Follow the transformation

Descriptive: summarise observed data.

Diagnostic: compare segments, time periods or explanatory factors to investigate possible drivers.

Predictive: estimate an unknown or future outcome from patterns learned in historical data.

Evidence

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 distinctionDescriptive: Revenue fell 8% this quarter.
Visual demonstration of Descriptive Diagnostic Predictive and Prescriptive Analytics
Visual demonstration: use the diagram to trace the main objects and state changes involved in Descriptive Diagnostic Predictive and Prescriptive Analytics.
Click a stage to inspect what happens, what changes, and what should be checked before moving on.
Stage 1

Descriptive

Descriptive: summarise observed data. For Descriptive Diagnostic Predictive and Prescriptive Analytics, identify the exact state before this stage, the operation or rule applied here, and the observable state afterwards so the mechanism remains inspectable.

State focus: identify exactly what changed at this stage and what observable evidence confirms that change.
How it works

Trace the mechanism step by step

  1. Descriptive: summarise observed data.
  2. Diagnostic: compare segments, time periods or explanatory factors to investigate possible drivers.
  3. Predictive: estimate an unknown or future outcome from patterns learned in historical data.
  4. Prescriptive: combine predictions, constraints, objectives and assumptions to recommend an action.
  5. Keep causal claims separate from predictive association unless the design supports causality.
Worked demonstration

Make the concept concrete

Demonstration

Text example

Descriptive: “Revenue was $1.2M, down 8%.”
Diagnostic: “Most decline occurred in Region B after product returns increased.”
Predictive: “Next-month demand is estimated at 9,400 ± uncertainty.”
Prescriptive: “Allocate 55% of stock to Region A under cost/service constraints.”
Expected / illustrative result
Each stage answers a different question. Diagnostic patterns do not by themselves prove causes, and prescriptive recommendations require objectives and constraints.
Interpret the result.

For Descriptive Diagnostic Predictive and Prescriptive Analytics, connect the displayed result to the specific input and mechanism above; independently verify one value/state change rather than treating successful execution as proof.

Distinctions & related ideas

Know what this is — and what it is not

DescriptiveRevenue fell 8% this quarter.
DiagnosticThe decline is concentrated in two regions and one product family.
PredictiveA model estimates next-month demand.
PrescriptiveAn optimisation recommends inventory allocations given cost and service constraints.
Use deliberately

When it is appropriate

Use Descriptive Diagnostic Predictive and Prescriptive Analytics when it connects a clearly framed stakeholder question to measurable evidence and an action or decision.

Boundary conditions

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.

Common mistakes

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.
Verification

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.
Hands-on practice

Demonstrate understanding

Try this:

Build a tiny, inspectable example of Descriptive Diagnostic Predictive and Prescriptive Analytics. First descriptive: summarise observed data. Then diagnostic: compare segments, time periods or explanatory factors to investigate possible drivers. 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.
Knowledge check

Check reasoning, not memorisation

Before trusting a result from Descriptive Diagnostic Predictive and Prescriptive Analytics, which check provides the strongest evidence that you understand and applied it correctly?

Quick reference

Keep the important distinctions visible

Step 1Descriptive: summarise observed data.
Step 2Diagnostic: compare segments, time periods or explanatory factors to investigate possible drivers.
Step 3Predictive: estimate an unknown or future outcome from patterns learned in historical data.
Step 4Prescriptive: combine predictions, constraints, objectives and assumptions to recommend an action.
Lesson summary

What to remember

  • Descriptive, diagnostic, predictive and prescriptive analytics describe four different analytical goals. They are not a maturity ladder that every project must climb; the correct type depends on the decision and on what evidence is available.
  • Descriptive: summarise observed data.
  • 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.