Enterprise AI Measurement Guide

Quality

Team Level Breakdown

How do we see each engineer's code quality fields at the individual level per week, including review behavior as both author and reviewer?

What it shows

The Quality Team Level Breakdown is the most granular engineering quality table in Larridin, showing seventeen quality dimensions per engineer per week, including AI Code Share, code turnover at 30 and 90 days, PR size, review pushback rates, comment quality signals, rubber stamp rate both as author and reviewer, the AI Slop Index score, and unit test rate. Every dimension that the sixteen Quality metric tabs surface at the org level is available here at the individual contributor level, week by week.

Why it matters

This table is the engineering accountability layer that makes individual quality conversations possible without relying on manager judgment alone. An engineer with a 0% rubber stamp rate as an author but a 78% rubber stamp rate as a reviewer is behaving differently in the two roles, a signal invisible in aggregate quality metrics. An engineer whose AI Code Share jumped from 20% to 65% in one week while their 30D Turnover also jumped is a training conversation, not a performance conversation. Per-engineer, per-week data at this resolution makes those distinctions actionable.

The Larridin angle

Larridin's per-engineer quality scorecard distinguishes Author and Reviewer behaviors separately for pushback, comment quality, and rubber stamp rate, recognizing that how an engineer writes code and how they review it are different dimensions of quality, and that AI affects them differently. Most engineering platforms measure one or neither.

Related Quality Metrics

• Quality Metric Tabs
• Innovation Rate Chart