Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / How to Stay Visible in a Remote Company Without Annoying Anyone
Transcript
- Lucas: Okay, let me paint a picture for you. It's May 2026, and a data analyst at a 400-person fintech — let's call her Priya — has been fully remote for two years. She's hitting her numbers, her code reviews are clean, she's never late on a deliverable. But when a senior role opened up on the adjacent team, she didn't even get a look. The hiring manager literally said, 'I didn't realize Priya had those skills.' Luna: Ouch. And I bet she was doing the work of someone at that level already. Lucas: Exactly. That's the classic 'out of sight, out of mind' trap in remote work. It's not about performance — it's about visibility. And the frustrating part is, many remote workers swing too far in the opposite direction: they over-communicate, they ping their manager five times a day, they book unnecessary 1:1s. And then they get labeled as annoying or needy. Luna: Right. There's this really narrow sweet spot between being invisible and being a nuisance. And no one teaches you how to hit it. Lucas: That's exactly what we're going to unpack today. The mechanics of strategic visibility: what to share, how often, and through which channel — without making people dread seeing your name pop up. And we're going to use Priya's case as the through line, because she actually figured it out and got the promotion a few months later without changing her title. Luna: Before we dive in — and I'm saying this because it connects directly to visibility — we keep this show ad-free by choice. No sponsors, no mid-roll interruptions. If you've gotten anything useful out of these episodes, and you want to support that independence, you can find us at buy me a coffee dot com slash fexingo. It's a small way to keep this exactly what it is. Lucas: Exactly. We value the listener's time too much to wedge in ads. So if you've ever thought 'this helped me,' that link is there. But honestly, the best support is just sharing an episode with a colleague who might need it. Luna: Yeah, that's the real visibility right there. Okay, back to Priya. What was the first thing she changed? Lucas: She did an audit of her communication patterns over two weeks. Priya realized she was doing a lot of work but broadcasting almost none of it. She'd finish a project, update the ticket, and move on. No one above her manager knew what she'd done. So she started something called a 'strategic visibility rhythm' — a concept I first heard from a leadership coach named Jasmine Escalera. Luna: I love that term. What's the rhythm? Lucas: Three layers. First, a weekly async standup — not a meeting, just two or three bullet points posted in her team's Slack channel every Monday morning. Not 'I did X', but 'I finished X, which unblocks Y for the next sprint, and I noticed Z about our data pipeline that might be worth a quick sync.' Notice she tied her work to organizational impact. Luna: So she's signaling both competence and strategic thinking. Not just 'here's my to-do list.' Lucas: Right. The second layer was a monthly 15-minute 'progress note' — a brief document shared with her manager and her skip-level. She'd outline one key result, one obstacle she'd solved, and one thing she wanted to learn next. No fluff, no self-congratulation. Just data. Luna: And her manager probably loved that because it made his own reporting easier. He could just forward it up. Lucas: Exactly. That's a huge point. When you make your manager look good and save them time, you become someone they want to advocate for. The third layer was the most counterintuitive: she stopped sending direct messages to her manager for every little thing. Instead, she batched non-urgent questions into a single Slack thread on Friday afternoon. Luna: Oh, that's smart. Because constant pings during the week are what create the 'annoying' perception. Batching them signals that you respect their focus time. Lucas: Yes. And there's research backing this. A 2024 Microsoft Workplace Trends report found that managers rated employees as 'high potential' 1.7 times more often when those employees posted regular async updates compared to those who only spoke in meetings. But here's the catch: the updates had to be concise and work-focused. Personal check-ins didn't move the needle. Luna: So there's a specific ratio. How many updates per week? Lucas: Priya landed on three to four 'visibility touches' per week: the Monday standup, one thoughtful comment on a colleague's project in a shared channel, one contribution to a team doc or decision thread, and one asynchronous check-in with her manager — not a meeting, just a quick Loom or Slack message. That's it. Four touches, total maybe 20 minutes of her week. Luna: And within a couple months, she got that promotion. Did she even interview? Lucas: She didn't have to formally apply. The senior director on the other team saw her name come up in a cross-functional meeting because her manager mentioned her analytics work — which he only knew about because of her progress notes. The director reached out directly and asked if she'd be interested in a lead role. That's the whole point: you want people to come to you. Luna: It's almost like priming the pump. You're not asking for attention — you're just making it easy for the right people to notice you. Lucas: Exactly. And that's the key distinction. The people who fail at remote visibility are usually doing one of two things: either they're invisible, or they're performing 'visibility theatre' — posting fluff, reacting to everything, scheduling pointless syncs. Priya's approach was surgical. She targeted the information that mattered to decision-makers. Luna: Can we talk about the calendar trick you mentioned? The one that gets senior leaders to remember your name? Lucas: Sure. Priya started a practice she called 'skip-level shadowing.' Once a quarter, she'd ask her skip-level manager if she could observe a meeting that was one level above her — not participate, just listen. She'd send a brief email saying, 'I'd like to better understand how decisions are made at the director level so I can align my work more effectively.' No one ever said no. Luna: And that puts her face — well, her Zoom square — in front of the person who makes promotion decisions, in a low-pressure context. She's not pitching, she's learning. Lucas: Right. And after the meeting, she'd send a one-sentence thank-you with a specific observation — something like 'I found the discussion on data latency tradeoffs really helpful for how I think about our pipeline.' That's it. The director now has a positive, low-effort association with her name. Luna: I want to push back a little, though. This sounds great for someone in a role where the work is fairly visible — like data analytics. But what about people in support roles, or individual contributors whose work is mostly behind the scenes? Like a backend engineer who never talks to stakeholders directly? Lucas: Great question. The principles still apply, but the tactics shift. For someone like that, the visibility rhythm might lean more on written documentation and code review commentary. A backend engineer at a Shopify competitor I spoke to last year did something similar: he started writing short 'technical decision records' after every significant piece of work — not just for his team, but for the broader engineering org. Within six months, he was being asked to consult on architecture decisions across teams. Luna: So the core idea is: find the artifact that travels. A document, a recording, a well-written comment. Something that exists even when you're not in the room. Lucas: Exactly. And this brings us to a broader point about remote work in 2026. We're now four years past the peak of the remote work debate. Most companies have settled into a hybrid or fully remote model. But the promotion pipelines still haven't fully adapted. A 2025 study from the National Bureau of Economic Research found that remote workers were promoted 1.3 times less often than in-office peers, even when controlling for performance. Luna: That's a depressing statistic. But it also means that strategic visibility is a real competitive advantage. If you're doing it well, you're already ahead of most people. Lucas: Right. The bar is actually lower than you'd think. Most remote workers are either radio silent or oversharing. If you hit that middle ground — the strategic rhythm — you stand out. Priya's story is proof. She didn't become a different employee. She just got better at making her value known. Luna: Before we wrap, let's give listeners one actionable takeaway. If someone's listening right now and thinking, 'I need to start this today,' what's the first step? Lucas: Do the audit I mentioned. For the next two weeks, track every piece of work-related communication you send — Slack messages, emails, comments, meeting contributions. Categorize them: are they status updates? Questions? Strategic observations? You'll probably find that you're either doing a lot of low-value pings or almost no broadcasting at all. Then pick one channel — async standup, a weekly note, a shared doc — and commit to one additional visibility touch per week. That's it. Luna: Start small, stay consistent. And in a few months, you might find a senior director noticing your name. That's the goal, right? Lucas: That's the goal. And if you try it, let us know. We'd love to hear what worked — and what didn't. We'll be back next time with another career question that's probably sitting in your inbox right now.