Remote work means someone else is telling your story for you

It's a Tuesday afternoon somewhere you've never been, in a room with a whiteboard you've never stood in front of, and three or four people are deciding whether you get the promotion this cycle. One of them is your manager. The rest are working entirely off what your manager says, because none of them have ever actually watched you do the job.

That room exists whether you're remote or not. The difference is what reaches it.

In an office, you get credit by osmosis. Someone walks past while you're debugging the thing nobody else wanted to touch. Someone overhears you explain a tradeoff clearly in a hallway and mentions it later without even meaning to vouch for you — it just stuck. None of that is a system. It's ambient noise, and some fraction of it drifts into the room where decisions get made, without your manager having to do anything on purpose.

Remote, that channel is just gone. There's no ambient noise to drift anywhere. So the entire account of your work that makes it into that room is the one your manager constructs — consciously, from memory, usually under time pressure, usually compressed into a sentence because that's all the agenda allows for each person. And building an accurate, compelling account of somebody else's quarter, from memory, in thirty seconds, is a specific skill. It is not the same skill as being good at your job, and it's not the same skill as being a good manager generally, either. Some excellent managers are quietly bad at this one narrow thing, and you'd never know it, because the only symptom is that you don't get mentioned.

So the real situation isn't "remote work hurts your visibility." It's narrower and more useful than that: when you're not in the room, you are depending on someone else's memory and someone else's narration, and that dependency is usually invisible to you until a cycle goes by where it clearly didn't work.

It also compounds in a way that's easy to miss. One quiet cycle doesn't feel like much — you tell yourself it was a slow quarter, or the timing was off. But the mechanism doesn't reset between cycles. If your manager's account of you was thin in March, it's still the most recent account in their head come September, because nothing replaced it in between. You don't notice the pattern until you look back at two or three cycles in a row and realize the same thing happened each time, for the same reason, and you'd been treating each one as a one-off.

This is part of why some companies have started pulling people back into buildings — not because the work can't be done remotely, but because this exact gap is expensive for them too, and a desk is a cheaper fix for them than training managers to narrate well. That's a real tradeoff happening at a lot of places right now, and it's worth naming plainly: the office was never solving this problem on purpose, it was solving it as a side effect, and now that some companies don't have that side effect anymore, a few of them are buying it back the blunt way instead of the deliberate way. You don't have to agree with that choice to understand why it's being made.

You can't be in the room. But you can stop leaving the narration entirely to memory.

The clearest move: before the thing happens — the review, the calibration meeting, the 1:1 where the cycle gets summarized — tell your manager the sentence you'd want them to use. Not a list, one sentence: "Before you go in, can I tell you the one thing from this project I'd most want remembered? Might save you digging for it." That's it. You're not asking for credit. You're handing someone who already has to improvise a summary the exact line that improvisation would otherwise cost them time to find.

The second move is timing. Do this before the gap shows up, not after. If you wait until you notice you weren't mentioned, the conversation becomes about repairing an omission, which is a worse conversation for both of you. Send the sentence a week ahead, as part of a normal update, not as a special request: "heads up, the thing I'd flag from this sprint is the retry logic — it's the reason the on-call load dropped, and I'm the only one who has the context on how it's wired." You're pre-loading the material. Nobody has to remember anything, because it's already written down in their own inbox.

The third is for when it still doesn't land — you find out after the fact that you weren't mentioned, or mentioned thinly. The instinct is "that's not fair," which is true and also gets you nothing, because it reads as a complaint about an outcome nobody can undo. Ask instead: "Can you tell me how that came across in calibration? I want to understand so I can be clearer next time." Same frustration, completely different conversation. One asks someone to defend a decision. The other asks them to hand you information. People will give you the second thing far more easily than they'll give you the first.

Send that sentence every two weeks and it stops being a heads-up and starts being a campaign. Managers notice when every update doubles as a resume bullet, and the material that would've worked once starts reading as managing them instead of informing them. Once a quarter, around the actual review cycle, is about as often as this holds its shape. More than that, and you've made your manager's job of advocating for you feel like a performance you're staging for them, which is the opposite of what you want.

And there's a version of this that doesn't work at all, no matter how well you word it: if your manager doesn't actually attend the room where this gets decided, or attends it but has no real standing there — overloaded, new, themselves on thin ice — then handing them better material doesn't fix anything, because the room isn't weighing your material, it's weighing whether the person saying it carries any weight. You can't write your way around that one. The problem isn't your sentence. It's that the chain you're depending on has a broken link above the part you control.

There's also a quieter failure mode worth naming: doing this well for someone who then takes the sentence and says nothing with it, every cycle, without ever telling you why. At some point that stops being a narration problem and becomes information about whether this is a manager who will ever spend effort on your behalf, regardless of what you hand them. One or two quiet cycles is the normal noise this piece is about. A pattern across a year is a different, harder thing to sit with, and the fix for it probably isn't a better sentence.

Some of this is just luck, and pretending otherwise would be dishonest. You got a manager who's a careful narrator of other people's work, or you didn't. You got a manager with real standing in that room, or you got one who's fighting for their own footing. None of that is something you can fix by being better at sending the right sentence at the right time. The sentence helps the part that's reachable. It does nothing for the part that isn't, and the honest thing is to say that plainly instead of implying that enough self-advocacy closes every gap, because it doesn't.

It's also worth saying that the office genuinely does give people something remote doesn't — that ambient, unearned visibility is real, and it's not nothing. The answer isn't to insist remote and in-office are secretly equal, because for this one specific thing, they aren't. The answer is to do on purpose what the office does by accident: get the sentence into the room through the one channel you actually have, which is the person standing in it.

Before your next 1:1, send your manager one sentence: the single thing from the last few weeks you'd most want remembered, and why. Not a list, not a summary of everything — one sentence, the one you'd want quoted if someone only got to say one thing about you in a room you'll never see.

🚀 Want more like this? Every guide, playground, and quiz lives on bestpractic.org — open it and sign up free so the next one finds you.

Thanks for reading! Let's stay connected:

🤝 Want to make something with us? Write a piece, come on the podcast, or bring an idea that should exist — bestpractic.org/collaborate.

And if this one helped, send it to the person you know who needs it this week. That's what keeps these coming.