Your Work Doesn't Speak for Itself

Somewhere in your org right now, there's someone excellent who's about to get "meets expectations" while a louder colleague gets the promotion.

The manager isn't corrupt. They're not playing favourites. They just can't describe, in specific terms, what the quiet one actually did this year. And you can't reward what you can't describe.

If that stings a little, good. The quiet one might be you.

Most of us were raised on a comforting idea: do great work, and it will speak for itself.

It won't. Work doesn't speak. It sits in a finished spreadsheet, a closed ticket, a problem that never blew up because you quietly fixed it three weeks ago. The better you are at your job, the more of your value is invisible by design: the fire that never started, the complaint that never came in.

I learned the cost of being invisible the hard way. I once skipped a networking event with the CEO. Someone less experienced went, got the CEO's ear, and ended up becoming my boss. I left shortly after. Small rooms create big opportunities, and I wasn't in that one.

This module shows you how to be visible without becoming that person: a reframe, a few habits, and two simple tools you'll use every week.

The short version

• Visibility is information transfer, not bragging. You're closing the gap between what you did and what decision-makers believe you did.
• Report outcomes, not activity. Every update should carry a number or a clear result.
• Write it down. A short weekly note travels to rooms you'll never be in.
• Keep an impact log. You can't show what you never tracked.
• Give credit loudly. Naming other people's wins makes your own visibility read as generous, not grabby.

Visibility isn't politics. It's information transfer.

Your manager and your org are running on an incomplete picture of what you do. They see whatever lands in front of them and guess the rest. That guess is usually wrong, and usually not in your favour, because the hardest, most preventive work is the least visible.

Put it in colder terms: invisible work can't be rewarded, can't be defended, and can't be built on. When your review gets written, it isn't there. When a reorg happens and someone's redrawing the org chart from memory, it isn't there. You're not being humble. You're carrying a risk alone that you don't need to carry.

It's harder now than it used to be. When everyone sat in the same room, your manager picked up a steady stream of evidence just by being nearby. Remote and hybrid work cut that stream off. And as AI makes decent first drafts cheap for everyone, what sets you apart shifts toward judgment, ownership, and whether anyone can tell what you actually contributed.

Key idea: Doing the work and showing the work aren't two jobs, one noble and one dirty. The second is how the first one counts.

The line you shouldn't cross

Your discomfort isn't entirely wrong. There is a gross version of this. Busy, loud and empty work is not the goal. Neither is taking credit for other people's work, or narrating every task in the team channel.

The test: are you giving decision-makers information they genuinely need, or making noise to look busy? The first is legible work. The second is self-promotion. The trap is that most good people, scared of looking like the second, default to invisible.

Seven habits that make your work legible

You don't need a personal brand. You need a handful of habits.

1. Report outcomes, not activity. Not "worked on the onboarding emails." Instead: "rewrote the onboarding emails; first-week replies went from 12 to 31." Tie results to what leadership counts (revenue, profit, cost saved, customers kept) whenever you can. Managers can only repeat impact they can restate, so hand them the number.
2. Put it in writing. A short weekly note beats any amount of hallway heroics. A great save in a meeting evaporates when the meeting ends. Writing gets forwarded.
3. Connect your work to current priorities. Frame it in the language of whatever leadership is focused on this quarter. The same work reads as far more important when it's tied to what they're already worried about.
4. Keep an impact log. Not for your ego. For the review, the raise conversation, the layoff conversation you hope never comes.
5. Own the follow-up in the room. Take the notes. Send the recap. Name next steps and owners. It's visibility that also creates value, the rare kind nobody resents.
6. Give other people credit, loudly. This is the cheat code. Be the person who names everyone else's contribution first. It compounds, and people give it back.
7. Be visible before you need it. You can't backfill a reputation in December for a year you spent silent. Visibility is insurance, and insurance is useless the day you finally wish you had it.

Start with a reconstruction

Never kept an impact log? Start by rebuilding the last two weeks. Open your calendar, your sent folder and your chat history. Write down what you actually did, not your job description. The real list.

It's uncomfortable how much you've already forgotten. That's the point. If you can't remember it two weeks later, your manager definitely can't remember it at review time.

What it looks like in practice

A composite example. Tomás is a junior analyst on a finance team, two years in. He's good. He's also quiet, and in his last review his manager wrote that he "consistently delivers." Nothing about what.

He spends 30 minutes rebuilding his last month from his calendar and sent folder. Buried in there: he built a spreadsheet check that caught a duplicated vendor payment of $4,200, and he cut the monthly close report from two days to one by fixing a messy data pull. Nobody above his manager knows either happened.

He starts an impact log and writes one entry every Friday, five minutes each. He also starts sending his manager a five-line update every Friday afternoon.

The first one includes: "Close report now takes one day instead of two. Thanks to Lena in AP for flagging the source data issue." His manager forwards it to the finance director with one line: "Tomás did this."

At his next review, his manager doesn't have to remember anything. She copies from his log. He gets a stronger rating and a stretch project. The work didn't change. The information did.

Common traps

• Waiting to be noticed. It feels humble. It works out badly. Fix: send one written update a week, starting this Friday.
• Reporting effort instead of results. "Busy" isn't a result. Fix: every line needs a number, a before-and-after, or a clear outcome.
• Only showing up at review time. A sudden flood of self-promotion in Q4 reads as exactly that. Fix: log weekly so the evidence is already there.
• Taking all the credit. It costs trust fast. Fix: name the people who helped in the same sentence as the result.
• Skipping the small rooms. The informal event, the optional lunch, the cross-team call. Fix: say yes to the small rooms where decision-makers are.

Do this this week

1. Block 30 minutes. Open your calendar, sent folder and chat history from the last two weeks and write down everything you actually did.
2. Pick your top three items and rewrite each as an outcome with a number or before-and-after.
3. Start your impact log with those three entries.
4. On Friday, send your manager your first five-line update using the template below.

Your tool

CopyPART 1: IMPACT LOG (5 minutes every Friday)
One row per win. Keep it in one doc you'll never lose.

Date | What I did | Outcome (number or before/after) |
Ties to (revenue / cost / time / customers / risk) |
Who helped | Proof (link, email, screenshot)

Example:
Mar 14 | Rebuilt the close report data pull | Close report 2 days
-> 1 day | Time | Lena (AP) flagged source issue | email thread

Monthly (15 min): highlight your top 3 wins of the month.
Quarterly (30 min): turn the highlights into 3-5 bullet points you
could paste into a review, a raise request or your resume.

Prompts if you're stuck:
- What problem didn't happen because of me?
- What's faster, cheaper or more accurate than a month ago?
- Who did I unblock, train or help?
- What did a customer or teammate thank me for?

PART 2: FIVE-LINE WEEKLY UPDATE (send Friday)
Subject: Weekly update, [your name], [date]

1. Moved: [the most important outcome this week, with a number]
2. Also: [one or two smaller wins]
3. Credit: [who helped and how]
4. Next week: [your top 1-2 priorities]
5. Need: [one decision, input or blocker, or "nothing this week"]

Rules:
- Outcomes, not activity. Every line should pass "so what?"
- Under 120 words. Your manager should read it in one minute.
- Same day, same format, every week. Consistency is the signal.

Talk about it

1. Think of someone at work whose impact everyone can describe. What do they do that makes it legible?
2. Where's your personal line between being visible and being performative?
3. If your manager had to write your review today from memory alone, what would they miss?

— Evan