Planning as Translation: MDMP and JOPP
Planning frameworks are often treated as bureaucratic rituals. That reading misses why they persist: they are translation machinery.
A large organization cannot coordinate action directly from reality. It coordinates action from formats: mission statements, assumptions, courses of action, decision points, control measures, synchronization matrices, and orders. MDMP and JOPP are two variants of the same underlying logic: turn a complex environment into a small number of legible choices, then bind many actors to the chosen option.
The pipeline
The shared pipeline is:
- Frame the problem. What is happening, what matters, what is the mission, what constraints bind you, and what assumptions are you making to act.
- Generate options. Multiple plausible COAs.
- Stress-test options. Wargaming, friction, enemy reaction, time, sustainment.
- Choose. Make the decision explicit.
- Bind. Produce an order + synchronization products so others can act.
Translation across levels
The common failure in joint environments is not that one framework is wrong. It is that artifacts do not translate.
A practical translation discipline:
- Keep the same underlying artifacts (problem statement, assumptions, COAs, wargame results).
- Translate the language (service-specific to joint) without losing meaning.
- Make integration constraints explicit (capabilities, readiness, authorities).
Ritual failure mode
Ritual is not “too many steps.” Ritual is when the outputs no longer connect to decisions.
You can detect ritual by asking one question at each step:
- What decision is this product enabling?
If no one can answer, the product is theater.