Core Definition (BLUF)

The psychological operations (PSYOP) process is the systematic method for planning, analyzing, developing, designing, producing, distributing, disseminating, managing, and evaluating PSYOP products and actions presented to selected foreign target audiences (TAs). FM 3-05.301 organizes this as a seven-phase development process nested under supported-unit planning. Modern force language often says MISO; the process logic remains this TTP spine. Parent concept: Military Information Support Operations.


Doctrinal Framework

  • Primary: FM 3-05.301 (process TTP; original publication carries distribution restriction - this note is a digest)
  • Keystone context: FM 3-53 (MISO)
  • Related: FM 3-05.302 tactical PSYOP; evaluation and production chapters in 3-05.301
  • Coverage: draft on hierarchy, seven phases, TAA steps, evaluation. Not a product-design cookbook or approval-authority matrix for real operations.

Mechanics

Hierarchy of effort

Supported mission
 └─ MISO/PSYOP plan
     └─ Program (one PO)
         └─ Supporting program (one SPO)
             └─ Series (one TA × one SPO)
                 └─ Products and actions
TermDefinition in process use
POPsychological Operations objective: measurable desired behavior/attitude change
SPOSupporting objective: specific response that contributes to a PO
SeriesAll products/actions for one TA to achieve one SPO
TAAWTarget audience analysis work sheet - base document for series development
PAWProduct/action work sheet - design and production control for a single product/action

Seven phases (development process)

PhaseWork
I. Plan development and managementMDMP integration with supported unit; POs/SPOs/PTAL; continuous programming (re-phase and re-prioritize as evaluation and situation change)
II. Target audience analysisTAA process on each TA–SPO pair; complete TAAW
III. Series developmentBuild the series concept from the TAAW
IV. Product designPAWs, prototypes, media selection
V. ApprovalInternal review then external approval (program vs product delegation per order/policy)
VI. Production and disseminationProduce, distribute, disseminate; coordinate air/print/broadcast/face-to-face means
VII. EvaluationPretest; posttest; impact assessment; adjust fire

Phases run in parallel across series. One series may still be in TAA while another is disseminating.

Target audience analysis process (core of Phase II)

Doctrine walks TAA roughly as:

  1. Identify / refine the TA - secondary groups and categories beat aggregates; name geography, demographics, role.
  2. Define the TA completely - enough specificity that conditions and vulnerabilities can be researched.
  3. Conditions - elements affecting the TA with limited TA control, relevant to the SPO. Model as stimulus → orientation → behavior (events/issues/characteristics; attitudes/beliefs/values; observable response).
  4. Vulnerabilities - needs arising from conditions that the TA will strive to satisfy; the leverage for influence (biological and social needs; cultural variation).
  5. Further TAA factors (in full TAAW practice): lines of persuasion, susceptibility, accessibility, effectiveness - whether the TA can actually deliver the SPO behavior.

Conditions research uses secondary sources first (studies, intelligence holdings, open sources), then primary research in theater. Source every condition for update and credibility.

TA types with process implications:

TypeNote
AggregateRarely good (e.g. whole city) - too much internal variance
Secondary group / categoryPreferred when well defined
Center of gravity (audience sense)High impact if persuaded; often low susceptibility
Key communicatorIntermediate TA that carries credibility to the primary TA

Evaluation (Phase VII spine)

  • Pretest: check prototype understanding and reaction before full dissemination.
  • Posttest / impact assessment: did behavior or indicators move toward the SPO?
  • Measures of performance (did we disseminate?) are not measures of effectiveness (did the TA change?).
  • Results feed programming (Phase I continuous segment).

Supported-unit MDMP touchpoints

  • Build and maintain a PSYOP estimate (situation, media infrastructure, key target sets hostile/friendly/neutral, supportability of friendly COAs).
  • Derive specified/implied PSYOP tasks from higher orders.
  • Write POs/SPOs that survive cradle-to-grave phasing with the maneuver plan.
  • Provide COA supportability from a MISO perspective - not separate “PSYOP COAs” that ignore the supported scheme.

Application

Minimum process discipline for any influence series:

  1. Supported mission → PO → SPO (behavior) → TA (named) before product ideas.
  2. TAAW complete enough to defend lines of persuasion.
  3. Series of mutually reinforcing products/actions, not a single product.
  4. Approval path identified before production spends scarce print/air.
  5. Pretest if contact with TA analogs is possible; always plan posttest indicators.
  6. After action: update TAA files and programming priorities.

Detachment planners use this process when writing or reviewing MISO annexes, when integrating tactical MISO teams, and when red-teaming adversary influence (invert: what SPO are they seeking from which TA?).


Parent: Military Information Support Operations.

Sibling: Military Deception.

Analytic inputs: IPOE Process, PMESII-PT, ASCOPE, Pattern of Life.

Will/legitimacy targets: Center of Gravity.

Campaign homes: Foreign Internal Defense, Unconventional Warfare.


Failure Modes

  • Starting at Phase IV (product design) with no TAA.
  • SPO written as a theme (“support democracy”) rather than a behavior.
  • TA as aggregate or as a single elite with zero accessibility.
  • Pretest skipped; posttest never resourced.
  • Series that contradicts friendly actions on the ground.
  • Treating dissemination volume as effectiveness.

Key Connections