Joc Theory Building

---
name: joc-theory-building
description: Use when building the theoretical argument of a Journal of Communication (JoC) manuscript into a field-level contribution — whether the work is mechanistic-empirical, computational, interpretive, or critical. JoC rewards a clear, portable communication-theory argument over a bare finding. Structures the argument; it does not run analyses.
---

# Theory & Argument Building (joc-theory-building)

At JoC a result is not a contribution until it is attached to an **argument communication researchers
can use elsewhere.** This skill turns findings into theory: explicit mechanisms, scope conditions, and
observable implications, in the idiom appropriate to your kind of work. Communication theory is the
journal's core — a paper that only documents an effect on one platform rarely clears the bar.

## When to trigger

- The empirics are strong but the "so what / why" is thin
- A reviewer said the paper is "atheoretical," "ad hoc," or "just an effect"
- You need to state mechanisms, assumptions, and scope conditions explicitly
- Connecting your work to (or revising) an established communication theory

## Build the argument (by mode of work)

### Empirical paper with a theory
1. **Concept** — define the key constructs precisely (e.g., exposure, framing, presence); distinguish
   from neighbors.
2. **Mechanism** — the communication process: who sends/receives what, through which channel, with what
   cognitive/affective/social step.
3. **Observable implications** — what we should see if the mechanism operates (and what we should
   *not* see). These become the tests in `joc-research-design`.
4. **Scope conditions** — which audiences, messages, and contexts the argument holds for. Portability ≠ universality.

### Computational / text-as-data paper
- State the **substantive communication question** before the pipeline; the method serves the theory.
- Make latent constructs (topics, frames, stance) **theoretically interpretable and validated**, not
  just statistically extracted.
- Translate computational patterns into **claims about communication processes** a reader can recognize.

### Interpretive / critical paper
- Make the **conceptual, cultural, or normative stakes** explicit and connect them to communicative life.
- Build the argument through **texts, practices, and reasons**, engaging the strongest counter-reading.
- Show what the argument lets the field **see or critique** that it could not before.

## The "portability" test (JoC-specific)

Ask: *Could a researcher in another communication subfield import this mechanism/concept to their own
problem?* If yes, you have a field-level contribution. If the argument only works for your exact
platform or message, tighten it into a general communication logic or reframe (back to
`joc-topic-selection`).

## Anti-patterns

- "Hypothesizing after results are known" (HARKing) — state theory before tests; preregister where possible
- A finding tied so tightly to one platform that it cannot travel
- Mechanisms named but never made observable
- Universal claims with no scope conditions (which audiences? which messages? which contexts?)
- Burying the argument under the empirics — the contribution paragraph must state it plainly

## Output format

```
【Core claim】one sentence
【Mechanism】the communication process / causal-logical story
【Constructs】defined + distinguished from neighbors
【Observable implications】testable consequences → research-design
【Scope conditions】which audiences / messages / contexts
【Portability】who else in communication can use this argument
【Next】joc-research-design
```

## Supplementary resources

- [`../../resources/external_tools.md`](../../resources/external_tools.md) — measurement, SEM, and text-as-data tooling
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — JoC scope and contribution expectations