Speed Beats Perfection

Brett Adcock believes that moving fast and iterating quickly is fundamental to building successful products and companies. He argues that contrary to common belief, taking longer to develop something doesn't make it safer or better - instead, rapid iteration leads to superior outcomes through increased learning and improvement cycles.

Key Points:

• Speed vs Time Philosophy:

  • Longer development time doesn't equal better or safer products
  • Quick iterations allow for finding and fixing problems faster
  • Multiple iterations provide more real-world testing and improvement opportunities

• Company Structure for Speed:

  • Built entire company architecture around moving fast
  • Zero program managers among 120 engineers
  • Describes Figure as "anti-Silicon Valley company in Silicon Valley"
  • Speed must be designed into company from ground up

• Measuring Speed:

  • Track number of iterations completed
  • Evaluate progress between iteration cycles
  • Examples across industries:
    • Cars: versions released over a decade
    • Rockets: number of iterations
    • Phones: iPhone versions over 15 years
    • Robots: number of robot iterations

• Cultural Challenges:

  • Many people struggle with fast-paced environments
  • PhD students often face culture shock due to speed requirements
  • Some believe longer development equals better quality (which he argues is wrong)

• Speed Impact on Business:

  • Speed correlates with reduced risk of business failure
  • Faster iteration creates competitive advantage
  • Companies typically slow down as they grow larger
  • Must actively fight against organizational slowdown

• Communication Requirements:

  • Clear communication essential for speed
  • Avoid insider terminology and acronyms
  • Must be able to explain complex topics simply
  • Cross-disciplinary teams need common language