Enterprise AI Measurement Guide
Weekly Pulse
Quality Stats
What do this week's Innovation Rate % and 30D Code Turnover % show about engineering output quality?
What it shows
The Quality stats block shows two quality signals for the current week: Innovation Rate % (the share of engineering output that went toward new features rather than maintenance, bug fixes, or KTLO) and 30D Code Turnover % (the percentage of code written in the past 30 days that has already been reverted, deleted, or substantially rewritten). These two metrics together characterize the strategic quality of what the team shipped that week.
Why it matters
Innovation Rate answers the strategic question: is AI freeing engineers to build, or is it making maintenance faster? A week where Innovation Rate drops while AI Adoption rises is a signal that AI is being used for reactive work, the team is shipping more fixes, not more features. 30D Code Turnover is the durability signal: code that gets rewritten within 30 days is code that didn't stick, which is the operational definition of AI-generated code quality failure. Both metrics together give the CTO a weekly quality dashboard that catches problems before they appear in incident rates or customer satisfaction scores.
The Larridin angle
Weekly 30D Code Turnover in the Pulse view is an early warning system for the full Quality tab's code turnover data. Because the turnover window is rolling, always the past 30 days, the weekly Pulse reading shows whether turnover is trending up, down, or stable, allowing engineering leaders to spot a quality deterioration in its first week rather than discovering it in a monthly review.
Related Weekly Pulse Metrics
Common questions
What is the Innovation Rate in the context of AI-assisted engineering?
The Innovation Rate measures the percentage of engineering output focused on new features rather than maintenance or bug fixes, indicating the strategic use of AI in engineering.
How does the 30D Code Turnover metric relate to code quality?
The 30D Code Turnover metric shows the percentage of code that has been reverted, deleted, or substantially rewritten within 30 days, serving as an indicator of code durability and quality.
Why are these metrics important for the C-suite?
These metrics provide the CTO and other executives with insights into whether AI is enhancing innovation or merely speeding up maintenance, and they help identify potential quality issues early.
How can engineering leaders use the Weekly Pulse Quality stats?
Engineering leaders can use the Weekly Pulse Quality stats to monitor trends in code turnover and innovation, allowing them to detect and address quality issues promptly.