--- name: ppsych-editor-strategy description: Use when working with the Perspectives on Psychological Science (PoPS) editor and editorial team — proposal-stage scope, what review referees of a perspective evaluate, suggesting reviewers, and the author–editor relationship. Plans the interaction; it does not run the submission preflight (ppsych-submission) or draft the response letter (ppsych-revision). --- # Editor & Editorial Strategy (ppsych-editor-strategy) ## When to trigger - An editor reacted to a proposal and you are shaping scope before drafting - You want to anticipate what PoPS referees of a *perspective* will push on (different from a study) - You must suggest reviewers for submission and want to do it well - You are calibrating how the PoPS review cycle and the bimonthly schedule work ## Who you are working with at PoPS PoPS is published by **SAGE** in partnership with **APS**, with an **Editor-in-Chief** (Arturo Hernandez, University of Houston, since 2024-12-01;web-verified 2026-06-22;re-verify before relying) leading a board of associate/handling editors across psychology's areas (检索于 2026-06;以官网为准). The relationship runs through the **handling editor** the EiC assigns. Because PoPS mixes submitted and invited/cooperative work, the dynamic varies by route: for a **stand-alone** piece you may pitch a proposal first (de-risks fit, not acceptance); for **cooperative** work (special issues, adversarial collaborations) the editor approves the *structure* before assembly. In all cases acceptance is **not** automatic — every manuscript, solicited or not, goes through the **same review** (检索于 2026-06;以官网为准). ## How review differs for a perspective PoPS referees do **not** check an identification strategy or replicate a result — there is no study of the author's own. They evaluate the piece **as a perspective**: | Referee question | What they are really checking | |------------------|-------------------------------| | Is it broad enough / does it carry a superordinate message? | scope fit — not a single study dressed as a review (`ppsych-topic-selection`) | | Is there a real organizing argument? | the spine vs. an annotated bibliography (`ppsych-organizing-framework`) | | Is the coverage comprehensive across areas? | the saturation/coverage from `ppsych-literature-synthesis` | | Is it balanced and fair? | even-handedness across camps; no self-promotion; calibrated reform (`ppsych-comprehensiveness-and-balance`) | | Is it accessible and provocative? | can a cross-area psychologist follow and find it worth arguing about (`ppsych-writing-style`) | | Is the open-science layer exemplary? | deposits, protocol, reproducibility for meta-science (`ppsych-transparency-and-reproducibility`) | Referees of a PoPS piece are often **the surveyed authors or the camps being weighed** — the people whose work you appraise will read how you appraised it. This makes balance and accurate attribution strategic, not just ethical. ## Suggesting reviewers (a controllable lever) PoPS asks authors to **suggest objective reviewers** — name a minimum of five, excluding mentors, close colleagues, and collaborators (检索于 2026-06;以官网为准). Use this well: - Choose scholars across the **areas you integrate**, so coverage is judged by people who would notice a siloed omission. - Include credible representatives of **rival camps** — a balanced reviewer slate signals confidence in your even-handedness. - Disclose genuine conflicts; suggesting a collaborator as "objective" backfires. ## Scope and relationship management - **Settle scope at the proposal stage** where it is cheapest to change — confirm boundaries with the editor before months of reading (especially for cooperative work). - **Negotiate, don't capitulate, on coverage asks.** If a referee wants an added literature, assess whether it fits the spine; propose where it goes or explain why it is out of scope — a perspective should stay concise. - **Surface conflicts of interest.** If a likely referee is a central author you must critique, tell the editor. - **Keep a coverage ledger.** A short record of what is in scope and why (and what was deliberately excluded) lets you answer "why not X?" with a decision already made. ## Checklist - [ ] Route identified (stand-alone vs. cooperative); scope settled with the editor at the proposal stage where possible - [ ] Anticipated the six perspective-referee questions (breadth, framework, coverage, balance, accessibility, open science) - [ ] A reviewer slate of ≥5 objective scholars across integrated areas + rival camps, excluding collaborators (检索于 2026-06) - [ ] Coverage-expansion asks evaluated against the spine and conciseness before agreeing - [ ] Conflicts of interest (referees who are reviewed authors) flagged to the editor - [ ] Attribution and appraisals double-checked, knowing reviewed authors may referee - [ ] Current EiC / handling-editor structure re-confirmed on the official pages (volatile) ## Anti-patterns - Treating a warm proposal response as guaranteed acceptance — every manuscript is reviewed identically - Suggesting mentors/collaborators as "objective" reviewers (against policy; transparent to editors) - A reviewer slate from one area only — invites a "siloed coverage" critique you could have pre-empted - Accepting every "please also cover…" until the perspective loses its spine and conciseness - Mischaracterizing a reviewed author's work when that author may be your referee - Asserting the current EiC / board / reviewer rules from memory rather than the live SAGE/APS pages ## Output format ```text 【Route】stand-alone / cooperative; scope settled with editor? Y/N 【Referee anticipation】breadth / framework / coverage / balance / accessibility / open-science — prepared each? Y/N 【Reviewer slate】≥5 objective, cross-area + rival camps, no collaborators? Y/N 【Coverage asks】evaluated against spine + conciseness; accept/push-back plan? Y/N 【COI】reviewed-author referees flagged to editor? Y/N 【Source status】current EiC / board / reviewer rules re-confirmed on PoPS pages? Y/N · 待核实 【Next step】→ ppsych-submission (preflight) → ppsych-revision (after the decision) ```