Zero Commits, Highest Value

The most valuable person on your team last week may have shipped nothing you can see

He said it like a confession.

“I helped five people. Merged nothing. What did I even do?”

I asked him to walk me through the week anyway. Here’s what came out:

• he unblocked three engineers who were each about to spend a day on the wrong thing,

• he connected two efforts that were duplicating each other,

• he caught a dependency nobody else had flagged, the kind that surfaces four days before a release and turns a launch into a scramble.

Zero PRs. Zero lines of code authored. By every measure the team had available, he’d had an empty week.

He was, by a wide margin, the most valuable person on that team for those five days. And he was apologising for it.

The problem is that he had internalised the metric as a value judgment.

That’s how this work dies -by someone deciding that it doesn’t count.

1. If the only thing you can see is what got merged, you will systematically undervalue the people holding your team together

Code output is trivially easy to measure. Commits, PRs, review comments, story points — all of it is already instrumented, already aggregated, already sitting in a dashboard somewhere. Nobody has to advocate for it. It shows up whether you want it to or not.

The work that holds a team together has no instrumentation at all. There is no field for “prevented the wrong thing from being built.” There’s no counter for “noticed the two teams were solving the same problem.” The unblock that saved a day doesn’t appear anywhere, because the day it saved never happened. You can’t measure an averted disaster, only the one that you failed to prevent.

So you end up with a system where one category of contribution is visible, and the other is invisible by default. Not even undervalued but unvalued, in the literal sense that no value is ever assigned.

Then performance review season arrives and you’re asked to compare them.

I’ve watched managers do this with complete good faith and get it so, so wrong. They’re working with the evidence in front of them, and the evidence is structurally incomplete in a way that always favours the same kind of engineer. The person who spent the quarter heads-down on a well-scoped initative has a paper trail. The person who spent the quarter making sure six other people’s work fit together has a Slack history nobody’s going to read.

The fix: before you look at any output data, write down the names of the people whose absence would hurt most. Who you’d panic about losing. These may turn out to be different then the ones who ship the most. Every gap between the two lists is a place your measurement is lying to you, and it’s usually the same two or three names, quarter after quarter.

2. Glue work is the first thing to vanish when people feel measured only by output

Connecting work is genuinely expensive. Walking over to someone’s desk (or reaching out on slack for a quick huddle), understanding a problem that isn’t yours, holding two efforts in your head at once so you can spot the collision is real cognitive load. It comes out of the same budget as your own deliverables, and it comes out first, because interruptions land when they land.

Now add one piece of information: none of it counts.

Nobody has to say this out loud. It’s transmitted through what gets praised, what gets asked about in 1:1s, what shows up on the promotion packet. The engineer runs the calculation and adjusts.

They don’t announce that they’re stopping.
They just start being slightly less available.
The Slack reply comes an hour later.
They notice the duplicated effort and decide it’s not their call to raise.
The dependency question forms in their head and they let it go, because they’ve got their own thing to finish and their own thing is what gets looked at.

And for a few weeks, everything looks better. Their output goes up. They finally have contiguous focus time. Their metrics improve, which confirms to everyone including them that the trade was correct.

Then the seams start failing. Two teams ship incompatible interpretations of the same requirement. A dependency surfaces late and eats a release. The new hire takes eleven weeks to get productive instead of four. None of these failures point back to the cause, because the cause is an absence — a conversation that didn’t happen, a question nobody asked.

The fix: treat responsiveness to other people as a first-class line item in the work, with time protected for it. If someone’s job includes holding the team together, that has to appear in their goals, be defended when their delivery numbers dip, and be the reason they get promoted rather than a charming detail about how they operate.

3. Gratitude you never express is invisible

Most managers I work with genuinely appreciate their glue people. They’ll tell me about them at length.

Then I ask whether they’ve said any of it to the person.

The appreciation is real. It just lives entirely in the manager’s head, where it does nobody any good. And there’s a reason it stays there: appreciation for invisible work feels awkward to voice, because it’s hard to point at.

“Great work on that migration” is easy — there’s a migration.

“Thank you for the way you keep everyone aligned” sounds vague even when you mean it, so it doesn’t get said.

Meanwhile the person is drawing conclusions from silence. They shipped nothing visible, nobody mentioned anything, so the reasonable inference is that the week didn’t count. You didn’t tell them their work was invisible. But you didn’t tell them it wasn’t either.

The fix: name the achievement specifically. “The release shipped because you caught that dependency” does something that “you’re such a great team player” cannot. Say it in front of other people, because that’s how the team learns what actually counts here, and say it when it’s actually happening, while it’s still concrete enough to mean something.

4. Make the invisible work legible instead

You can’t fix this purely by asking managers to look harder. You need the work to leave a trace.

The instinct is to build a metric. But there is a trap here: the moment you count something like this, people optimise for the count, and you get performative helping instead of actual helping.

A few things that work:

Ask a different question in 1:1s. Not “what did you ship” — “what did you stop from going wrong, and who did you help?” People will underreport at first, because they’ve learned this isn’t the kind of thing you bring to a 1:1. Ask it every week and they stop underreporting, and you start accumulating the evidence you’ll need in six months.

Give retro a slot for it. One question: what nearly went wrong and didn’t, and why didn’t it? The answer is almost always a person who noticed something. That’s the record, generated by the team, in front of the team.

Write it down when it happens. Keep a running note per person of the specific unblocks, catches and connections. This is the difference between a promotion case built on evidence and one built on the phrase “everyone knows how important she is”, which, in a calibration meeting against someone with a commit graph, loses every single time.

Check the shape of who does it. Glue work distributes unevenly and the pattern is rarely random. It tends to accumulate on the most senior person on the team, the person who’s been there longest, and on women. If the same people are absorbing all of it while a different set of people get credit for shipping, you have a problem.

5. The teams that get this right don’t have better people

They have a shared answer to a specific question: what does a good week look like here?

On most teams, the answer is “a week where you shipped something.”

On teams that hold together, a good week can also mean the week where you noticed the thing. Where you made the connection. Where you spent Tuesday on someone else’s problem because their problem was going to become the team’s problem by Thursday. It’s visible in what gets asked about, what gets praised, and who gets promoted.

That’s the whole intervention, really. Getting the team to a place where the answer to “what did I even do this week?” can be “you held it together” and everyone in the room, including the person who asked, understands that to be a great answer.

So: who on your team does the work that never shows up anywhere?

Name it this week.