Team Health Checks: A Practical Guide (with Dimensions)

A team health check is a lightweight, recurring pulse survey that measures how a team is doing across dimensions like collaboration, clarity, workload, and morale. Where a retrospective looks at the last sprint, a health check looks at the team itself — and tracked over time, it reveals trends a single retro never could.

What a health check measures

Spotify popularized the format with its "squad health check," but the idea is simple: pick a handful of dimensions and have each person rate them, usually on a red / amber / green scale. Common dimensions include:

• Mission — do we know why our work matters?
• Collaboration — do we work well together?
• Delivery — do we ship at a healthy, sustainable pace?
• Learning — are we growing our skills?
• Support — do we get what we need to do our jobs?
• Fun — do we enjoy working here?
• Psychological safety — can we be honest without fear?

Why run health checks?

Retrospectives are great at catching sprint-level issues, but they can miss slow-moving problems: creeping workload, eroding trust, a mission that's gone fuzzy. A health check makes those trends visible before they become a crisis. The magic is in the trend line — a "green" that's been sliding toward "amber" for three months is a louder signal than any single data point.

How to run a team health check

1. Pick 6–8 dimensions that matter to your team. Don't overload it.
2. Have everyone rate privately. Red / amber / green, plus a one-line "why." Anonymity gets you honesty.
3. Aggregate and discuss. Look at where people disagree — split votes are the most interesting.
4. Track the trend. Compare against last check. Which dimensions are improving? Declining?
5. Pick one thing to improve. Convert the weakest dimension into a concrete commitment.

Health check vs. retrospective

They're complementary, not competing. Run a sprint retrospective every sprint for tactical improvements, and a health check every month or quarter for the bigger picture. Pair the health check with a few team reflection questions for a richer conversation.

A retro tells you about last sprint. A health check tells you about the team.

Making it stick

Keep it short

Five minutes to complete. If it feels like a performance review, people stop being honest.

Act on it

The fastest way to kill a health check is to run it and change nothing. Always close with one improvement, and review it next time.

Protect anonymity

Health checks live or die on honesty, which depends on psychological safety. If people fear their ratings will be traced back to them, you'll get all-green results that mean nothing.