Communication Strategy and Operations Officer

You are the junior officer in the information environment — the lieutenant who is learning to see the battlefield as a contest of narratives and perceptions before you are trusted to shape either. The IO cell runs on analysis and coordination; your job is to build the habit of both before you own anything.

You commission through OCS or NROTC and complete TBS at Quantico before accessing the 4502 community. Your initial billet is inside an IO cell at the battalion, regimental, or MEF level — functionally embedded in the S3 or G3 planning shop, cross-coordinating with the public affairs officer, the MISO element, and the fires cell on a daily basis. The day-to-day work is less glamorous than the community's résumé suggests: you are drafting IO annexes to OPORDs, attending targeting meetings to understand how non-kinetic effects integrate with fires and maneuver, building information environment assessments from open-source reporting and S2 products, and maintaining the information effects synchronization matrix the senior IO officer uses to brief the commanding general. You will track adversary information operations — disinformation, narrative exploitation, influence activity — and you will learn to separate observable effects from comfortable assumptions before you are allowed to brief either to the commanding officer. The gap between theory (the joint doctrine your MOS school taught) and the unit's actual IO capacity — resources, bandwidth, command interest — is the first thing the senior 4502 will make you understand. You will also write white papers and INFOOPS coordination requests that go nowhere for months, and you will learn patience as a professional skill.

• 01Draft an IO annex to a battalion or regimental OPORD that integrates the information environment assessment, specified non-kinetic tasks, and coordination requirements with PA, MISO, cyber, and fires elements — per JP 3-13 and the MEF SOP — tight enough that the IO cell chief does not rewrite it before the targeting brief.
• 02Build and maintain the information effects synchronization matrix: specified IO tasks, responsible elements, supported maneuver units, assessment indicators, and MOE/MOP linkage — the tool the IO cell chief uses to brief synchronization to the commander.
• 03Conduct an open-source information environment assessment using publicly available media, social platforms, and adversary-facing messaging to describe the current narrative environment and support the S2 threat picture — no fabricated indicators, no conclusions without observable evidence.
• 04Coordinate non-kinetic effects requests across the MAGTF information-related capabilities (IRCs) — PA, MISO, cyber, EW, PSYOP — through the proper coordination channels, tracking tasking status and deconflicting effects with the fires cell.
• 05Brief the IO synchronization products to the S3 or G3 using the information environment framing the commander expects: threat activities, friendly information actions, assessment indicators, and the gap between intended and observed effects.
• 06Apply the law of armed conflict (LOAC) and applicable policy constraints to proposed information actions — know what JP 3-13 permits at what echelon, what requires higher approval, and what is flatly prohibited — before any IO product leaves the planning cell.

• —JP 3-13 — Information Operations (the joint doctrinal authority for IO planning, synchronization, and assessment; the IO annex structure the MEF G3 expects is built from this document).
• —JP 3-61 — Public Affairs (the deconfliction doctrine between IO and PA — the PAO coordination requirement is not optional and the senior IO officer will ask if you have read this before you brief the synchronization matrix).
• —MCWP 3-32 — Marine Air-Ground Task Force Information Operations (the Marine Corps institutional implementation of JP 3-13; the IO planning products the MEF G3 evaluates are built to the standards in this manual).
• —DoD Directive 3600.01 — Information Operations (the policy authority that governs what IO actions require SecDef or higher approval; a 4502 lieutenant who does not know the approval thresholds will be corrected at the targeting board).
• —MCDP 1 — Warfighting (the foundational document for understanding maneuver warfare and commander's intent — IO planning that is not nested in the commander's scheme of maneuver is a product the G3 will not use).
• —MCO 1610.7 — Performance Evaluation System (your FitRep is written by the IO cell chief or the G3; understand the relative-value ranking structure before the first reporting cycle).

• —TBS graduate (The Basic School, Quantico, six months) — the IO community is small; your TBS class standing and leadership read arrive at the gaining unit before you do.
• —MOS school completion (IO-related coursework at Quantico or the joint schoolhouse) — the MEF IO cell chief assumes you have the doctrinal baseline; arriving without it means remedial self-study on the IO cell's time.
• —IO annex submitted to the IO cell chief without doctrinal error in the task, effects, and synchronization sections — one annex that requires a full rewrite at the cell chief level becomes the entry in the standard the next annex is compared against.
• —Active coordination account and working relationship with the PAO and MISO officer within the first 60 days — IO deconfliction is relationship-dependent; the lieutenant who waits for a crisis to introduce themselves has already failed the coordination requirement.
• —O-1 to O-2 is timeline-driven; O-2 to O-3 (Capt) is a board — pull current MMPB promotion board releases before acting on rumored community selection rates.

