1 min lesson
The quality pillar
Answer this as if it were happening now: "An engineering VP asks for the single ROI metric to put on their board. What do you point to and why?" Say what supports your choice.
Step 1 of 2
The quality pillar
Quality is what keeps velocity honest. Lead with the number that matters most to the business and treat the rest as supporting evidence.
- Customer-facing defects - the headline. Flat or declining is the win; if shipping faster pushes this up, the velocity gain was an illusion.
- Test coverage - whether the safety net grew with the code, so faster shipping isn't quietly raising risk.
- Code half-life - how long a line of code survives before it's changed again. Longer-lived code points to fewer thrash-and-rewrite cycles.
- Developer sentiment - whether engineers trust the codebase and the workflow, an early signal before defects ever surface.
Set quality expectations to incremental, not dramatic. The honest claim is that defects stay flat or decline while velocity rises - not that quality leaps. Promising a step-change in quality invites the same skepticism as the "55% faster" overclaim and a CTO who's run real teams will catch it instantly.
When an executive asks for the one ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. number, point at time-to-marketHow fast a feature actually reaches customers; the outcome metric the velocity and quality pillars ultimately serve. Press Enter for the full definition.: how long it takes an idea to reach customers. It's the metric the velocity x quality frame rolls up into, because it only improves when you ship faster and the quality line holds. Velocity layers and quality signals are how you explain the movement; time-to-market is the outcome you're moving.