Framework · People leadership · 2 min read
Team health check
A quarterly anonymous 1–5 survey on clarity, safety, feedback, growth, workload and cross-domain connection, followed by a discussion of the lowest scores, so you see team problems before they become crises.
Do people know what is expected of them?
"I understand what's expected of me."Can people speak up without fear?
"I can raise problems and tough issues."Does feedback reach people and help them?
"I get useful feedback on my work."Are people developing their skills?
"I'm learning and growing."Can people keep this pace over time?
"My workload is sustainable."Matters most when designers are embedded in separate product teams.
"I feel connected to designers in other teams."Quarterly · anonymous · 1–5 · discuss the lowest score
Use it when
- You want a regular, honest signal of how the team is doing, beyond what you hear in 1:1s.
- Your designers are embedded in different product teams and rarely work together.
- You have changed something (a new ritual, a reorganisation) and want to see if it helped.
How to use it
- Keep it to about six questions. Use the six statements in the diagram, each scored 1 to 5, and keep the wording the same every quarter so you can compare. Output: a short anonymous survey.
- Run it quarterly and anonymously. Use a tool that hides names. Tell the team why you ask and what you will do with the answers. Output: scores from most of the team.
- Find the lowest score. Look at averages and the spread. One very low score can matter more than a medium average. Output: the one item to discuss.
- Discuss the lowest item, not all of them. In a team session of about 45 minutes, share the results and ask "What is behind this score? What would move it up by one?" Output: one or two causes the team agrees on.
- Change one thing and track the trend. Agree one action with an owner. Next quarter, compare the trend for that item. Output: one action and a trend line per item.
Worked example
A UX lead on an internal operations platform runs the health check with seven designers spread across product teams.
| Item | Q1 | Q2 |
|---|---|---|
| I understand what's expected of me. | 4.1 | 4.2 |
| I can raise problems and tough issues. | 3.6 | 3.8 |
| I get useful feedback on my work. | 3.4 | 3.9 |
| I'm learning and growing. | 3.8 | 3.7 |
| My workload is sustainable. | 3.2 | 3.3 |
| I feel connected to designers in other teams. | 2.4 | 3.1 |
In Q1, connection is lowest. The team says they only meet at the monthly all-hands. They start a bi-weekly cross-team Design critique, and the score rises in Q2. Workload is now the lowest, so that becomes the next discussion.
Watch out for
- Discussing everything. Six items in one session gives shallow talk and no action. Pick the lowest one.
- Chasing the number. A score of 3.5 means little on its own. The direction over several quarters tells the story.
- Breaking anonymity. In a small team, splitting results by role or location can reveal who said what. Only show team-level results.
- No visible action. If nothing changes after the survey, fewer people answer next time, and they answer less honestly.
Template
Copy these statements into your survey tool. Scale: 1 = strongly disagree, 5 = strongly agree.
Team health check (quarterly, anonymous, 1-5)
1. I understand what's expected of me.
2. I can raise problems and tough issues.
3. I get useful feedback on my work.
4. I'm learning and growing.
5. My workload is sustainable.
6. I feel connected to designers in other teams.
Optional: What is one thing that would make this team better?
Results discussion
Lowest item:
What is behind this score?
What would move it up by one?
Action / owner / check next quarter: