We keep repeating the same error because we keep rewarding the same metric.

In moments like this, success gets defined as a dramatic event: a strike, a decapitation, a public declaration of strength, a moment that can be summarized in a single sentence. And then, because it feels like control, we mistake the event for the outcome.

But the outcomes we claim to want, reduced violence, reduced recruitment, fewer retaliatory cycles, stable trade routes, fewer civilian deaths, less radicalization, don’t live on the same clock as headlines. They live on a multi-year clock. That is where blowback is born.

This week’s reporting describes a large U.S.–Israeli strike campaign against Iran in which Iran’s Supreme Leader Ayatollah Ali Khamenei was killed, followed by widening retaliation dynamics and international calls to halt escalation and return to talks.

The question is not whether a strike can be tactically effective. The question is whether the strategic approach changes the system’s trajectory, or whether it simply accelerates the cycle.

Right now, it looks like we’re accelerating the cycle.

The core problem: actions are immediate, consequences are delayed

When a society repeatedly experiences surprise retaliation years after an action, it isn’t because the retaliation is unforeseeable. It’s because the decision architecture is built to externalize the tail risk.

There are four clocks running at the same time

1. The political clock (days to months): approval ratings, elections, coalition stability
2. The security clock (months to years): retaliation planning, network adaptation, counter-adaptation
3. The narrative clock (years): martyrdom, grievance compounding, ideological inheritance
4. The generational clock (5–20 years): who pays the cost, who inherits the trauma, who grows up inside the story

A system that optimizes for the first clock will reliably lose on the other three.

That’s what “blowback” really is… not a mysterious force, but a predictable outcome of time-horizon mismatch.

What “doing this correctly” actually means

If we want different outcomes, the approach has to change at the level of mechanism. “More resolve” is not a mechanism. “Harder strikes” is not a mechanism. “Killing the leader” is not a mechanism. Those are events.

A correct approach has five requirements.

1) Define the end-state before the first strike

This is the part that usually gets skipped because it forces accountability.

A serious end-state is not “they stop.” It is measurable and time-bound

• Reduced rocket/drone/missile launches over 12–24 months
• Reduced proxy capability (funding, logistics, commanders) over 6–18 months
• Reduced recruitment/radicalization indicators over 1–3 years
• Stabilized maritime shipping and energy flows over weeks to months
• A verification framework that survives leadership turnover

If you cannot state the end-state clearly, then the operation is not a strategy. It is coercion plus hope.

This week’s reporting suggests there was no breakthrough in nuclear talks immediately prior to the strikes, and international bodies quickly moved into emergency posture. That’s not inherently wrong, but it is a signal that the end-state architecture was either absent or not publicly credible.¹

2) Treat the system, not the face

Decapitation logic assumes a highly centralized system where removing the leader collapses the machine.

But mature systems are built for continuity. They have succession, redundancy, ideology, security services, and a queue of younger actors shaped by the same incentives, often with fewer constraints and more appetite to prove legitimacy.

A “system-first” strategy targets the machine

• financing channels
• logistics corridors
• command-and-control infrastructure
• weapons supply chains
• information operations
• internal elite cohesion (fracture lines)
• the grievance fuel that sustains replenishment

If you don’t weaken replenishment, you’re not reducing the problem; you’re merely rotating the cast.

If the strategy is a single dramatic event, the outcome will be a long, delayed invoice.

3) Build an off-ramp before you apply pressure

Pressure without an off-ramp doesn’t produce surrender. It produces proof of toughness.

Every regime, faction, and militant network is playing an internal legitimacy game. When you corner them publicly without a credible exit, the rational move is escalation, because backing down is politically fatal.

A credible off-ramp has four elements

• Security assurances (not love, not trust; just clear limits)
• Verification (inspection, monitoring, phased compliance)
• Reversible incentives (relief that can be snapped back)
• Face-saving narrative for all parties (because domestic politics is a constraint, not a footnote)

Right now, the public posture being reported is… widening strikes + retaliation + global leaders urging a return to talks. That is the after-the-fact version of an off-ramp; reactive, not designed.²

4) Measure success on lagging indicators, not theater

Theater is seductive because it is legible. The problem is that theater often correlates with the opposite of strategic progress.

If you want reduced long-run violence, you track

• recruitment and mobilization signals
• propaganda resonance and diaspora amplification
• internal faction shifts (hardliners vs pragmatists)
• proxy operational tempo
• cross-border strike frequency
• retaliatory targeting patterns
• economic stress signals that correlate with instability

The headline metric is whether you struck. The real metric is whether the system’s capacity and incentives shifted.

Emergency UN dynamics, briefings, division, calls to halt escalation, are not themselves proof of failure. But they are a reliable marker of how fast the situation can widen once the cycle is activated.³

5) Force accountability to match the time horizon of the risk

This is the hardest part because it demands institutional humility.

Blowback is a governance failure… actions are authorized under short-term incentives while long-term costs are paid by people who did not make the decisions.

If you want a different trajectory, you need structural constraints like

• pre-registered success criteria (what “done” means)
• an independent post-action assessment
• periodic renewal thresholds (continuation isn’t automatic)
• explicit civilian harm accounting
• long-tail risk ownership that cannot be avoided by turnover

Without this, the system will keep purchasing a feeling of control today, with an invoice delivered later.

So what direction are we heading?

Based on current reporting, the direction looks closer to the traditional cycle

• major strikes and leadership targeting
• widening retaliation dynamics ⁴
• emergency international crisis diplomacy and calls to return to talks

That is an event-first strategy. It may achieve tactical goals. But it predictably increases the probability of

• martyrdom narratives that recruit on a multi-year clock
• succession hardening (younger leaders needing to prove legitimacy)
• a retaliation ladder that expands targets
• a generational mismatch where today’s decision-makers won’t be the ones absorbing the ultimate cost

None of this is pacifism. It is systems thinking.

A better doctrine: de-escalate the system, not just the moment

Here is the correct approach in one sentence

Define the end-state, weaken replenishment, design the off-ramp, measure lagging indicators, and bind leadership to the long tail.

Or, more bluntly

If you don’t change the mechanism, you don’t get different outcomes; you just get different headlines.

If we want to avoid inheriting another delayed invoice, we should stop pretending that dramatic events are synonymous with strategic resolution.

We should start acting like blowback is not a surprise; it’s a predictable output of how we choose to operate.

There is a better way forward, but it starts by acknowledging the two parties steering the ship.