Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Remote Employee Who Disappears Mid-Day
Transcript
- Lucas: Luna, have you ever had a remote team member who just goes dark for two or three hours in the middle of the afternoon? No message, no status update, just gone. Luna: Yeah, I think every manager who's led a distributed team has felt that knot in their stomach when Slack goes quiet and you don't know if they're doing deep work or watching Netflix. Lucas: Exactly. And the default instinct is usually to enforce core hours — everyone online 9 to 5, no exceptions. But that can backfire, especially if the person is a high performer hitting their deliverables. Luna: So what do you do when the output is fine but the presence is missing? I've seen that create real resentment on teams. Lucas: Let me give you a specific case. I was talking to a VP of Engineering at a mid-sized SaaS company — about 80 people, fully remote. They had a senior data analyst, let's call her Priya. Priya was in the top 5 percent of performers by output. But around 2 PM every day, she'd go offline until 4 or 4:30. Her teammates started noticing because they'd need a quick question answered and get radio silence. Luna: And the VP's first move was to check her output, right? Lucas: He did. And her sprint velocity was fine, her project deadlines were fine. But the team's trust was eroding. People felt like she was 'only working 6 hours' while they were grinding through the afternoon. So he called her. Luna: And what did Priya say? Lucas: She said she was doing deep analytical work — building models, running complex queries — and that the 2-to-4 window was when her concentration peaked. She was putting on headphones, closing all chat apps, and focusing. She admitted she should have communicated that, but she assumed results spoke for themselves. Luna: So the issue wasn't laziness. It was a mismatch in expectations about visibility. She thought output was enough; the team wanted availability. Lucas: Right. And that's the core tension in remote management: do you manage by presence or by outcomes? The VP took a third path. He didn't mandate strict core hours. Instead, he asked Priya to do two things. First, set a recurring calendar block called 'Deep Work — Responding to urgent messages only, will respond to non-urgent by end of day.' Second, she had to be available for one 15-minute window at 3 PM, by phone, for anything time-sensitive. Luna: That's smart. The block signals intent to the team, and the window creates a safety valve. But does that fully solve the resentment? I can imagine teammates still thinking, 'Great, she's protected, but I'm still answering pings all afternoon.' Lucas: That's exactly what the VP was worried about. So he took it a step further. He surveyed the whole team about their ideal deep work windows and found that about 40 percent of them preferred late morning, 35 percent preferred early afternoon, and 25 percent were flexible. He then introduced a team-wide norm: you can block up to two hours a day as 'focus time,' but you have to label it clearly in your calendar and specify how urgent messages should reach you — Slack DM, phone call, or email. Luna: So he turned Priya's 'problem' into a team policy. That's actually pretty elegant. You avoid singling her out and give everyone the same flexibility. Lucas: Exactly. And the policy came with one more rule: any meeting scheduled during focus time required the organizer to explain why it couldn't be async. That cut unnecessary sync meetings by about 30 percent within two months. Luna: I love that. But I also wonder about the manager who doesn't have a VP willing to rethink norms. For a first-time manager with one or two remote reports, what's the practical first step? Lucas: I'd say start with a single conversation — and I'd frame it around impact, not suspicion. Say something like, 'I notice you tend to go offline mid-afternoon. I'm not questioning your work — your output has been strong. But I want to make sure the team feels supported and that you're set up to do your best work. Can we talk about what your ideal schedule looks like and how we can make it transparent to everyone?' Luna: That's a much better opener than 'I need you to be available from 2 to 4.' It invites collaboration instead of enforcement. Lucas: And the goal isn't to eliminate flexibility — it's to create predictability. The team doesn't need everyone online at the same time. They need to know when they can expect a response. If Priya says, 'I'll respond to all Slack messages within 90 minutes during my focus block,' that's a promise the team can rely on. Luna: Which is really about setting service-level agreements for communication, not hours. Lucas: Exactly. And that's a much more mature way to run a remote team. It also surfaces a deeper issue: are you measuring the right things? If Priya's output is stellar, why does her schedule bother anyone? The answer is usually that the team has unspoken norms about responsiveness that nobody ever wrote down. Luna: So part of the fix is making those norms explicit. We've talked on this show before about the power of a team charter — this feels like a perfect use case. Lucas: Yeah. And this connects to something we hear a lot from listeners — that they feel torn between trusting their people and holding them accountable. The thing is, those aren't opposites. Trust is the foundation, but accountability is how you protect trust. If you never address the disappearing act, trust actually erodes because resentment builds. Luna: It's like the trust bank account — you have to make small deposits regularly, and a conversation like this is a deposit because you're showing you care about both the individual and the team. Lucas: Right. And if we've helped you think through a tricky management situation like this one, we want you to know that these episodes are only possible because listeners like you support the show. A couple of dollars a month at buy me a coffee dot com slash fexingo genuinely keeps us ad-free and focused on real cases. We don't have a big production team — it's just the two of us and a mic. Luna: And we hear from managers all the time who say a single episode helped them handle a conversation they'd been dreading. That's why we do it. Lucas: So back to Priya. After the policy was in place, the VP checked in with her three months later. She said she felt more respected because her work style was acknowledged, and the team actually started scheduling their own focus blocks. The resentment disappeared. Luna: And the team's overall satisfaction scores went up, I'm guessing? Lucas: They did. In the next engagement survey, the question about 'work-life balance' improved by 12 points, and 'team collaboration' held steady. So they gained flexibility without losing cohesion. Luna: That's the kind of win that makes you wonder why more companies don't do this. But I think the barrier is that managers are afraid to have the conversation in the first place. Lucas: Absolutely. And that fear is usually about not wanting to seem controlling or distrustful. But here's the reframe: if you avoid the conversation, you're actually failing the employee, because they don't know there's a problem until someone quits or complains. You're doing them a disservice by staying silent. Luna: So the key takeaway for a manager listening today: if you have a remote team member who goes dark mid-day, start with curiosity, not control. Ask what their ideal deep work schedule looks like, and then work together to make it visible to the team. Lucas: And if you're that employee yourself — maybe you're Priya — consider volunteering the information before your manager has to ask. Say, 'Hey, I do my best analytical work between 2 and 4. I'll be offline then, but I'll respond to anything urgent within 30 minutes. Here's how to reach me in an emergency.' That kind of proactive communication builds trust faster than any output report. Luna: It also signals that you understand the team dynamic, which is exactly what managers look for in potential leaders. Lucas: Right. So whether you're the manager or the employee, the principle is the same: make the invisible visible. Set expectations, not mandates. And remember that the goal isn't to watch people work — it's to get great work done together. Luna: Well said. And I think that's a good note to leave on. Next week, we'll tackle another listener question about managing someone who always says 'I need more time' — and the line between reasonable pacing and procrastination. Lucas: Looking forward to it. Until then, keep having the hard conversations — they're the ones that matter.