Why Quantitative Methods.

1. The premise of the course

Most business decisions are made under uncertainty. A manager rarely knows the exact return on a campaign, the exact probability of a supplier delivering on time, or the exact effect of a price change on demand. Quantitative methods are the discipline of acting responsibly when those exact numbers are not available — by estimating ranges, by stating assumptions explicitly, and by tracking how outcomes update what was believed before.

Students often arrive at a quantitative course expecting algebra-heavy lectures and disconnected formulas. That expectation is wrong. The substantive content of this course is decision-making under uncertainty, with numbers as the medium rather than the message. By Week 15 you should be able to defend a recommendation to a manager with a chart, a model, and an honest statement of what could still be wrong with it.

The aim is not to turn business students into statisticians. It is to make you a credible reader of the analytical work you will be sent in the first five years of your career — pricing studies, A/B test results, demand forecasts, employee surveys, budget sensitivity analyses — and a competent producer of the simpler versions of that work yourself.

2. Where quantitative methods show up in a business degree

Inside the degree, you will meet quantitative methods in marketing analytics, operations, finance, HR analytics, and strategy. Each subject borrows the same toolkit — descriptive statistics, sampling, hypothesis testing, regression, optimisation, simulation — and applies it to its own questions. The toolkit does not change; only the data does.

Outside the degree, the same toolkit shows up under different names: 'business intelligence' on the analytics team, 'experimentation' on the product team, 'pricing science' on the commercial team, 'people analytics' on the HR team. The labels are marketing; the underlying methods are the ones you will learn here.

The practical implication is that what you learn in this course is paid back in every later course and most professional roles. Skipping it as a hurdle subject means later courses become harder than they need to be, and analytical work in your first job becomes intimidating rather than ordinary.

3. The cost of being innumerate as a manager

A manager who cannot read a chart, interpret a confidence interval, or smell a manipulated metric is dependent on whoever produced the analysis. That dependence is not neutral — it is exploitable. A finance analyst who knows the manager will not check the assumptions can quietly steer a decision by choosing the discount rate. A marketing analyst can show a 'lift' that is within the noise of the test. A consultant can present a model whose conclusions are mainly artefacts of the input assumptions.

These are not hypothetical examples. They happen in ordinary corporate life because the people producing the numbers are usually more numerate than the people receiving them. The corrective is not for every manager to become an analyst. It is for every manager to become a credible reader of analysis — someone who can ask the three or four questions that catch most problems.

By the end of this course you should have those three or four questions ready in your head. The questions are not technical. They are: 'What is the sample?' 'What is the comparison?' 'What is the uncertainty?' 'What would change the conclusion?'

4. How this course is structured

Weeks 2–4 cover the descriptive layer — how to characterise data honestly with summary statistics, distributions, and charts. Weeks 5–7 cover probability and sampling — how to think about uncertainty before you ever look at a result. Weeks 8–10 cover statistical inference — hypothesis tests, confidence intervals, and the discipline of comparing groups. Weeks 11–13 cover regression and forecasting — the workhorse methods of business analytics. Weeks 14–15 cover optimisation and simulation, the methods you reach for when prediction alone is not enough.

Each week has a reading like this one, two activities (a Smart Assessment and a Simulation), and a reflection. The reading sets the concept; the activities make you do the move with real data; the reflection makes the habit yours rather than the textbook's. The single best predictor of success in this course is doing the simulations rather than only reading.

By Week 15 you will have produced a small portfolio of analyses — descriptive summaries, hypothesis tests, simple regressions, optimisation problems — that you can show in a job interview as evidence that quantitative work is not abstract for you. The portfolio matters more than the marks.

5. What this course will and will not do

The course will teach you to read and produce the analytical artefacts most common in business: tables, charts, summary statistics, simple regression outputs, A/B test reports, demand forecasts, and small optimisation models. It will give you a working command of Excel as an analytical tool and a basic familiarity with the logic of statistical software (without requiring you to write code).

The course will not turn you into a data scientist or a statistician. It will not cover causal inference at the level of an econometrics course, machine learning at the level of a computer science course, or operations research at the level of an industrial engineering course. Those are specialist careers that build on a quantitative foundation; this course is that foundation.

If your prior maths is rusty — and for many business students it is — the early weeks of this course are designed to recalibrate without leaving you behind. The recalibration phase is real, normal, and not a sign of weakness. By Week 5 the students who put in the recalibration work are usually indistinguishable from those who started ahead.

Advanced practice: future-ready professional judgement

Advanced work in Quantitative Methods for Business requires more than remembering the week's terminology. A future-ready practitioner connects the concept to a decision, checks the evidence behind that decision and names the conditions under which the recommendation would change. This is especially important in professional decision practice, where professional credibility depends on knowing what the evidence can support and what remains uncertain.

The practical standard is to move from explanation to judgement. First, identify the stakeholder who must act. Second, define the evidence needed for a defensible decision. Third, test whether digital or AI-supported tools can improve speed, coverage or pattern recognition without weakening accountability. Fourth, communicate the trade-off in language the stakeholder can use. This sequence turns reading into capability rather than passive familiarity.

The future of this field will reward learners who can work across disciplines. A strong response to why quantitative methods belong in a business degree should consider data quality, inclusion, sustainability, risk and communication, even when those issues are not the headline topic. The best portfolio evidence shows that the learner can make these connections visibly: a chart with interpretation, a memo with assumptions, a prototype with critique or a decision matrix with ethical notes.

Use this week as a rehearsal for professional practice. When the answer seems obvious, ask who benefits, who is exposed to risk, which data is missing and what would happen if the recommendation were scaled. That discipline is what separates a basic course response from advanced work that can survive review, implementation pressure and changing technology.

6. What to take into Week 02

Next week we cover describing data honestly — measures of centre, spread, and shape, and the chart choices that match each.