Team Health Vocabulary

The Spotify Squad Health Check is a team-owned, low-ceremony model for making the implicit (how the team feels about its work) explicit — it works because it surfaces problems through structured conversation, not management metrics.

The model was created by Henrik Kniberg and Kristian Lindwall at Spotify. Each session works in two parts: (1) each dimension is voted on by the whole squad simultaneously (show of hands or card flip) — the simultaneous reveal prevents anchoring to the first person's vote; (2) the team discusses significant disagreements (one person votes green, another votes red) to understand different perspectives. The output is a team "health board" showing trend over time. Critically, the results stay with the team — they're not reported upward as a management tool. The Scrum Master's role is to facilitate the discussion and help the team decide what to improve.

Key vocabulary:
• Squad Health Check — a team self-assessment model with categorical dimensions rated green/yellow/red
• health dimension — a specific aspect of team wellbeing assessed in the health check (e.g., "Easy to Release", "Fun", "Learning")
• team health board — a visual showing health check results over time, owned and visible to the team

"Easy to release" is one of the most strategically important health check dimensions — a team that struggles to deploy frequently has constrained feedback loops, deferred integration risk, and reduced ability to respond to user needs.

The ideal release process described by high-health teams: one-button deployment, automated tests as the quality gate, deployment on demand without fear, and fast rollback if something goes wrong. Red on this dimension often traces to: insufficient test automation (fear of breaking production), complex manual deployment steps (documentation debt), environment drift (dev/staging/prod diverge), or cultural factors (blame for broken deployments makes people risk-averse). The Scrum Master facilitates the problem-mapping and helps the team structure improvement work — they may also need to escalate if the blockers require resources beyond the team's control (e.g., infrastructure investment or platform team support).

Key vocabulary:
• easy to release — a health dimension assessing how frictionless and fearless the team's deployment process is
• release friction — manual steps, delays, or risks that make deploying to production difficult or scary
• deployment on demand — the ability to release to production at any time without a scheduled release window or special approval

The health radar makes the team's assessment of its own functioning visible as a multi-dimensional picture — the irregular shape immediately highlights where the team is thriving versus struggling, without reducing everything to a single score.

The radar format has specific advantages: teams immediately spot outlier dimensions (one very long spike = exceptional strength; one very short spike = critical weakness); the overall "area" of the shape roughly indicates overall team health; and overlaying two radars (this quarter vs. last) shows improvement or regression at a glance. Teams can create their own dimensions relevant to their context — a DevOps-heavy team might include "deployment confidence" and "on-call burden" alongside more standard dimensions like "clarity of goals" and "team cohesion." The Scrum Master facilitates the rating session and coaches the team to discuss rather than just score.

Key vocabulary:
• health radar — a spider/radar diagram showing team self-assessment across multiple health dimensions
• health dimension — a specific aspect of team functioning assessed in the radar (collaboration, technical practices, morale, etc.)
• trend overlay — comparing two time-period radars to visualise improvement or regression across dimensions

Psychological safety is the foundation of high-performing teams — without it, retrospective feedback becomes sanitised, impediments go unspoken, and problems compound in silence until they become crises.

Amy Edmondson's research shows psychological safety is the single strongest predictor of team learning and performance (Google's Project Aristotle confirmed this). A drop can be caused by: a specific incident where someone was publicly criticised or blamed; leadership behaviour that signals disagreement is unwelcome; high-pressure delivery environments where "raising concerns" is perceived as being negative; or team composition changes. The Scrum Master's investigation should be careful — directly asking "do you feel psychologically safe?" may not get honest answers. Better approaches: observe behaviour in meetings (who speaks, who stays silent), conduct private 1:1 conversations, use anonymous retrospective formats, and examine whether retrospective actions are actually followed through (inaction on raised issues kills trust).

Key vocabulary:
• psychological safety — the team belief that interpersonal risk-taking (speaking up, admitting mistakes, disagreeing) will not be punished
• interpersonal risk — the perceived risk of being embarrassed, rejected, or punished for contributing ideas, questions, or concerns
• learning organisation — a team or company that systematically learns from mistakes and improves, enabled by psychological safety

Simultaneous reveal is the most important facilitation technique in a health check — it produces authentic data by preventing the anchoring effect where people adjust their rating to match whoever spoke first.

The anchoring effect is powerful: if the first person says "I think our deployment process is pretty good — yellow," most people will anchor near yellow even if their private assessment was red. Simultaneous reveal (Roman voting with thumbs, playing cards, or digital tools like Mentimeter) captures each person's independent assessment. The most valuable moments in health check facilitation are the "maximum variance" points — where one person's green and another's red coexist. This disagreement usually reveals that people have different information, different definitions of "good," or different experiences of the same team. Exploring these gaps is where the real team learning happens.

Key vocabulary:
• simultaneous reveal — a facilitation technique where all participants show their votes at the same time to prevent anchoring
• anchoring effect — the cognitive bias where people adjust their assessment toward the first number or opinion they hear
• maximum variance — the health check dimensions where team members' ratings differ most widely, indicating the richest discussion opportunities

This message is focused on facilitating open communication and identifying impediments. The goal isn't task assignment or formal feedback requests; instead, it's a proactive attempt to create a more supportive environment by surfacing potential issues that could be slowing down the team's velocity. Recognizing and addressing these roadblocks is key to maintaining healthy sprint flow.

The health radar indicates a systemic issue requiring focused attention. While training or champions can be helpful long-term, the immediate step is to proactively address the conflict through structured discussion and root cause analysis – a retrospective specifically designed for this purpose is most effective. Impact mapping provides a tangible way to understand the consequences of the conflict, driving more productive conversation.

The lack of context in David's comment signals a potential issue with transparency and collaboration. A healthy team proactively shares information about complexity, impact, and dependencies – this demonstrates consideration for others and reduces the risk of unintended consequences. Concise comments aren't necessarily bad, but they can mask underlying problems.

'Blocked' due to documentation suggests a breakdown in communication and dependency management. Teams rely on each other's knowledge; if someone is blocked because they lack clarity on an API endpoint, it highlights a need for improved processes around requirement definition, knowledge sharing, or potentially poorly defined dependencies. This isn't necessarily about skill – it's about efficient collaboration.

Structured feedback methods are more likely to promote honest responses. Standardized questionnaires with rating scales provide a safe and measurable way for individuals to express their views without feeling judged. This minimizes defensiveness because the data itself is less subjective than a free-flowing discussion.