Analytics Thinking & Problem Framing · Lesson 1

What Data Analytics is

Data analytics is the disciplined process of turning raw observations into evidence that supports a decision.

ConceptWorked examplePracticeKnowledge check
Textbook walkthrough

What What Data Analytics is actually means

Data analytics is the disciplined process of turning raw observations into evidence that supports a decision. It includes defining the question, collecting or accessing data, cleaning and reshaping it, analysing patterns, quantifying uncertainty, and communicating a conclusion that is appropriate to the evidence.

What Data Analytics is 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 What Data Analytics is as a mechanism, not a recipe

Treat this as a sequence of observable decisions rather than one opaque command. Stage 1: Start with a decision or stakeholder question, not a chart. Stage 2: Define the unit of analysis and the measures needed. Stage 3: Acquire and validate the data. Final checkpoint: Summarise patterns with tables/statistics/visuals and communicate limitations before recommending action.

Mechanism

Follow the transformation

Start with a decision or stakeholder question, not a chart.

Define the unit of analysis and the measures needed.

Acquire and validate the 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: What happened?
How it works

Trace the mechanism step by step

  1. Start with a decision or stakeholder question, not a chart.
  2. Define the unit of analysis and the measures needed.
  3. Acquire and validate the data.
  4. Explore, clean and transform while preserving an audit trail.
  5. Summarise patterns with tables/statistics/visuals and communicate limitations before recommending action.
Worked demonstration

Make the concept concrete

Demonstration

Text example

Decision: should a retailer adjust weekend staffing?
Data: hourly transactions and queue times.
Process: validate timestamps → summarise by hour/store → compare weekdays/weekends → quantify uncertainty → recommend staffing change.
Expected / illustrative result
Analytics connects raw observations to a decision through cleaning, analysis, interpretation and communication.
Interpret the result.

For What Data Analytics is, 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

DescriptiveWhat happened?
DiagnosticWhy might it have happened?
PredictiveWhat is likely to happen?
PrescriptiveWhat action should be taken under stated assumptions?
Use deliberately

When it is appropriate

Use What Data Analytics is 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 What Data Analytics is. First start with a decision or stakeholder question, not a chart. Then define the unit of analysis and the measures needed. 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 What Data Analytics is, which check provides the strongest evidence that you understand and applied it correctly?

Quick reference

Keep the important distinctions visible

Step 1Start with a decision or stakeholder question, not a chart.
Step 2Define the unit of analysis and the measures needed.
Step 3Acquire and validate the data.
Step 4Explore, clean and transform while preserving an audit trail.
Lesson summary

What to remember

  • Data analytics is the disciplined process of turning raw observations into evidence that supports a decision. It includes defining the question, collecting or accessing data, cleaning and reshaping it, analysing patterns, quantifying uncertainty, and communicating a conclusion that is appropriate to the evidence.
  • Start with a decision or stakeholder question, not a chart.
  • 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.