• —Submitting an IO annex that specifies effects without a connected assessment indicator. The targeting board will ask "how will you know if this worked?" — if the annex cannot answer that question, the IO officer gets an immediate re-do and a reputation for producing unassessable products.
• —Conflating public affairs with information operations in a planning product. PA is audience-facing truthful communication; IO is broader and includes non-kinetic effects. A planning document that merges the two in a way that implies PA is an IO tool draws a legal and policy flag from both the PAO and the JAG at the targeting board.
• —Briefing an information environment assessment to the commanding officer that contains an indicator you cannot attribute to an observable source. The S2 will ask for the raw intelligence trace; "assessed" and "observed" are not the same word in a targeting brief, and the IO officer who uses them interchangeably loses credibility in the room.
• —Missing a required coordination action with the EW officer or cyber element before publishing an IO synchronization product. Non-kinetic effects in the electromagnetic spectrum need EW deconfliction; an IO product that schedules effects the EW officer cannot execute — or that conflicts with a cyber action — becomes a synchronization failure with your name on the brief.
• —Failing to flag a proposed IO action that requires higher-than-MEF approval. DoD Directive 3600.01 sets specific thresholds; the IO cell chief will not be the one in front of the commanding general explaining why an unapproved action was planned — the 2ndLt who drafted it will.

The good IO lieutenant is the officer the IO cell chief hands the synchronization matrix to before the targeting board because the matrix is accurate, sourced, and the coordination with PA, MISO, and EW is already done. By the end of the first deployment cycle, the S3 is asking the IO lieutenant for the information environment read at the morning update — not because the brief is expected, but because it is useful. The senior IO officer is already writing the Capt captain's career course recommendation for the lieutenant whose IO products the MEF G3 actually uses.

You are the officer who owns the information environment for the commander. The maneuver plan shapes terrain; you shape perception, narrative, and the adversary's decision calculus. At Maj, you are advising the commanding general — and every IO product that leaves your cell reflects on the command's credibility as much as on yours.

Your captain arc runs through post-lieutenant staff utilization — G3 IO planner, MEF information operations coordinator, or joint information operations billet — before the Key Developmental billet as IO cell chief or MEF information operations officer. As IO cell chief you own the full scope of information operations planning for the MAGTF: the information environment assessment, the IO annex to the OPORD, the targeting synchronization of all information-related capabilities (PA, MISO, cyber, EW, PSYOP, and key leader engagement), and the assessment framework that tells the commanding general whether the information campaign is achieving effects. You sit at the targeting board as the non-kinetic fires voice. You deconflict IO tasks with the kinetic fires cell, the maneuver commanders, and the joint information operations element when the MAGTF is operating under a joint task force. You write the IO inputs to the commanding general's decision brief — which means you are writing to the specific intellectual and operational sensibility of a general officer who has seen bad IO products and does not forget them. As MEF information operations officer at the major tier, the scope expands to multi-battalion coordination and you are the officer the commanding general asks when an adversary information operation surfaces in the AO that the MAGTF did not plan for. The MMPB Maj board is the first genuinely competitive gate in the 4502 career; the KD FitRep and the EWS or Command and Staff selection are the documents the LtCol board weighs in a community small enough that the peer-group ranking resolves quickly.

• 01Write and brief a MEF-level IO annex to a MAGTF OPORD: information environment assessment, desired effects by phase, information-related capability task matrix, synchronization timeline, and assessment indicators — per JP 3-13 and MCWP 3-32 — at a quality the commanding general briefs to the joint task force commander without revision.
• 02Lead the information operations synchronization process at the targeting board: present the non-kinetic fires synchronization matrix, deconflict IO tasks with kinetic effects, coordinate EW and cyber integration, and answer the commander's "so what" question for the information campaign in the current phase.
• 03Advise the commanding general on adversary information operations: characterize the threat's information activities, assess the information environment impact on MAGTF operations, and recommend friendly IO actions that counter or exploit adversary messaging — in the language the general officer uses to make decisions, not the language of joint doctrine.
• 04Manage and develop junior 4502 officers and IO-affiliated SNCOs: initial counseling, event-driven FitRep entries, T&R task tracking, and a relative-value ranking that accurately reflects the section's capability and the officer's potential — the MMPB assignment monitor reads the FitRep package before the board does.
• 05Coordinate IO actions with the joint information operations element (JIOE) or theater information operations coordination cell (TIOCC) when the MAGTF operates under a joint task force — understand which effects require joint approval authorities and which the MEF IO officer can task unilaterally.
• 06Build and maintain the information effects assessment framework: MOE and MOP per phase, data collection plan, reporting cadence, and the analytical discipline to distinguish observed effects from assumed ones in the commanding general's update brief.

