Slack messages tell you what your team is doing. They do not tell you how your team is feeling. By the time burnout, frustration, or disengagement show up in Slack behavior (shorter replies, slower response times, less emoji), the damage is already done.
This guide shows you how to use the Team Health Check alongside Slack to catch problems early and build a team that actually talks about how work feels.
Why Slack Teams Need Health Checks
Remote and hybrid teams live in Slack. The tool is excellent for coordination but terrible for surfacing how people feel about the work itself. Nobody posts "I'm burning out" in a public channel. Health checks create a structured, safe way to surface these signals.
The Spotify model popularized team health checks: a set of dimensions (speed, quality, fun, learning, mission) that teams rate on a simple scale. Green means good. Yellow means warning. Red means fix this now.
The Health Check Workflow
Step 1: Generate your health check. Open the Team Health Check and select the dimensions that matter for your team. Common ones include: delivery speed, code quality, teamwork, learning, support from leadership, and work-life balance.
Step 2: Set up a Slack channel. Create a dedicated channel called #team-health or #retro-pulse. This is where health check results are shared and discussed. Keep it separate from project channels so it does not get buried.
Step 3: Run the check bi-weekly. Share the health check link in Slack every two weeks. Give the team 24 hours to respond. Anonymous responses get more honest answers than public ones.
Step 4: Share and discuss results. Post the aggregated results in #team-health. Highlight dimensions that changed since last time. A metric dropping from green to yellow is more important than one that has been yellow for three months.
Integrating with Slack Workflows
Use Slack's Workflow Builder to automate the health check cadence. Create a workflow that posts a reminder to #team-health every other Monday with the health check link. No manual effort required after setup.
For teams that want quick pulse checks between full health assessments, use Slack's built-in polls. Post a simple question each Friday: "How was your week? Rate 1-5." Track the average over time. When it trends downward, run a full health check to understand why.
Create a Slack bookmark in your team channel that links directly to the health check tool. This removes the friction of finding the URL every two weeks.
What to Do with Health Check Results
Results without action destroy trust. If your team reports that "learning" is red, you need to respond within the next sprint. Here are common interventions by dimension:
- Speed (red): Remove blockers. Cut WIP limits. Cancel unnecessary meetings.
- Quality (yellow): Allocate time for tech debt. Add code review standards.
- Fun (red): This is often a symptom, not a root cause. Dig deeper. Fun drops when autonomy or mastery drops.
- Support (yellow): Schedule 1:1s. Ask what your team needs that they are not getting.
Connecting Health Checks to Retrospectives
Health checks show the trend. Retrospectives dig into the why. Run health checks bi-weekly and retrospectives at the end of each sprint. When a health check dimension drops, make it a retro discussion topic.
This creates a feedback loop: health check surfaces the signal, retro identifies the root cause, action items fix the problem, next health check confirms the fix worked.
For teams that need to understand how health connects to delivery, pair your health data with sprint velocity tracking. Teams with consistently red health metrics often have declining velocity. The data makes the case for investing in team health.
Review the RICE framework if you need to prioritize which health issues to fix first when multiple dimensions are struggling.