---
name: isr-contribution-framing
description: Use when turning results into an explicit contribution to IS for an Information Systems Research (ISR) manuscript and when drafting the mandatory ~500-word cover-letter contribution statement (required since June 1, 2023). Frames the contribution; it does not position the literature (isr-literature-positioning) or run the submission preflight (isr-submission).
---

# Contribution Framing (isr-contribution-framing)

## When to trigger

- Results exist but the "so what for IS?" is thin or implicit
- You must write the **~500-word contribution statement** required in every ISR cover letter
- A reviewer or Senior Editor says the contribution is incremental or single-paradigm
- The paper reads as a competent study with no clear advance to an IS conversation

## ISR's mandatory contribution statement

Since **June 1, 2023**, ISR requires a **~500-word contribution statement** in every cover letter. It must articulate the **novel, rigorous, original contribution to IS** — what the paper adds beyond existing literature and why it matters. Generic or missing statements are returned for revision, so this is not boilerplate; it is the first thing the EIC reads at the **fit gate** before a Senior Editor is assigned. Draft it to answer, concretely: What did we not know? What do we now know? Why does it matter for IS scholarship and for practice/policy/society?

## Frame the contribution to ISR's mission

ISR is sociotechnical and intradisciplinary, so the strongest contributions:

- **Advance an IS conversation**, not just a reference discipline — state which stream you change and how.
- **Bridge IS silos** where possible: a contribution that connects behavioral, economic, design-science, or organizational perspectives is valued over a single-paradigm increment.
- **Center the IT artifact**: the advance should depend on the technology, across the relevant level(s) of analysis.
- **Match the genre**: an analytical paper contributes new equilibrium/comparative-static insight; a behavioral paper contributes a validated mechanism; a design-science paper contributes a useful, evaluated artifact and design principles.

## Echo the contribution in intro and discussion

The cover-letter statement and the manuscript must agree. State the contribution explicitly in the introduction (the "we show that…" sentences) and revisit it in the discussion with implications for theory, for IS practice, and — where apt — for policy or society, plus honest boundary conditions and future work. Do not leave the contribution implicit for the reader to infer.

## Checklist

- [ ] ~500-word contribution statement drafted (novelty, what's added, why it matters)
- [ ] Contribution advances a named IS conversation, not only a reference discipline
- [ ] Intradisciplinary/silo-bridging angle stated where available
- [ ] IT artifact is essential to the advance
- [ ] Genre-appropriate contribution (insight / mechanism / evaluated artifact)
- [ ] Intro and discussion state the contribution explicitly and consistently
- [ ] Practice/policy/societal relevance noted; boundary conditions honest

## Anti-patterns

- **Boilerplate contribution statement** that any paper could submit.
- **Reference-discipline contribution** with no IS advance.
- **Implicit contribution** left for the reader to reconstruct.
- **Overclaiming** beyond what the identification/proof/evaluation supports.


## Contribution pass for Information Systems Research

Run this as a concrete capability pass. First lock the digital artifact or system, user/firm behavior, identification or design evidence, and IS-theory contribution; then test whether the manuscript addresses IS reviewers who expect digital-technology theory, empirical or design leverage, and implications for organizations or markets.

- **Primary move:** Translate the result into who learns what, which mechanism changes, and which alternative explanation is ruled out; keep the claim narrower than the evidence.
- **Decision ledger:** return `claim / evidence / blocker / next edit` rows so the next pass can patch the manuscript directly.
- **Sibling comparison:** compare against MIS Quarterly for broader IS theory, Management Science for OR/MS generality, Journal of Management Information Systems for applied IS systems; if the neighboring outlet has the stronger audience claim, recommend re-routing before polishing.
- **Verification floor:** before submission-ready advice, re-open `resources/official-source-map.md` for volatile rules and name the one unresolved fact that could change the recommendation.

## Output format

```
【Contribution statement (~500 words)】drafted? [...]
【IS conversation advanced】[...]
【Intradisciplinary bridge】[...]
【IT-artifact dependence】[...]
【Genre fit】insight / mechanism / artifact
【Intro & discussion alignment】[...]
【Next step】isr-tables-figures or isr-submission
```