❤️

Team Health Check

Run a Spotify-style squad health check with your team. 10 dimensions, traffic-light voting, trend tracking over time. Recommended once per quarter.

Start a free session

No account required. Share a code and you are in. Password-protected rooms supported.

What is a team health check?

A team health check is a structured retrospective exercise where team members rate different aspects of their working environment using a traffic-light system: green (great), yellow (some concerns), or red (needs attention). The format was popularised by Spotify's engineering organisation as a way to track squad health over time.

Unlike a standard retrospective, a health check covers 10 consistent dimensions across every session. That consistency is what makes trend tracking possible - you can see whether Easy to Release has been red for three quarters running, or whether a new working agreement actually improved Suitable Process scores.

The 10 health dimensions

🚀
Easy to Release
Delivering to production is painless and predictable
🔧
Suitable Process
Our way of working fits the team and the work
😄
Fun
We enjoy the work and each other
🏗️
Tech Quality
The codebase is healthy, maintainable, and not a source of dread
📚
Learning
We are growing professionally as individuals and as a team
🧭
Mission
We know why we are here and what we are building
🎮
Value
We build things our users actually need and care about
Speed
We deliver at a good pace without cutting corners
⚙️
Support
We get the help we need when we need it
🤝
Teamwork
We collaborate well, trust each other, and handle conflict constructively

Why run a health check?

🔍

Surface what retrospectives miss

A standard retro focuses on the last sprint. A health check zooms out to the team's working environment - the things that accumulate slowly and are easy to ignore until they become a crisis.

📊

Track trends over time

A single session is a snapshot. Multiple sessions reveal patterns. If Learning has been yellow for two quarters, that is a signal worth acting on.

🛡️

Safe, anonymous by design

Votes are hidden until the host reveals. Nobody can anchor to someone else's vote, and nobody feels singled out. You get honest signal, not diplomatic signal.

🗺️

Actionable by leadership

Engineering managers and agile coaches can use health check results to identify where investment is needed - whether that is tooling, process, people, or just more time to breathe.

When to run it

Once per quarter

The recommended cadence. Frequent enough to track trends, infrequent enough that each session feels meaningful rather than routine.

After a major delivery

A big release, a migration, or a period of crunch is a good moment to check in. Teams often carry stress or technical debt they have not had time to surface.

When something feels off

If morale seems low or collaboration has gotten harder, a health check gives the team a structured, anonymous way to say what is going on.

When a new team forms

Run a baseline early in the team's life. It sets expectations, starts the conversation about ways of working, and gives you a reference point for future sessions.

How it works

1

Host creates a room and shares the 6-character code with the team.

2

Everyone joins with their name - no account needed.

3

The facilitator walks through each of the 10 dimensions one at a time. For each one, team members privately select green, yellow, or red.

4

Host reveals votes for each dimension. The breakdown appears immediately - you see how many greens, yellows, and reds the team gave.

5

Team discusses the results, especially any dimensions with strong red or mixed signals.

6

Results are saved to history. The next time you run a health check, you can compare to previous sessions and spot trends.

Ready to check in on your team?

Create a free session in seconds and invite your team with a code. No account, no setup.

Start a free Team Health Check