Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage the Employee Always in Meeting Mode
Transcript
- Lucas: So I was talking to a friend who manages a small engineering team, and he said something that stuck with me. He has one employee — great guy, really smart — who is in meetings from nine to five, back to back, every single day. And at the end of the week, he's exhausted but he hasn't shipped a thing. Luna: The meeting addict. I've seen that. They're the first to accept every invite, and somehow they never get their actual work done. Lucas: Exactly. And it's a tricky one to manage because on paper, they look like the most collaborative person on the team. They're in all the right rooms, they're responsive, they're visible. But the output just isn't there. Luna: So what do you do? Do you ban them from meetings? That feels too punitive. Lucas: Right, you don't want to punish collaboration. But the first thing you need to do is get curious about why they're in so many meetings in the first place. Because there's usually a reason underneath the calendar clutter. Luna: Like what? Lucas: Fear of missing out is a big one. They're afraid that if they're not in the meeting, they'll lose visibility or get left out of a decision. Another is that they genuinely want to be helpful — they say yes to every invite because they don't want to let anyone down. Luna: That's my default, honestly. I hate saying no to a meeting invite because I feel like I'm being rude. Lucas: And that's exactly why the two-question test is so powerful. Before accepting any meeting, ask yourself: one, do I need to be in this room to make a decision or contribute something specific? And two, is there someone else on the team who could represent me? Luna: I like that. It's not about saying no to everything — it's about being intentional. Lucas: Right. And for the manager, the job is to help your employee build that muscle. You can't just tell them to stop going to meetings. You have to walk them through the audit. Luna: Walk me through the audit. Lucas: So you sit down with them and you literally go through their calendar for the past two weeks. You categorize every meeting as one of three things: decision-making, information-sharing, or alignment. Then you ask, for each one, could this have been an email? Could it have been a quick chat? And the real kicker — could someone more junior have attended and brought back the highlights? Luna: That last one is clever. It turns a meeting into a development opportunity for someone else. Lucas: Exactly. And it's a great way to delegate without making the employee feel like they're being sidelined. You're saying, I trust you to identify what's important, and you're also helping someone else grow. Luna: So what did your friend's teammate's audit show? Lucas: He was averaging about thirty hours of meetings a week. And when they went through it, they found that about half of those meetings — fifteen hours — were ones where he was just a listener. He didn't need to speak, he didn't own an agenda item, he was there because he hadn't been given permission to leave. Luna: Permission to leave. That's such a big part of it. A lot of people feel like they can't leave a meeting early or decline an invite without a good excuse. Lucas: And that's where the manager comes in. You have to explicitly give that permission. In fact, I'd go further — you can make it a team norm. Something like, if you don't have a speaking role or a decision to make, you're welcome to leave. Just let the organizer know. Luna: That would change so many cultures. I remember at my last job, we had a guy who would book a room for an hour to sync on a project, and by minute fifteen, everyone was just checking their laptop. Nobody wanted to be the first to say, can we wrap this up? Lucas: Right. And that's another tool — the stand-up meeting format. If you force people to stand, or you cap it at fifteen minutes with a tight agenda, you suddenly find that a lot of meetings don't need to be an hour long. Luna: So we're giving managers a bunch of tactics. But what about the employee who honestly believes every meeting is essential? They push back and say, I need to be in all of these. Lucas: That's a harder conversation. And you have to respect that they might be right about some of them. The key is to shift the framing from attendance to outcome. Ask them, what is your specific contribution in that meeting? If they can't articulate it, that's a sign. Luna: And if they say, I'm just there to stay informed? What do you do with that? Lucas: Then you say, great — staying informed can happen in a shared document or a two-minute recap from a colleague. Let's find you a way to get that information without sacrificing your deep work time. Luna: I also think managers need to look at their own behavior. If you're the one who calls a meeting for every little thing, you're modeling that behavior. Lucas: A hundred percent. I've seen teams where the manager books a meeting to discuss a meeting. And then they wonder why nobody gets anything done. You have to be the change you want to see. Luna: Speaking of modeling behavior — I was at a conference last month, and one of the speakers said that the best leaders protect their team's focus time like it's the most precious resource they have. And I think that's a great lens for this whole thing. Lucas: It is. And honestly, if this episode helps you reclaim even a few hours a week for you and your team, that's a win. And if you want to help us keep making these episodes, the best thing you can do is buy us a coffee — just head to buy me a coffee dot com slash fexingo. It's a small way to keep this show ad-free and independent. Luna: And it really does make a difference. We appreciate every single person who does that. Lucas: So back to the meeting audit. Once you've identified which meetings are truly necessary, the next step is to create a 'meeting budget'. Decide, as a team, how many hours per week you're willing to spend in meetings, and then work backward from there. Luna: A meeting budget. That's a concrete number everyone can get behind. Lucas: For my friend's team, they decided on a maximum of twelve hours of meetings per person per week. And it forced them to be ruthless about what actually got on the calendar. Luna: What happened to the guy who was at thirty hours? Lucas: He cut down to around fifteen, and he told my friend that he finally felt like he had time to breathe. And his output actually went up, because he could finally focus on his actual projects. Luna: It's almost like meetings were the distraction, not the work itself. Lucas: Exactly. And that's the message you want to send to your team — that meetings are a tool, not a reward. They should serve the work, not the other way around.