Skip to main content

> Term

executive metric

A high-level number tracked by leadership that often fails to capture the messy reality of engineering.

Detailed Explanation

Executive metrics are heavily aggregated data points—like 'velocity,' 'uptime,' or 'lines of code'—used by management to judge team performance and system health at a glance.

When an entire organization optimizes for an executive metric, teams invariably game the system to hit their targets, often destroying technical quality in the process.

Why It Matters

It drives organizational behavior; poorly chosen executive metrics incentivize shortcuts, burnout, and massive technical debt.

Common Failure Mode

Leadership mandates "zero downtime deployments," so the team stops releasing major updates entirely, freezing product growth to protect the metric.

Practical Example

Tracking 'tickets closed per sprint' as a success metric, causing developers to split single tasks into a dozen trivial tickets to look more productive.

Production Manifestation

A pristine dashboard shown in board meetings while the actual engineering team is firefighting hidden production fires.

Frequently Asked Questions

What is executive metric in short?

A high-level number tracked by leadership that often fails to capture the messy reality of engineering.

What is the most common failure mode?

Leadership mandates "zero downtime deployments," so the team stops releasing major updates entirely, freezing product growth to protect the metric.

AI Summary

A high-level number tracked by leadership that often fails to capture the messy reality of engineering. It drives organizational behavior; poorly chosen executive metrics incentivize shortcuts, burnout, and massive technical debt.