Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The One Meeting Type You Can Decline Without Guilt
Transcript
- Lucas: So I want to start with a number that keeps rattling around in my head. Microsoft did a study a couple of years ago — and it's been widely cited since — that fifty-seven percent of all meetings are what they call 'status update' meetings. Luna: Fifty-seven percent. That's more than half. Lucas: More than half. And the recommendation from Microsoft's own research was that those meetings should be replaced with asynchronous updates — a shared document, a Slack thread, a quick Loom video. But most of us still accept them. We feel like we have to. Luna: Right. And I think the pressure is especially strong when the meeting is from a senior person or a cross-functional stakeholder. Saying no feels risky. Lucas: Exactly. And that's what I want to drill into today. Not just 'decline more meetings' — that advice is everywhere. But specifically: which meeting type is almost always safe to decline, and how do you actually do it in a way that doesn't damage your reputation? Luna: Okay, I'm all ears. Because I've definitely sat in meetings where I'm thinking, 'I could have read this in five minutes.' Lucas: Right. So let me give you the category I've started calling the 'no-agenda meeting.' It's any meeting that lands on your calendar without a written agenda shared at least twenty-four hours in advance. If there's no agenda, there's no defined outcome. And if there's no defined outcome, the meeting is almost certainly going to be a status update disguised as a collaboration. Luna: But what if the meeting is with your manager or a director? You can't just say, 'I need an agenda or I'm not coming.' Lucas: You can — but you have to phrase it carefully. The key is to frame it as a productivity concern, not a personal preference. So instead of saying 'I don't attend meetings without agendas,' you say something like, 'I want to make sure I'm fully prepared so we can use the time effectively. Could you share a quick agenda or the specific topics you'd like to cover?' Luna: That does sound less confrontational. But what if they say, 'It's just a quick sync, no agenda needed'? Lucas: That's the most common response. And in that case, I have a follow-up. I say, 'Great, then maybe a five-minute async update would work instead? I can share my status in writing and you can review it when you have a moment.' Nine times out of ten, they agree. Because if it really is just a status update, async is faster for everyone. Luna: So you're basically offering an alternative, not just declining. That makes it a collaboration, not a rejection. Lucas: Exactly. And the interesting thing is, once you start doing this, people actually respect you more. You're seen as someone who values time — not just your own, but theirs. I've had managers tell me, 'Thanks for being upfront. I hate those meetings too.' Luna: That's the ideal outcome. But I imagine there are some meetings where you genuinely need to be there, even without an agenda. Like a brainstorming session or a crisis. Lucas: Sure. The rule isn't absolute. If there's a fire drill, you show up. But here's the thing — even a crisis meeting should have a stated goal. 'We need to decide on the vendor by end of day.' That's an agenda. The point is, if no one can articulate why you're meeting, you're probably wasting time. Luna: So let's talk about that fifty-seven percent again. If you could reclaim even half of those status update meetings, how much time would that be per week? Lucas: Let's do the math. The average professional attends about ten meetings a week. Fifty-seven percent of ten is about six status update meetings. If each one is thirty minutes, that's three hours. If you can cut half of them — three meetings — you save ninety minutes a week. That's six hours a month. Seventy-two hours a year. Luna: Seventy-two hours. That's almost two full workweeks. Lucas: Exactly. And that's just from status update meetings. There are other types you can decline too — like the 'let's circle back' meeting, or the 'I just want to pick your brain' meeting. But the no-agenda filter catches most of them. Luna: I want to push back on one thing though. Some people argue that informal meetings build relationships. If you only accept meetings with agendas, you might miss out on serendipitous conversations. Lucas: I think that's a fair point, but I'd separate relationship-building from status updates. A coffee chat or a walking one-on-one is different from a standing thirty-minute meeting where everyone reads their bullet points aloud. The former is valuable; the latter is a productivity sink. Luna: So how do you distinguish? I mean, sometimes a meeting starts as a status update but turns into a useful discussion. Lucas: That happens. And if it does, great. But the problem is that most status update meetings don't turn into anything else. They just cycle through the same updates week after week. My rule is: if the meeting has a clear agenda and a specific outcome, I'm in. If it's just 'let's touch base,' I decline or suggest async. Luna: I like that. 'Let's touch base' is probably the most dangerous phrase in corporate calendars. Lucas: It really is. So here's a practical step listeners can take today. Open your calendar for this week. Look at every meeting that doesn't have an agenda attached. For each one, ask yourself: 'If this meeting were canceled, would anyone notice? Could the information be shared in a document?' If the answer is yes to either, send a polite message suggesting async. Luna: And if you get pushback, what's your go-to script? Lucas: I say: 'I want to make sure I'm using our time well. I've been trying to batch my deep work, and meetings without an agenda tend to pull me out of focus. Would it work if I shared my update in writing before the meeting, so we can use the time for discussion if needed?' Most people respond to that because it's respectful and shows you've thought about it. Luna: There's also the option of a 'meeting audit' — where you and your team review recurring meetings every quarter and kill the dead ones. I've seen teams cut their meeting load by thirty percent just by doing that. Lucas: Absolutely. And that's actually a great way to do it collectively, so no one feels singled out. You can say, 'Let's look at all our recurring meetings and ask: is this still serving us?' It turns it into a team experiment rather than a personal boundary. Luna: Speaking of experiments, I've been trying something similar myself. I now have a rule: no meeting before ten AM. That gives me ninety minutes of focused time every morning. It's made a huge difference. Lucas: That's a great boundary. And it's the same principle — you're protecting your most productive hours from the default meeting culture. The thing is, most meetings aren't malicious. They're just thoughtless. People invite you because it's easier than writing a brief. Luna: So the solution is to make the thoughtful choice easier. If you decline or suggest async, you're actually helping the organizer think about whether the meeting is necessary. Lucas: Exactly. And over time, you train your colleagues to only invite you when they really need you. That's a huge win for your focus and your schedule. Luna: I think that's a really helpful reframe. It's not about being difficult. It's about being intentional with your time. Lucas: Right. And if you've found this conversation useful — if it's helped you think about how you protect your time — we'd love it if you considered supporting the show. We keep it ad-free, and listener support is what makes that possible. You can find us at buy me a coffee dot com slash fexingo. Luna: Yeah, even a small contribution goes a long way in keeping these episodes coming. And we really appreciate it. Lucas: So back to the meeting question. One more thing I want to mention: the 'reverse meeting' concept. Instead of a regular status update, you send a written update before the meeting and then only meet if someone has a question. That can cut meeting time by eighty percent. Luna: I've heard of that. Some teams call it 'the async-first approach.' It works especially well for teams that are already remote or hybrid. Lucas: Exactly. And it respects everyone's time. So to wrap up: the one meeting type you can decline without guilt is the no-agenda status update. Use the scripts we talked about, offer an async alternative, and watch your calendar open up. Luna: And if you try it, let us know how it goes. We'd love to hear your stories. Lucas: Absolutely. Until next time.