Sovereign states scale force in their responses. It is a deliberate act — measured, signaled, and reversible. The tools built to deliver that force should be designed the same way: proportional by default, defensible by design.
Overmatch is not a strategy
“Overmatch” has quietly become a synonym for “buy the most expensive thing available.” But overmatch against the wrong threat, at the wrong cost, in the wrong place, is just waste wearing a uniform. Capability that can’t be sustained isn’t capability — it’s a liability with a maintenance schedule.
Proportionality is the harder discipline. It requires you to know the threat well enough to answer it precisely, and to have the confidence to stop building once you have.
Design backward from intent
Every good concept of operation starts with a decision-maker’s intent and works backward:
- What effect is intended? State it in plain language.
- What is the real threat? Assess it honestly — no inflation, no theater.
- What is the smallest defensible response? Build that. Then stop.
The step most programs skip is the third one. There is always pressure to add margin, add features, add scope — each defensible in isolation, ruinous in aggregate.
As simple as possible, no simpler
The goal is not minimalism for its own sake. It’s fitness for purpose. A solution should be exactly as complex as the mission demands and not one requirement more — because every ounce of unnecessary complexity is paid for twice: once at acquisition, and again every day it’s in the field.
Measure the response. Match it to the intent. Make it make sense.