Here’s a short passage focused only on **reported bugs**, aligned with the Engineering Impact language: --- **Reported bugs** reflect the issues that escaped code review and surfaced after deployment. They are a lagging signal, but an important one. Reported bugs show where review coverage was insufficient, where risk was underestimated, or where certain change patterns consistently slip through. By tracking reported bugs over time, teams can see not just how many issues reach production, but how that trend evolves as review practices change. Engineering Impact treats reported bugs not as a failure metric, but as feedback for improving how and where review effort is applied.