Latest / Office Hours with Fexingo: Daily Career Q&A, Workplace Questions, and Professional Advice / The Five-Minute Rule That Rescues Bad Meetings
Transcript
- Lucas: There's a meeting format that I think is quietly one of the most powerful tools in a professional's toolkit, and almost nobody uses it correctly. Luna: Are we talking about the stand-up? Because I have feelings about stand-ups. Lucas: We're talking about something even more basic — the asynchronous status update. Specifically, what I call the five-minute rule. The idea is simple: any written update you send to a team should take no more than five minutes to read in full. If it takes longer, you've lost your audience. Luna: That sounds almost too simple. But I've definitely received emails that read like novellas. Lucas: Right. And the result is that people skim, they miss key details, and then the next meeting starts with 'did everyone read the update?' — which nobody really did. So you spend the first ten minutes rehashing what was already written. Luna: I've been in that exact meeting more times than I can count. So what does a proper five-minute update look like? Lucas: Three sections, no more. First: what was accomplished since the last update — bullet points, no more than three. Second: what's blocked or needs input — again, three max. Third: what's coming in the next period — three bullets. That's it. If you can't fit your update into nine total bullet points, you're either doing too much or not delegating enough. Luna: Nine bullets, five minutes. That's a tight constraint. But I imagine it forces clarity. Lucas: It does. And here's where the data comes in. I worked with a marketing team at a mid-size software company — about forty people — that had a weekly all-hands stand-up that routinely ran forty-five minutes. They switched to a written five-minute update sent every Monday morning, with the meeting reduced to fifteen minutes for questions only. Their throughput actually went up twelve percent in the next quarter. They weren't spending time on status updates in the room; they were spending it on decisions. Luna: Twelve percent is significant. And I bet people actually read the updates because they knew they'd only take five minutes. Lucas: Exactly. The constraint becomes a feature. If someone sends a ten-bullet update, people notice. There's social pressure to keep it tight. Luna: But what about managers who love to hear themselves talk? Or executives who want the full narrative? Lucas: That's the pushback I always get. And it's a fair one. Some leaders genuinely believe that context is lost in a short format. But I'd argue that if the context is that important, it deserves its own document — not a status update. The update is a signal, not the full story. Luna: So how do you handle the executive who insists on a three-paragraph email every Friday? Lucas: You offer a pilot. Say: 'For the next month, I'll send you a five-minute version. If you feel you're missing context, we'll go back to the long format.' Nine times out of ten, they realize they were reading the long version the same way they'd read the short one — skimming. Luna: That's a smart framing. It's not confrontational, it's experimental. Lucas: And it works because it respects their time, even if they don't realize they need it. Now, there's a related technique I want to mention — the one-sentence status. Some teams use a daily Slack thread where each person posts exactly one sentence about what they're working on. That's a version of the same principle. Luna: One sentence seems almost too short. But I've seen it work in engineering teams. It creates a habit of brevity. Lucas: Exactly. And the key is consistency. If you only do it once, it feels forced. If you do it every day for two weeks, it becomes part of the rhythm. Luna: Before we keep going, I want to mention something quick. If today's episode was useful to you and you want to keep it ad-free, buy me a coffee dot com slash fexingo helps. That's literally what keeps these conversations going. Lucas: Yeah, and we mean it. A handful of listeners chip in, and that's what funds the production. So if it's worth that to you, the link is buy me a coffee dot com slash fexingo. Luna: All right, back to the topic. So we've talked about the format. But what about the listener who says, 'My manager doesn't want written updates, they want a meeting'? Lucas: That's a great question. And it gets at the heart of why this is hard. Some managers use meetings as a way to feel in control. The written update feels like a loss of visibility. Luna: So how do you handle that? You can't just refuse to meet. Lucas: You don't refuse. You reframe the meeting. Say: 'I'll send the written update by Tuesday end of day. Then on Wednesday, instead of me walking through it, we can spend the whole fifteen minutes on the two or three things that need your input.' That turns the meeting from a status read-out into a decision session. Luna: That's a subtle shift, but I can see how it changes the dynamic. The manager still gets their meeting, but it's more productive. Lucas: Right. And the funny thing is, once they experience a few of those decision-focused meetings, they rarely want to go back. I've seen it happen. Luna: Any other tips for making the five-minute update actually stick? Because I know from personal experience that writing short is harder than writing long. Lucas: It is. The discipline is real. One trick: set a timer. Write your update, then spend two minutes cutting it down. Another trick: read it aloud. If it takes more than a minute to speak, it's too long. And finally, use a template. Even a simple one like 'Done, Blocked, Next' forces structure. Luna: I like the reading aloud test. That's one I'll try myself. Lucas: Give it a shot. And if you're in a team that's resistant, start with yourself. Just send your own five-minute update to your manager for two weeks. Don't ask anyone else to change. Often, they'll start asking, 'Hey, can you show me how you do that?' Luna: Lead by example — it's the oldest trick in the book, but it works. Lucas: Exactly. And one more thing — I want to emphasize that this isn't just for status updates. It works for project proposals, for weekly reports, even for email replies. The principle is the same: respect the reader's time. Luna: So the five-minute rule is really a mindset, not just a format. Lucas: That's exactly right. It's a commitment to clarity. And in a world where the average professional gets a hundred and twenty emails a day, clarity is a competitive advantage. Luna: Alright, I'm convinced. I'm going to try the one-sentence status with my team next week. Lucas: Let me know how it goes. And for everyone listening, if you have a question about making this work in your specific situation, send it in. We read every one. Luna: That's a wrap for today. See you next time.