I got very good at things nobody pays extra for

On the difference between a week of activity and a week of consequence.

I spent years trying to be the perfect employee in my manager’s eyes, and it very nearly capped what I could earn for the rest of my career.

Not because I was coasting. The opposite, if anything. I was excellent at finishing things, hitting dates, keeping status reports current, being the person who never dropped anything. I built an entire professional identity out of reliability, and it worked, in the sense that everyone liked working with me and nothing I owned ever caught fire.

What took me an embarrassingly long time to notice was that I had become excellent at a set of skills nobody was willing to pay a premium for. And once you see it in those terms the ceiling makes complete sense. Why would anyone pay more for something they can already get easily, and reliably, from several people?

Two ways to describe the same week

Think about how you’d describe last week to someone who wasn’t there.

One version is about what you finished. Ten tickets closed, the report went out on Thursday, the migration completed over the weekend without incident. It’s true, it’s verifiable, and it’s the version nearly everyone reaches for, partly because it’s the version we can remember. Completion is memorable. It has an edge to it.

The other version is about what changed because you finished. The report went out and the exec finally understood where the cost was going, so they stopped a workstream that had been burning through its budget without anyone knowing why. You caught an assumption in week two that would have sent four engineers down a dead end for a quarter.

Same week both times. Same person, same hours, same effort. Organisations pay very differently for those two descriptions, and the gap widens the more senior the role.

Here’s the part that stings a bit. If every win you can name from this week is a version of “I finished the thing” or “I hit the date”, that’s not just a storytelling problem you can fix with better phrasing. It’s usually accurate. It’s telling you something real about where your attention has been going, and no amount of resume-writing advice will paper over it.

Why almost nobody has the second kind of story

The second kind requires information that arrives after you’ve stopped paying attention.

You deliver, and then you’re immediately on the next thing, because the next thing has a date attached and the last thing doesn’t anymore. The results come in three weeks later, into an inbox that isn’t yours, in a meeting you’re not in. Nobody is going to walk over and tell you that the assumption you challenged in discovery saved a quarter of engineering time, because nobody experienced the counterfactual. Prevented waste is invisible by definition. That’s what makes it so hard to claim and so valuable to be able to claim.

So the practice is deliberately going back to look, which feels slightly indulgent and is the single highest-leverage habit I’ve picked up.

Did it work. Did anyone use it. Did the number it was supposed to move move. Did the process it was supposed to fix stay fixed at the three month mark, or did everyone revert.

That’s uncomfortable more often than it’s flattering. Plenty of things I’ve shipped turned out to do very little, and I only know that because I went and checked, and nobody would have told me otherwise. But those checks are where the stories come from. They’re also, and this matters more, the only reliable way to get better at predicting which work is worth doing before you do it.

When you really can’t trace it, because the metric belongs to another team or you’ve moved on, the fallback is just to ask. Find the person who would know and ask them what happened. Most people are surprisingly pleased to be asked, and the asking itself starts to change what you notice while you’re still building.

What changes when you have the material

After a few months of this you stop writing “completed ten projects” and start writing something closer to “caught a flawed assumption during discovery that would have cost roughly two hundred thousand in build”.

One of those is a description of activity. The other is a description of judgment, and judgment is the thing that scales with seniority.

But the CV line is the smallest part of it, and I’d be misrepresenting this if I made it the point. The real change is upstream. Once you’re routinely looking at what happened after, you start choosing differently before. You get a feel for which requests are load-bearing and which ones are somebody’s discomfort looking for a task. Your instinct about what to push back on gets calibrated by evidence rather than by how confident the person asking sounded.

That calibration is quiet and it takes years and nobody can see it happening. It’s also the thing that eventually makes the ceiling irrelevant.