Scope neglect is the failure to adjust judgment or willingness to pay when the scale of the problem changes. People often react similarly to "100 birds at risk" and "10,000 birds at risk" — the emotional and behavioural response does not scale with the number. The same pattern appears for lives, dollars, and impact: doubling the scope often produces far less than double the response. The mental model that would match reality is scope sensitivity: larger problems should command proportionally more attention, money, or effort. Scope neglect is the deviation from that — we underweight magnitude.
The psychological mechanism is limited affective response. We have a rough "this matters" feeling that saturates. One victim is salient; 100 victims are not 100× more salient. Paul Slovic and others showed that donations and policy preferences often fail to scale with the size of the affected population. People may give similar amounts to save 2,000 vs 200,000 lives. Scope neglect is a bug in how we allocate concern across scale.
The strategic implication is twofold. When you are evaluating impact or setting priorities, correct for scope neglect: explicitly ask how the response should scale with size and whether your reaction matches. When you are communicating or fundraising, know that adding zeros often does not add proportionally to engagement. One vivid case can outweigh statistics about thousands. Use that for good (make impact tangible) or guard against it (don't let one story override the aggregate).
Section 2
How to See It
Scope neglect appears when responses fail to scale with magnitude. Look for similar reactions to "10 affected" vs "10,000 affected," or for decisions that would change if the numbers were taken seriously. The diagnostic: would the decision change if we doubled or halved the scope? If not, scope may be neglected.
Business
You're seeing Scope Neglect when a leadership team allocates the same meeting time and urgency to a bug affecting 50 users and one affecting 50,000 users. The larger scope should command more resources, but the emotional pull of "we have a problem" is similar. Correcting for scope means explicitly weighting impact by number affected.
Technology
You're seeing Scope Neglect when a product team prioritises one loud customer's request over data showing that a different issue affects 100× more users. The one vivid voice triggers more response than the aggregate. Scope-sensitive prioritisation would weight by impact × users.
Investing
You're seeing Scope Neglect when an investor or allocator treats a $10M opportunity and a $500M opportunity with similar process and diligence. The potential upside scales with size; the effort to evaluate should scale too. Underweighting scope leads to under-investing in large opportunities or over-spending time on small ones.
Markets
You're seeing Scope Neglect when public or donor response to a crisis is similar whether 200 or 200,000 people are affected. Media and policy attention often follow vividness rather than scale. Understanding scope neglect explains why big problems sometimes get less than proportionally more resources.
Section 3
How to Use It
Decision filter
"When allocating attention, money, or effort across options that differ in scale, ask: am I scaling my response with magnitude? If doubling the scope would not roughly double my response, correct for scope neglect. Use explicit scaling rules (e.g. impact × number affected) so that size is in the formula."
As a founder
Prioritise by scope. A feature that helps 10% of users should usually beat one that helps 0.1%, all else equal. A bug affecting 10,000 DAU should get more weight than one affecting 100. Build scope into your prioritisation: score by reach × impact, not just impact. When a single customer or internal voice dominates, ask: what is the scope of this vs the alternative?
As an investor
Size the opportunity explicitly. A company with a $1B TAM and 10% share potential is different from a $50M TAM with the same share. Don't treat them the same because "both could work." Scope of outcome should influence position size and bar. When you catch yourself giving similar weight to very different scale outcomes, correct for scope neglect.
As a decision-maker
When comparing initiatives, put scope in the numerator. How many people or units are affected? How much value or risk is at stake? Decisions that ignore scope underweight big problems and overweight small ones. Use back-of-envelope scope checks: "If we 10× the number, would our response 10×?" If not, revise.
Common misapplication: Letting one vivid case dominate aggregate data. One story can trigger scope neglect in reverse — overreacting to the single case while underreacting to the thousands. The correction is to require scope-weighted reasoning when the stakes are large.
Second misapplication: Assuming others will scale. When you present numbers, assume your audience will underweight scope. Make magnitude explicit: "This affects 50,000 users" and "That affects 500." Don't rely on the number alone to do the work.
Bezos insisted on customer obsession but also on scale. Amazon's mechanisms — metrics by cohort, impact at scale — force scope into the picture. "What's good for the customer?" is checked against "how many customers?" Decisions that don't scale with scope get questioned. The two-pizza team rule and single-threaded ownership also reduce the chance that one loud voice (small scope) overrides aggregate impact.
Buffett sizes positions by opportunity size and conviction. A small idea never gets a large allocation; a large idea can. That is scope-sensitive capital allocation. He also warns against being swayed by one vivid story (e.g. a single bad experience) when the aggregate data matter. Scope is explicit in his sizing and in his resistance to anecdote over statistics.
Section 6
Visual Explanation
Scope neglect: response (e.g. willingness to pay, attention) does not scale with scope. Ideal: response ∝ scope. Actual: response flattens as scope grows. Correct by making scope explicit in the decision rule.
Section 7
Connected Models
Scope neglect connects to how we perceive magnitude (Weber-Fechner), how we anchor (anchoring), and how we react to vivid vs statistical information. These models either explain scope neglect or help correct it.
Reinforces
Anchoring
Anchoring is the tendency to rely heavily on the first number we see. When scope is presented as "2,000" or "200,000," we may anchor on the first magnitude we process and under-adjust. Scope neglect is the result when the anchor is small or when we don't adjust enough for scale. Both suggest making magnitude explicit and recalculating.
Reinforces
Diminishing [Utility](/mental-models/utility)
Diminishing utility says each additional unit of something (wealth, lives saved) adds less marginal value. Scope neglect is related: we don't scale our response with additional units. The difference: diminishing utility can be rational (e.g. first $1M matters more than the next); scope neglect is the failure to scale at all when we should.
Tension
Availability Heuristic
Availability is using what comes easily to mind. One vivid story is highly available and can dominate; large statistics are less available. The tension: availability pushes us toward the vivid (often small scope); scope-sensitive reasoning pushes us toward the aggregate. Correct by making scope explicit when availability would otherwise dominate.
Tension
Weber-Fechner Law
Weber-Fechner says we perceive proportional differences — we notice relative change. That can make "2,000 vs 200,000" feel less different than the 100× ratio implies. The tension: our perception is built for relative scale; rational allocation often needs absolute scope in the decision. Add explicit scope weighting.
Section 8
One Key Quote
"The same psychological mechanisms that enable us to function in the face of uncertainty also produce systematic failures in our ability to respond to threats that are large in scope."
— Paul Slovic
We are built to react to immediate, vivid, local problems. Large-scale problems are abstract and don't trigger proportional concern. The mechanism that helps us act in the moment also makes us underreact to scope. The fix is procedural: build scope into the decision rule so that we don't rely on feeling alone.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Put scope in the formula. When prioritising, allocating, or evaluating impact, multiply by scope (users, dollars, lives). If your prioritisation doesn't have a "how many?" component, you're at risk of scope neglect. Add it explicitly: impact × reach, or cost per unit of outcome.
Test with 10×. Ask: if this problem were 10× bigger, would our response be 10×? If not, we're underweighting scope. Use the 10× test to spot scope neglect in existing processes and in your own reactions.
One story can hijack scope. The identifiable victim effect means one vivid case can outweigh thousands in the aggregate. When someone says "but we had this one customer who…," ask: how many does this affect? Don't let the single case set policy unless the scope is comparable.
Communicate scope when you want a scaled response. If you want donors, boards, or teams to take scale seriously, state the number and repeat it. "This affects 50,000 users" is better than "this affects many users." Make scope impossible to ignore.
Section 10
Test Yourself
Is this mental model at work here?
Scenario 1
A team spends two days fixing a bug reported by one enterprise customer and defers a bug that causes 5% of free users to hit an error. The free-user bug affects 50,000 people.
Scenario 2
A founder prioritises roadmap by 'impact × number of users affected.' Features that help more users get higher rank, all else equal.
Scenario 3
Donors give similar amounts to a campaign to save 2,000 birds and a campaign to save 200,000 birds. The campaigns are otherwise identical.
Scenario 4
A board allocates the same amount of discussion time to a $10M investment opportunity and a $500M opportunity. Both are in the same sector.
Section 11
Further Reading
Scope neglect and psychophysical numbing are documented in psychology and behavioural economics. These sources cover the evidence and implications.
Singer on effective altruism and the moral importance of scope. One theme: we should scale our concern and our giving with the number of people we can help.
Background on why we perceive proportional rather than absolute differences. Helps explain why large numbers don't feel proportionally larger.
Summary: Scope neglect is the failure to scale our response (attention, money, effort) with the magnitude of the problem. People often react similarly to 100 vs 10,000 affected. Correct by putting scope in the decision rule: prioritise by impact × reach, and test whether your response would scale if the problem were 10× bigger.
Leads-to
Scope Sensitivity
Scope sensitivity is the corrective: designing decisions so that response scales with scope. Prioritisation by impact × reach, resource allocation by size of opportunity, and explicit "how many?" in every impact claim. Scope neglect describes the bug; scope sensitivity is the patch.
Leads-to
Psychophysical Numbing
Psychophysical numbing is the emotional side of scope neglect: as the number of victims grows, our affective response does not keep pace. We "numb" to large numbers. The concept leads to the same prescription: use rules and explicit scaling so that decisions are scope-sensitive even when feeling is not.
