Policy relevance of causal quantities in networks

This paper argues that while many common causal estimands in network settings fail to simultaneously offer interpretable summaries of unit-level effects and support optimal policy choice due to the mismatch between homogeneous exposure assumptions and heterogeneous realities, the expected average outcome serves as a superior estimand that fulfills both criteria.

Sahil Loomba, Dean Eckles

Published 2026-03-10
📖 5 min read🧠 Deep dive

Imagine you are the mayor of a town, and you want to decide whether to launch a new public health campaign (like a free flu shot or a new recycling program).

In a simple world, you just look at the people who got the shot and compare them to those who didn't. If the vaccinated group is healthier, you give the shot to everyone. This is the standard way scientists measure "cause and effect."

But here's the problem: People don't live in bubbles. If your neighbor gets the flu shot, you are less likely to get the flu, even if you didn't get one. This is called interference or spillover. Your outcome depends not just on your own treatment, but on what your neighbors do.

This paper argues that when we have these "network effects," most of the statistical tools researchers use to measure success are actually misleading guides for policy. They might tell you what happened, but they won't tell you what to do next.

Here is the breakdown using a simple analogy: The "Party Planner" Dilemma.

The Two Ways to Measure a Party's Success

Imagine you are planning a party. You want to know: "How happy will the guests be?"

Method A: The "Local Vibe" Check (What researchers usually do)

You ask every guest: "How happy are you based on how many of your friends are here?"

  • You calculate the average happiness of guests who have 0 friends at the party.
  • You calculate the average happiness of guests who have 1 friend at the party.
  • You calculate the average happiness of guests who have 2+ friends at the party.

The Trap: This tells you that "Guests with 1 friend are the happiest."
The Policy Failure: You now think, "Great! I should invite guests until everyone has exactly one friend."
The Reality: In a real network (like a town or a social media graph), you often cannot arrange the party so that everyone has exactly one friend. Some people will inevitably have 0, some will have 3, and some will have 5.
Because you only looked at the "Local Vibe" (Method A), you don't know what the total happiness of the whole party will be under a realistic invitation list. You might invite 50% of the town, thinking it's perfect, but end up with a chaotic mix of lonely people and overcrowded groups, resulting in a terrible party.

Method B: The "Total Party Score" (What the authors suggest)

Instead of asking "How happy are people with X friends?", you ask: "If I invite 50% of the town randomly, what is the total average happiness of the entire party?"

You simulate the whole party, look at the final result, and then try a different percentage (say, 60%) and see the new total result.

The Benefit: This number (called the Expected Average Outcome or EAO) tells you exactly what will happen if you choose a specific policy. It doesn't matter if the distribution of friends is messy; it just tells you the bottom line: "If we do Policy X, the town's total well-being will be Y."

The Core Argument

The authors, Sahil Loomba and Dean Eckles, argue that the scientific community has been obsessed with Method A (the "Local Vibe" or AFEO).

  • Why they like it: It feels very "scientific" and causal. It isolates specific effects (e.g., "Having one treated neighbor causes a 5% boost").
  • Why it fails for policy: It assumes you can control the environment perfectly to create those specific conditions. In the real world, you can't force everyone to have exactly one treated neighbor. So, these numbers are often useless for deciding which policy to actually implement.

They argue we should switch to Method B (the EAO).

  • Why it works: It averages over both the people and the random chance of who gets treated. It answers the question the decision-maker actually cares about: "Which policy makes the whole population better off?"
  • The Twist: Even though Method B is less "pure" in terms of isolating specific causal mechanisms, it is the only number that is guaranteed to help you pick the best policy, especially when you care about the total well-being of the group (utilitarian welfare).

The "Map" Metaphor

Think of the network of people as a city map.

  • Method A gives you a detailed report on every single street corner: "Corner A has 2 potholes, Corner B has 1."
  • Method B gives you a traffic report: "If we send 10% of the cars down Main Street, the average commute time for the whole city will be 20 minutes."

If you are a city planner trying to reduce traffic, the street-corner report (Method A) is interesting, but it doesn't tell you how to set the traffic lights to minimize the total commute time. You need the traffic report (Method B).

The Takeaway

  1. Stop getting distracted by the details: Just because a statistical number sounds like a precise "causal effect" (like "the effect of having one treated neighbor") doesn't mean it helps you make a decision.
  2. Focus on the bottom line: If you want to know which policy to choose, you need to estimate the Expected Average Outcome (EAO). This is the average result you get if you run the whole policy on the whole population.
  3. The "Double Average": The authors show that if you average the results correctly (averaging over people and over the randomness of the policy), you get a number that is both easy to interpret and perfectly suited for making decisions.

In short: Don't try to optimize for a hypothetical scenario where everyone has the exact same number of treated neighbors. Instead, calculate the average outcome of the messy, real-world policies you can actually implement. That is the only number that will save you from making a bad decision.