# Pubar Theory Building > Use when building the theoretical argument of a Public Administration Review (PAR) manuscript into a contribution that advances public-management theory and informs practice. PAR rewards a clear, portable mechanism with explicit scope conditions plus a defensible practitioner "so-what." Structures the argument; it does not run analyses. - Skill: `thedixitjain/pubar-theory-building` (Agent Skill) - Install (CLI): `npx skillmds add thedixitjain/pubar-theory-building` - Raw SKILL.md: https://api.skillmd.com/api/skills/thedixitjain/pubar-theory-building/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: thedixitjain (https://skillmd.com/u/thedixitjain) - Updated: 2026-09-08 - Page: https://skillmd.com/skills/thedixitjain/pubar-theory-building --- # Theory & Argument Building (pubar-theory-building) At PAR a result is not a contribution until it is attached to an **argument public-management scholars can use elsewhere** *and* a **practical implication a manager can act on.** This skill turns findings into theory: explicit mechanisms, scope conditions, and observable implications — in the idiom of public administration, where context (institutions, law, political control, public values) is central. ## When to trigger - The empirics are strong but the "so what / why" is thin - A reviewer said the paper is "atheoretical," "ad hoc," or "just a program description" - You need to state mechanisms, assumptions, and scope conditions explicitly - A **Conceptualizing Public Administration** thought piece (theory is the whole contribution) ## Build the argument (by mode of work) ### Empirical paper with a theory 1. **Concept** — define the key constructs precisely (e.g., red tape, goal ambiguity, PSM, network integration); distinguish from neighbors and from informal usage. 2. **Mechanism** — the behavioral/organizational story: which actor (bureaucrat, manager, citizen, politician) does what, under which incentives, constraints, and public-sector context. 3. **Observable implications** — what we should see if the mechanism operates (and what we should *not* see). These become the tests in `pubar-research-design`. 4. **Scope conditions** — which governance level, sector, or institutional setting the argument holds in. Portability ≠ universality; public-sector context is a feature, not noise. ### Conceptual / theory piece (Conceptualizing PA) - State the **field-level problem** the concept addresses before the synthesis. - Build the argument through **reasoning and the literature**, not hypotheses; engage the strongest counter-view and rival framings. - Show what the reframing lets the field **see, measure, or manage** that it could not before. ## The dual test (PAR-specific) Ask **two** questions: 1. **Portability** — *Could a scholar in another PA subfield import this mechanism/concept?* If only your exact case works, tighten it into a general logic or reframe (back to `pubar-topic-selection`). 2. **Practice** — *Can the mechanism be stated as something a manager could change?* If the mechanism has no managerial lever, the **Evidence for Practice** points will ring hollow. ## The "Evidence for Practice" box (a PAR signature requirement) PAR asks empirical articles to carry an **Evidence for Practice** box — a short bulleted list (typically 3–5 points) of what the findings mean for those who run public organizations. Editors and reviewers treat it as a checked contribution element, not decoration, so build it *from the mechanism*, not as an afterthought: - **One actionable bullet per implication; lead with the action**, not the finding ("Protect frontline discretion when…", not "We found discretion matters"). - **Trace each bullet to the mechanism** so a reviewer can follow bullet → lever → evidence; if a bullet has no antecedent mechanism, it is decorative and will be cut. - **Calibrate certainty to the design** — an observational association is not a causal lever; hedge honestly and stay inside the scope conditions ("in turbulent environments," not "everywhere"). - **Address the right actor and level** — frontline supervisor vs. agency head vs. oversight body; a lever only one of them controls should name that actor. - **Avoid generic exhortation** ("managers should pay attention to X"); say what to *do differently*. ## Position within PAR's live theory conversations A contribution lands when it advances a recognized public-administration conversation rather than a private vocabulary. Name and engage the relevant tradition, and say what your mechanism adds or revises: - **Behavioral / individual level** — public service motivation (PSM), red tape and administrative burden, goal ambiguity, representative bureaucracy at the street level. - **Organizational / political level** — bureaucratic discretion, political control of agencies, performance management and accountability regimes. - **Institutional / values level** — public values and public-value creation, equity and procedural justice, legitimacy. - **System / network level** — collaborative governance, networks, co-production, and reform paradigms (NPM, post-NPM, digital-era / AI-era governance). "Context as a feature, not noise" means stating *which* of these settings your scope conditions invoke, and (for the strongest papers) bridging two levels with an explicit cross-level logic. ## Anti-patterns - "Hypothesizing after results are known" (HARKing) — state theory before tests; preregister where possible - A mechanism named but never made observable - Universal claims with no scope conditions, ignoring public-sector context - A practitioner "so-what" that does not follow from the mechanism (decorative Evidence for Practice) - Burying the argument under the empirics — the contribution paragraph must state it plainly ## Worked micro-example (before → after) **Before (thin):** "We find that managerial networking is positively associated with school district performance. Managers should network more." — an association plus a generic exhortation; no mechanism, no scope, decorative practice point. **After (PAR-grade):** - **Mechanism** — external networking lets public managers buffer environmental shocks and import resources and legitimacy; the **managerial lever** is how the manager allocates time between external and internal management. - **Observable implications** — performance gains concentrate where environmental turbulence is high and slack is low, and are absent where the task environment is stable (a test, and a *placebo*). - **Scope conditions** — local service agencies whose managers hold discretion over external engagement; the logic weakens under tight central control. - **Portability** — any PA subfield where managers mediate an organization–environment boundary can import the time-allocation lever. - **Practice so-what (Evidence for Practice seed)** — "In turbulent environments, protect managers' time for external engagement; in stable environments, redirect that time to internal management." The "after" version is portable *and* gives a manager something to change — both arms of the dual test. ## Output format ``` 【Core claim】one sentence 【Mechanism】the behavioral/organizational story + the managerial lever 【Observable implications】testable consequences → research-design 【Scope conditions】which level / sector / institutional setting 【Portability】who else in PA can use this argument 【Practice so-what】the Evidence-for-Practice seed 【Next】pubar-research-design ``` ## Supplementary resources - [`../../resources/external_tools.md`](../../resources/external_tools.md) — measurement and analysis tooling - [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — PAR scope and contribution expectations --- **Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Public-Administration-Review-Skills/skills/pubar-theory-building/SKILL.md`