What to Track When You Manage a Small Team

When I managed my first team, I tracked everything and understood almost none of it. I had a project board with color-coded statuses, a spreadsheet of weekly outputs, and a running log of every task I'd assigned. I spent maybe 90 minutes a week maintaining all of it. And at the end of the quarter, I still got blindsided by a performance issue I hadn't seen coming, a deliverable that was three weeks behind without anyone telling me, and a team member who was quietly looking for a new job.

The problem wasn't too little data. It was the wrong data.

I was tracking activity and output. I wasn't tracking health. I had no signal for whether people were overwhelmed, whether blockers were sitting unresolved, whether anyone felt disconnected from what we were actually trying to accomplish.

The team member who was job-searching, her name was Jordan, had been signaling for months in ways I wasn't reading. Her 1:1s were getting shorter. She was asking fewer questions in team meetings. She'd stopped volunteering for things. None of those signals showed up in my color-coded board. They weren't tracked anywhere. I only understood them in retrospect, after she gave notice, when I replayed the last three months and saw exactly what I'd missed.

Most small-team managers make the same mistake. Here's what I'd do differently.

The trap: output metrics vs. health signals

There's a meaningful difference between tracking outputs (what your team produced) and tracking signals (what your team is experiencing). Both matter. But most managers default entirely to outputs because they're concrete and easy to count.

The problem with output-only tracking is that it's a rearview mirror. By the time you see that output dropped last month, you're looking at a problem that was building for four weeks. The cause might be a team member who's been quietly overwhelmed, or a process that's broken, or a priority shift that nobody communicated clearly. Output numbers tell you something happened. They don't tell you why, and they don't tell you in time to do anything useful.

Leading indicators, the signals, are what tell you something is about to happen. And for small teams, leading indicators are almost entirely interpersonal and operational. They come from your 1:1s, your weekly reviews, and paying attention to patterns that don't show up in any spreadsheet.

"If you don't track anything, you're managing on vibes. That works until it doesn't, and when it doesn't, it tends to fail loudly."

The five signals worth tracking

For a team of three to eight people, I'd track these five things, and only these five. More than this and you're either managing the metrics instead of the work, or you're creating a surveillance dynamic that poisons the team culture.

1. Work in progress per person. Not what's assigned. What's actively being worked on right now. If someone has 14 open items and nothing's moving, that's a problem. If someone has 2 items and both are stuck waiting on someone else, that's a different problem. Work in progress is one of the best early signals for whether someone is underwater or underutilized, and it's almost impossible to see if you're not looking. I check this weekly, informally, sometimes just by asking "what are you actually working on right now" in a 1:1.

2. Blockers sitting more than 48 hours. This is the metric I wish I'd been watching earlier in my career. A blocker that's been unresolved for two days is usually a sign that either the person doesn't feel comfortable escalating, or they've tried and nothing happened, or there's a dependency problem nobody's admitted yet. I ask about blockers in every 1:1, not as a box-checking exercise but specifically: "Is there anything that's been in your way for more than a couple of days that you haven't been able to clear?" That framing surfaces things that "any blockers?" doesn't.

3. Completion rate vs. commitments. Are people finishing what they said they'd finish, at roughly the rate they said they'd finish it? Not as a performance measurement. As a calibration signal. When someone consistently over-commits and under-delivers, that's usually a problem with estimation or priorities, not effort. When the whole team starts missing commitments at once, something has shifted in the environment: capacity, clarity, or morale. Tracking this over time lets you see the pattern before it becomes a crisis.

4. Energy and engagement. This one isn't a metric. It's a read. But it's one of the most important signals you have. Are your 1:1s getting shorter and more surface-level? Is someone who used to bring ideas to team meetings now just nodding along? Are questions that used to get asked in group settings now going unasked? Gallup's research on employee engagement consistently finds that these behavioral shifts precede formal disengagement by weeks, sometimes months. Energy shifts show up in behavior before they show up in any performance measure. If you're paying attention, you can have the conversation early. If you're not, you find out when someone hands you a resignation.

5. Goal alignment: does your team know what matters this quarter? This sounds obvious. It isn't. I've done spot checks with teams where I ask each person individually: "What are the two or three things that matter most for us to accomplish this quarter?" The variance in answers is often stunning. People are working hard. They're just not all working toward the same thing. That's a manager problem, not a team problem. If your team can't articulate the current priorities without hesitation, the priorities aren't clear enough.

Try this week: In your next round of 1:1s, ask each person: "What's slowing you down right now that I probably don't know about?" That phrasing is different from "any blockers?" It acknowledges that you might not have visibility, which makes people more likely to actually tell you.

What to stop tracking

Just as important as what to track is what to let go of. There are metrics that feel useful and aren't. Hours worked. Meeting attendance. Slack response times. Lines of code. Tasks opened. These are activity metrics. They measure presence and motion, not outcomes and health.

Tracking activity at the individual level creates a surveillance dynamic, and surveillance culture poisons teams quickly. People start managing their metrics instead of their work. They spend time on things that look productive rather than things that are productive. You get compliance instead of commitment, and you spend more of your time auditing than managing.

The other thing to stop tracking: anything you look at every week but never act on. If a number changes and it doesn't change anything you do, you're not tracking a signal. You're collecting data for its own sake. Audit your tracking quarterly. Kill what you don't use.

"The best signal is often the one that doesn't show up in any dashboard. It's a shift in tone, a change in how someone carries themselves in a meeting, a question that used to get asked that suddenly isn't."

The 15-minute weekly review

Once a week, Friday afternoons, I spend 15 minutes looking at my team with a specific set of questions. Not checking dashboards. Not reviewing task boards. Just thinking:

• Who had a good week? Who had a hard one?
• Is anything at risk of slipping that I haven't addressed?
• Is anyone carrying significantly more or less than the others right now?
• Are we working on the right things, or are we busy with things that won't matter in three months?
• What conversation am I avoiding that I should have next week?

That last question is the one that produces the most value. There's almost always a conversation I've been putting off: feedback I've been softening, a concern I've been watching but not naming, a priority conflict I've been hoping would resolve itself. The weekly review forces me to surface it and decide: am I having this conversation next week, or am I choosing to let it sit?

I'll be honest: I don't always have the conversation. Sometimes I let it sit another week. But at least I've made a deliberate choice rather than just drifting past it.

The real question: If you were building a dashboard for your own team from scratch, not what your company asks you to report on, but what you'd actually want to see, what would it show? That's probably a better starting point than whatever tool you were handed.

I built Cadence with this in mind: a place where small-team managers can see the signals that matter without building the tracking system themselves. The goal isn't a comprehensive view of everything. It's a clear answer to "is my team healthy right now?" If you're managing a small team and still don't have a good answer to that question, start with five minutes of honest reflection before your next 1:1 cycle. That alone will tell you more than most dashboards will.

Track the signals that actually matter.

Cadence gives you team visibility, goal tracking, 1:1 insights, and team meeting agendas — without the overhead of building a system from scratch. 14-day free trial.