---
name: jom-contribution-framing
description: Use when articulating the theoretical and practical contribution of a Journal of Operations Management (JOM) manuscript — stating what new OM theory the study delivers, why operations is central to the contribution, and what it means for operations managers, in the intro and discussion.
---

# Contribution Framing for JOM (jom-contribution-framing)

## When to trigger

- Results exist but the "so what for operations theory and practice" is thin
- A reviewer/Department Editor says "the empirical work is solid but the contribution is unclear"
- You can state findings but not what the field now knows that it did not before
- The practical (managerial) implications read as generic

## JOM's dual contribution standard

JOM publishes empirical OM research with **both academic and practical relevance**, where **operations are at the heart of the research question**. So the contribution must be stated on two axes, and both must foreground operations:

1. **Theoretical contribution.** What OM-relevant theory does the study test, extend, qualify, or build? Name the specific belief that changes. "We confirm prior work" is not a contribution; "the buffering effect reverses under high automation" is. Tie the change explicitly to the operations mechanism from `jom-theory-development`.
2. **Practical relevance.** Because ASCM is a practitioner association, spell out what an operations or supply-chain manager should do differently — concretely, in operational terms (inventory policy, supplier selection, scheduling, quality protocol, sustainability practice), not as a platitude.

## Make operations central, not incidental

State why the contribution would not exist outside an operations context. If the same conclusion could be drawn from a generic management study, the framing is too thin for JOM. The empirical observation — the recall pattern, the field-measured behavior, the intervention outcome — should be load-bearing in the claim.

## Write explicit contribution sentences

- **In the introduction:** one or two sentences naming the new operations insight, placed before the method preview.
- **In the discussion:** a dedicated subsection that (a) restates the theoretical advance, (b) draws boundary conditions from your moderators/contexts, and (c) gives actionable operations guidance.
- Connect to the **Department mission** you routed to — the contribution should advance that Department's conversation specifically.

## Anti-patterns

- "First study to..." novelty claims with no theory movement.
- Practical implications that any management paper could write.
- Burying the contribution in the discussion's last paragraph.
- A contribution that survives if you delete the operations setting.

## What JOM referees weigh on contribution

JOM evaluation foregrounds the operations-as-heart test alongside theory movement; the table is an interpretive reading, not a published rubric (confirm against current author guidelines).

| Referee question | Strong signal | Weak signal |
|------------------|---------------|-------------|
| Is operations at the heart? | The claim depends on an OM/supply-chain mechanism | Operations is only the setting |
| Does OM theory move? | A prior belief is qualified, reversed, or bounded | "First study to look at X" |
| Is relevance operational? | A specific lever changes (reorder point, audit cadence) | Generic "managers should attend" |

## Desk-reject and early-return triggers on framing

- Operations reads as context, not phenomenon — the commonest JOM scope rejection.
- The "so what" is a methods novelty rather than an OM-theory advance.
- Practical implications could appear unchanged in a generic paper.

## Worked vignette: a supply-chain-integration survey

A team surveys 214 plants and finds supplier integration raises on-time delivery, but the effect weakens sharply when demand volatility is high (illustrative). The JOM-grade framing names the belief that changes: the field has treated integration as monotonically beneficial, yet its delivery benefit is contingent on a stable environment — buffering and integration are partial substitutes under volatility. Theoretical contribution: a boundary condition on integration theory. Operations centrality: both mechanism (information-sharing reducing schedule variance) and moderator (volatility) are operational. Practical relevance: under volatile demand, pair integration with explicit buffer capacity. Belief changed, operations load-bearing, lever specified — that triad is what a Department Editor wants.

## Common contribution objections and how to answer them

- *"The theoretical contribution to OM is not articulated."* Add an explicit contribution sentence in the intro naming the prior belief and how your evidence revises it; mirror it with a discussion subsection drawing boundary conditions.
- *"This could be any management paper."* Re-anchor on the operations mechanism and show the conclusion collapses if the operations setting is removed.
- *"Practical implications are generic."* Replace platitudes with a concrete operational decision rule.

## Calibrating the dual-contribution bar (hedged)

JOM expects a clear theoretical contribution to operations management paired with demonstrated practical relevance; a phenomenon-only paper, however well-measured, tends to stall. These are directional norms — confirm scope against current Department missions.

## Output format

```
【Theoretical contribution】the OM belief that changes ...
【Operations centrality】why this needs an operations context ...
【Practical relevance】what an operations manager does differently ...
【Department fit】advances the conversation in ...
【Intro sentence + Discussion subsection】drafted? ...
【Next step】jom-tables-figures
```