Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / The Hidden Cost of Meeting Fatigue
Transcript
- Lucas: I want to start with a number that feels almost insulting in its simplicity. Last week, I spoke with an operations director at a mid-sized logistics firm who told me her team spends forty-two hours a month in meetings. That is more than ten percent of their total available working time. And here is the kicker: when she asked them what those meetings actually achieved, most couldn’t name a single decision that was made. Luna: Forty-two hours? That sounds like they are paying people to watch paint dry while waiting for permission to do the painting. Lucas: Exactly. And the tragedy isn't just the lost time; it's the cognitive fragmentation. When you have back to back calls, your brain never gets the chance to enter a state of deep focus. You become reactive rather than proactive. Today, we are going to talk about how to stop managing by calendar and start managing by outcomes. Specifically, how to audit your team’s meetings so you can cut the fat without losing the muscle. Luna: But how do you cut meetings without people feeling like they are being left out of the loop? Lucas: That is the core tension. People confuse visibility with value. They think if they are in the room, or on the Zoom call, they are contributing. But often, they are just consuming bandwidth. Before we get into the framework, I want to take a second to acknowledge the people who make this show possible. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that is literally what funds making these episodes ad-free. It keeps us independent and focused on the stuff that matters, rather than chasing clicks. Luna: Yeah, it is great to have a resource that doesn't interrupt the actual advice with sponsored segments every three minutes. Lucas: It really is. So, let’s get back to the audit. The first step in fixing meeting fatigue is realizing that most of your recurring meetings are not failing because of poor facilitation. They are failing because they lack a clear purpose. If you cannot write the agenda on a single sticky note, you should probably cancel the meeting. Luna: That is a hard rule. Sticky note or it didn't happen. Lucas: Sticky note or it didn't happen. Let’s look at a specific example from a tech startup I advised last year. They had a daily stand-up that lasted thirty minutes. Thirty minutes for fifteen people. Half of those people weren't even working on the same product line. They were there out of habit, not necessity. We cut the attendance list down to four key stakeholders. We moved the rest of the updates to a shared document. The meeting went from thirty minutes to five minutes. And guess what? Nothing broke. The team actually started talking more in the hallway after the meeting because they had their energy back. Luna: So the issue isn't the meeting itself, it's the audience bloat. You invite everyone because you don't trust anyone else to read the update. Lucas: Precisely. It is a trust deficit disguised as collaboration. When you invite someone who doesn't need to act on the information, you aren't helping them stay informed. You are robbing them of twenty-nine minutes of deep work. And deep work is expensive. Cal Newport wrote a whole book on it, but practically speaking, it takes about fifteen minutes for your brain to fully engage with a complex problem. If your meeting cuts that off every day, your team is operating at a perpetual half-power state. Luna: But what about the people who genuinely need to see the faces of their colleagues? Especially in hybrid setups. Lucas: Social connection is important, but it shouldn't be the primary function of a business meeting. If your team needs social connection, create space for that outside of transactional workflows. Schedule a virtual coffee chat, or a casual Friday afternoon session. Do not bury it inside a project status review. Keep the two separate. One is for bonding, one is for doing. Luna: So you are saying we need to decouple relationship building from task management entirely. Lucas: Yes. And this leads to my second point: the difference between synchronous and asynchronous communication. Most managers use meetings for everything. They want to share an email, so they call a meeting. They want to brainstorm, so they call a meeting. They want to decide, so they call a meeting. This is lazy management. You should only use synchronous time—meetings—for things that require real-time interaction, debate, or immediate feedback. Luna: Right. Reading a report is not real-time interaction. Deciding on a vendor is. Lucas: Exactly. If the goal is to inform, send a memo. If the goal is to decide, schedule a meeting. If the goal is to build rapport, grab lunch. Stop mixing them up. I worked with a marketing director who implemented a strict policy: no meeting could be scheduled without a pre-read document attached to the invite. If there was no pre-read, the meeting was automatically cancelled. At first, people complained. Then they realized they had to prepare better. And then they realized they spent less time in meetings and more time writing clear memos. Their decision-making speed actually doubled. Luna: That is interesting because it shifts the burden of preparation onto the presenter. Usually, presenters hate that. Lucas: They do, initially. But it forces clarity. When you force someone to write down their thoughts, they find the holes in their logic before they present them. It saves the group from spending an hour untangling a bad idea. It is painful for the individual, but it is efficient for the team. And efficiency is what we are trying to buy back. Luna: So the metric for success isn't just fewer meetings, it's clearer thinking. Lucas: Clearer thinking and faster execution. Let’s talk about the structure of the meetings you do keep. Most managers run meetings like they are broadcasting a radio show. They talk, everyone listens. Then maybe there is a Q&A at the end. This is passive engagement. It is the lowest form of collaboration. Instead, try the 'silent start.' For the first five minutes of any meeting, everyone reads the agenda and the supporting documents in silence. No small talk. No checking emails. Just reading. Luna: That feels awkward at first. People will wonder if something is wrong. Lucas: It does feel awkward. But once they get past the initial weirdness, the quality of the discussion skyrockets. Because now everyone is on the same page. You skip the 'let me recap what I said' phase. You go straight to analysis. It respects people's intelligence and their time. It assumes they can read. Which, frankly, they should be able to do. Luna: I like that. It cuts out the noise immediately. But what about the people who dominate the conversation? Even with a silent start, the loudest voice usually takes over. Lucas: That is a facilitation issue, not a meeting format issue. But you can mitigate it by using round-robin structures. Go around the table and ask for one sentence from each person. No interruptions. Just input. It forces the quiet people to speak and limits the volume of the loud people. It levels the playing field. And it ensures that you hear from the person in the corner who might have the best idea in the room. Luna: Because often the quietest person is the one who has been thinking about this problem for weeks while the others were arguing. Lucas: Exactly. And if you don't create space for them, you lose that insight. Meeting fatigue isn't just about exhaustion; it's about missed opportunity. You are missing the signal because you are too busy amplifying the noise. Another tactic is the 'parking lot.' If a topic comes up that is relevant but not part of the current agenda, write it down on a virtual whiteboard or a physical pad. Tell the group, 'We are parking this for next week.' Then move on. It validates the contributor without derailing the current objective. Luna: It’s a way of saying 'I heard you' without saying 'yes' to the detour. Lucas: Precisely. It keeps the train on the tracks. Now, let’s talk about the aftermath of the meeting. How many of your meetings end with a clear list of action items, owners, and deadlines? If you are nodding yes, be honest. How many of those action items actually get done? I would bet less than fifty percent. Why? Because the notes are vague. 'John will follow up' is not an action item. 'John will email Sarah by Tuesday at noon to confirm the vendor contract' is an action item. Luna: Specificity is accountability. Vagueness is procrastination. Lucas: Vagueness is chaos. And chaos breeds more meetings. Because if nothing gets done, you have to meet again to figure out why. It is a vicious cycle. Break the cycle by ending every meeting with five minutes dedicated solely to recapping actions. Read them out loud. Confirm the owner. Confirm the date. If someone hesitates, push back. 'Can you commit to that date?' If they say no, negotiate until they can. Or change the scope. Don't let ambiguous commitments slide. Luna: It requires a bit of backbone from the chair. Not everyone wants to be that person. Lucas: It does. But leadership is about setting norms. If you tolerate vague meetings, your team will tolerate vague results. If you enforce precision, your team will learn to deliver precision. And over time, the amount of time you spend in meetings will drop simply because the work is getting done outside of them. You won't need to meet to chase progress. Luna: So the ultimate goal is to make yourself obsolete in terms of meeting facilitation. Lucas: Ideally, yes. Your role is to remove barriers, not create them. If your team can communicate effectively asynchronously, and only come together for high-value decisions, you have built a resilient system. It scales better. It survives when you are sick or on vacation. And it reduces burnout because people know exactly what is expected of them and when they are free to focus. Luna: That sense of autonomy must be huge for retention. People leave when they feel micromanaged, but they also leave when they feel overwhelmed by process. Lucas: Both. Process overload is a form of micromanagement. It implies you don't trust them to manage their own time. By cutting meetings and clarifying expectations, you are giving them back control. And control is a powerful motivator. I want to leave you with one final thought. Look at your calendar for next week. Pick three recurring meetings. Ask yourself: 'If this meeting didn't exist, would anything important change?' If the answer is no, cancel it. Send a brief email summarizing the status. Give your team the gift of time. It is the most valuable thing you can offer. Luna: And if the answer is yes, make sure you have a sticky note ready. Lucas: A sticky note and a pre-read. Thank you for listening. What is one meeting you could cancel tomorrow to give your team some breathing room?