Ask any team lead: "Is your team healthy?" You'll probably get "I guess so" or "there are some issues."
Push further: "Which areas are good, which need work?" They'll hedge: "Communication... maybe some... collaboration... overall it's okay."
This isn't because the lead doesn't know the team. It's because "team health" is too vague. Without a structured assessment framework, any discussion about team state devolves into everyone talking past each other.
Team health checks decompose that fuzzy concept into evaluable dimensions, turning "can't quite articulate" into "clearly visible."
What Is a Team Health Check?
A team health check is a structured self-assessment tool—team members anonymously rate a set of dimensions, quickly producing a health profile of the team as a whole.
Atlassian has a tool called Team Health Monitor. SessionLab has team health check retrospective templates. The concept is the same: break "team health" into several dimensions, have everyone rate anonymously, then review and discuss the results together.
The core value isn't the scores themselves—it's the conversation the assessment process triggers. When team members see "goal clarity scored only 2.5," they naturally ask "why is it so low?" That question drives more natural, more motivated discussion than any facilitator prompt.
Choosing Assessment Dimensions
There's no standard answer for team health dimensions, but a good framework should cover the key aspects of how a team operates. I typically use these 6 dimensions:
Each dimension gets 3-4 items on a 5-point scale. Total: 18-24 questions, 5 minutes to complete.
Dimensions should be tailored to the team type. Engineering teams might need "technical debt" and "engineering culture." Sales teams might need "incentive structure" and "customer orientation." The key is aligning dimensions with what the team actually cares about, not applying a generic template.
How to Use It in a Workshop
The most typical use case is as a workshop pre-assessment and opening activity.
Send the assessment link 3 days before the workshop. Participants fill it anonymously, and the system automatically aggregates results. The facilitator walks into the workshop already holding the team's health profile—which dimensions scored low, which have high variance (large standard deviations).
Display results at the workshop opening. Show each dimension's score on a radar chart. Don't rush to analyze "why is this so low?"—first let everyone see it.
One critical detail: never display individual scores—only team aggregates. If the team has only 5 people, even anonymous responses can be traced. For teams under 5 people, health check data should be treated as directional—its main value is "starting the conversation," not "precise measurement."
Design discussion based on results. The 1-2 lowest-scoring dimensions become the workshop's focus topics. If "psychological safety" scored 2.5, spend more time on that. Don't skip the highest-scoring dimensions either—"why do you think this dimension scores high? What's working?" Success patterns are equally worth surfacing and reinforcing.
Disagreement is more valuable than low scores. If "goal clarity" averages 3.5 but has high standard deviation—some team members think goals are clear, others don't. That disagreement itself is the problem to discuss: "Why do people have different understandings of the team's goals?"
The Importance of Anonymity
Team health checks must be collected anonymously. If participants worry their responses can be traced, they'll inflate scores—especially on sensitive dimensions like "psychological safety" and "feedback frequency."
Practices for ensuring anonymity:
- Use a third-party tool for collection, not someone internal to the team
- For teams under 5, don't show individual dimension data—only team averages
- State clearly at the survey's start: "Data is collected anonymously and cannot be traced to individuals"
- When presenting results, don't say "someone rated 1"—say "the lowest score on this dimension was 1"
From Snapshot to Trend: Quarterly Tracking
A single health check is just a "snapshot"—it tells you the team's current state. The real value comes from running it regularly and building a trend.
I recommend quarterly team health checks. After three rounds, you have trend data: which dimensions are improving, which are stagnant, which suddenly dropped. Trends are far more persuasive than single snapshots—"psychological safety improved from 2.8 in Q1 to 3.6 in Q3" carries more information than "current psychological safety is 3.6."
Regular checks also validate interventions. If Q1 showed "feedback frequency" was low, and Q2 introduced weekly 1:1 feedback sessions, did the Q3 score improve? If yes, the intervention worked. If not, the mechanism didn't stick or the approach needs adjusting.
The most overlooked value of team health checks is "making silent problems visible." Many team problems don't not exist—nobody voices them. Members feel "feedback is lacking" but don't want to say it. Managers feel "goals aren't clear enough" but assume it's just them. Health checks use anonymous data to surface these issues—no one needs to bravely raise their hand. The data speaks for itself.
🛠️ Build a Team Health Check in FormLM
From dimension design to result display, FormLM supports the full health check flow:
- Use scale fields to design a 6-dimension assessment, each with behavior-anchored descriptions
- Use share links for anonymous collection—participants don't need to register, 3 minutes to complete
- Use radar charts to display the team's health profile—strengths and gaps visible at a glance
- Use dimension scores to view each dimension's average and distribution, identifying disagreement
- Use Insight pre-post comparison for quarterly tracking with dimension score trend lines
- Use AI reports to auto-generate a team health diagnostic report with improvement recommendations
✅ Key Takeaways
- Team health checks decompose vague "team state" into evaluable dimensions, making problems visible
- Core value isn't in scores—it's in the conversation the assessment triggers. Data surfaces silent problems
- Six common dimensions: Goal clarity, role clarity, collaboration quality, psychological safety, feedback frequency, growth
- Send assessment 3 days pre-workshop, display radar chart at opening, focus discussion on low-scoring dimensions
- Disagreement (high standard deviation) is more diagnostically valuable than low scores
- Anonymous collection is non-negotiable; quarterly tracking turns snapshots into trends