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.