Learning goal: treat MDMP and JOPP as compatible planning pipelines, and understand what each pipeline is trying to prevent.
Design comes first
MDMP and JOPP are planning paradigms [@jointchiefs2011jp5; @usarmy2014fm6]. They work best when fed by a clear problem frame and an operational approach from operational design.
If you want a comparative view of modern doctrinal design paradigms (Army ADM, MCPP, NATO), see: Operational design frameworks: ADM, MCPP, and NATO.
The shared structure
Both MDMP and JOPP exist because complex operations need a repeatable way to translate ambiguity into executable coordination. Their shared structure is:
- frame the problem,
- generate options,
- wargame and compare,
- decide,
- produce an order plus synchronization products.
The difference is the integration problem
- MDMP is optimized for producing detailed orders and staff products inside a service’s staff structure.
- JOPP is optimized for integrating multiple services and partners into a joint operational approach.
The practical rule: keep the same underlying artifacts (problem statement, assumptions, COAs, wargame results) and translate them into the vocabulary and products the HQ needs.
Paradigm hygiene (what makes these processes fail)
Planning paradigms fail when they become ritual. Watch for:
- steps completed without confronting uncertainty,
- wargaming treated as false precision,
- products treated as ends rather than decision support.
Exercise
Pick a scenario and do a minimalist pipeline:
- write a problem statement and 5 assumptions,
- sketch 2 COAs,
- wargame each in three moves,
- write the decision you would need to make under time pressure,
- list the one synchronization rule that must hold for the plan to work.