jmis-methods
Use when choosing and defending the research design for a Journal of Management Information Systems (JMIS) manuscript — IT-value/platform econometrics, a behavioral survey or experiment, an analytical/economic model, or a design-science/data-science artifact. Matches the method to the IS claim and the ≤50-page budget; it designs the study and hands estimation/evaluation to jmis-data-analysis.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-methods --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Research Design & Methods (jmis-methods) ## When to trigger - You have a mechanism or propositions but no defensible way to test/evaluate them - The method may not match the claim (a causal IT-value claim resting on a cross-sectional correlation) - A reviewer asks "what identifies this effect?" or "how do you know the artifact is useful?" - You need to decide what evidence fits inside the **50-page** complete-manuscript ceiling ## Match the design to the JMIS research style and the strength of the claim JMIS is methodologically broad but the design must earn the causal/economic verb in the claim. | Style | Typical designs | The design must establish | |-------|-----------------|----------------------------| | **IT business value / firm** | Panel econometrics, natural experiment, DiD, IV, matching | Credible identification of IT's causal value against endogenous IT investment | | **Platform / e-commerce** | Quasi-experiments on platform shocks, structural demand, field experiments | The network/two-sided mechanism, controlling for selection on platform data | | **Behavioral IS** | Lab/online/field experiment, multi-wave survey, panel | Internal + construct validity and *procedural
- When to trigger
- Match the design to the JMIS research style and the strength of the claim
- IT-value and platform empirics: identify, do not just control
- Behavioral IS: design out the threats before you collect data
- Design-science / data-science: plan the utility evaluation up front
- Scope the evidence to the 50-page budget
- Worked vignette: identifying IT business value (illustrative)
- Referee pushback mapped to a design fix
- Execution bridge (StatsPAI / Stata MCP)
- Checklist
- Platform and e-commerce data: design around its pathologies
- Anti-patterns
- Make the method serve the claim, not fashion
- Output format
What does the jmis-methods skill do?
Use when choosing and defending the research design for a Journal of Management Information Systems (JMIS) manuscript — IT-value/platform econometrics, a behavioral survey or experiment, an analytical/economic model, or a design-science/data-science artifact. Matches the method to the IS claim and the ≤50-page budget; it designs the study and hands estimation/evaluation to jmis-data-analysis.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jmis-methods --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.