jppm-writing-style

name	jppm-writing-style
description	Use when drafting or revising the prose of a Journal of Public Policy & Marketing (JPP&M) manuscript — the policy-problem-led introduction, the 200-word abstract, dual-audience clarity, and the evidence-not-advocacy voice. Polishes the writing; it does not change design, analysis, or framing decisions.

Writing Style (jppm-writing-style)

When to trigger

• The introduction opens with a literature gap instead of the policy problem
• The abstract never says who should do what differently
• Method jargon (ATTs, bandwidths, moderated mediation) floods sections a practitioner must read
• The tone slips from findings into editorializing about what government "must" do
• Prose is the last bottleneck — estimates, framing, and exhibits are stable

Write for the reader who can act

A JPP&M paper is read by marketing academics, by scholars in law and policy, and — if it succeeds — by people inside agencies and NGOs. The prose contract: the policy problem carries the story, the evidence carries the authority, and any reader should be able to extract the actionable takeaway without decoding the econometrics. That means plain-language topic sentences, technical depth layered underneath rather than in front, and a strict separation between what the data show and what the authors prefer. The manuscript is double-spaced, at most 50 pages including everything, with a 200-word unstructured abstract and at least three keywords (per the AMA journals guidelines; re-check current specifics on ama.org).

The JPP&M introduction, beat by beat

1. The policy problem, concretely. Open with the marketplace harm or regulatory decision — the pending rule, the enforcement gap, the population being hurt — with a fact and a source, not throat-clearing about "growing interest."
2. Why existing knowledge cannot settle it. What the marketing-and-policy literature and the regulatory record establish, and the decision-relevant unknown that remains.
3. What this paper does. The design and setting in two or three sentences, in words a policy reader follows ("we compare purchases in states that adopted the rule to matched states that did not").
4. What was found, with magnitude. The headline estimate in decision units, including the heterogeneity or backfire result if it matters.
5. Who should do what. One or two sentences previewing the stakeholder actions the findings support — the intro's version of the Policy Contribution Statement.

The abstract

Two hundred words must state the policy question, the method in one clause, the key finding with direction and rough magnitude, and the implication for named stakeholders. Editors desk-screen from the abstract plus the Policy Contribution Statement; an abstract that ends at "implications are discussed" invites the bolted-on-policy suspicion.

Voice: evidence, not editorial

• Verbs match identification: "shows/reduces" for well-identified estimates; "suggests/is consistent with" for correlational or lab-only evidence.
• No advocacy adverbs: "clearly," "obviously," "alarmingly" signal a brief, not a study.
• Respect the other side of the ledger: costs to firms, implementation burden, and speech or preemption constraints get honest sentences, not dismissals.
• Define instruments on first use: not every reader knows what the Green Guides or a consent order is; not every reader knows what an ATT is either. One clause each.
• Vulnerable populations are people: person-first, non-stigmatizing language; describe constraints, not deficiencies.

Sentence-level craft

• Lead paragraphs with the claim, follow with the evidence; never make the reader assemble the point from a stack of citations.
• Keep one term per construct — a "warning," "disclosure," and "label" that are the same thing multiply confusion.
• Numbers in text carry their units and comparison ("a 2-percentage-point drop from a 14% base"), never naked coefficients.
• Cut the methods-section prose that repeats the table; cite the exhibit and interpret it instead.

Checklist

• The intro opens on the policy problem with a sourced fact
• The decision-relevant unknown is stated before the method
• Headline results appear in decision units in both intro and abstract
• Abstract ≤200 words: question, method, finding, stakeholder implication
• Claim verbs are calibrated to identification strength throughout
• No advocacy tone; trade-offs acknowledged in the discussion
• Jargon layered: any section a practitioner needs is readable without training

Anti-patterns

• Gap-first opening: "despite growing interest, little research…" before any reader knows why to care
• "Implications are discussed": an abstract that hides the takeaway
• Brief-speak: prose whose conviction outruns its confidence intervals
• Jargon front-loading: estimator names in the introduction, harms in the appendix
• Term drift: the same instrument renamed section by section
• Deficit framing: writing about vulnerable consumers as problems rather than as people the market underserves

Output format

【Intro lead】policy problem + sourced fact in paragraph one? [Y/N]
【Unknown】decision-relevant gap stated pre-method? [Y/N]
【Abstract】≤200 words with question/method/finding/actor? [Y/N]
【Voice audit】verbs calibrated; advocacy adverbs removed? [Y/N]
【Dual-audience pass】practitioner-readable sections confirmed? [Y/N]
【Next skill】jppm-submission