What I learned from measuring team health instead of productivity

Productivity tells you what a team produces. Health tells you whether they can keep producing. These are not the same thing — and only one of them predicts burnout before it happens.

---

When I built my first team of technical communicators, I set myself a goal that wasn't in any management handbook I'd read: I wanted to know if my team was okay. Not performing — okay.

The problem was that most team health metrics I found were really productivity metrics in disguise. Some quantity of output over some unit of time. Useful, sure, but they told me nothing about how people felt walking into work on a Monday, or how close someone might be to burning out quietly while still hitting their numbers.

Productivity is a lagging indicator. By the time it drops, something has usually already gone wrong. I wanted to catch the signal earlier.

Why this team, specifically

My team occupied an unusual position. They were technical communicators deployed to support agile development teams — but they weren't included in agile rituals like sprint health checks, because they were considered observers rather than participants. Their output was high-visibility and in constant demand, but their role as the people producing it was largely invisible. They were good enough at their jobs that they were often only noticed when something went wrong.

I also had something specific I wanted to reinforce: a team culture built around two values — meaning and learning. I had plenty of ways to quantify their work's impact on stakeholders. What I didn't have was any way to measure how they felt about it. That gap felt like a risk, both to the people and to the team.

The survey

I used a Slack integration to deliver a monthly four-question survey. Each question used a simple 1–4 scale (1 = not really, 4 = very much):

1. My work feels meaningful

2. Meaningful work matters to me

3. I am learning through my work

4. Learning through my work matters to me

The pairing was intentional. Asking both "does this feel meaningful?" and "does meaningfulness matter to you?" let me calibrate. Someone for whom learning is a core value but who isn't learning right now has a real problem to solve. Someone who rates learning low on both dimensions is probably fine — it's just not what drives them.

Before rolling this out, I was transparent with my team about three things: their responses would not automatically trigger action; they would be a topic in our next 1:1; and nothing would go further without their permission. That last part mattered. People need to know the data isn't being used against them.

What the data showed

Both meaning and learning were consistently rated as highly important. But both declined noticeably in the lead-up to quarterly and annual roadmap planning — high-stress periods when everyone's bandwidth was compressed and work felt reactive rather than purposeful.

I couldn't restructure the company's planning cycle. What I could do was show up differently during those windows: building learning content into team meetings, sending small gestures of acknowledgment, making it explicit that I knew the current sprint wasn't their favorite work and that it still mattered.

This is what I'd now call a regenerative approach to leadership — not eliminating stress, but building the conditions that help people recover from it and stay in the work long-term.

How it changed my 1:1s

The survey data gave me a standing agenda item that had nothing to do with output. A quick glance before each 1:1 told me how much space I needed to hold. If meaning mattered a lot and current work felt meaningful, we'd have a brief, energizing conversation and I'd learn something about what made it land. If meaning mattered a lot but current work didn't feel meaningful, we had something to solve.

Two examples of what that problem-solving looked like in practice:

Issue: "This work is really meaningful, but I feel like I'm stagnating. I wish I had more opportunities to learn new skills."

Resolution: "Let's look at your capacity and carve out 5% of the next quarter's sprints for learning. Come back to me with what you'd most want to explore — a soft skill, a tool, or an internal product area."

Issue: "I'm learning a lot supporting the backend team, but it's not super meaningful for me. I prefer user-facing work."

Resolution: "I can't move you full-time right now, but one of the user-facing teams is a bit under-resourced. Your capacity could accommodate 10% of your time there. Would that help?"

Neither of those conversations would have happened if I'd been looking only at output metrics. The work was getting done. There was nothing in the data to flag — until there was.

A few things worth noting before you try this

Both companies where I ran this had whole-person wellbeing as an explicit company value, which gave the effort organizational legitimacy. If that's not the case where you work, you'll want to think about how to frame it. The tactic can still work — but it needs to be credible, not performative.

The survey questions I chose were specific to the values I'd defined for my team. Other functional teams — business development, customer success — might use the same structure but with entirely different health dimensions. That's the point: this isn't a plug-and-play template. It's a way of taking seriously the question of what your team actually needs to sustain their best work.

That question is worth asking more often than most of us do.