11.4Making Invisible Work Visible

Anti-Pattern: QA engineers rely on their manager to notice and appreciate their work. Performance reviews focus on activities ("wrote tests") rather than outcomes ("prevented incidents").

Pattern: Maintain an impact log, collect metrics continuously, and frame contributions in business terms.

The Impact Log

Keep a running document, updated weekly:

• Date: What month/year
• What: Specific contribution
• Impact: Quantified result
• Scope: How many teams/engineers benefited

When review time comes, you have twelve months of concrete, quantified contributions to choose from — instead of scrambling to remember what you did.

Framing for Non-Technical Reviewers

Instead of: "Implemented contract testing using Pact for the order service API."

Write: "Implemented API contract testing that caught 12 backward-incompatible changes before production, preventing an estimated 48 hours of incident response."