Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage a Night Owl Team Member
Transcript
- Lucas: So we talked last week about diagnosing team dysfunction in five minutes. Today I want to get into something that comes up in almost every team I've ever worked with, but rarely gets a proper conversation: what do you do when your best work happens at midnight, but your manager lives in a 9-to-5 world? Luna: Oh, this is personal for me. I've been that midnight worker at more than one job. It's not just about preference either — there's research now. Lucas: Exactly. And that's where I want to start, because there's a really solid 2024 study out of MIT and Harvard Business School that looked at time-shifted work patterns in knowledge teams. They followed about 400 people across 40 teams over six months. The finding that jumped out: teams that explicitly agreed on asynchronous workflows and stopped expecting real-time responses saw a 12 percent increase in output. Luna: That's a big number. But let me guess — the catch is that you can't just say 'work whenever' and disappear. Lucas: Right. The teams that succeeded had a structure. They had a shared decision log — a simple document where anyone could drop a question or a proposal, and everyone knew to check it by end of day. They also had a single daily sync, usually a 15-minute standup recorded and transcribed, so if you missed it because you started at noon, you could catch up on your own time. Luna: So the structure is about communication, not about hours. That makes sense. Because the friction usually isn't the work itself — it's the handoffs. Lucas: Exactly. The handoffs. Let me give you a real case. I talked to a product manager at a mid-sized SaaS company — let's call her Priya. She had a senior engineer, Mark, who consistently did his deepest coding between 10 PM and 2 AM. His output was phenomenal, but her team had a culture of quick Slack responses during the day. Mark would get pinged at 3 PM and not reply until 10 PM. Other team members started to resent it. Luna: I've seen that resentment firsthand. It feels like the person isn't pulling their weight, even if the code is pristine. How did Priya handle it? Lucas: She started with a one-on-one, not a policy. She asked Mark what his ideal work rhythm looked like, and he was honest — he'd been forcing himself to be visible from 9 to 5, but he was groggy and unproductive. His best thinking happened after dinner. So they agreed on a hybrid: Mark would commit to being available for three core hours each afternoon, say 1 PM to 4 PM, for meetings and quick questions. Outside that, he'd work his own hours, but he had to post a daily summary of what he'd completed by 9 AM the next morning. Luna: The daily summary is key. It builds trust. Everyone can see the output. I'd add that the team also needs to agree on response time norms across the board — not just for the night owl. Lucas: That's exactly what Priya did next. She brought the whole team together and said, 'We're going to shift to an async-first communication model. Slack is not instant. Expect replies within four hours during the core window, and within 12 hours outside of it.' She also introduced a team decision log — a shared Google Doc where any decision that affected the group had to be written down and reviewed within 24 hours. It cut the number of meetings by 20 percent in the first month. Luna: And what about Mark? Did his output change? Lucas: His velocity went up about 15 percent, but the bigger win was that his code review turnaround time dropped. He was submitting pull requests at midnight, and the team started reviewing them during their morning. So the handoff actually got faster because it matched natural rhythms. The MIT study saw the same pattern — async teams had shorter cycle times because work moved when people were fresh, not when the clock said 3 PM. Luna: I want to push back a little though. What about managers who are night owls themselves? I've had bosses who schedule meetings at 8 PM because that's when they're on fire. That can be just as toxic. Lucas: Great point. The power dynamic matters. If the manager is a night owl, they have to resist the temptation to default to their own rhythm. The rule should be: the team defines the core collaboration hours, not the manager's personal preference. Priya was actually a morning person, so she had to work hard not to schedule 8 AM standups. She moved hers to 11 AM, which was the overlap between the early birds and the night owls. Luna: That's a good compromise. An 11 AM standup is late enough for the morning people, early enough for the afternoon starters. What about teams that are fully distributed across time zones? That's a whole other layer. Lucas: It is, but the same principles apply. I worked with a team that had people in San Francisco, London, and Bangalore. They had two overlapping core hours — 9 AM to 11 AM Pacific, which was 5 PM to 7 PM in London and 9:30 PM to 11:30 PM in Bangalore. That two-hour window was sacred for synchronous decision-making. Everything else was async. The London people would leave at 6 PM, the Bangalore people would start their day at 9 AM. It worked because they protected that window. Luna: So the core hours aren't about policing when people work — they're about creating a shared space for collaboration. The rest is up to the individual. That's a liberating frame. Lucas: Liberating, but it requires discipline. The biggest failure I've seen is when a manager says 'work whenever you want' but then sends Slack messages at 9 PM expecting a reply. You have to walk the talk. If you're a manager, model the behavior: don't send late-night messages unless you truly don't expect a response until morning. Use scheduled send. Or better yet, write it in a document and discuss it in the core window. Luna: I think there's also a coaching opportunity here. If a team member is a night owl, help them structure their off-hours work so it's not just reactive. Help them identify the deep work tasks that benefit from solitude. That way, the night hours aren't just about catching up on email. Lucas: That's a manager's job. You're not just accommodating a preference — you're optimizing for output. Mark told Priya he did his best code when he had two or three uninterrupted hours. So she started carving out those tasks — complex refactoring, new feature design — and assigning them to his evening block. The routine stuff, like bug fixes, she left for the core hours when he was available for quick feedback. Luna: That's smart segmentation. It also sends a signal that you trust the person to manage their own time. And trust, as we've said in other episodes, is the currency of high-performing teams. Lucas: Yeah. And speaking of trust — and I know this is a bit of a pivot, but it's connected — we deliberately keep this podcast ad-free. No sponsors, no ads, no interruptions. If that model works for you and you'd like to support it, the link is buy me a coffee dot com slash fexingo. That's all lowercase. It helps us keep doing this without selling your attention. Luna: And honestly, it's how we keep the conversation honest. We're not trying to sell you anything. Just share what we've seen work. So if you've gotten value from episodes like this one, that's the place. Lucas: Exactly. Now, back to night owls and core hours — one more thing I want to mention. There's a trap where the night owl starts to feel like an outsider. If the team goes out for lunch or does a spontaneous brainstorming session at 3 PM, and Mark is asleep, he misses out. So you have to be intentional about inclusion. Luna: Yeah, I've felt that FOMO. How do you solve it? You can't shift the whole team's social life. Lucas: You can't, but you can record the brainstorming session and ask Mark to review it before the next core window. You can schedule one team social event per month that rotates time slots — sometimes a lunch, sometimes a breakfast, sometimes a late-afternoon coffee. The MIT study showed that teams that rotated their social touchpoints had higher cohesion scores than teams that just did async happy hours. Luna: Rotation is smart. It signals that no one's schedule is the default. That's a small move with big cultural impact. Lucas: Alright, so let's wrap with a concrete takeaway. If you have a night owl on your team — or if you are one — the move is not to fight your biology. Agree on core hours, build an async communication system, use a decision log, and protect the off-hours for deep work. Measure output, not hours. And if you're the night owl, be explicit about your availability and always deliver on your commitments. Trust is built on reliability, not on being visible. Luna: And managers, if you do this right, you'll keep your best people. Because nothing says 'I trust you' like letting someone work at their best time. Lucas: That's it for this Monday. Next week, we're going to talk about the one thing first-time managers get wrong in their first 90 days — and it's not what you think. See you then.