Team Health Check Workshops: How to Make Them Honest

If your team health check wraps up with everyone nodding at a series of amber scores and agreeing to communicate better, you've missed the mark. That's not a health check; that's just being polite. The real question isn't whether dysfunction exists—it's whether your workshop is set up to uncover it.

Team health checks may be a staple in agile and high-performance teams, but they're flawed from the start. Asking for honesty in the very environment that makes it risky to be honest is a design failure. You need more than good intentions and a scoring template; you need meticulous planning to get it right.

Why Team Health Checks Often Mislead

The biggest obstacle to honesty in health checks is social desirability bias. In group settings, people often tailor their responses to fit in or avoid conflict. Amy Edmondson's research at Harvard Business School on psychological safety makes it clear: individuals under-report issues when they fear personal risk, even in supposedly anonymous surveys if they think their answers could be traced back.

Most ready-made health check templates exacerbate this by favoring consensus. Averaging scores and displaying team means effectively silences outliers, which is where the real issues often hide. If three people rate 'Psychological Safety' as a 9 and one as a 2, averaging to a 7 doesn't mean the team is fine. It signals that someone is experiencing something different, and no one has called it out yet.

Timing is another factor. Health checks right before or after evaluations can suppress honest feedback. Separating health checks from performance reviews isn't optional; it's essential for real candor.

Spotify's Squad Health Check Model was built to encourage honest self-assessment on factors like Delivery Pace and Mission. But as Henrik Kniberg noted, the model fails if facilitators accept green scores at face value without digging deeper. The scores aren't the outcome—the conversation they spark is.

Designing for Anonymous Input Without Losing Accountability

Balancing anonymity with accountability isn't about choosing one over the other; it's about timing. Delay attribution long enough for scores to reflect true perceptions, not social maneuvering.

A two-step process can help: participants submit scores privately using tools like Mentimeter or physical cards. Reveal these scores in aggregate before any discussion starts. This prevents dominant voices from setting the tone.

Importantly, separate scoring from explanations. Have participants jot down private, one-sentence rationales for their scores before seeing results. These notes become your discussion points, revealing issues like "we never finish what we start" or "direction changes without warning" without forcing anyone to own them publicly.

The Atlassian Team Health Monitor reduces scoring pressure by using a simple 'Works Well / Needs Attention' format. Their facilitation guide suggests simultaneous voting with physical cards flipped on a count of three, similar to Planning Poker, to make disagreements visible before verbal input can sway opinions.

For remote teams, platforms like Miro, EasyRetro, or Parabol allow for anonymous submissions with timed reveals. The golden rule: no peeking before the reveal. If the facilitator sees results early, they might unintentionally bias the session.

Bridging the Gap Between Voiced and Voted Opinions

Once scores are up, your job isn't to guide toward agreement but to uncover honesty. That's a different ballgame.

Discussions tend toward optimism unless managed otherwise. This isn't lying; it's conflict avoidance and a desire for resolution. APA's Group Dynamics journal shows groups often converge on the majority opinion, a behavior in line with Asch conformity effects. Who speaks first after scores are revealed shapes the entire narrative. Calling on the senior person first stifles diverse opinions.

Look out for the polite pivot: someone acknowledges a low score but quickly offers a justification—"we've been swamped" or "things will improve post-deadline." Note it, but bring the discussion back to the unvarnished truth. What do the scores indicate about the usual state, not just the exceptions?

A powerful tool from Liberating Structures is the 1-2-4-All technique. This sequence—solo reflection, pair discussion, groups of four, then the entire room—after score reveals helps ensure that low scores get the exploration they need. Minority opinions can be safely expressed before facing the entire group.

When Scores and Conversations Don't Align

The most telling signal isn't always the lowest score; it's the gap between the scores and the conversation that follows. If a team votes poorly on 'Decision Making' but then talks optimistically, something’s off. Address it directly: "The votes show concern, but our talk seems positive. What's happening between those two views?"

Guiding the Post-Score Conversation

Your first move after revealing scores sets the stage. The worst start is "What does everyone think?"—it hands the narrative to the loudest or most senior person. A better opener is neutral and observational: "I see disagreement on Delivery Pace and near-consensus on Psychological Safety. Let’s start with where we disagree." This positions you as an observer, not a conclusion-maker.

Before anything else, establish a clear understanding of data usage at the session's start. Participants need to know who will see the data, in what form, and for what purpose. If you can't answer, don't proceed—your trust architecture isn't ready.

Google's Project Aristotle found psychological safety is the top predictor of team effectiveness. This underscores why the post-score talk is crucial: it either strengthens or erodes the safety necessary for honest future scoring.

Guide the group toward action, not just diagnosis. Ask: "What one dimension do we want to improve before the next health check?" Teams that see no follow-up actions learn that scores are performative, degrading honesty in future sessions. A useful framework is celebrate, investigate, commit: acknowledge the green, dive into the amber or red, and end with a team-owned commitment.

Handling Leadership as a Problem

If the data points to leadership issues, and everyone is unsure what to do, that's a governance issue—not a facilitation one. Gallup research shows managers account for a significant portion of engagement variance. Leadership issues in health checks aren't rare—they're statistically likely.

Before the session, clarify whether the manager will participate as a scorer or an observer. Mixing these roles suppresses honest feedback, anonymity or not.

If scores consistently point to leadership behaviors, resist reframing as systemic issues. Address it head-on: "The data suggests issues with how direction is set or communicated. Is that accurate?"

Follow-up is as important as in-session handling. Help the team and leader agree on a specific, actionable change. "I will share quarterly priorities in writing before planning sessions" is actionable. "I'll improve communication" is not. If the leader won’t commit behaviorally, that's information HR or organizational partners need.

Making Checks Routine, Not One-Offs

A single health check is a snapshot. Regular checks—quarterly, or every two sprints—create trends. Trends tell the real story.

Teams seeing 'Delivery Pace' improve from amber to green over cycles understand what changed. Those stuck on red for 'Psychological Safety' over multiple sessions know something's unaddressed. Regular checks turn subjective feelings into evidence.

Rotate facilitators after a few sessions with an external coach. An internal facilitator transfers ownership, but having an external coach observe and debrief adds value.

Finally, adapt your dimensions. Using the same measures for a year teaches teams to optimize for them, not genuine improvement. Periodically retire mastered dimensions and replace them with new challenges. The tool should match the team's growth, not its origin.

McKinsey's look at ING Bank's agile transformation shows the key was not the tool itself but the consistent cadence and commitment to act on emerging patterns. The data informed systemic decisions, not just individual team retrospectives.

The Real Aim of a Team Health Check

Here's the shift: a team health check isn't just diagnostic. It's about building trust.

Each session that surfaces and addresses real issues increases honesty for the next. Sessions that gloss over discomfort train your team to ignore the process. The tool itself is secondary. What matters is the culture of honesty you nurture around it.

Workshop Weaver believes that thoughtful facilitation separates performative workshops from truly valuable ones. Team health checks illustrate this perfectly.

Before your next session, evaluate your health check design with one question: Does our process make it safer to voice the uncomfortable, or easier to avoid it?

If you're uncertain, you've got your answer.