Learn-Driven Development
Practice

Key Metrics

What to track instead of velocity.

By Martin Alaimo

Instead of velocity, we track:

  • Learning loop velocity: How many validated learning loops can we close per week?
  • Learning-to-shipping ratio: What percentage of validated learning makes it to production?
  • Time-to-validation: How fast can we close a learning loop from bet to decision?
  • Customer impact of validated learning: Of the learning we shipped, how much mattered to customers?

The goal is to maintain healthy ratios, rather than to maximize any single metric. If you're validating fast but shipping slowly, something's wrong. If you're shipping a lot but validating little, you're drifting.

For solo builders, the most telling metric is simpler: what percentage of the things I built last month did I validate with a real user? If that number is low, you're vibe-coding. If it's high, you're learning.