Team health checks give engineering managers a structured way to assess how their team is doing across multiple dimensions — from technical practices to psychological safety. Regular health checks surface problems before they become crises, celebrate what is working well, and create a shared understanding of team dynamics. This guide covers how to design, facilitate, and act on team health checks.
What Is a Team Health Check
A team health check is a structured assessment where team members evaluate their collective performance, practices, and wellbeing across a set of predefined dimensions. Unlike individual performance reviews, health checks focus on team-level dynamics — how well the team collaborates, whether processes support or hinder delivery, and whether people feel engaged and supported.
The most well-known model is the Spotify Squad Health Check, which evaluates dimensions like 'Easy to Release,' 'Teamwork,' 'Pawns or Players,' 'Mission,' and 'Fun.' Each dimension is rated using a traffic light system: green (good), amber (some concerns), or red (significant problems). The simplicity of this approach makes it accessible and non-threatening, which encourages honest participation.
For engineering managers, health checks serve multiple purposes. They provide early warning signals about team dysfunction, create a forum for discussing issues that might not surface in sprint retrospectives, and generate longitudinal data about team trends. A team that has been amber on 'Sustainable Pace' for three consecutive quarters is telling you something important.
Designing Your Health Check Dimensions
While the Spotify model is a good starting point, the most effective health checks use dimensions tailored to your team's context. An infrastructure team might include dimensions like 'On-Call Balance' and 'Toil Reduction,' while a product team might focus on 'Customer Understanding' and 'Feature Impact.' The dimensions should reflect what matters most for your team's success.
Aim for eight to twelve dimensions — enough to cover the important areas but not so many that the exercise becomes tedious. Group related dimensions into categories like Technical Practices, Team Dynamics, Process Effectiveness, and Individual Wellbeing. This structure makes it easier to identify patterns and focus improvement efforts.
Include at least one dimension that asks about psychological safety — whether team members feel safe to take risks, raise concerns, and admit mistakes. Research consistently shows that psychological safety is the strongest predictor of team performance, yet it rarely surfaces in traditional metrics or retrospectives.
- Technical Practices: code quality, testing, deployment confidence, technical debt management
- Team Dynamics: collaboration, communication, trust, conflict resolution
- Process Effectiveness: sprint planning, estimation accuracy, delivery predictability
- Individual Wellbeing: sustainable pace, learning opportunities, role clarity, psychological safety
Facilitating the Health Check
Run health checks quarterly — frequently enough to track trends but not so often that they become a burden. Set aside sixty to ninety minutes for the session. If your team is co-located, use physical cards or a whiteboard. For remote teams, use tools like Miro, Retrium, or a simple shared spreadsheet.
Start by explaining the purpose and ground rules. Emphasise that the health check is about the team, not about individual performance. Responses should be anonymous during the initial rating phase to encourage honesty. After everyone has rated each dimension, reveal the aggregate results and facilitate a discussion about areas with the most divergent ratings or the most concerning trends.
The facilitation skill lies in creating space for honest conversation without letting the discussion become a complaint session. When the team rates a dimension as red, ask structured questions: What specifically is not working? What would good look like? What is one concrete step we could take to improve? This solution-oriented approach keeps the energy constructive.
Acting on Health Check Results
A health check without follow-through is worse than no health check at all — it signals that leadership asks for feedback but does not act on it. After each session, identify one to three specific actions the team will take to address the most pressing concerns. Assign owners and deadlines to each action.
Not every red dimension requires immediate action. Some issues are outside the team's control, and others may be temporary. Prioritise actions based on impact and addressability. An amber rating on 'Learning Opportunities' that has been trending downward for two quarters deserves more attention than a one-time red on 'Sprint Planning' caused by a specific unusual event.
Track actions from previous health checks and report on progress at the next session. This creates accountability and demonstrates that the exercise has real consequences. Over time, teams that see their feedback leading to tangible improvements become more engaged and more honest in their responses.
Common Health Check Pitfalls
The most damaging pitfall is using health check data to compare teams against each other or to evaluate engineering managers. If teams believe their health check ratings will be used to judge them, they will inflate their scores and the data becomes worthless. Health check data should be owned by the team and shared upward only with the team's consent.
Another common mistake is running the health check but never changing anything as a result. After two or three cycles of raising the same concerns without seeing action, team members disengage from the process entirely. If you cannot address a concern, explain why — transparency about constraints builds trust even when the outcome is not what the team hoped for.
Avoid letting the loudest voices dominate the discussion. Use structured facilitation techniques like silent brainstorming, round-robin sharing, or anonymous voting to ensure that quieter team members have an equal opportunity to share their perspectives. The most valuable insights often come from people who do not naturally speak up in group settings.
Key Takeaways
- Run health checks quarterly with eight to twelve dimensions tailored to your team's context
- Include at least one dimension on psychological safety — it is the strongest predictor of team performance
- Always follow through with one to three concrete actions after each health check
- Keep health check data owned by the team to ensure honest participation
- Track trends over time — patterns across quarters are more valuable than individual snapshots
Frequently Asked Questions
- How is a team health check different from a sprint retrospective?
- Sprint retrospectives focus on recent work and specific process improvements within a short time frame. Team health checks take a broader, longer-term view of team dynamics, practices, and wellbeing. Retrospectives ask 'What went well and what should we change about our last sprint?' Health checks ask 'How healthy is our team across multiple dimensions and how has that changed over time?' Both are valuable and complementary — retrospectives for tactical improvements and health checks for strategic team health.
- Should health check responses be anonymous?
- Anonymous responses during the initial rating phase encourage honesty, especially for sensitive dimensions like psychological safety or management effectiveness. However, the discussion phase should be open and attributed — the value of a health check comes from the conversation, not just the ratings. A common approach is to collect anonymous ratings, reveal the aggregate results, and then invite open discussion about the patterns. Over time, as trust increases, teams often become comfortable sharing their individual ratings openly.
- What if my team's health check scores are consistently low?
- Consistently low scores indicate systemic issues that need sustained attention. Start by identifying the root causes — are the issues within the team's control or driven by organisational factors? For internal issues, create a focused improvement plan with measurable goals. For external factors, escalate to your leadership with data from the health checks to support your case. Do not try to fix everything at once; focus on the one or two dimensions that, if improved, would have the biggest positive impact on the others.
Browse the EM Field Guide
Access team health check templates, facilitation guides, and action planning worksheets designed for engineering managers.
Learn More