• —JP 3-13 — Information Operations (the doctrinal authority you now execute against at MEF scale; the IO cell you lead is responsible for implementing this doctrine across all information-related capabilities in the MAGTF).
• —MCWP 3-32 — Marine Air-Ground Task Force Information Operations (the Marine Corps implementation document; the IO annex standard the MEF G3 evaluates and the commanding general signs is built to this spec).
• —JP 3-61 — Public Affairs (the deconfliction boundary between IO and PA that you manage at the MEF level — the PAO coordination requirement that a 2ndLt could miss you cannot; the JAG reads both products and so does the MEF IG).
• —DoD Directive 3600.01 — Information Operations (the approval authority thresholds that determine what IO actions you can authorize at MEF level versus what requires joint task force or SECDEF approval; the legal and policy constraints the commanding general expects you to have memorized).
• —MCO 1610.7 — Performance Evaluation System (you now write FitReps on the IO cell lieutenants and the senior IO SNCO; the relative-value ranking you assign is the input the MMPB Capt board uses for the community's competitive range).
• —MCO 1400.32 — Marine Corps Promotion Manual (the Maj board mechanics, the IPZ/BZ/AZ math, and the FitRep relative-value weighting for the 4502 community — understand the board construct before the KD FitRep cycle closes).
• —MCO 1540.8 series — Officer Professional Military Education; EWS and Command and Staff College catalog (the PME gates the LtCol board reads for the 4502 community in the context of a small peer-group promotion cohort).

• —IO cell chief or MEF information operations officer KD tour — 18 to 24 months, slated through MMPB. The single FitRep the Maj board weights as heavily as the platoon commander tour mattered at O-2. One weak relative-value ranking in the KD billet in a community this size is not survivable on the LtCol board.
• —IO annex accepted at the MEF G3 and commanding general level without major doctrinal revision — the G3 staff's read of the IO annex product is the first independent assessment of the IO cell chief's planning competency at the MEF level.
• —Adversary IO assessment brief delivered to the commanding general that influences a decision — a clean operational track record means the general asked for the IO read before the brief was scheduled; that is the standard the MEF IO officer is measured against.
• —Maj board at the IPZ window — pull the current MMPB promotion board release for the actual FY selection rate for the 4502 community; the cohort is small and the peer-group relative-value ranking resolves faster than in a large-community MOS.
• —Expeditionary Warfare School or Command and Staff College resident selection — the PME credential the LtCol board reads as the institution's assessment of the officer's potential in a community too small to have a statistical selection rate.
• —Joint information operations billet or TIOCC tour between KD assignments — the career-broadening assignment that signals operational versatility to the LtCol board and to the MMPB assignment monitor who is already thinking about the colonel's slate.

• —Delivering an information environment assessment to the commanding general that conflates adversary intent with adversary capability. A general officer who asks "how do you know they intended that?" and receives an uncertain answer hears that the IO cell is not doing analysis — it is doing storytelling. Separate what is observed from what is inferred, every time, in every brief.
• —Publishing a MEF IO synchronization product that schedules an IO action without completing the approval authority check against DoD Directive 3600.01. An unapproved IO action discovered by the joint task force J3 becomes a commander's inquiry with the IO cell chief's name in the subject line — not the action officer who drafted it.
• —Failing to deconflict IO tasks with the kinetic fires cell before the targeting board. An IO action that interferes with a kinetic effect — or that the fires cell is simultaneously targeting through a different means — surfaces at the board as an IO synchronization failure, and the IO officer is the one who owns it.
• —Treating the PA coordination requirement as a formality. PA and IO share the information environment and legal deconfliction is real. An IO product that is later argued to have influenced US domestic audiences or that blurred the PA/IO boundary in a way the JAG flags creates a command-level policy problem with the IO cell chief's signature on the originating document.
• —Underestimating the FitRep relative-value conversation with the commanding officer. In a community as small as 4502, the difference between a #1 of 4 captains and a #3 of 4 captains on the KD FitRep is not a rounding error — it is a structural disadvantage at the Maj board. The IO cell chief who does not understand how the ranking works and does not advocate for accurate placement ends up in the wrong tier of a peer group they out-performed in the field.
• —Coasting through the post-KD MEF staff billet. The MEF G3 is reading the IO planning product; the commanding general's intelligence officer is reading the information environment assessments. A captain who treats the staff billet as wind-down after the KD tour arrives at EWS selection with a flat second act — and in this community, a flat second act looks like a gap.

The good IO cell chief is the captain the commanding general quotes from at the MAGTF planning conference. Not "the IO annex says…" — the general knows who built the product, and when the adversary information operation surfaced in the AO two weeks into the operation, the IO cell had already framed the response in the morning brief before the G3 asked for it. The PA officer and the MISO officer both have the IO cell chief in their phones because the coordination happens in the hallway before the targeting board, not as a correction at the board. The two IO lieutenants in the section know what a sound assessment looks like because the cell chief ran actual section training events and gave them honest counseling — not performance theater — and their FitRep packages reflect work the MMPB assignment monitor recognizes as genuine differentiation in a small community. The good just-pinned major is the officer whose joint IO billet produced a TIOCC product the combatant command J3 actually used, whose Command and Staff application arrived with a PRO recommendation from both the MEF IO officer and the commanding general, and whose MMPB assignment monitor called before the LtCol board convened — because the board outcome was not a question worth asking.