Key Takeaways

  • True Anomaly designs defense spacecraft from two baseline anchors: orbital battlefield requirements and first-principles physics.
  • The company abandoned outsourced manufacturing for vertical integration to protect its iteration speed from slow supply chains.
  • Defense procurement must transition toward firm-fixed-price contracts because cost-plus billing disincentivizes rapid hardware testing and venture investment.
  • Rogers relies on John Boyd's OODA loop to compress engineering cycles, treating adaptation velocity as the primary metric of organizational survival.
  • True Anomaly enforces Even Rogers' Rubric for Failure to allow early engineering risk while preventing lazy, uninstrumented mistakes.

The Even Rogers' Rubric for Failure

Rogers insists that rapid prototyping requires high risk tolerance, but risk without structure produces sloppy engineering. “The number one and most important skill at True Anomaly is problem solving,” (play from 44:40) Rogers explains. “We problem solve from really two perspectives: the battlefield, and physics.” (play from 44:47) To keep teams solving problems without creating careless waste, the company enforces three explicit criteria before greenlighting high-risk hardware trials.

Rule 1: Give 100% Effort (The 'No YOLO' Rule)

You must give whatever you are doing 100% effort. You cannot just throw things at a wall carelessly without diligence, particularly later in program development.

Rule 2: Generate Meaningful Data

Do not fail in a data-sparse way. Experiments and tests must produce sufficient data so that the team can analyze results, execute the 'five whys' root-cause analysis, and pinpoint the objective truth.

Rule 3: Never Make the Same Mistake Twice

When a failure occurs, conduct a structured debrief, extract the lesson, articulate it across the organization, and ensure that specific failure mode is never repeated.

When This Works (and When It Doesn't)

This rubric applies across business operations and engineering prototyping, especially early in development cycles when financial and programmatic blast radiuses are low, allowing teams to take aggressive risks while driving rapid organizational learning. When a component costs tens of thousands of dollars rather than tens of millions, breaking it yields cheap, high-signal data that shortens design timelines.

The framework fails when programs migrate from research and prototyping to operational manufacturing. Later in production, unit economics and delivery schedules take precedence over discovery. If a team applies high failure tolerance during final assembly or flight qualification, the financial blast radius expands rapidly, customer schedules slip, and capital efficiency collapses. It also breaks down in organizations lacking the technical telemetry required to capture rich data during a test anomaly.

Why It Matters

Private equity and growth investors backing defense technology face a structural tension: venture-backed hardware developers cannot survive on the slow feedback loops of traditional prime contractors. Incumbents operating under cost-plus contracts are financially incentivized to drag out engineering cycles and avoid public test failures. Rogers proves that hardware startups must build high iteration speed directly into their culture to win firm-fixed-price awards.

Controlling hardware fabrication in-house decouples prototyping speed from third-party vendor delays. For sponsors underwriting defense tech platforms, the critical due diligence question is whether an engineering culture can absorb early physical failure without burning programmatic capital. Companies that pair rigorous telemetry with strict operational debriefs turn hardware destruction into an intellectual property moat.