Spotify Health Check

The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions.
Read more

The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions. It comes in two forms, Spotify Team or Squad Health Check. The dimensions are evaluated, providing insights for improvements.

Dimension colors

  • GREEN: Things are going very well, not necessarily perfect, but satisfactory.
  • YELLOW: Some not disastrous problems to be addressed.
  • RED: Things are going wrong, and need to be improved urgently.

A trend can be pictured with an arrow (up, down, no arrow).

Spotify Health Check Dimentions


There are 11 dimensions which are evaluated by all participants.

Delivering value

  • Good: Great stuff is delivered! Both the team and stakeholders are happy.
  • Bad: We deliver crap, and are ashamed, stakeholders hate it.

Easy to release

  • Good: Simple, safe, painless, and automated releases.
  • Bad: Risky, painful, and manual releases take forever.


  • Good: The work is fun.
  • Bad: The work is boring.

Health of codebase

  • Good: The code is clean, easy to read, and test-covered.
  • Bad: The code is not good with a lot of technical debt.


  • Good: New things are learned constantly.
  • Bad: No time to learn.


  • Good: The mission is understood and it is exciting.
  • Bad: The mission is missing, unclear, or uninspiring.

Player or pawn

  • Good: We are in control of what and how to build stuff.
  • Bad: No influence over what we build or how we build it.


  • Good: No waiting and no delays, stuff is done quickly.
  • Bad: It is hard to get anything done, work gets stuck or interrupted.

Suitable processes

  • Good: Our way of working fits us perfectly.
  • Bad: Our way of working sucks!


  • Good: Quality support is provided if needed.
  • Bad: No support or help is available, and it is often blocking the progress.


  • Good: The team works great.
  • Bad: Group of individuals who do not care about others on the team.

Similar posters

Minto Pyramid
Minto Pyramid The Minto Pyramid Principle, a communication framework, advocates for a top-down approach to convey messages effectively
Maslow's Hierarchy Of Needs
Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.
RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices 6 Kanban Practices: Visualize, Limit WIP, Manage Flow, Make policies explicit, Implement feedback loops, Improve collaboratively
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.