Speed Through Iteration Counts

Brett Adcock shares his framework for measuring speed and progress in technology companies, focusing on iteration cycles and meaningful improvements between versions.

Core Philosophy on Speed

• Speed is fundamental to reducing business risk long-term
• Longer development cycles don't equal better or safer products
• Faster iteration allows for:
  • Finding problems sooner
  • More opportunities to fix issues
  • Recursive improvements
  • Better overall product quality

How to Measure Speed

• Track number of iterations over time
  • Count versions/generations of product released
  • Measure progress between each iteration
  • Examples:
    • Cars: Number of versions over a decade
    • Rockets: Launch iterations and improvements
    • Robots: Different robot generations
    • iPhones: Versions over 15 years

Building for Speed

• Design entire company structure around speed
• Eliminate common slowdown factors:
  • No program managers
  • Avoid unnecessary bureaucracy
  • Clear communication across disciplines
  • Minimize use of technical jargon/acronyms

Common Speed Barriers

• Adding headcount typically slows companies down
• Board pressure to be "safer" reduces speed
• Complex communication between different technical disciplines
• People from slow-paced backgrounds struggling to adapt
• Misconception that longer development equals better quality

Communication Requirements

• Must clearly explain complex topics "to a 12-year old on a barstool"
• Cross-disciplinary teams need common language
• Avoid insider terminology
• Focus on fundamental understanding before details
• Clear communication correlates with true understanding