As a project manager, how do you approach diagnosis of poor team health?

Khaled El Haj Ismail
Excellent article — the five symptoms outlined (especially the “Comfort Trap” and high turnover) offer a clear and actionable framework for proactively diagnosing team dysfunction. Concise, memorable, and strategically relevant.

In some project environments, professionals have found it helpful to complement this type of symptom-based monitoring with a mix of structured tools and informal observation.

A few effective practices include:
- Team health checks:
Tools like the Spotify Squad Health Check or even basic Niko-Niko calendars provide real-time, visual indicators of morale, trust, and team alignment. More than just dashboards, they initiate meaningful dialogue.
- A four-layer listening model, inspired by clinical diagnostics:
* Inspection: observing visible behaviors and energy shifts
* Palpation: informal check-ins to detect early tensions
* Percussion: one-on-one conversations to reveal deeper disconnects
* Auscultation: anonymous surveys or feedback mechanisms to surface what remains unsaid
- Root-cause techniques:
When teams feel disengaged or “off,” applying methods like the 5 Whys often helps reveal hidden causes — such as lack of recognition or misaligned priorities.
- Retrospectives with emotional mapping: Going beyond deliverables to explore how the team felt during a sprint — identifying energy drains or sources of motivation — supports adaptive leadership and psychological safety.

Altogether, this approach frames team health not as a periodic check-up, but as a dynamic system shaped by culture, clarity, cadence, and care.

It would be interesting to know whether the original five-symptom model is envisioned as an open framework — or whether there’s room for integrating some of these practical tools into future iterations.

Thanks again for initiating such an important and timely conversation.