The 5 Team Health Metrics Every CTO Should Be Tracking
Most CTOs can tell you their deployment frequency, their mean time to recovery, and how many tickets are in flight this sprint. That data is visible, trackable, and sitting right there in your tooling.
What most CTOs cannot tell you is whether their team is actually okay.
Not in the “nobody has quit this month” sense. In the real sense: whether people feel heard, whether the work feels sustainable, whether engineers know what they’re supposed to be focused on. That information exists too. It’s just not being collected in any systematic way.
That’s the gap CrewPulse is built to close. And it starts with five signals.
Why “metrics” and not just “vibes”
Before we get into the list, it’s worth being direct about why this matters as a measurement problem and not just a management one.
Gut feel is a lagging indicator. By the time something starts to feel wrong, it usually already is. The engineer who seems disengaged has been disengaged for weeks. The team that feels underwater has been underwater for a sprint or two. The friction that surfaced in your last retrospective has been building since the one before.
The SPACE framework, developed by researchers from Microsoft Research, GitHub, and the University of Victoria, was built on exactly this premise: developer productivity cannot be captured by any single metric. It spans five dimensions including satisfaction and wellbeing, communication and collaboration, and efficiency and flow. The human dimensions aren’t separate from the performance dimensions. They are performance dimensions. And when they start to slip, there are early signals well before output drops.
The five metrics below are what CrewPulse tracks every week, across every team. They are lightweight by design: a single question per signal, answered in under a minute, aggregated across the team so no individual response is exposed. The goal isn’t surveillance. It’s visibility.
1. Morale
The question: How much are you enjoying your work this week?
Morale is the one most leaders already have an instinct for, which is exactly why it’s dangerous to rely on instinct alone. A team can look fine in standup and score low on morale consistently for weeks. The gap between how people perform in a group setting and what they actually feel is real, and it’s wider than most leaders want to admit.
Low morale is rarely about the work itself. It’s usually about the conditions around the work: unclear direction, interpersonal friction, feeling like effort isn’t being recognized, or simply being asked to do too much for too long. Tracking it weekly means you catch the trend before it becomes a crisis.
What to watch for: a steady decline over three or more weeks, or a sudden drop that coincides with a specific event like a reorg, a missed launch, or a difficult sprint.
2. Workload
The question: How sustainable is your current workload?
This one is deceptively simple. Engineers are generally reluctant to say they’re overwhelmed, especially in high-performing cultures where carrying a heavy load can feel like a badge of honor. A direct weekly question cuts through that.
Sustained overload is one of the most predictable paths to disengagement and attrition. And the cost of replacing a senior engineer is high enough that catching it early is always worth the effort.
What to watch for: workload scores trending down during periods of high delivery pressure, which often signals that scope needs to be cut or capacity needs to be added before something breaks.
3. Priority Clarity
The question: How clear are your priorities for this week?
This is the signal that surprises leaders most when they first see it scored. Teams that look aligned in planning often have very different individual experiences of what actually matters day to day. When engineers are unclear on priorities, they either grind through everything at once (leading to workload problems) or make their own calls about what to focus on (leading to delivery surprises).
Unclear priorities are usually a systems problem, not a people problem. They show up when roadmaps shift faster than communication does, when there are too many competing priorities at the team level, or when individual engineers are being pulled in multiple directions by multiple stakeholders.
What to watch for: low priority clarity scores that correlate with PRs sitting open longer than usual or tickets stalling mid-sprint. That combination is a strong signal that engineers don’t know what to finish first.
4. Communication
The question: How well is the team communicating right now?
Communication is the connective tissue of a healthy engineering team. When it’s working, problems surface early, decisions get made cleanly, and people feel like they’re rowing in the same direction. When it breaks down, the symptoms show up everywhere else: in morale, in workload, in delivery.
This signal is particularly valuable for distributed and remote teams, where the ambient feedback of an office environment doesn’t exist. Without intentional structure, remote teams can drift into silos without anyone noticing until the work starts to show it.
What to watch for: communication scores dropping during periods of team growth, leadership change, or increased remote work. These are the moments when communication norms need the most active maintenance and get the least.
5. Blocked
The question: How blocked are you feeling right now?
This one is scored inversely: a high score means the engineer feels very blocked, which is bad. It’s also the signal most directly connected to delivery.
Being blocked is different from being busy. A blocked engineer isn’t making progress regardless of how much effort they put in. They’re waiting on a decision, a dependency, a review, or a piece of information that hasn’t arrived. And in most teams, blocked work is invisible until someone mentions it in standup – which, as we’ve already established, doesn’t always happen.
What to watch for: high blocked scores alongside stale tickets or PRs that have been open for days with no activity. That combination almost always means something specific is stuck and needs active intervention, not just a process tweak.
How the signals work together
The real power of these five metrics isn’t any one signal in isolation. It’s what happens when you read them together, and when you layer them against your delivery data.
A team with low morale and high blocked scores is a different problem than a team with low morale and unsustainable workload. A team with unclear priorities and stalling PRs needs a different conversation than a team with poor communication and unclear priorities.
The combinations tell you not just that something is wrong, but roughly where to look and what kind of conversation to have. That’s what turns a set of weekly check-in scores into something actionable for an engineering leader who already has too much on their plate.
None of this replaces good management. It makes good management more informed.
CrewPulse tracks all five of these signals weekly, alongside your delivery data, so you can see the full picture in one place. Get early access here.