Visibility without politics — getting recognised for real IT work
Quiet, excellent engineers often watch louder colleagues get the credit — and conclude that recognition requires politics. It doesn't. Here's how to make genuinely good work visible without becoming someone you're not.
Key takeaways
- "Just do great work and it'll be noticed" is a myth
- so is "you must play politics"
- The honest middle is making your real work legible — visible, understood, connected to impact
- Communicate outcomes and their business meaning, not activity
- Being known for something specific beats being vaguely appreciated
Many strong engineers hold two beliefs that trap them: "if my work is good enough, it'll be noticed" and, when it isn't, "recognition must require politics I refuse to play." Both are wrong, and together they keep excellent people invisible and quietly resentful. There's an honest middle path — making genuinely good work legible — that has nothing to do with politics and everything to do with communication. Here's how it works.
Why great work goes unnoticed
Good work does not announce itself. Decision-makers are busy, removed from the detail, and juggling many people's contributions. If your excellent work sits silently inside a system only you fully understand, it's genuinely invisible to them — not because they're unfair, but because they can't see what they're not shown. "The work speaks for itself" assumes an audience listening closely to every detail. There isn't one.
So the choice isn't "stay silent and pure" versus "play politics." It's "let good work stay invisible" versus "make good work visible" — and the second is completely honest.
Legible, not loud
Politics is claiming credit you didn't earn, undermining others, managing up at the expense of the work. That's not what this is. Legibility is making sure your real contributions are understood by the people who should understand them. The distinction matters: one distorts reality for advantage; the other simply removes the fog around genuine work. You can be completely honest and still be visible.
Three habits that make you legible
Communicate outcomes, not activity. "I fixed 40 tickets" is activity. "I cut the checkout failure rate by half, which recovered X in lost orders" is an outcome with meaning. Frame your work in terms of what changed for the business or the user, not how busy you were.
Connect your work to what leadership cares about. The same technical achievement lands very differently when you tie it to a priority the business is actually worried about. Speak in the terms your audience values — reliability, cost, speed, risk — not only in technical detail.
Be known for something specific. Vague general competence is hard to remember or advocate for. Being the person for a particular thing — a system, a capability, a kind of hard problem — makes you legible and referenceable. Depth in one visible area beats broad, forgettable competence.
None of this requires becoming someone you're not. It requires letting your real work be seen — which quiet, excellent engineers often skip, and then wonder why louder colleagues advance. Building this into how you work, authentically, is part of what the ProThink workshops develop.
FAQ
How do I get recognised at work without playing politics?
Make your real work legible rather than loud. Politics is claiming unearned credit or undermining others; legibility is simply ensuring your genuine contributions are understood by the people who should understand them. Communicate outcomes and their business impact, connect your work to leadership's priorities, and be known for something specific — all completely honest.
Why doesn't my good work get noticed on its own?
Because good work doesn't announce itself, and decision-makers are busy and removed from the detail. Excellent work sitting silently inside a system only you understand is genuinely invisible to them — not from unfairness, but because they can't see what they aren't shown. "The work speaks for itself" assumes an attentive audience that doesn't exist.
What's the difference between visibility and politics?
Politics distorts reality for advantage — claiming credit you didn't earn, undermining peers, managing up over the work. Visibility (legibility) just removes the fog around your genuine contributions so the right people understand them. One is dishonest; the other is honest. You can be completely straight and still make sure your real work is seen.
How do I make my technical work matter to non-technical leaders?
Translate it into their terms. Frame achievements as outcomes with business meaning — reliability, cost, speed, risk reduced — rather than technical activity, and connect them to priorities leadership is actually worried about. The same accomplishment lands far better tied to something they care about than described in technical detail alone.
