A lot of standard statistical practice — t-tests, the F-tests behind ANOVA, many regression standard errors — leans on large-sample approximations (the Central Limit Theorem and its relatives) to justify treating a p-value or confidence interval as roughly correct. With a sample of 15 or 20, those approximations can be shaky. And yet plenty of real work — pilot studies, research on rare populations, early-stage program evaluations — is stuck at exactly that sample size, with no realistic path to more data before a decision has to get made.
The prior isn't magic. With very little data, a result can be more sensitive to the prior than researchers expect, which makes a sensitivity analysis — does the conclusion hold across a range of reasonable priors, not just your favorite one — essential rather than optional for small-N Bayesian work. A badly chosen or overly strong prior can produce a misleading, "wants to be true" result just as easily as p-hacking can on the frequentist side. The honesty comes from being explicit about the assumptions and testing them, not from the word "Bayesian" itself.
It's also worth planning for the audience: a reviewer or committee member unfamiliar with Bayesian methods will need the model, the prior, and the reasoning behind both explained plainly. That's part of making the analysis defensible, not optional extra labor.
If you're weighing a Bayesian approach for a small-sample study, this is exactly the kind of design decision worth talking through before you commit to a model.
One email whenever we publish something new. No spam, unsubscribe anytime.
{{ subscribeErrorMsg }}