The Other Side of Achievement: On Things Not Done

Things not done

When we talk about someone’s achievements, we naturally ask “what did they do?” Which project did they lead, what results did they produce, what numbers did they hit. Achievement is the result of action, and action requires a subject. “Who did what.” There’s always a clear owner behind every achievement.

But I often find myself thinking about “what that person didn’t do.”

Necessary, but didn’t have to

By “didn’t do,” I don’t mean things that weren’t necessary. These are things that clearly needed to happen, things someone absolutely had to do — it’s just that this particular person didn’t have to. Because someone else behind the scenes made sure they wouldn’t have to.

Say there’s someone with a big presentation coming up. If they nail it on stage, we praise their delivery, their logic, their preparation. But if you look at what made it possible for them to focus solely on the presentation, there’s a list of invisible work behind it. The person who organized the data, the one who coordinated schedules, the one who polished the slide design, the one who set up the rehearsal environment, the one who checked for potential technical issues in advance. Because of the people who handled everything the presenter “didn’t have to do,” they could fully focus on what they do best.

I’m not talking about division of labor. Division of labor assumes everyone has clearly separated domains. The kind of support I’m talking about is a bit different. It’s more like reducing friction and noise in someone else’s domain. Sometimes it’s about making sure the other person doesn’t even realize that friction existed in the first place. Good support doesn’t show. No problems erupted, no delays occurred, one less thing to worry about. But “things that didn’t happen” are hard to put on record.

What did I even accomplish?

So people in support roles end up with a peculiar dilemma. The question: “What did I even accomplish?”

The project succeeded. The team hit its targets. But there’s no deliverable with my name on it. What I produced either dissolved into someone else’s output or never took the shape of an output at all. What I did was “make it so that person didn’t have to do that thing” — but how do you even explain that? If I said “I made sure nothing went wrong this quarter,” would that be taken seriously in a performance review?

This isn’t just about wanting recognition. If you can’t define the value of your own work, you can’t sustain it for long. Burnout doesn’t only come from overwork — it comes from a lack of meaning too. If you don’t have confidence that what you do every day is contributing to something, you lose momentum at some point, no matter how well the team is running.

A different frame

So I think we need to look at the outcomes of support through a different frame. Instead of “what did I create,” try “what did the other person not have to do because I was there.”

I think this frame works because it makes things measurable, at least to some degree.

The first thing to consider is the size of the friction you removed. If a process that used to take three days now takes one, that two-day difference is the support person’s achievement. But this kind of contribution is only visible when there’s something to compare it to. If nobody shares the premise that “this used to take this long,” it just gets perceived as a one-day task from the start.

Next is the time you freed up. The time someone could spend on their core work — time not lost to peripheral tasks — that’s what support created. This isn’t just about efficiency, it’s about quality too. When people get more time to focus, the same person produces better results.

And one of the most undervalued contributions is providing information that improves decision quality. Good judgment stands on good information. The person who organized the right data at the right time, the person who structured a complex situation and clarified the options — even if someone else made the final call, the quality of that decision was built on the work of the person who prepared the information.

What it means to be inseparable

Of course, proving all of this as measurable achievement is still hard. If the nature of support is enabling other people’s results, then separating out the causal relationship when those results come in is nearly impossible. You can’t precisely determine whether a presentation succeeded because of the presenter’s skill, the support person’s contribution, or just the audience’s mood that day.

But I think this uncertainty itself is a feature of support. The fact that you can’t cleanly separate the causality means that support is deeply intertwined with the other person’s achievement. Maybe the real indicator of good support is exactly that — you can’t extract your contribution from their results.

Making invisible work visible

I think what I’m trying to say in this post comes down to roughly two things.

First, people who do support work need to have the language to explain their own contribution. Not “I did this,” but “because of me, this person didn’t have to do that.” You need to be able to define the value of your work in those terms. That’s how you keep doing it, and do it better. Even better if you can put numbers to it.

Second, organizations need to be able to recognize the value of “things that didn’t have to be done.” In organizations that only ask “who did what” when talking about performance, the contributions of people quietly reducing friction stay invisible. And invisible contributions eventually disappear. You only realize what was there after it’s gone, and by then it’s already too late.

When you see someone’s outstanding achievement, try thinking not just about what they did, but also about what they didn’t have to do. On the other side of that list, there’s someone working without a name.

And yet

That said, I’m not saying you should stay in a support role forever. Being good at reducing friction behind the scenes also means you already know what matters — in your bones. And when someone who knows that steps up to the front, the difference is clear. I think of support not as a destination but as a place you pass through, and the difference between someone who’s been through it and someone who hasn’t is definitely there.