Skip to content
BiliMind
Roadmap

How to learn statistics

This path assumes you can handle basic algebra and are willing to work with real datasets from the first week. It gets you to the point where you can design a sample, quantify uncertainty, run and defend common tests, and read a regression output without treating it as magic. That takes roughly 140-180 hours, not a weekend.

Hours

140-180 hours

Calendar

about 24 weeks at 6-8 hours a week

Stages

6

Start from

Arithmetic, basic algebra, and comfort with mathematical notation. You do not need calculus for introductory statistics, though many people wrongly believe it is required.

Why the usual order fails

Most statistics courses start with descriptive measures, then probability, then a parade of tests. By the time you meet a p-value, you have no reason to trust it, because you never watched a sample mean move. The subject is not a collection of procedures; it is the study of what happens when you observe part of a population and try to say something about the whole. Sampling error is the central fact. Without it, a t-test is a recipe, a confidence interval is a slogan, and a regression coefficient is a number with no weight. Learn uncertainty first and the tests become consequences, not rules to memorise.

This path reverses the usual order. In week one you take a small dataset, draw repeated samples from it, and watch the distribution of the sample mean form. You do not memorise the central limit theorem; you see it. Most plans have you computing means and standard deviations for two weeks before any uncertainty appears. Here, descriptive statistics arrive only after you know why a summary of a sample is not a summary of the world. Every later stage returns to that idea: a test is a statement about sampling variability, a regression coefficient is an estimate with error, and a model is a claim you can check against data.

The path, in the order it has to be walked.

Each stage assumes the one above it and nothing below it. The check at the foot of each is the point — you are meant to fail it, go back, and try again before moving on.

  1. Sampling and uncertainty

    weeks 1-4

    This stage builds the core intuition that a sample statistic is a random quantity. You simulate sampling from a known population, estimate standard error, and construct bootstrap intervals before any formal test. It sits first because every later method is a way of managing the variability you see here.

    • population vs sample
    • random sampling
    • sampling bias
    • sample mean distribution
    • standard error
    • bootstrap resampling
    • confidence interval interpretation

    You can now: Take a dataset of 100 values, draw 1,000 bootstrap samples, and state a 95% interval for the mean, explaining what the interval does and does not say.

  2. Describing data honestly

    weeks 5-7

    Once you know a sample is uncertain, you can summarise it without overclaiming. This stage covers measures of centre and spread, skew, outliers, and the normal distribution as a model, not a fact. It sits after sampling because summaries are only useful when attached to the sample that produced them.

    • mean vs median
    • variance and standard deviation
    • quartiles and IQR
    • histograms and box plots
    • skewness
    • outliers
    • z-scores
    • normal distribution

    You can now: Given a skewed dataset, choose median and IQR over mean and standard deviation, and justify the choice with a plot and one sentence.

  3. Probability for inference

    weeks 8-10

    Probability supplies the language for uncertainty. You learn rules for combining events, conditional probability, Bayes' theorem, and the common distributions that generate data. It sits here, not first, because probability only matters once you have a question about a sample and a population.

    • probability rules
    • conditional probability
    • independence
    • Bayes' theorem
    • random variables
    • expectation and variance
    • binomial and Poisson distributions

    You can now: Given disease prevalence 1%, test sensitivity 90%, specificity 95%, calculate the probability that a positive result is a true positive.

  4. Estimation and testing

    weeks 11-15

    Here the sampling intuition becomes formal method. You construct confidence intervals for means and proportions, then meet null hypotheses, p-values, and the errors a test can make. It sits after probability because a p-value is a conditional probability, and after sampling because a test is a claim about sampling variability.

    • point estimation
    • confidence intervals for a mean
    • confidence intervals for a proportion
    • null and alternative hypotheses
    • p-value
    • type I and type II errors
    • statistical power
    • two-sample t-test

    You can now: Run a two-sample t-test on two small datasets and report the difference in means with a 95% confidence interval, not just a p-value.

  5. Regression and modelling

    weeks 16-20

    Regression connects variables and lets you estimate effects while holding others constant. You learn to fit a line, interpret coefficients, check residuals, and recognise confounding and interaction. It sits after testing because a regression coefficient is an estimate with a standard error, and every test you ran applies here.

    • simple linear regression
    • least squares
    • interpretation of slope and intercept
    • R-squared
    • residual plots
    • multiple regression
    • confounding
    • logistic regression

    You can now: Fit a simple linear regression to a dataset, check the residuals for curvature or changing spread, and interpret one coefficient in plain language.

  6. Analysis and communication

    weeks 21-24

    The final stage forces you to work with messy, unfamiliar data and report what you can and cannot conclude. You choose methods, check assumptions, and write results with uncertainty intervals. It sits last because everything before it is a tool; here you decide which tool fits and defend that choice.

    • data cleaning
    • exploratory data analysis
    • assumption checking
    • method selection
    • effect sizes
    • confidence intervals in reporting
    • visualisation
    • limitations and caveats

    You can now: Take an unfamiliar dataset, choose an appropriate analysis, and write a one-page summary that includes uncertainty intervals and states what the data cannot tell you.

