We’ve all been there. A stakeholder asks, “How can we increase the team’s velocity?” It’s a simple question with a dangerous subtext. For years, we’ve used metrics like story points and velocity to measure progress, but they’ve become a trap—confusing busyness with impact.
Chasing a higher velocity number often incentivizes the wrong behaviors. It can lead to cutting corners on quality, ignoring tech debt, and shipping features without proper validation. We end up in a feature factory, churning out code that doesn’t actually solve user problems or move business metrics. We’re running faster on the treadmill but not getting any closer to our destination.
The real goal isn’t to ship more code; it’s to deliver more value. This requires a shift from measuring output to measuring outcomes. Frameworks like DORA and SPACE are a great starting point, focusing on things like deployment frequency, lead time, and team satisfaction. True alignment happens when every engineer understands the ‘why’ behind their work. At my company, we’ve focused on tightening this loop by using tools like Leera to connect development tasks directly back to specific customer feedback and strategic goals.
This shift isn’t easy, as it requires educating stakeholders and resetting expectations. But it’s essential for building sustainable, high-impact products.
How does your team navigate the pressure for speed versus the need to deliver real, validated customer value?