Run a product team health check and build an improvement plan

The Team Health Problem Nobody Talks About Until It's Too Late

Product teams don't fail overnight. They decay slowly: one skipped retro, one ignored conflict, one quarter where "we'll fix the process after this deadline" becomes permanent. By the time leadership notices, the damage is done — top performers have checked out, and the remaining team is stuck in a pattern they can't diagnose from the inside.

According to Google's Project Aristotle research, the single strongest predictor of team effectiveness is psychological safety — the belief that you won't be punished for making a mistake or raising a concern. Yet a 2024 Atlassian survey found that only 31% of product team members feel "very safe" expressing disagreement with their manager's product decisions.

Why Ad Hoc Retrospectives Aren't Enough

Most teams rely on sprint retrospectives for team health. The problem is that retros focus on recent events ("this sprint was hard because...") rather than systemic patterns. A team that consistently scores low on customer connection won't surface that in a retro about missed deadlines. You need a periodic, structured assessment that covers all dimensions of team health — not just what's top of mind today.

Spotify pioneered the Squad Health Check model, where teams self-assess across multiple dimensions using red/yellow/green ratings. The power isn't in the scores themselves but in the conversations they trigger. When a team collectively rates "mission clarity" at 2/5, that's a different conversation than any individual complaint could produce.

How the Product Team Health Check Prompt Works

This prompt assesses 12 dimensions across four categories: product & strategy, process & delivery, collaboration & culture, and growth & sustainability. Each dimension gets a 1-5 score with specific criteria. Pattern analysis groups weak dimensions into themes and maps cause-and-effect relationships. The improvement plan targets the top 3 issues with specific interventions, owners, and metrics. A team agreement step ensures the improvement plan isn't imposed top-down but owned collectively.

The cause-and-effect mapping in Step 2 is where the real insight happens. Low decision speed often causes low shipping cadence, which causes low morale, which causes low psychological safety. Fixing the downstream symptoms without addressing decision speed guarantees the problems return.

When to Use It

• Your team has been together for 3+ months and hasn't done a structured health assessment
• Retrospectives keep surfacing the same themes without resolution
• Team attrition is increasing or engagement survey scores have dropped
• You've recently reorged and need to establish a baseline for the new team
• Cross-functional tension (PM vs. eng, design vs. PM) is affecting output quality

Common Pitfalls

The PM runs the health check and "fixes" everything. Team health is a shared responsibility. If the PM diagnoses, plans, and assigns all improvements, you've reinforced the dynamic that caused the problems. Distribute ownership.

Scoring too generously. Teams that consistently rate themselves 4-5/5 are either exceptional or in denial. Calibrate by asking: "Would you recommend this team to a talented friend?" The answer reveals the truth.

Treating it as a one-time exercise. One health check finds problems. Quarterly health checks build a culture of continuous improvement. The trend matters more than any single snapshot.

Sources

• Project Aristotle: What Makes Teams Effective — Google's landmark research on team effectiveness
• Only 31% of Team Members Feel Safe Expressing Disagreement — Atlassian's team health research and playbook
• Spotify Squad Health Check Model — Spotify's original framework for team self-assessment