本文へ移動
cccskills
無料GitHub で公開

asq-theory-development

Use when building the theoretical engine for an Administrative Science Quarterly (ASQ) manuscript — mechanisms, process vs. variance logic, constructs, and boundary conditions. Builds the argument; it does not select methods or run analysis.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Theory Development (asq-theory-development)

When to trigger

  • You have a puzzle (from asq-topic-selection) but no theoretical machinery to explain it
  • Your "theory" is a box-and-arrow diagram with labeled constructs but no mechanism
  • You are unsure whether your phenomenon needs a process theory or a variance theory
  • Reviewers say the theory is "thin," "post hoc," or "a relabeling of the finding"

Process theory vs. variance theory

This is the central choice at ASQ. Get it right before drafting.

  • Variance theory explains how much of an outcome varies with antecedents: X → Y, with moderators/mediators. Appropriate for "whether and under what conditions" questions, typically quantitative.
  • Process theory explains how and why something unfolds over time: sequences, events, feedback, transformation. Appropriate for emergence, becoming, contestation, and dynamics — typically qualitative/inductive.

ASQ punishes variance framing forced onto a process question: if your data show a sequence of events transforming an organization but you write it as "factor A increases outcome B," reviewers will say the theory and phenomenon are mismatched. Match the form of the theory to the form of the phenomenon. ASQ's lineage makes process and interpretive theorizing fully legitimate as the main contribution — this is a real difference from journals where the variance/hypothesis template is the implicit standard. Barley's (1986) ASQ study of CT scanners, for instance, theorized structuring as a process rather than estimating an effect of technology on structure.

Mechanism first

A construct is not a mechanism. State the generative mechanism — the social/organizational process that produces the relationship or sequence:

  • Name the actors and what they are doing (sensemaking, competing, imitating, categorizing, coordinating, resisting). ASQ's sociology-of-organizations roots mean collective and field-level mechanisms (mimetic, normative, and coercive isomorphism in the DiMaggio & Powell 1983 sense) are as welcome as micro ones.
  • Name the social structure in which they act (field, hierarchy, network, category system, status order)
  • Specify the causal/processual logic: why does this actor, in this structure, produce this outcome or this next step?
  • Specify boundary conditions: where does the mechanism hold, weaken, or reverse?

A good test: could a reader predict a new, non-obvious implication from your mechanism? If not, you have a label, not a theory.

For inductive papers

If theory is emergent (grounded), this skill still applies — but in reverse order:

  • Theory is the output, presented after the data structure (see asq-data-analysis)
  • Still required: a named mechanism, a process model (often a figure with phases/feedback), and a clear statement of what is novel relative to existing organizational theory
  • A grounded, inductively-built theory can be the entire contribution at ASQ — it need not be a stepping stone to a later deductive test, as it might be framed elsewhere
  • Avoid "theory by adjective": calling a pattern "dynamic" or "recursive" without specifying the process

For deductive papers

  • Hypotheses must be derived, each with an explicit causal logic paragraph — not asserted
  • Each hypothesis should connect back to the same core mechanism (avoid a "bag of hypotheses")
  • Moderators must be theoretically motivated (why this boundary?), not data-driven fishing

Checklist

  • Process vs. variance form matches the phenomenon
  • A named generative mechanism (actors + structure + logic), not just constructs
  • Boundary conditions stated (where it holds / weakens / reverses)
  • Mechanism yields at least one non-obvious, testable/observable implication
  • Constructs are defined precisely and consistently with the literature
  • For deductive: each hypothesis has its own derivation paragraph tied to the mechanism
  • For inductive: a process/theory model figure is planned, with novelty stated

Anti-patterns

  • Box-and-arrow models with no mechanism ("constructs in search of a story")
  • Variance framing for a process phenomenon (or vice versa)
  • Hypotheses asserted rather than derived; a moderator zoo with no logic
  • "Theory by adjective" — naming a pattern instead of explaining it
  • Borrowing a fashionable construct as a veneer over an under-theorized finding

Output format

【Theory form】process / variance + why it matches the phenomenon
【Core mechanism】actors + structure + causal/processual logic
【Boundary conditions】where it holds / weakens / reverses
【Novel implication】the non-obvious prediction or insight
【Deductive only】hypotheses + derivation status
【Next step】asq-literature-positioning

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.

日本語の概要は準備中です。原文の説明を表示しています。

brycewang-stanford/Awesome-Journal-Skills1,2482026年9月27日 更新

brycewang-stanford のスキルをすべて見る

このスキルの問題を報告する