Business Analytics

Business Analytics — From Data to Defensible Action

A decision-first course in descriptive, predictive and prescriptive analytics

Business Analytics — From Data to Defensible Action

Business analytics is not the production of dashboards or model scores. It is a disciplined chain:

decisionmeasurementdescriptionpredictionactionfeedback.\text{decision} \rightarrow \text{measurement} \rightarrow \text{description} \rightarrow \text{prediction} \rightarrow \text{action} \rightarrow \text{feedback}.

This course asks one question at every step: what decision becomes better, for whom, and how will we know?

The running case: HarborMart

HarborMart is a fictional UK omnichannel grocer. Customers browse online, order for delivery or collection, redeem promotions and sometimes stop buying. Stores replenish perishable and non-perishable products, schedule pickers and drivers, and promise delivery windows.

Business concernAnalytic objectPossible action
late deliveriesprobability an accepted order misses its windowchange capacity or promise rules
stockoutsdemand distribution by product–store–daychange replenishment quantity
promotion wasteincremental contribution caused by an offertarget, redesign or stop the offer
customer losscalibrated probability of inactivityintervene only when treatment is worthwhile
queue congestionwaiting-time distribution by houralter staffing or appointment capacity

All HarborMart records and amounts are synthetic. Real organisations and studies are explicitly labelled.

Learning outcomes

By the end, you should be able to:

  1. turn an ambiguous request into a decision, unit of analysis, target, horizon, constraints and loss function;
  2. audit data grain, timestamps, missingness, joins, denominators and lineage before calculation;
  3. describe distributions, cohorts, funnels and KPIs without hiding uncertainty or subgroup differences;
  4. validate regression, forecasting and classification models against decision-relevant baselines without leakage;
  5. convert calibrated predictions into thresholds, allocations, inventory, staffing or pricing decisions;
  6. distinguish association, prediction, causal effect and optimisation;
  7. evaluate fairness, privacy, security, human review and failure recovery across an analytic system;
  8. present a recommendation that another analyst can reproduce and a decision owner can contest.

These outcomes suit advanced undergraduates and taught postgraduates. Graduate extensions add formal decision theory, causal identification, robust optimisation and deployment critique.

Preparation

You need percentages, algebra, probability, confidence intervals and basic Python. Prior machine learning or optimisation is not required.

Ten-minute readiness check
  1. Sales rise from £100,000 to £120,000. Is the growth rate 20 percentage points?
  2. A churn model is 95% accurate when only 3% of customers churn. Is it useful?
  3. A forecast is made on Monday using a field updated on Wednesday. What failed?
  4. A promotion is associated with larger baskets. Does that prove the promotion caused the increase?
  5. A model predicts demand perfectly. Can inventory be ordered without knowing holding and shortage costs?

Answers: no, it is 20%; not necessarily—a no-churn rule is already 97% accurate; temporal leakage; no, targeting and selection may confound the comparison; no, prediction does not specify the action or objective.

Course route

ModuleCentral questionMain deliverable
0. Decision and data foundationsWhat decision, population and evidence are we analysing?analysis contract and data audit
1. Descriptive analyticsWhat happened, to whom and with what uncertainty?diagnostic brief and decision display
2. Predictive analyticsWhat can be forecast at the decision time?validated score or forecast
3. Prescriptive analyticsWhich feasible action has the best expected consequence?policy, allocation or schedule
4. Deployment and governanceWill the decision system remain useful, safe and accountable?monitoring and control plan
CapstoneCan the entire chain survive an audit?executive decision memo plus technical appendix
Appendix and revision toolsWhich formula, pitfall or source supports the decision?revision map and evidence trail

The analytics contract

Complete this before opening a modelling library:

FieldHarborMart delivery example
decision ownerregional fulfilment manager
decisionaccept, re-promise or reroute an order
decision timeimmediately before checkout confirmation
unitone proposed order–delivery window
targetdelivered after the promised end time
horizonsame-day operational outcome
available informationbasket, store, slot, distance and capacity known at checkout
objectivecontribution after delivery and service-failure costs
constraintspicker hours, driver routes, food safety and customer commitments
baselineexisting capacity rule
review rulehuman override for disruptions; log reason and outcome

A model without this contract may be statistically correct and operationally unusable.

Four claims that must not be merged

ClaimDefensible exampleEvidence required
descriptive“Late-delivery rate was 8.2% last month.”defined denominator and complete period
predictive“This order has a 0.31 late-delivery risk.”time-valid out-of-sample calibration
causal“Adding one picker reduces lateness by 2 points.”credible counterfactual design
prescriptive“Add a picker from 17:00 to 20:00.”effects, costs, constraints and alternatives

Prediction can rank risks without identifying what intervention will work. Causal evidence can estimate an effect without selecting a feasible schedule. Optimisation can return a precise answer to a badly specified objective.

A 12-week teaching route

WeekPreparationWorkshop output
1decision framingone-page analytics contract
2data grain, time and lineagejoin and leakage audit
3distributions and robust summariesdiagnostic data profile
4KPIs, cohorts and funnelsmetric tree with denominator checks
5visual evidence and uncertaintyone decision display and critique
6validation and baselinestime-respecting evaluation plan
7regression and forecastingbenchmark comparison
8classification and calibrationprobability audit and threshold table
9trees, ensembles and driftmodel card and monitoring triggers
10optimisation, inventory and queuesfeasible policy with sensitivity analysis
11experiments and causal targetingexperiment or identification design
12deployment and capstone defencedecision memo, rollback rule and oral defence

Suggested workload is 90 minutes of preparation, two hours of workshop activity and 90 minutes of follow-up per week. Every interactive cell has a static worked example, so students can participate without running code. Text alternatives accompany diagrams and colour is never the only carrier of meaning.

Assessment alignment

The following is a teaching template, not an institutional grading rule:

TaskSuggested shareEvidence assessed
data and metric audit20%grain, timestamps, joins, denominator, uncertainty
predictive notebook25%baseline, split, calibration, subgroup error, reproducibility
prescriptive case25%objective, constraints, sensitivity and implementation
integrated capstone30%complete decision chain, communication and governance

For postgraduate work, require an explicit identification argument, robustness analysis and comparison between statistical loss and decision regret.

Current evidence window

The reading map was checked on 1 August 2026. Three current boundaries matter:

  • NIST’s voluntary AI Risk Management Framework remains a useful govern–map–measure–manage structure; NIST also notes that version 1.0 is being revised.
  • The EU framework changed days before this course check: Regulation (EU) 2026/1744 amended the AI Act, including implementation timelines. Legal conclusions must therefore be dated and checked, not copied from an old slide.
  • Current organisational evidence shows analytics as a system problem: Walmart’s fiscal-2026 10-K links AI, automation and supply-chain investment, while Airbnb’s Chronon feature platform emphasises lineage, temporal correctness and training–serving consistency.

The reading and evidence map separates standards, scholarly results, organisational cases and emerging work. It is selective teaching evidence, not a systematic review.

Study discipline

For every chapter, produce four lines:

  1. claim: what is being asserted;
  2. calculation: how the number was produced;
  3. assumption: what must hold;
  4. decision consequence: what changes if the claim is wrong.

Start with decision framing, or use the formula and decision map when revising.

Copyright © 2026