Stop Being Invisible at Work
You deliver good work. You hit your deadlines. Your manager knows you're reliable — they'd say so if asked. And yet somehow, when the promotion conversation happens, your name isn't the first one mentioned. Maybe it isn't mentioned at all.
The instinct is to work harder. Deliver more. Make the output undeniable. That instinct is wrong, and following it will keep you stuck for years.
The problem isn't your output. It's that your work isn't legible to the people who decide what happens next.
Why this is harder than it sounds
There's a version of this advice that makes it sound like a marketing problem — just talk about yourself more, post on LinkedIn, send a weekly update email. That's not what I mean, and if you've tried that and felt like you were performing rather than communicating, I understand why it didn't stick.
The real issue is structural.
Most knowledge work is invisible by design. You sit in meetings, you fix problems before they become crises, you unblock other people, you write the document that saves the project. None of that has a natural moment of visibility. The crisis that didn't happen has no announcement. The problem you solved in twenty minutes, because you've seen it before and knew exactly what to do, looks like nothing happened.
Meanwhile, the person who makes a lot of noise about straightforward work looks busy and impactful. You know the work is less impressive. Your manager might not.
This isn't about being worse at politics than your loudest colleague. It's about the fact that technical competence and communication of technical competence are two separate skills, and most people only develop the first one.
What actually helps
Make your work visible at the point it happens, not in your performance review.
Your performance review is the worst time to make a case for yourself. You're working from memory, your manager is working from memory, and the conversation is already framed as evaluation rather than information. The people who get promoted have already built the record — the review is just confirming it.
The practical version: when you finish something meaningful, say so. Not a speech — one sentence in the team channel, a note in the project doc, a reply in the thread where the problem was raised. "Resolved — the issue was X, fixed by Y." That's it. You're not boasting. You're closing the loop in a way that's visible.
Translate the work, don't just describe it.
"I refactored the data pipeline" means nothing to someone who doesn't know what the pipeline does or what it was like before. "The data pipeline was taking four hours to run and blocking the Monday morning report — it now runs in forty minutes" means something to everyone.
This isn't spin. It's translation. You already know why the work mattered — the gap is that you haven't said it out loud to anyone who wasn't in the room when you decided to do it.
Find out how decisions actually get made.
This one is uncomfortable, but it's the most useful thing on the list. In most organisations, promotion decisions are made in a room you're not in, by people whose picture of your work is assembled from secondhand information. Your direct manager advocates for you based on what they know. What they know is what you've told them, what they've seen directly, and what other people have said about you.
That third category - what other people say - is something you can influence. When you help someone, make it easy for them to describe what you did. When you finish a project, make sure the stakeholders outside your immediate team know who was responsible for the parts that went well.
None of this requires you to be someone you're not. It requires you to stop assuming that good work speaks for itself, because it doesn't. Work speaks through people, and people need material to work with.
This week
Pick one thing you finished in the last two weeks that you haven't told anyone about. Not in a meeting, not in a review — just write one sentence describing what you did and why it mattered, and put it somewhere it will be read. A Slack channel. A project update. An email to your manager. One sentence.
That's the starting point. Not a personal brand. Not a self-promotion strategy. One sentence, once.