The hours are fixed. The calendar is yours.

The same path at three speeds, and what actually goes wrong at each.

3 hours a week

At three hours a week, the full path takes about a year. Sessions are far apart, so sampling intuition fades between them and you spend the first twenty minutes relearning. It works only if you protect the time and accept slow progress.

8 hours a week

At eight hours a week, the path takes about five months. That is enough for regular practice and simulation, but regression and communication will feel compressed. Keep a notebook of mistakes, because there is little time to revisit.

20 hours a week

At twenty hours a week, the path takes seven to nine weeks. Fast enough to keep sampling intuition warm, but no room for a bad week. You finish with broad exposure and less depth in regression and reporting.

What goes wrong

Four ways people lose a year on this.

Each of these is appealing for a real reason, which is why they are common. What they cost is the part nobody mentions.

  • Memorising tests before understanding sampling error

    People learn a flowchart: if two groups, use a t-test; if categorical, use chi-square. It feels productive because you can pass exams and run software quickly. The cost is that you cannot defend a test when assumptions break, and you treat p-values as verdicts rather than statements about sampling variability. You end up with a toolbox and no judgement.

  • Treating p < 0.05 as proof of an effect

    A small p-value is appealing because it gives a yes/no answer. People stop there and never report the effect size or confidence interval. The cost is that a trivially small effect can be 'significant' with a large sample, and a real effect can be missed with a small one. You make decisions on a threshold, not on the size of the difference.

  • Skipping simulation and bootstrap

    Formulas for standard error and confidence intervals look faster, so people memorise them and move on. The appeal is speed. The cost is that you never see a sampling distribution form, so you cannot explain why a confidence interval is not a probability statement about the parameter. When a dataset is skewed or small, you have no fallback.

  • Fitting regression models without checking residuals

    Software makes it easy to fit a regression and report coefficients, so people do that first. The appeal is that the output looks authoritative. The cost is that curvature, outliers, or changing spread can invalidate the model, and you will not know. You report a slope as an effect when the data do not support a straight line.

How to know it worked.

Not a syllabus you tick off — six things to attempt. If one of them is still hard, the stage it belongs to is the one to go back to.

  1. Explain why a sample mean varies from sample to sample in one paragraph
  2. Take 30 numbers, draw 100 bootstrap samples, and state a 95% interval for the mean
  3. Given sensitivity 90%, specificity 95%, prevalence 1%, calculate the chance a positive test is true positive
  4. Run a two-sample t-test on two small datasets and report the confidence interval for the difference
  5. Fit a simple linear regression and check the residuals for curvature or changing spread
  6. Analyse an unfamiliar dataset and write a one-page summary with uncertainty and what the data cannot tell you
Questions

Questions about learning statistics.

The five we hear most. The intro film answers most of them in a minute and a half.

how long does it take to learn statistics

It takes about 140-180 hours of focused work, which is roughly 24 weeks at 6-8 hours a week, if you start with basic algebra. That gets you to genuine working competence: designing samples, running and defending common tests, and reading regression output. If you only need to pass a single exam, 40-60 hours can cover the mechanics, but you will not be able to defend your choices.

do i need calculus for statistics

No, you do not need calculus for introductory statistics. Arithmetic, basic algebra, and comfort with notation are enough for sampling, confidence intervals, hypothesis tests, and regression. Calculus becomes necessary only if you go into mathematical statistics or probability theory, where you derive distributions and work with integrals. Many people wrongly delay statistics because they think calculus is a prerequisite.

is statistics harder than calculus

Statistics is not harder in the sense of symbolic manipulation, but it is harder in a different way: you must make judgements under uncertainty and defend them. Calculus has right answers; statistics has intervals, assumptions, and trade-offs. Many people find statistics more difficult because there is no single number to circle at the end of a problem.

can i learn statistics without a teacher

Yes, you can learn statistics without a teacher if you work with real datasets and run simulations, because the feedback comes from the data and the plots. The hard part is interpretation: a p-value or a residual plot can look fine while you misread it. You will need to check your conclusions against worked examples or someone who can spot a wrong interpretation.

what is the difference between probability and statistics

Probability starts with a known model and predicts what data you will see. Statistics starts with data and infers what model might have produced it. The direction of reasoning is reversed. That is why statistics needs sampling distributions and uncertainty: you are going backwards from a sample to a population, and many populations could have produced the same sample.

A path is not a course.

This is the shape of statistics, not the teaching of it. Hand the same path to BiliMind and it writes the lessons onto it — in the form each one calls for, with practice that gets marked and a schedule that bends when your week does. Mapping a course is free and unlimited.

This roadmap was drafted on 18 September 2026 by the same engine that builds BiliMind courses, and reviewed before publishing. Hours are honest estimates for working competence, not for a demo — treat them as a starting point and adjust them against your own first fortnight.

The intro · 1:25