Standard : Learning Velocity
Description
Learning Velocity measures the speed at which teams generate validated insights from discovery activities or experiments. It focuses on how quickly teams move from hypothesis to decision.
This metric encourages teams to reduce cycle time from idea to learning, enabling faster pivots and better roadmap decisions.
How to Use
What to Measure
- Time from experiment kickoff to capturing actionable learning.
- Count of insights generated per quarter.
Learning Velocity = Number of Insights ÷ Time Period
Example: 20 insights generated in one quarter → Learning Velocity = 20 per quarter.
Instrumentation Tips
- Maintain a shared learning log with timestamps.
- Tag insights to specific opportunities or features.
- Review velocity trends to identify process bottlenecks.
Why It Matters
- Faster feedback loops: Accelerates product improvement.
- Higher agility: Enables quicker pivots and reduces sunk cost.
- Organisational learning: Builds a repository of evidence.
Best Practices
- Automate data collection for experiment outcomes.
- Focus on actionable learnings, not just data points.
- Regularly review and socialise top learnings with leadership.
Common Pitfalls
- Measuring output (experiments run) instead of outcome (insights).
- Failing to share learnings across teams.
- Not acting on insights quickly enough.
Signals of Success
- Shorter average cycle time from idea to learning.
- Teams making data-backed decisions faster.
- Measurable improvement in roadmap outcomes.
- [[Experiment Success Rate]]
- [[Opportunity Validation Rate]]
- [[Discovery-to-Delivery Ratio]]