← Latest papers
📊 statistics

Untangling Sample and Population Level Estimands in Bayesian Causal Inference

This paper clarifies the critical distinctions between sample and population-level causal estimands in Bayesian inference to prevent common implementation errors, demonstrating through four detailed Stan examples how to correctly apply first-principles thinking and Bayes' theorem across identification, modeling, and computation.

Original authors: Arman Oganisian

Published 2026-03-03
📖 6 min read🧠 Deep dive

Original authors: Arman Oganisian

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Idea: The "Who" Matters

Imagine you are a doctor trying to figure out if a new medicine works. You have a group of patients in your clinic (your Sample). You want to know two things:

  1. The Specifics: "How does this drug work for these specific 50 people sitting in my waiting room right now?"
  2. The General Rule: "How does this drug work for all people in the world who might have this condition?"

The paper argues that many researchers are accidentally mixing these two questions up. They think they are answering the "General Rule" question, but they are actually only answering the "Specifics" question. This leads to wrong conclusions and overconfident predictions.

The author, Arman Oganisian, says: "Stop guessing. Be precise about who you are talking about."


The Core Confusion: The "Missing Puzzle Piece"

To understand why this is hard, imagine a puzzle.

  • The Factual Piece: You see what happened to a patient who took the drug. (We have this piece).
  • The Counterfactual Piece: You don't see what would have happened to that same patient if they had taken the sugar pill instead. (This piece is missing).

In statistics, we call this missing piece the Counterfactual.

  • Sample-Level Inference (The "Who's in the Room" approach): You want to know the average effect for the specific people you have. To do this, you have to guess (impute) the missing puzzle piece for every single person in your room. You have to imagine, "If Person A took the pill, they got better. But what if they took the sugar pill? Would they have gotten better? Worse?"

    • The Trap: To guess this, you have to make a wild assumption about how the "Pill World" and the "Sugar Pill World" are connected. The paper calls this a "Cross-World Assumption." It's like assuming that if you jumped off a cliff in one universe, you would land in a specific spot in a parallel universe. It's impossible to prove, but you have to assume it to do the math.
  • Population-Level Inference (The "General Rule" approach): You want to know the average effect for the whole world. You don't care about the specific missing piece for Person A. You only care about the average shape of the puzzle pieces for the whole population.

    • The Benefit: You don't need to guess the missing piece for every single person. You just need to understand the general rules of the population. You can ignore the "Cross-World" connection because you are averaging it out.

The Four Main Mistakes People Make

The paper highlights four ways people get tripped up:

1. The "One Size Fits All" Mistake (Interpretation)

  • Analogy: Imagine you measure the height of 10 specific students in a classroom.
    • Sample Effect: "The average height of these 10 kids is 5'4"."
    • Population Effect: "The average height of all kids in the city is 5'2"."
  • The Error: If you calculate the average of your 10 kids but claim it represents the whole city, you might be wrong. The paper shows that the "uncertainty" (how much you might be wrong) is totally different for the 10 kids vs. the whole city. The city estimate is usually fuzzier because the city is bigger and more diverse.

2. The "Magic Assumption" Mistake (Cross-World Modeling)

  • Analogy: To guess what Person A would have done if they took the sugar pill, you have to assume a magical link between their "Drug Self" and their "Sugar Self."
  • The Error: For the "Specifics" (Sample), you must make this magical assumption. For the "General Rule" (Population), you usually don't have to. Many researchers try to calculate the "General Rule" but accidentally use the "Magical Assumption" meant for the "Specifics." This makes their results look more certain than they really are.

3. The "Blind Spot" Mistake (Uncertainty)

  • Analogy: If you guess the missing puzzle piece for one person, you are very unsure. If you guess the average for a million people, the errors cancel out, and you are more sure.
  • The Error: If you treat the "Specifics" (which are very uncertain) as if they are the "General Rule" (which should be more certain), you will draw the wrong conclusions. Your "Confidence Interval" (your safety net) will be too narrow, and you might think you know more than you do.

4. The "Shortcut" Mistake (Computation)

  • Analogy: Imagine you want to know the average weight of all apples in a warehouse.
    • The Right Way (Population): You take a few samples, build a model of the warehouse, and simulate the average weight of new imaginary apples based on that model.
    • The Wrong Way (Sample/Shortcut): You just take the 50 apples you have, weigh them, and say, "This is the average for the whole warehouse."
  • The Error: The paper critiques a popular method (the Bayesian G-Formula) where researchers take their specific sample, simulate new outcomes for those same people, and call it a "Population Average." It's not. It's just a fancy way of describing the specific people you already have.

The "Stan" Code and the "Black Box"

The author uses a computer program called Stan to show exactly how to do the math correctly.

  • The Old Way: Researchers would put the missing puzzle pieces (counterfactuals) into a "black box" at the end of the code, pretending they were just numbers to be averaged.
  • The New Way: The author says, "If you want to know about the specific people, you must declare those missing pieces as unknown variables right at the start of the code." If you want to know about the population, you must integrate them out (mathematically remove them) and focus only on the population rules.

The "Recipe" for Success

The paper ends with a simple recipe for anyone doing this kind of research:

  1. Ask "Who?": Before you write a single line of code, ask: "Am I trying to learn about these specific people or everyone like them?"
  2. Check the Ingredients:
    • If it's Specific People: You must model the missing pieces for everyone. Be ready to make "Cross-World" assumptions (and admit they are assumptions).
    • If it's Everyone: You don't need to guess the missing pieces for individuals. You just need to model the population distribution.
  3. Follow the Math: Don't take shortcuts. If you want the population average, don't just average the specific people you have. Simulate new people based on your model.

Summary

Think of this paper as a warning label on a complex machine. It says: "Don't confuse the specific parts you are holding with the whole machine they came from."

If you want to know how a machine works for everyone, don't just tinker with the one you have in your hand. Build a model of the factory that made it. If you mix them up, your machine might work for you, but it will explode for everyone else.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →