How do you measure team effectiveness and health?

Question

Accepted Answer

Measure effectiveness with a **balanced set of delivery, quality, and human-health signals — used as conversation starters, never as a stick**. Any single metric, optimized in isolation, gets gamed.

## What to look at

```text
DELIVERY (DORA)         HEALTH                  OUTCOMES
─────────────────────────────────────────────────────────────
Deploy frequency        Engagement / sentiment   Did it move the business goal?
Lead time for changes   Attrition / retention    Customer/user impact
Change failure rate     Burnout signals          Quality in production
Time to restore (MTTR)  Psychological safety
```

## Use them well

- **Pair speed with stability.** DORA does this on purpose — fast *and* safe, not one at the expense of the other.
- **Trends over absolutes.** Direction matters more than a number on a given day.
- **Triangulate.** Combine metrics with what 1:1s and retros tell you.

## Pitfalls

- **Lines of code, commits, or velocity as performance metrics** — they're instantly gamed and punish good behavior.
- **Goodhart's Law:** once a metric becomes a target, it stops being a good measure.
- **Measuring only delivery** while the team quietly burns out.
- **Individual surveillance metrics** that destroy trust.

## Why it matters

You can't improve what you can't see, but the wrong metrics actively harm — chasing velocity invites gaming and discourages the refactoring and review that keep a team healthy.

A balanced view keeps you honest: a team can ship fast and be falling apart, or look slow while building the foundation for years of speed.

Good measurement tells the difference.