thedixitjain 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
../../resources/external_tools.md— analysis tooling across methods../../resources/official-source-map.md— ASR scope and contribution expectations
Source: brycewang-stanford/Awesome-Journal-Skills → American-Sociological-Review-Skills/skills/asr-theory-building/SKILL.md