Team Health Scan

Rate twelve factors on what you have actually seen, set your picture against the team's own, and choose the one condition worth fixing first. The factors cover how the team is set up, how it works together and what it produces.

Psychological safety is strong research (Edmondson, 1999; meta-analysis: Frazier et al., 2017). Hackman's team conditions have mixed support (Hackman, 2002; Wageman, Hackman & Lehman, 2005). Relationship conflict is reliably harmful, while the effect of task conflict is contested (Jehn, 1995; de Wit, Greer & Jehn, 2012). The twelve factors, the lens mapping and the traffic-light bands are a practice tool, not a validated instrument.

Use it when:

• You lead a team, or have just taken one over, and want a structured picture before you change anything.
• Something feels off (missed handoffs, quiet meetings, rising friction) and you want to locate it instead of guessing.
• You are a team member and want to raise a concern with your manager as an observation with evidence, not a complaint.

Skip it when:

• The problem is one conflict between two people: use 4.6 Conflict & Feedback Guide.
• You need a full culture or climate survey across several teams: use 4.10 Culture Snapshot.

Team research keeps pointing away from personalities and toward set-up. Hackman (2002) argued that teams do well when a few conditions hold: a real team with stable membership, a compelling direction, an enabling structure, a supportive context and coaching on hand. Those conditions can be measured reliably (Wageman, Hackman & Lehman, 2005), but whether they cause performance is less settled, so use them as a strong checklist rather than a law. Two climate factors sit on top. Psychological safety, the shared belief that it is safe to ask, admit an error or disagree, has strong support as a driver of team learning (Edmondson, 1999). And the kind of conflict matters: personal friction is consistently linked to worse team outcomes, while disagreement about the work is neither reliably good nor reliably bad (Jehn, 1995; de Wit, Greer & Jehn, 2012).

So a red rating here is a design question before it is a people question. Conditions can be redesigned and climate can be built. The limit: a twelve-factor scan is a structured opinion, not a measurement, which is why every rating needs evidence and a second view.

Write down what you are rating and from where. A manager and a team member see different parts of the same team.

Strong answer: "Customer service team, 9 people, last three months, rated by me as team lead; I see the planning side well and the evening shift poorly."

Team and size:

Period you are rating:

Your seat, and what you cannot see from it:

Illustrative example: the roles, the company and all numbers are made up.

The team lead of a nine-person customer service team at a Danish ferry operator runs the scan after a quarter with more complaints.

Section 1: three months, rated as team lead; the evening shift is a blind spot.

Section 2: seven greens, three ambers (psychological safety, energy, accountability), two reds (workload, results). Evidence for workload: "Evening queue over 20 minutes on 31 of 60 days."

Section 3: anonymous form, 8 of 9 answered. The team agrees on workload but rates role clarity green, which she had expected to be the problem.

Section 4: workload is the root: a condition, not a people problem. A second route opened and the rota stayed the same. Results and energy follow from it.

Section 5: one person moves to evening shift twice a week from next month, and the team agrees which evening tasks can wait until morning. Rescan in eight weeks. At the rescan, workload is amber and results green; psychological safety is still amber and becomes the next focus.