jom-methods
Use when choosing and defending the research design for a Journal of Operations Management (JOM) empirical study — matching survey, archival/secondary, field, case, experimental, or intervention-based research to the operations question, anticipating the Empirical Research Methods Department's method check, and keeping the design observation-grounded rather than analytical.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-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 for Empirical OM (jom-methods) ## When to trigger - You must pick a design that can actually test your operations hypotheses - A reviewer questions whether the method fits the operations phenomenon or the level of analysis - You are weighing a behavioral lab experiment vs. archival panel vs. survey vs. field/intervention - You anticipate the **Empirical Research Methods Department** method check on incoming submissions ## JOM's empirical-only design space JOM publishes empirical OM research and **does not** publish purely analytical models or optimization techniques. Every design must rest on **observation**. The native JOM design families are: | Operations question / claim | Design | |--------------------------------------------------------------|---------------------------------------------------------------| | Perceptions, practices, constructs across firms/plants | **Survey** (validated multi-item scales; multi-respondent) | | Cause–effect on operational outcomes from secondary data | **Archival/secondary** panel (recalls, inventory, supply ties)| | Human operational decisions, biases, incentives | **Behavioral-OM experiment** (lab/online, manipulation checks)
- When to trigger
- JOM's empirical-only design space
- Match design to claim and level
- Intervention Based Research (a JOM-distinctive genre)
- Pre-empt the Empirical Research Methods check
- Execution bridge (StatsPAI / Stata MCP)
- Anti-patterns
- Design-defense checklist the methods check applies
- Desk-reject and return triggers on design
- Worked vignette: archival vs. field for a quality-practice question
- Design objections and the JOM-grounded response
- Output format
What does the jom-methods skill do?
Use when choosing and defending the research design for a Journal of Operations Management (JOM) empirical study — matching survey, archival/secondary, field, case, experimental, or intervention-based research to the operations question, anticipating the Empirical Research Methods Department's method check, and keeping the design observation-grounded rather than analytical.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jom-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.