Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Run Effective Status Meetings
Transcript
- Lucas: Let me start with a number that stuck with me: the average employee spends roughly 31 hours a month in meetings. And according to a survey from Atlassian, half of that time is wasted. So if you're a new manager, your status meeting — the one where everyone goes around and says what they're working on — might be the biggest time sink on your calendar. Luna: And it's especially painful because nobody wants to be the one who says 'I didn't get much done this week' in front of the whole team. Lucas: Exactly. So the meeting becomes a performance, not a useful update. I want to talk about a simple structure that a friend of mine — let's call her Priya — used when she became a marketing manager at a B2B SaaS company called Logix. She inherited a weekly team status meeting that ran 45 minutes and had eleven people. By the end, everyone was tuning out. Luna: Eleven people in a status meeting? That's a recipe for boredom. Lucas: Right. So she redesigned it around what I call the 'three-by-three' framework. Three minutes of prep, three agenda items maximum, and a three-word status per person. Luna: Three-word status? So someone says 'working on email campaign' and that's it? Lucas: Close — but it's three words plus a color. Red, yellow, or green. Green means on track, yellow means needs attention, red means blocked. So someone might say: 'Email campaign — green.' That's it. If they're yellow or red, they get two minutes to explain what they need. But green gets no extra time. Luna: That forces people to actually think about their status before the meeting. And it stops the meeting from turning into a long story about everything that happened. Lucas: Exactly. Priya told me that in the first week, two people said yellow, one said red. The red was a developer waiting on legal approval for a landing page. That blocker had been sitting for four days, but nobody had escalated it because there was no forum for it. The status meeting became the place to escalate. Luna: Quick honest thing — we do something similar here at Fexingo. This podcast stays ad-free because a small group of listeners chips in through buy me a coffee dot com slash fexingo. It helps us keep making episodes like this one, where we can dig into real frameworks without selling anything. Lucas: Yeah, it's a small thing that makes a big difference. So back to the three-by-three — the other piece is the three-minute prep. Priya asked everyone to send their three-word status in a Slack thread 15 minutes before the meeting. That way, she could see if anyone was red and decide whether to cancel the meeting altogether. Luna: Wait — cancel the meeting if everyone is green? Lucas: Exactly. If everyone is green and there's nothing to escalate, the meeting is a waste. So she'd send a note: 'All green, canceling status. See you next week.' That saved the team about 30 minutes per week. Luna: But doesn't that risk missing informal updates or team bonding? Lucas: Good question. Priya found that the informal stuff happened anyway — people would grab coffee after the canceled meeting. And for team bonding, she started a separate weekly 15-minute 'water cooler' standup where they talked about non-work stuff. The status meeting was for blockers, not bonding. Luna: So the three agenda items — what goes in there? Lucas: Only things that need a decision or a discussion from the whole group. For example: 'Should we push the launch date by two weeks?' or 'How do we allocate the new budget?' Priya banned status updates from the agenda. If it's just an update, it goes in the async Slack thread. Luna: That's a big shift for a lot of managers. I've seen people use status meetings to justify their existence by listing everything they did. Lucas: Right. And that's the micromanagement trap. When you're a new manager, you feel like you need to know everything your team is doing. But the three-word status gives you a snapshot without the noise. You can always drill down in one-on-ones. Luna: So what about remote teams? Does this work when everyone's on Zoom? Lucas: Priya's team was fully remote, actually. She did the async Slack thread for status, then the meeting was a 15-minute Zoom call for red and yellow items only. She also asked everyone to turn their cameras on for the escalation part, so you could see if someone looked stressed. Luna: That's smart. Because a red status in Slack might not convey urgency, but seeing someone's face does. Lucas: Exactly. The other thing she did was timebox the escalation. Two minutes per person, with a timer. If the issue needed more time, she'd schedule a separate follow-up with just the relevant people. Luna: So the whole meeting never exceeded 15 minutes? Lucas: Usually 10 to 12. And the team loved it. After a month, she surveyed them and the average satisfaction with meetings went from 3.2 to 4.6 out of 5. One person said, 'I actually look forward to status now because it's efficient.' Luna: That's a huge win for a new manager. Because your team's perception of you is shaped by how you run meetings. Lucas: Totally. If you're the manager who runs a tight, useful status meeting, people think you're organized and respectful of their time. If you let it drag, they think you're clueless. Luna: So what about the urge to add more items? Like, 'while we're all here, let's also talk about...' Lucas: That's the death of the meeting. Priya had a rule: if it's not on the agenda before the meeting, it doesn't get discussed. She'd say, 'Let's put that on next week's agenda.' And she stuck to it. Luna: It takes discipline. But I think new managers especially struggle with that because they want to be helpful and inclusive. Lucas: Right. But being inclusive means respecting everyone's time. If you let one person go off-topic, you've just wasted ten other people's minutes. Priya told me that the hardest part was learning to say no to herself. Luna: What about the three-minute prep? Did people actually do it? Lucas: At first, no. She had to remind them. But after two weeks, it became a habit. She also made it easy by creating a Slack slash command: /status. So people could type '/status green email campaign' and it would post to the thread. Luna: That lowers the friction. I love that. Lucas: The big takeaway for new managers is: your status meeting is not about you. It's about surfacing blockers and making decisions. If you design it for the team's needs, not your need to feel informed, it will be ten times more effective. Luna: And if you're still not sure, try the three-by-three for two weeks. Worst case, you save a few hours. Lucas: Yeah. And if it doesn't work, you can always go back to the 45-minute slog. But I bet you won't.