At a Pentagon briefing on March 2, 2026, War Secretary Pete Hegseth used blunt language about how the United States would fight, saying there would be “no stupid rules of engagement,” “no politically correct wars,” and “no nation-building quagmire.”
Those remarks became a flashpoint because rules of engagement, or ROE, are not “vibes” or slogans. They are a formal control system that ties tactical force decisions to strategy, law, and escalation management. Human Rights Watch responded the same day by warning that dismissing ROE in public can read as minimizing legal constraints that exist to protect civilians and keep operations compliant with the laws of war.
What Rules Of Engagement Are In U.S. Practice
In U.S. doctrine, ROE start with standing baseline rules and then get tailored by commanders for a mission, geography, and threat picture. The Joint Staff’s Standing Rules of Engagement and Standing Rules for the Use of Force (CJCSI 3121.01B) are the backbone reference that describes how U.S. forces think about self defense, hostile act, hostile intent, and the conditions for using force.
ROE also function as a practical translation layer between the law of armed conflict and split-second decisions on the ground. They define who can be targeted, what “positive identification” and “hostile intent” mean in context, and what steps troops must take before escalating force. A plain-English training example is the Marine Corps lesson on law of war and ROE, which defines ROE as directives that set the “circumstances and limitations” under which U.S. forces initiate or continue combat engagement.
Why “No Stupid ROE” Can Be Misread
Hegseth’s phrasing is politically resonant for many, but it is also easy to misunderstand. No competent military runs “no ROE,” because U.S. forces remain bound by domestic orders and the law of armed conflict, including concepts such as distinction and proportionality. The Department of Defense Law of War Manual lays out those rules as operational obligations, not optional preferences.
Hegseth may be trying to signal ROE should not be over-lawyered, overly restrictive, or drafted in ways that create tactical paralysis. Even that narrower point can still be risky as public messaging, because the phrase “stupid ROE” implies the problem is the existence of constraints rather than the quality of the constraints.
When ROE Have Clearly Helped The U.S.
There are well-documented cases where tighter guidance on the use of force improved strategic outcomes by reducing civilian harm and preserving legitimacy with the population. In Afghanistan, ISAF’s 2009 Tactical Directive under Gen. Stanley McChrystal tightened standards for air-to-ground fires and emphasized protecting civilians, explicitly shaping how units used force in populated areas.
U.S. military analysis later described how that directive and related command emphasis drove changes in how airpower was used and contributed to decreased civilian casualties from airpower during that period. That is not a moral victory lap; it is operational logic. Civilian harm can create tactical blowback, degrade intelligence access, and strengthen enemy recruiting.
Counterinsurgency doctrine makes the same point in more formal language: in COIN, legitimacy and civilian protection are not side quests. They are part of the theory of victory, which means ROE can become an instrument of strategy rather than just a compliance checklist.
When ROE Feel “Stupid” In The Field
Troops often complain about ROE when they are complex, change frequently, or are poorly explained. The Army’s ROE vignettes and escalation-of-force training materials exist for a reason: memorizing a card is not enough, and uncertainty in how rules apply at a checkpoint or convoy can cause hesitation, overreaction, or inconsistent outcomes across units.
Some ROE problems are not about being too restrictive or too permissive, but about ambiguity. The Operational Law Handbook material on ROE emphasizes that key terms like “imminent” are contextual and fact-dependent, which means unclear drafting and uneven training create the very confusion troops hate.
Why The U.S. Cannot Treat ROE As Mere Politics
Even when policymakers want “maximum lethality,” modern U.S. operations still face legal, alliance, and information-environment constraints. A strike that is lawful but poorly executed can still be strategically catastrophic if it creates civilian harm that breaks partner support or drives escalation. That is one reason the Defense Department has formal policy on civilian harm mitigation and response, including processes for acknowledging and responding to civilian harm.
This is where a balanced critique lands. Overly bureaucratic, risk-averse ROE can endanger forces and miss opportunities. Overly permissive, poorly supervised ROE can increase civilian casualties and produce long-term strategic costs that outweigh short-term tactical ease. The hard part is writing ROE that are operationally workable, legally compliant, and matched to the mission.
What A Serious Standard Would Look Like
If the Pentagon wants to claim it is dropping “stupid” ROE, the test should be clarity and effectiveness, not the absence of limits. Good ROE give commanders speed and discretion while preserving the core law of war requirements and making escalation control explicit. The standing ROE framework exists precisely to keep that balance across theaters and to avoid improvisation under stress.
Hegseth’s rhetoric is easiest to defend if it is paired with transparent reassurance that ROE remain grounded in the laws of war and that civilian protection measures are not being stripped for messaging value. Without that clarification, “no stupid ROE” will keep being heard as “fewer rules,” even if the real intent is “better rules.”
