Theory & Argument Building (asr-theory-building)
At ASR a finding becomes a contribution when it is attached to a theoretical argument other
sociologists can use. This skill turns evidence into theory: explicit mechanisms, scope conditions,
and concepts, in the idiom appropriate to your method.
When to trigger
- The empirics are strong but the "so what / why" is thin
- A reviewer said the paper is "atheoretical," "merely descriptive," or "case-bound"
- You need to state the mechanism, the concepts, and where the argument holds
- Reconciling rich case material (ethnography/history) with a general claim
Build the argument (by mode of work)
Quantitative / demographic
- Concept — define key constructs (e.g., the form of inequality, mobility, the social process)
and distinguish them from neighbors.
- Mechanism — the social process generating the pattern: who, why, under what structural
conditions.
- Observable implications — what we should and should not see if the mechanism operates; these
become tests in
asr-research-design.
- Scope conditions — populations, periods, contexts where the argument holds.
Comparative-historical
- Build the argument through cases and sequences; specify the causal logic (necessary/sufficient
conditions, conjunctures, path dependence) rather than a loose narrative.
- State what comparison or counterfactual the cases support.
Ethnographic / interview
- Move from rich observation to a named mechanism and concept the discipline can carry
elsewhere. Say what the site is a case of.
- Show what the case lets sociology see that surveys or aggregates cannot.
Network / computational
- Tie structure or computational result to a substantive social mechanism, not just a metric.
The "portability" test (ASR-specific)
Ask: Could a sociologist in another subfield import this mechanism or concept to their own problem?
If yes, you have a discipline-level contribution. If it only works for your case, generalize the logic
or reframe (back to asr-topic-selection).
What "theoretical contribution" means to an ASR referee
At the ASA flagship, the premium is on a mechanism a sociologist in another subfield could carry to a
different problem. Referees grade portability, not local cleverness.
| Referee judgment |
A passing argument shows |
A failing argument shows |
| "Merely descriptive" |
a named mechanism generating the pattern |
an association with no "why" |
| "Case-bound" |
a concept that travels beyond the site |
insight that only fits this case |
| "Atheoretical" |
scope conditions + observable implications |
a finding with no stated theory |
| "Where's the payoff?" |
what general understanding shifts |
a point only its subfield notices |
Worked micro-example (illustrative)
An ethnography of a public defender's office is built from observation to a portable claim.
Observation: defenders triage clients by perceived "workability" under caseload pressure
Concept: "administrative triage" — a frontline rationing logic, distinct from bias and formal rules
Mechanism: resource scarcity + discretion → categorization that reproduces inequality
Scope conditions: high-caseload, discretion-rich street-level bureaucracies
Implication: where caseloads fall, triage categories should weaken (a testable corollary)
Portability: an organizations or welfare scholar could import "administrative triage" directly
The site work yields a concept and mechanism another subfield can use — the move from a vivid case to a
discipline-level contribution ASR rewards.
Referee pushback → ASR-specific fix
- "Association, not explanation." → State the social process generating the pattern — who, why, under
what structural conditions — before the evidence.
- "Beautiful case, but so what for sociology?" → Name the portable concept and one outside subfield
that could adopt it.
- "Where does the argument stop?" → Add explicit scope conditions; unbounded claims read as
unserious.
Calibration anchors
- Portability is the contribution. ASR's defining demand is a mechanism or concept that travels; a
setting-bound finding, however clean, under-performs.
- Theory before tests. State the argument and its observable implications first; theorizing after
the results are known reads as HARKing to expert referees.
- State the claim plainly. The flagship rewards an argument a generalist can restate in a sentence
over one buried under data — hedge the scope, not the claim.
Anti-patterns
- A finding with no mechanism ("X is associated with Y" and stop)
- Case material that never rises to a portable concept
- "Hypothesizing after results are known" — state the theory before the tests
- Grand claims with no scope conditions
- Burying the argument under data — the contribution must be stated plainly
Output format
【Core claim】one sentence
【Mechanism】the social process / causal logic
【Key concept(s)】defined and distinguished
【Observable implications】testable consequences → research-design
【Scope conditions】populations / periods / contexts where it holds
【Portability】who else can use this argument
【Next】asr-research-design
Supplementary resources
1---2name: asr-theory-building3description: Use when building the theoretical argument of an American Sociological Review (ASR) manuscript into a portable contribution — for quantitative, demographic, comparative-historical, ethnographic, network, or computational work. ASR rewards a mechanism that travels over a setting-bound finding. Structures the argument; it does not run analyses.4---56# Theory & Argument Building (asr-theory-building)78At ASR a finding becomes a contribution when it is attached to a **theoretical argument other9sociologists can use.** This skill turns evidence into theory: explicit mechanisms, scope conditions,10and concepts, in the idiom appropriate to your method.1112## When to trigger1314- The empirics are strong but the "so what / why" is thin15- A reviewer said the paper is "atheoretical," "merely descriptive," or "case-bound"16- You need to state the mechanism, the concepts, and where the argument holds17- Reconciling rich case material (ethnography/history) with a general claim1819## Build the argument (by mode of work)2021### Quantitative / demographic221. **Concept** — define key constructs (e.g., the form of inequality, mobility, the social process)23 and distinguish them from neighbors.242. **Mechanism** — the social process generating the pattern: who, why, under what structural25 conditions.263. **Observable implications** — what we should and should not see if the mechanism operates; these27 become tests in `asr-research-design`.284. **Scope conditions** — populations, periods, contexts where the argument holds.2930### Comparative-historical31- Build the argument through **cases and sequences**; specify the causal logic (necessary/sufficient32 conditions, conjunctures, path dependence) rather than a loose narrative.33- State what comparison or counterfactual the cases support.3435### Ethnographic / interview36- Move from rich observation to a **named mechanism** and **concept** the discipline can carry37 elsewhere. Say what the site is a case *of*.38- Show what the case lets sociology **see** that surveys or aggregates cannot.3940### Network / computational41- Tie structure or computational result to a **substantive social mechanism**, not just a metric.4243## The "portability" test (ASR-specific)4445Ask: *Could a sociologist in another subfield import this mechanism or concept to their own problem?*46If yes, you have a discipline-level contribution. If it only works for your case, generalize the logic47or reframe (back to `asr-topic-selection`).4849## What "theoretical contribution" means to an ASR referee5051At the ASA flagship, the premium is on a mechanism a sociologist in another subfield could carry to a52different problem. Referees grade portability, not local cleverness.5354| Referee judgment | A passing argument shows | A failing argument shows |55|------------------|---------------------------|---------------------------|56| "Merely descriptive" | a named mechanism generating the pattern | an association with no "why" |57| "Case-bound" | a concept that travels beyond the site | insight that only fits this case |58| "Atheoretical" | scope conditions + observable implications | a finding with no stated theory |59| "Where's the payoff?" | what general understanding shifts | a point only its subfield notices |6061## Worked micro-example (illustrative)6263An ethnography of a public defender's office is built from observation to a portable claim.6465```66Observation: defenders triage clients by perceived "workability" under caseload pressure67Concept: "administrative triage" — a frontline rationing logic, distinct from bias and formal rules68Mechanism: resource scarcity + discretion → categorization that reproduces inequality69Scope conditions: high-caseload, discretion-rich street-level bureaucracies70Implication: where caseloads fall, triage categories should weaken (a testable corollary)71Portability: an organizations or welfare scholar could import "administrative triage" directly72```7374The site work yields a concept and mechanism another subfield can use — the move from a vivid case to a75discipline-level contribution ASR rewards.7677## Referee pushback → ASR-specific fix7879- *"Association, not explanation."* → State the social process generating the pattern — who, why, under80 what structural conditions — before the evidence.81- *"Beautiful case, but so what for sociology?"* → Name the portable concept and one outside subfield82 that could adopt it.83- *"Where does the argument stop?"* → Add explicit scope conditions; unbounded claims read as84 unserious.8586## Calibration anchors8788- **Portability is the contribution.** ASR's defining demand is a mechanism or concept that travels; a89 setting-bound finding, however clean, under-performs.90- **Theory before tests.** State the argument and its observable implications first; theorizing after91 the results are known reads as HARKing to expert referees.92- **State the claim plainly.** The flagship rewards an argument a generalist can restate in a sentence93 over one buried under data — hedge the scope, not the claim.9495## Anti-patterns9697- A finding with no mechanism ("X is associated with Y" and stop)98- Case material that never rises to a portable concept99- "Hypothesizing after results are known" — state the theory before the tests100- Grand claims with no scope conditions101- Burying the argument under data — the contribution must be stated plainly102103## Output format104105```106【Core claim】one sentence107【Mechanism】the social process / causal logic108【Key concept(s)】defined and distinguished109【Observable implications】testable consequences → research-design110【Scope conditions】populations / periods / contexts where it holds111【Portability】who else can use this argument112【Next】asr-research-design113```114115## Supplementary resources116117- [`../../resources/external_tools.md`](../../resources/external_tools.md) — analysis tooling across methods118- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — ASR scope and contribution expectations