❤️

Team Health Check

A Spotify-style squad health radar for distributed teams. Identify what is working, what needs attention, and track trends over time. Recommended once per quarter.

Run a free health check

No account required. Anonymous voting. Password-protected rooms.

What is a team health check?

The Spotify Squad Health Check is a model originally developed at Spotify to help engineering teams assess themselves across multiple dimensions of health - from technical practices to team morale. Each member votes Green, Yellow, or Red per dimension, votes are hidden until revealed, and the team discusses the results together.

The real value comes from doing it regularly. A single session is useful; comparing three sessions in a row reveals whether things are improving, stagnating, or quietly getting worse. That trend data is what makes health checks worth repeating.

The 10 health dimensions

🚀
Delivering value
Are we shipping things that matter to users?
🔧
Easy to release
Is deploying painless and low-risk?
😄
Fun
Do we actually enjoy the work?
🏗️
Health of codebase
Are we proud of the code we write?
📚
Learning
Are we growing as engineers and as a team?
🧭
Mission
Do we know why we are here and does it matter?
🎮
Pawns or players
Do we influence decisions or just execute orders?
Speed
Are we moving fast enough to feel momentum?
⚙️
Suitable process
Does our process help or slow us down?
🤝
Teamwork
Do we collaborate well and trust each other?

Why teams use it

🔍

Early warning system

Problems that go unspoken compound over time. A health check surfaces them before they become crises - when they are still fixable.

📊

Trend tracking

A single snapshot is interesting. Three quarters in a row tells a story. Track progress on specific dimensions and see whether changes you made are actually working.

🛡️

Safe for honest answers

Votes are anonymous and hidden until the host reveals them. Team members can rate honestly without fear of being singled out.

🗺️

Covers the whole picture

10 dimensions spanning delivery, process, morale, and collaboration. No important angle gets skipped because someone forgot to ask.

When to run a health check

Once per quarter

Run it often enough to track trends but not so often it feels like surveillance. A quarter gives the team enough time to actually act on previous findings and see whether things improved before measuring again.

After team changes

New team members, a reorg, or a change in tech stack all shift team dynamics. A health check after any major change gives the team a baseline to work from.

Before a big delivery or PI planning

Knowing where the team stands before a high-pressure period lets leadership address problems proactively instead of reactively.

When something feels off

Sometimes things feel wrong but no one can articulate what. A health check gives the team a structured way to surface that unease and point at specific dimensions.

How it works

1

Host creates a session with an optional password and shares the room code.

2

Team joins - no account needed.

3

Each member votes Green, Yellow, or Red on each of the 10 health dimensions. Votes are private.

4

Host reveals votes when everyone is done. The distribution for each dimension is visible.

5

Team focuses discussion on Red and Yellow dimensions, especially where there is disagreement.

6

Results are saved so the next session can be compared to this one.

See how your team is really doing

Create a session, share the code, and get honest signal across 10 dimensions. Free, real-time, anonymous.

Start a free Team Health Check