amann-writing-style

Annals Writing Style — "Reviews with an Attitude" (amann-writing-style)

When to trigger

• The framework and evidence appraisal are settled and it is time to make the review read well
• The draft is descriptive and balanced but has no voice, no position, no agenda
• The opening buries the field's problem under throat-clearing or method machinery
• The abstract reads like a paper abstract ("we find…") rather than a review abstract

The Annals voice: authoritative + integrative + has attitude

Annals is read by management and organization scholars across subfields, plus allied audiences (organizational psychology, sociology of organizations). The voice is that of a trusted, fair expert who has read the whole field and is willing to say what it got right, what it got wrong, and what to do next. Four qualities define it:

1. Authoritative. Confident judgments about what is known, contested, and how good the evidence is. The reader wants the author's appraisal, not neutrality-as-evasion — but authority is earned by comprehensiveness and balance, never asserted.
2. Has attitude. This is the Annals signature. The review takes a critical, potentially provocative position grounded in the evidence: it names the field's blind spots, over-studied questions, and conceptual confusions. A balanced, accurate, positionless review is the most common stylistic miss.
3. Integrative, not descriptive. Sentences make streams talk to each other ("Whereas the X tradition treats … as …, the Y stream implies …"), reorganizing the field rather than touring it stream by stream.
4. Agenda-setting. The review points forward. The payoff is what becomes researchable after it — propositions, open questions, a future-research roadmap tied to the framework's empty cells.

The Annals opening arc

An Annals introduction differs from a research-paper intro and even from a generic review:

frame the field and its problem (what it studies, and the specific way it is fragmented/contradictory/confused) → why a review is needed now (a wave of work, a method shift, a hardened debate) → the organizing framework (the new way of seeing the field — the map the reader is given) → the position and the agenda (the "attitude" and what the review will conclude the field should do) → roadmap (brief).

State the framework and the position early. A review that withholds its organizing idea to a final section wastes the reader's time and reads as indecisive — the opposite of "attitude."

The abstract

A review abstract describes what the review does for the field: the literature, why a review now, the integrative framework, the critical position, and the agenda. Avoid "we hypothesize / we find a coefficient…"; that is a primary-paper abstract. (Confirm any length/format limits at submission via amann-submission; 待核实.)

Length and the reader's stamina

Annals reviews are long (~50 pages of text; 检索于 2026-06；以官网为准), and length is a privilege, not a license. Every section must earn its pages by advancing the argument about the field; confirmatory coverage (the lower tiers of amann-evidence-standards) belongs in compact citation clusters, not paragraph-length summaries. Use strong section architecture that mirrors the framework, periodic "where we are / where we go next" cues, and subsection summaries so a reader who puts the review down can re-enter without rereading.

Checklist

• Opening follows the arc: field+problem → why now → framework → position+agenda → roadmap
• The framework and the critical position are stated early, not withheld to the end
• The review has attitude: it names blind spots / over-studied questions / confusions, grounded in evidence
• Prose integrates (streams in dialogue), not describes (stream-by-stream tour)
• A forward-looking agenda is explicit and tied to the framework's gaps
• Technical material introduced intuition-first; jargon defined or avoided for cross-subfield readers
• Section architecture mirrors the framework; periodic signposting present
• Abstract describes the review's contribution to the field, not a single finding

Anti-patterns

• The annotated-bibliography drone: "Smith (2010) found… Jones (2012) found…" with no connective argument
• A balanced, accurate, positionless review — coverage without the Annals "attitude"
• Opening with method/notation before the field's problem and stakes
• Withholding the framework or the conclusions until the final section
• Closing with a generic "more research is needed" instead of a structured, framework-tied agenda
• A primary-paper abstract ("we find…") on a review; neutrality-as-evasion in place of appraisal

Output format

【Opening arc】field+problem → why-now → framework → position+agenda → roadmap? Y/N
【Framework early】organizing idea stated up front? Y/N
【Attitude】names blind spots / over-studied / confusions, evidence-grounded? Y/N
【Integrative prose】streams in dialogue, not toured? Y/N
【Agenda】forward-looking, tied to framework gaps? Y/N
【Accessibility】intuition-first; jargon controlled for cross-subfield readers? Y/N
【Abstract】review-style (contribution to the field), not a single finding? Y/N
【Next skill】→ amann-editor-strategy / amann-submission