More Jocko Podcast episodes

566: Leading Through Chaos. Lessons From the Battle of Ramadi with The 1st of The 506th Band Of Brother. With General Ron Clark thumbnail

566: Leading Through Chaos. Lessons From the Battle of Ramadi with The 1st of The 506th Band Of Brother. With General Ron Clark

Published 11 Nov 2026

Duration: 04:03:08

General Ron Clark discusses leadership in Ramadi, emphasizing character, adaptability, and the critical bond between SEALs and infantry during sustained urban combat.

Episode Description

>Join Jocko Underground Full Episodes<General Ron Clark shares his journey from growing up in an Army family to commanding troops during the brutal Ba...

Overview

General Ron Clark, commander of US Army Pacific, recounts his career from military brat to four-star general. He describes growing up as a dependent of the US Army for 60 years, attending West Point after a brigade XO encouraged him to become an officer, and early assignments including Ranger school, a rifle platoon in Germany, and company command in Hawaii. A pivotal lesson came from a West Point economics professor who told him "school is your job do your job," transforming his academic performance and setting the trajectory for his career.

The central focus is his battalion command in Ramadi as 1st Battalion 506th Infantry, Task Force Red Curry, arriving in "November of oh five" and completing their rotation on "the 15th of november." He details the embedded SEAL platoon, the blue-on-blue incident caused by Iraqi forces clearing in the wrong direction, and the loss of soldiers including SEAL Mickey Monsoor, whose family "was presented the medal of honor." Clark emphasizes bonds formed in crisis, noting the SEALs "pulled all their personal money and gave it to the family of the soldier that was killed."

Clark distills leadership lessons: training leaders first so they can train their own people, adapting to unfamiliar environments (his unit did "zero urban overwatch positions" in workup but "I think 106 of those types of operations" during deployment), the shift from single-mission planning to sustained combat operations, and the principle that "teach and train character and competence will follow."

What If

  • What if you built your product's "urban ops SOP" before scaling, so every contributor follows one standard?

    • Move: Document a single deployment pipeline or incident-response runbook, then train all senior contributors to that standard before onboarding new people. Clark's battalion trained all leaders to the same SOP to "buy down the risk through procedure."
    • Why Now? If you're about to add a second developer or new service, inconsistent processes compound. Clark notes: "if everybody from squad leader up in the battalion does this the same way Then we buy down that risk."
    • Expected Upside (proposed): New contributors integrate without retraining the entire system, reducing the "wrong star cluster" failure mode where a signal is misread and the whole unit advances into a gap.
  • What if you stopped pre-building features for unvalidated scenarios and built an adaptation protocol instead?

    • Move: Ship a minimal version and invest in feedback loops (analytics, user interviews) rather than pre-building variations. Clark's unit trained zero urban overwatch positions in workup but conducted 106 during deployment: "we just adapted."
    • Why Now? If your roadmap is filled with speculative features, you're spending capacity on unvalidated assumptions. The adaptation protocol lets you respond to real user behavior.
    • Expected Upside (proposed): You avoid wasted engineering on unneeded features and build the muscle to pivot when real data contradicts your plan.
  • What if you planned your product lifecycle as "sustained operations" with built-in recovery cycles rather than a single launch?

    • Move: Structure your roadmap in 90-day cycles, each with a "deployment" phase followed by a recovery phase (bug fixes, documentation, rest). Clark contrasts the 1990s mindset - "you're gonna go do one mission" - with "sustained combat operations" where "you're gonna run out of ammunition."
    • Why Now? If your plan is one big launch followed by quiet, competitors and technical debt don't stop while you recover.
    • Expected Upside (proposed): You maintain continuous momentum, catch issues before they compound, and avoid the morale collapse Clark describes when soldiers must "put our gear back on" the day after a loss.

Takeaway

  • Document repeatable procedures before scaling. Clark's team built an urban operations SOP to "buy down the risk through procedure" so that "everybody from squad leader up in the battalion does this the same way". Write step-by-step runbooks for every recurring task - deployments, incident response, onboarding - so execution never depends on memory.

  • Master fundamentals before adopting new tools. Clark warns, "you got to be brilliant at the basics first" and that "the fundamental ways of war are not changing but the contemporary environment is changing". Before integrating a new framework or AI tool, ensure your core codebase, testing, and CI/CD pipeline are rock-solid.

  • Ship a minimal approach when unprepared. Clark's unit "did zero urban overwatch positions" in workup yet "did I think 106 of those types of operations" in deployment by adapting on the fly. Entering a new market or stack, launch a rough first version and iterate rather than waiting for perfect preparation.

  • Thank departing users and leave the door open. Clark tells soldiers leaving mid-deployment, "I tell him thank you," and "75% of the time they're knocking on my door like two hours later like I want to stay". When a client churns or a tool fails, send a genuine thank-you; many will return.

  • Know every user by name. Clark's biggest fear was "conduct a memorial service for a soldier that I didn't know," so he walked the motor pool, chow hall, and tents daily. Personally respond to every support ticket and learn your top users' names and workflows.

Recent Episodes of Jocko Podcast

More Jocko Podcast episodes