MISQ publishes research on the development, use, impact, management, and economics of information technology — IT-based services, the management of IT resources, and the use and impact of IT with managerial, organizational, and societal implications. The IT artifact (a system, algorithm, platform, data, or digitally enabled practice) should be central, not incidental. If the technology could be swapped for "any treatment" without changing the theory, the paper is probably not an IS paper.
| Tradition | The paper's job | Typical category |
|---|---|---|
| Behavioral | Explain/predict how people and organizations adopt, use, and are affected by IT | Research Article / Research Notes |
| Design science | Build and rigorously evaluate a novel, purposeful IT artifact that solves a real problem | Design Science |
| Economics of IS | Identify the causal economic effects/mechanisms of IT (markets, platforms, productivity, pricing) | Research Article / Research Notes |
| Organizational | Theorize IT in organizational and social context (governance, transformation, work) | Research Article / Theory Development |
MISQ explicitly welcomes cross-tradition blends (e.g., a design-science artifact evaluated with a behavioral experiment, or an economics-of-IS question with organizational theory). Name the primary tradition, then declare the blend.
Self-select the genre up front, because length and evaluation criteria differ:
Page limits count everything (text, tables, figures, references, appendices), so the category constrains the scope of the question.
The fastest fit diagnostic: can you swap the IT artifact for a generic treatment without changing the theory? Three cases:
If the mechanism survives deleting the technology, it is not yet a MISQ paper; return to the mechanism before choosing a category.
| Situation | Category | Why |
|---|---|---|
| A single clean field experiment on IT-enabled nudging | Research Note | Focused single contribution; ~half a Research Article |
| A build-and-evaluate of a novel ML pipeline with design principles | Design Science | Prescriptive design knowledge is the contribution |
| A new theory of algorithmic control at work, lightly empirical | Theory Development (55pp) | Theory is the primary output |
| A synthesis of the IS-security literature that generates propositions | Theory-Generative Synthesis (65pp) | Synthesis that yields theory |
Because the page limit counts everything, choose the category before scoping the study, not after drafting.
【IS question?】central IT artifact: yes/no — why
【Tradition】behavioral / design science / economics / organizational (+ blend)
【Category】Research Article / Research Notes / Theory Dev / Synthesis / Design Science / I&O
【Scope fits page budget?】yes / trim needed
【Next step】misq-theory-development