A training guide for officers across all warfighting domains — deconstructing single-service habits and rebuilding native joint TTPs that leverage the full spectrum of combined arms.
The primary question is never "What can my platform do?" It is "What effect must be achieved, and which combination of capabilities across all domains will produce it most efficiently?" Every TTP must be rooted in desired effects.
Land, Sea, Air, Space, and Cyber are not fiefdoms — they are physical or virtual environments in which capabilities operate. No domain is inherently decisive. Advantage accrues to the force that integrates effects across all five simultaneously.
A peer adversary that integrates multi-domain effects faster than you can react has already won the engagement. Joint TTPs must compress the time between sensing, deciding, and acting across service boundaries — not just within them.
Each service enables the others. Naval fires suppress threat air defense, allowing land forces to maneuver; land ECM degrades adversary ISR, allowing naval forces to approach undetected. The feedback loop is the TTP.
The deepest challenge is cultural. Officers trained entirely within one branch develop platform-centric mental models that persist even when assigned to joint billets. This guide systematically identifies and replaces those reflexes.
Joint effectiveness collapses when components operate on different sensor timelines. Shared, authoritative, latency-matched information is not a staff aspiration — it is a tactical requirement underpinning every scenario in this guide.
| Platform-Centric Reflex | Capability-Centric Approach | Domain(s) Integrated | |
|---|---|---|---|
| "Call in the fighters to suppress that SAM site." | → | Suppress / degrade the adversary IAD capability via the fastest available path: cyber intrusion, EW jamming, land-based SEAD, naval fires, or manned strike — whichever creates the required effect in time. | Air Cyber Sea |
| "We need boots on the ground to hold the town." | → | Determine what effect "holding" requires: physical presence, surveillance dominance, fires on approach routes, or information operations denial. Select the minimal footprint that achieves those effects. | Land Air Space |
| "The ship needs to close range to engage." | → | Extend the engagement envelope using space-based targeting, land- or air-relayed data links, and cyber-enabled fire control — the platform maneuvers only when no other path achieves the effect. | Sea Space Cyber |
| "I'm waiting on air tasking order approval to support." | → | Pre-authority delegation, effects synchronisation matrices, and standing rules of engagement allow immediate fires integration without sequential bureaucratic clearance when time is critical. | All domains |
| "That's a Navy target — not my lane." | → | In a joint operating area the first capable system to hold the target at risk fires it — assignment by proximity and effect, not by service ownership. | All domains |
| "GPS is down — we can't operate until it's restored." | → | Trigger GNSS-denied TTP immediately: inertial navigation, terrestrial ranging, space-based backup constellation, and mesh-networked peer positioning across ground, air, and maritime elements. | Land Air Space Cyber |
| "Cyber is a strategic tool — not tactical." | → | Tactical cyber effects (comms denial, sensor spoofing, C2 disruption) can collapse an adversary's OODA loop at the tactical level — they must be pre-coordinated into the fires plan like any other effect. | Cyber All domains |
A coastal industrial target is ringed by four SA-21 batteries, a command radar node, and OTH radar offshore. Platform-centric planning produces a 36-aircraft SEAD/DEAD package with unacceptable attrition. The joint fires cell must collapse the IAD through layered effects.
The adversary IAD is a system — it has C2 links, power, data links, and radar emissions. Severing the system's nervous system (cyber), blinding its eyes (EW), decapitating its command (naval fires), and then killing its residual effectors (air) is more effective and cheaper in aircraft and aircrew than a frontal all-air assault on its nodes.
Effects must be sequenced and timed as a system. Ask: what degrades first so that subsequent effects are easier? The answer almost always crosses domain boundaries.
MEU approaches a defended shoreline. MAGTF organic fires (AV-8B, ACE Cobras, 81mm mortars) are insufficient to suppress three CDCM batteries and mobile artillery. Space-based radar detects artillery relocation cycles. Navy fires ships are 60 nm offshore. Land-based Army rocket artillery is pre-positioned 80 km away.
The MAGTF's self-sufficiency doctrine was designed for expeditionary operations where joint support was uncertain. When joint support IS available and IS coordinated, insisting on organic self-sufficiency wastes joint enablers and risks unnecessary Marine casualties. The evolved TTP is to plan jointly first, with organic as the fallback.
Information from a superior domain (space-based radar) must be pushed to the lowest capable echelon that can act on it — not retained at joint HQ level where it becomes a planning curiosity rather than a tactical weapon.
A surface action group must strike an adversary logistics hub. GPS-guided TLAM, JDAM, and artillery precision fuse functions are degraded. The jamming source is mobile. Adversary fighter cover is active. The joint fires cell has 6 hours to restore precision or find non-GPS strike paths.
GPS is a single point of failure in current service TTPs. The adversary knows this and will attack it. Every fires plan must include GPS-denied alternatives as primary — not as contingency. The joint force that plans for this first will dominate the precision fires window when GPS is denied to both sides.
Redundancy in precision is a joint responsibility: no single component has enough alternative PNT sources, but the joint force collectively does. This only works if the data chains are established before conflict, not improvised during it.
The adversary theatre logistics command hub is identified inside a populated urban area. Physical strike is approved only if civilian proximity analysis passes. Cyber cell has persistent access to the facility's SCADA and command systems. Electronic archives contain high-value intelligence. The joint commander wants maximum effect with minimum signature.
Cyber effects should not wait at the back of the fires queue because approvers cannot translate their effects into military terms. The joint force must invest in developing a common effects vocabulary that allows cyber, EW, and kinetic options to be evaluated and approved in a single effects assessment framework.
Cyber and EW can achieve effects faster, cheaper, and with lower escalation risk than kinetic fires in many scenarios — but only if they are planned first, not as a last resort after kinetic options have already been declined.
Space-based infrared sensor detects launch preparation signature. The battery has moved to a new location not in the current air tasking order target database. Available shooters: naval vessels (Tomahawk), air force strike on 45-min alert, and Army ATACMS battery within range. C2 chain for nomination, prosecution, and BDA must complete in under 10 minutes.
The kill chain for time-critical targets must be pre-built, pre-approved, and pre-exercised. Any step that requires human nomination, approval, or translation during a 12-minute window will cause that step to become the point of failure. The joint TTP is to push decision authority down to the lowest appropriate level and automate the data link from sensor to fires cell.
Kill chain compression is not a technology problem — it is primarily an authority delegation and pre-planning problem. The technology exists. The C2 framework and standing authorities must match the speed the technology enables.
3rd Brigade Combat Team is isolated on a peninsula. Road routes are interdicted by adversary ATGM teams and controlled airspace prevents C-130 delivery. A naval vessel is 20 nm offshore with 600 tonnes of supplies. UAS delivery capability is available but payload-limited. Space-based weather provides 4-hour wind windows over the beach.
Logistics is a warfighting function — not an administrative one. When the adversary targets the logistics system as part of their campaign, the response must be joint. Single-service logistics planning is a vulnerability that peer adversaries will specifically exploit. Joint logistics plans must be as carefully integrated as joint fires plans.
Every alternative delivery mode must be coordinated and pre-authorised in the logistics annex before operations begin. The battle position is always known; the supply path should be planned with equal rigour as the manoeuvre plan.
| SCENARIO | COST ↓ | RISK ↓ | SCHEDULE ↓ | CRITICAL ENABLER | SINGLE-SERVICE FAILURE MODE |
|---|---|---|---|---|---|
| 01 · Iron Lattice SEAD/DEAD |
−62% | −78% | −44% | Cyber pre-fires sever IAD C2 before kinetic action | 36-aircraft all-air SEAD; 5–7 aircraft lost; 72h ATO cycle |
| 02 · Granite Passage Amphibious |
−55% | −85% | −60% | Space-sensor cueing → MLRS/SM-6 simultaneous CDCM suppression | MAGTF organic-only; CDCM active during approach; 18–24h D-day delay |
| 03 · Silent Meridian GNSS-Denied |
−71% | −88% | −67% | LEO PNT backup + multi-static SIGINT jammer kill | Abort on GPS denial; 12–18h repositioning; laser fallback exposes aircrew |
| 04 · Copper Thread Urban HVT |
−91% | −95% | −89% | Cyber-primary creates evacuation window; CDE threshold drops | Kinetic-first blocked by 4h CDE; target escapes; mission fails entirely |
| 05 · Deep Watch Kill Chain |
−83% | −97% | −93% | Pre-delegated TST authority + direct sensor-to-fires data link | ATO routing 47min; JTFC approval chain; missile launches; $45M+ BMD response |
| 06 · Endurance Bridge Joint Logistics |
−48% | −74% | −100% | Multi-path redundancy: sea + UAS + land; space weather cueing | Single air route denied; brigade combat-ineffective in 72h |