Visibility vs Hard Work: What Actually Wins in the Office

I have a vivid memory of sitting in a review meeting and watching a colleague walk through a project that, I knew for a fact, had required significantly less effort and significantly less rigour than work I had submitted two weeks earlier. Their version got praised. Mine got noted. I walked out of that room with a specific flavour of frustration that I think a lot of individual contributors recognise: the feeling that the game is rigged and that quality alone is not going to fix it.

That feeling is real. But the conclusion I drew from it at the time was wrong.

For a long stretch of my career, I believed, with genuine conviction, that good work would speak for itself. That if I produced rigorous, well-evidenced, thoughtful output, the recognition would follow naturally. It is a comforting belief. It is also, in most organisational contexts, demonstrably false.

The problem is not that organisations are unfair, though some are. The problem is that visibility and quality are different signals, and most organisational systems are better at measuring the first than the second. Your manager's manager cannot read every document you produce. Your skip-level does not have the context to evaluate the depth of analysis you ran last quarter. What they have are the impressions that surface from what gets communicated upward, outward, and sideways. If you are not shaping those impressions, someone else is shaping them, or no one is, which amounts to the same thing.

This is the thing that took me a while to actually understand. Visibility is not self-promotion. Self-promotion is noise. Visibility is signal. The difference is between emailing your team a summary of what you accomplished this week versus sending your manager a concise note on what you built, what it enabled, and what you are working on next. One is about credit. The other is about context. Context is what decisions get made on, and decisions about people's careers are no different.

Being an individual contributor is a specific kind of professional loneliness. You do deep work, often alone or in a small group, and the output lands wherever it lands and gets used or not used and that is frequently the last you hear of it. The work compounds, mostly invisibly. The skills get sharper. The judgment gets better. None of it shows up in any metric that a promotion committee can easily see unless someone builds the case for it, and that someone is usually you.

What I eventually worked out, later than I should have, is that communicating about your work is not separate from doing the work. It is part of the work. An insight that nobody knows about is an insight that did not happen in any practical sense. A project that produced real results but left no organisational memory of how or why is a project that cannot be repeated, built on, or attributed. Visibility done well is documentation. It is how institutions remember what their people have actually contributed.

I am not going to tell you that hard work does not matter. It matters enormously, and I do not think the alternative is to become someone who performs output without producing it. But hard work without visibility is a tax on your own ambition. You are doing the thing and then declining to tell anyone you did it, which is a strange choice when you put it that way.

The frustration I felt in that meeting was legitimate. The lesson I eventually drew from it was not that the system is unfair and that is simply how things are. The lesson was that I had been delivering work and not delivering the understanding of that work. Those are different deliverables. And the second one is learnable.