EO StudioThe Navy Leadership Lesson That Built a $450M Company | Blue Water Autonomy, Rylan Hamilton
CHAPTERS
- 0:00 – 1:30
Deck-plate leadership: earning trust by being in the problem with your team
Hamilton reflects on joining the Navy and learning—sometimes the hard way—that leadership isn’t directive management from afar. Trust is built by working alongside sailors during real operational failures and removing barriers in the moment.
- •Early leadership mistakes and the realization that people-management drives mission outcomes
- •“Deck plate leadership” as leading from the front, not from a desk
- •Earning trust by showing up during hard, messy work (engine room troubleshooting)
- •Handling shipboard incidents like loss of steering, power failures, flooding, and fires
- 1:30 – 2:32
Blue Water Autonomy’s mission: autonomous ships for the US Navy
Hamilton introduces Blue Water Autonomy and frames the opportunity: risky naval missions shouldn’t require hundreds of sailors in harm’s way. He shares early traction, including an autonomous test vessel and major funding to accelerate development.
- •Company focus: designing and building autonomous warships for the US Navy
- •Autonomy as a way to remove humans from high-risk missions like mine hunting
- •Current progress: a 145-ton autonomous test vessel operating near Boston
- •Funding milestone: $50M investment led by Google Ventures to “turbocharge” execution
- 2:32 – 3:02
9/11 and choosing a life away from the desk
The 9/11 attacks become a turning point that pushes Hamilton away from conventional post-college paths. Influenced by family Navy history, he chooses military service as a more mission-driven, hands-on career.
- •9/11 as a catalyst for rethinking life and career direction
- •Rejecting consulting/investment banking in favor of operational work
- •Family legacy in the Navy shaping confidence in the decision
- •Joining the Navy framed as one of his best life choices
- 3:02 – 4:02
First hour on a warship: Iranian missiles, general quarters, and the myth of “the plan”
Hamilton recounts arriving to a carrier in civilian clothes when Iran launches missiles and the ship goes to general quarters. The experience becomes an early lesson in uncertainty: planning matters, but reality will diverge immediately.
- •Unprepared arrival scenario: civilian clothes, no situational familiarity
- •General quarters as an abrupt introduction to operational stakes
- •Anything can happen at any moment—especially in defense environments
- •Plans rarely unfold as expected; adaptability is a core competency
- 4:02 – 6:03
What sailors actually want: aligning mission delivery with human motivation
He explains a practical leadership insight: sailors may care about the mission, but day-to-day motivation often ties to life at home. By focusing on execution and getting people home on time, leaders unlock sustained performance and morale.
- •In constrained organizations, you don’t pick your team—you develop them
- •Motivation is personal: balance, family, and time matter alongside patriotism
- •Operational focus: finish tasks efficiently so the team can go home
- •Leadership growth through understanding people, not just objectives
- 6:03 – 7:03
From Navy to Amazon Robotics: “concrete-floor leadership” in warehouses
After military service and graduate school, Hamilton enters warehouse automation at Kiva Systems, later Amazon Robotics. The same “lead from the front” principle shows up in a different environment—being present with teams on the warehouse floor during deployments.
- •Career transition: Navy → grad school → Kiva Systems (2011-era robotics scale)
- •Acquisition: Kiva becomes Amazon Robotics; growth to over a million robots
- •Leadership principle transfers: presence in the field signals care and commitment
- •Hands-on commissioning work across warehouses globally
- 7:03 – 8:04
Mission obsession vs. customer obsession: operating rhythms that win deployments
Hamilton contrasts Navy mission-first culture with startup/customer delivery discipline. As a program manager, he learns to hit contractual milestones by coordinating cross-functional execution and doing whatever is necessary to satisfy customer acceptance.
- •Navy mindset: complete the mission at all costs
- •Startup/enterprise mindset: customer acceptance and milestones define success
- •Cross-functional coordination as the program manager’s core job
- •Resourcefulness in the field—solving unglamorous blockers to keep timelines intact
- 8:04 – 9:04
Two exits and a bias for hard problems: why he keeps choosing “pain”
He describes startup intensity as a passion rather than a balanced lifestyle choice, then recounts co-founding 6 River Systems and selling it to Shopify. Despite knowing how hard it is to start again, he’s drawn to difficult, meaningful problems.
- •Startups as obsession-driven work—high joy, low balance
- •Founding 6 River Systems to build collaborative autonomous warehouse robots
- •Exit: acquisition by Shopify (Amazon competitor)
- •Personal operating principle: choose hard paths for the gratification of solving them
- 9:04 – 10:05
Discovering defense tech as a startup arena—and pressure-testing the idea
Hamilton explores defense technology after learning from peers (e.g., Anduril) that startups can sell into defense. He emphasizes deep market learning and iterative idea refinement before committing to a specific company direction.
- •New realization: venture-backed companies can succeed in defense markets
- •Deliberate exploration phase before committing to a concept
- •High learning cadence: 10–20 conversations per week
- •Avoiding “first idea bias” by staying open and gathering signal
- 10:05 – 10:48
The strategic reality: China’s shipbuilding scale and why the US must compete on tech
He outlines the macro driver behind Blue Water Autonomy: the world has changed since his Navy years, with China’s massive shipbuilding advantage. Since US capacity won’t change overnight, autonomy and software become the competitive lever.
- •Then vs. now: from no peer competitor to major pacing threat
- •China’s dominance in global shipbuilding and raw tonnage capacity
- •US constraint: shipbuilding capacity won’t rapidly expand
- •Strategic pivot: compete via autonomy/technology rather than tonnage
- 10:48 – 11:18
Why retrofitting is a trap: redesigning unmanned ships from the keel up
Hamilton argues that making existing ships autonomous is fundamentally flawed because current designs rely on onboard engineers constantly maintaining and repairing systems. Blue Water chooses to design vessels specifically for months-long unmanned operation, reducing single points of failure.
- •Conventional ships assume human watchstanders and repair capability onboard
- •Unmanned operation exposes too many single points of failure in legacy designs
- •Customer/market feedback reinforcing that retrofit won’t meet mission needs
- •Design choice: build purpose-designed autonomous ships from the keel up
- 11:18 – 12:49
Focus as an early-stage advantage: one customer, one product, and a clear wedge
He explains why Blue Water focuses on defense first despite commercial autonomy being attractive long-term. Defense offers urgency, willingness to pay, fewer regulatory constraints, and strong institutional support—making it the best initial wedge for building capability.
- •Early-stage principle: narrow focus beats broad exploration once committed
- •Commercial market: compelling but constrained by regulatory hurdles
- •Defense market: urgent need, clear buyer, and fewer blockers
- •Signals of demand: Navy support and Congressional allocation (over $2B)
- 12:49 – 14:19
Building teams like a ship’s crew: trust, integrity, and sharing bad news early
Hamilton ties shipboard teamwork to startup execution: when teams trust each other, they reduce defensive “contingency buffers” and move faster. He underscores integrity and transparency, repeating a Navy lesson that bad news only gets worse with time.
- •Ocean/ship dynamics: you can’t “go home”—teams must function as one unit
- •Trust reduces friction at interfaces between teams and functions
- •Integrity and transparency as operating requirements in high-uncertainty startups
- •Leadership maxim: bad news never gets better with time—surface issues early
- 14:19 – 15:36
The “Waymo of the open ocean”: software-defined ships as the long-term vision
Hamilton closes with a clear north star: making autonomous maritime vessels as acceptable and normal as getting into a driverless Waymo. He frames Blue Water not as a shipbuilder, but as a creator of software-defined ships that can automate dull/dangerous work and reshape maritime jobs.
- •Vision: normalize unmanned ships the way Waymo normalized driverless cars
- •Positioning: software-defined vehicles, not traditional vehicle manufacturing
- •Automation to remove dull/dangerous tasks and improve human roles
- •Long-term aspiration: build the platform for autonomous ships broadly
