The thinking behind it
Visibility at work isn't about becoming louder. It's usually about a handful of small mechanics that most people never sit down to think through. Here's how we think about it.
Why good work goes unnoticed
Plenty of solid work happens in places nobody is looking. A well-scoped Slack thread. A quiet fix that prevented a bigger problem three weeks later. A thoughtful comment in a meeting that shaped the decision but didn't get attributed in the notes.
None of this is anyone's fault exactly. Work has gotten more asynchronous, updates get buried under a dozen other channels, and credit in group projects tends to diffuse toward whoever spoke last or loudest. Quiet, methodical people often get read as less strategic, even when the substance of their work says otherwise.
Not a script for sounding impressive
This isn't personal branding advice about crafting a "narrative" or rehearsing talking points before a meeting. We're not interested in helping anyone sound more confident than the work supports.
The goal is closer to bookkeeping than marketing. If you did something worth noting, it should be recorded somewhere useful, said clearly once, and findable later. That's a fairly unglamorous standard, and it holds up better over time than performance does.
Five areas, considered separately
We treat meetings, updates, project selection, relationships, and documentation as five distinct skills. Each has its own small mechanics worth understanding on their own terms.
Meetings
The mechanic isn't talking more. It's preparing one point worth making, naming it so it's memorable, and reinforcing it in writing afterward.
Updates
Most updates fail because they try to cover everything. A shorter update, structured around what changed and why it matters, tends to get read.
Projects
Saying yes to everything looks busy but rarely reads as strategic. Choosing based on visibility and stretch tends to matter more than volume.
Relationships
People two levels up rarely need long meetings with you. A short, well-timed update or question, sent occasionally, tends to do more.
Documentation
The one most people skip until it's urgent. Writing down context, contribution, and outcome close to when it happened is far easier than reconstructing a year of work from memory during review season, and it produces something you can actually reuse in a self-review or promotion packet.
Why the moment matters more than the memory
Performance review cycles reward recency and specificity. A vague sense that "it was a good year" doesn't carry the same weight as three or four dated, specific examples with context attached.
The habit that tends to matter most isn't writing a brilliant paragraph. It's writing a rough one, right after the work happens, before the details soften into a general impression. A messy note in the moment beats a polished memory six months later.
See what a sample lesson looks like
If the reasoning here makes sense, the preview page shows the actual format: prompts, templates, and a sample entry.
