At a company two jobs back, I got promoted twice in three years. I was getting better that whole time — but I’d been getting better for the three years before it too, and that got me nothing. The growth was steady. The outcome wasn’t.
One variable moved between the work that went nowhere and the work that got me promoted, and it wasn’t the work. I started reporting it.
Some of what I did genuinely couldn’t be seen — a week on a migration that quietly deleted an entire category of incident, where the only artifact was a dashboard staying green, and nobody looks at a dashboard that’s green. But that’s the comfortable example. Most of my work was perfectly visible, and I made it invisible anyway. I’d lead a project and let the win go out as a team win. Every time. I thought that was humility.
Unreported work is invisible state
A team is a distributed system. Your manager, your skip-level, the person deciding who leads the next big thing — they’re nodes. They hold a model of what’s running, and that model is built entirely out of what gets reported to them.
Work that never gets reported is invisible state. It isn’t undervalued. It isn’t underappreciated. As far as the system is concerned, it is not running.
Nobody was withholding recognition from me. They were reasoning correctly over the data they had, and I was the one who’d shipped a service that emits no telemetry. You’d never deploy something silent and then blame the on-call for not knowing it was down. That’s not humility. That’s a missing exporter.
So making your work visible isn’t marketing. It’s instrumentation — the same discipline you already apply to every system you respect, pointed for once at your own.
The four signals
- Report continuously, not at the end. This did more than the other three combined. Report decisions while you’re still making them: what you’re solving, the approach you picked, the one you threw away. And when you led something, write I led it. Not arrogantly — accurately. Being disagreed with is still a win: afterwards the record doesn’t say he was wrong about the fix, it says he’s the one who found it.
- Ship the dashboard with the feature. Public, linked, showing whether the thing did what you said it would. Wait a week, then post the chart. A launch post is an announcement; a chart showing the error rate dropped and stayed down is evidence, and it argues for you when you’re not in the room. For work with no natural metric, invent one — the number that would have gotten worse if you hadn’t done it.
- Have an opinion about other people’s work. Say what you actually think about your teammates’ designs and pull requests, including when you disagree with the decision and not just the missing null check. There’s no silent way to demonstrate judgment. “LGTM” is a signal too: it says you had nothing to add.
- Arm your manager. Somewhere, in a room you’re not in, someone has to make your case out of evidence you aren’t there to supply. Hand over the decisions, the dashboards, the problems you flagged, in a form they can paste straight into a document.
One rule runs underneath all four: report the misses the same way you report the wins. Visibility built only on wins reads as marketing. Visibility that includes the misses reads as trust.
A third of the week already emits nothing
Harness’s State of Engineering Excellence 2026 (Sapio Research, 700 engineers and engineering managers) found respondents estimate about 31% of their time now goes to invisible work: reviewing code the AI wrote, fixing it, context-switching to keep track of it all.
To be precise, the study measures what productivity metrics miss, not what your manager misses. Not the same claim. But they overlap, because a manager’s read of you is assembled out of what gets reported — and a third of the week that no dashboard captures is a third of the week reporting nothing on your behalf.
No clip, didn’t happen
I’d made this exact mistake once before, fifteen years earlier. I skated, seriously enough that going pro felt like a plan rather than a fantasy, and I believed that if I skated well enough someone would find me. What actually builds a skate career isn’t contests. It’s footage. I didn’t film.
Skateboarding has a phrase for that, and it’s ruthless: no clip, didn’t happen. You can land the trick of your life in an empty lot at midnight, and with no footage, it didn’t happen. That law was running under both my careers the whole time. The full version of that story is in the video above.
And then it decays
The promotions were real. Then I left, and none of it came with me. Not the skills — those travel fine. The visibility. It resets to zero on every job change, every reorg, every new manager, and the person making decisions about you is reading a dashboard that’s only been up six weeks. I’m rebuilding mine right now.
That’s not the ending I wanted. It’s the more useful one. Instrumentation isn’t a bug you close. It’s a service you run.
Do the work. Then make sure there’s a clip.
This opens a new series. It picks up where AI Didn’t Take Your Job – It Revealed It left off: if your job was never the typing, this is the part of it nobody puts in the job description.