MISQ spans four traditions, so there is no single mandated method. Pick the design that the claim requires.
| Tradition | Typical designs | The design must establish |
|---|---|---|
| Behavioral | Lab/online experiment, field experiment, multi-wave survey, panel | Internal validity, construct validity, and (for surveys) procedural remedies for common-method bias |
| Design science | Build-and-evaluate of an IT artifact | That the artifact is novel and useful for a real problem — utility demonstrated, not asserted |
| Economics of IS | Natural experiment, DiD, IV, RD, structural model | A credible identification strategy for the causal/economic effect |
| Organizational | Case study, ethnography, mixed methods, longitudinal field | Trustworthiness, rich context, and a transparent path from data to constructs |
A MISQ design-science paper lives or dies on evaluation. Following Hevner et al. (2004), decide before building how you will demonstrate utility: held-out benchmarks against credible baselines, a controlled experiment or A/B field deployment, simulation, or expert evaluation — and tie each back to the design propositions. State the problem's relevance, the artifact's novelty, and the evaluation criteria so reviewers can judge rigor and relevance. "We built it and it ran" is not an evaluation.
Because supplementary materials are discouraged and the page limit counts text, tables, figures, references, and appendices, design a study whose evidence fits the chosen category. Scope the design to the page budget rather than planning to offload it to an online appendix.
For the empirical / causal lane, estimate and audit rather than only specify. Full
map: execution-with-mcp. MISQ is empirical IS — surveys, econometric panels, experiments, and design science; the chain below serves the causal / econometric lane, while design-science artifacts use their own evaluation standards.
detect_design → recommend → fit with as_handle=true → audit_result to
enumerate the checks the design owes.callaway_santanna / sun_abraham + bacon_decomposition
honest_did_from_result. IV: effective_f_test + anderson_rubin_ci. RDD:
rdrobust + mccrary_test.romano_wolf for the many-outcome
family-wise correction reviewers expect.Match the toolchain to the reviewer pool, and report the effect size the venue wants. A run end-to-end (synthetic data, real returns) is in the JF execution walkthrough.
【Tradition & design】experiment / survey / DiD-IV-RD / build-and-evaluate / qualitative
【Identification or evaluation】source of variation OR evaluation plan + baselines
【Validity threats handled】CMB / confounds / trustworthiness
【Fits page budget?】yes / trim
【Next step】misq-data-analysis