Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Lead Team Meetings That Actually Work
Transcript
- Lucas: There is a specific moment every new manager hits where you realize you've become a full-time meeting scheduler who also does a little bit of actual work on the side. Luna: Oh, that moment. And it usually lands somewhere around week six or seven, right? Lucas: Exactly. Week six, you've got your one-on-ones dialed in, you're starting to feel like you know your team, and then you look at your calendar and it is just walls of recurring invites. The biggest single block is almost always the weekly team meeting. Luna: And that's the one that everyone hates. It's the meeting where people are checking email, or they're the one person who talks the whole time. Lucas: Right. So today I want to walk through one real case. A first-time manager at a logistics software company — about 200 people, they're growing fast. Her name is Priya. She inherited a team of eight, and the weekly team meeting was a ninety-minute block, every Tuesday at 10 AM. Luna: Classic. I can already guess the format: each person stands up and reads their status update from last week. Lucas: You nailed it. Each person would go around the table — or around the Zoom grid — and say what they did, what they're doing, and maybe mention a blocker. By the time the eighth person finished, the first person had already forgotten everything. And Priya told me the energy in the room was just dead. Luna: So what did she do? She couldn't just cancel it, right? The team needs to align. Lucas: She didn't cancel it. She redesigned it. And the first thing she changed was the agenda structure. Instead of a status-update round-robin, she flipped it to problem-first. Each person had to submit one sentence before the meeting: 'The one decision I need from the team this week' or 'The one obstacle I can't clear on my own.' Luna: Oh, that's smart. It makes the meeting about unblocking, not reporting. Lucas: Exactly. And then during the meeting, they only spent time on items that actually needed collective input. If someone's update was purely informational — 'I finished the API integration' — that went into a shared document that everyone read async. Luna: So the meeting itself went from ninety minutes down to what, forty-five? Lucas: She got it to forty minutes on average. But the second change was even more important. She capped each person's presentation time at five minutes, and she introduced a rotating facilitator role. Luna: Rotating facilitator meaning someone else runs the meeting each week? Lucas: Yes. Priya stayed in the room as a participant, but she handed the facilitation — timekeeping, keeping the conversation on track, making sure everyone spoke — to a different team member each week. And the rule was, as facilitator, you don't get to present your own update that week. Luna: That's fascinating. It forces the facilitator to be fully present and listen to everyone else. Lucas: And it builds a skill that most new managers overlook: the ability to run a meeting well. The team members started learning how to manage airtime, how to cut off a rambling update politely, how to ask 'What do you need from us?' versus 'What did you do?' Luna: I bet some of them were nervous at first. I would be if I had to run the meeting as an individual contributor. Lucas: Priya said the first few weeks were rough. The first facilitator, a senior engineer named Marcus, let one person talk for fifteen minutes straight because he didn't want to interrupt. But they debriefed after each meeting — just five minutes — on what the facilitator did well and what they'd try differently next time. Luna: So the meeting itself became a teaching tool. That's elegant. Lucas: And it solved another problem Priya hadn't anticipated. There was a senior leader on the team — let's call him Derek — who had been at the company for years and was used to dominating the conversation. When Priya was the sole facilitator, she'd have to actively cut him off, which was awkward. Luna: Ah, the classic 'I have a lot of context to share' person. Lucas: Exactly. But when the facilitator role rotated, Derek was put in that seat twice in eight weeks. And as facilitator, he couldn't interrupt or go on tangents. He had to manage the time. Priya said it was the single most effective thing she did to change his behavior — he experienced what it felt like to have someone else dominate the room. Luna: That is such a low-confrontation way to handle it. You're not telling Derek to stop talking; you're just giving him a different job. Lucas: And it worked. After a few weeks, Derek started self-regulating even when he wasn't the facilitator. He'd say things like 'I have a thought on that, but I'll put it in the doc so we don't derail.' Luna: Okay, so we've got problem-first agenda, time caps, rotating facilitator. What was the third fix? Lucas: The third fix was something Priya calls 'the one-question close.' At the end of every meeting, she asks the team to answer one question in a single sentence: 'What is the one thing from this meeting that will change how you work this week?' Luna: And they have to say it out loud? Lucas: They go around the virtual room. Everyone says their one sentence. And it does two things. First, it forces people to actually listen and extract something actionable. Second, it gives Priya a real-time signal of whether the meeting was useful. If seven out of eight people say something vague like 'I'll keep that in mind,' she knows the meeting didn't land. Luna: That is a brutal but brilliant feedback loop. And it must help her improve the agenda for next week. Lucas: Exactly. She told me that after three months, the average meeting value rating — she uses a simple thumbs-up/thumbs-down poll — went from about 60 percent positive to 92 percent positive. And the meeting length dropped to 35 minutes. Luna: So the team got back fifty-five minutes per week, per person. That's seven hours a week across the team. Over a quarter, that's huge. Lucas: It is. And look, this specific format might not work for every team. But the principles are transferable. Let me just name them. One, separate informational updates from decision-making time. Two, distribute the facilitation load. Three, build in a closing ritual that surfaces value — or the lack of it. Luna: And I think there's a fourth one that Priya didn't name but that I see in her story: the meeting itself is a leadership development tool. Your team learns how to run meetings by running them. Lucas: That's right. And if you're a new manager listening, you might be thinking, 'My team is too senior for this' or 'My boss would never let me change the format.' But the thing is, the trust to make these changes usually comes from being transparent about the cost of the current meeting. Luna: Yeah. You can literally say, 'This ninety-minute meeting costs the company about X dollars in salary per week. I think we can get more value in less time.' That's a language senior leaders understand. Lucas: And when you have a proposal that saves time and builds capability, most bosses will say yes. Priya's boss was actually surprised she had taken the initiative — he'd been wanting to change that meeting for a year but never had the bandwidth. Luna: So she got credit for solving a problem her boss had been unable to solve. That's a career win in itself. Lucas: It is. And I think that's the deeper point: the team meeting is not just a logistics chore. It's the most visible artifact of your leadership style. How you run it signals to the team whether you value their time, whether you trust them, and whether you're willing to experiment. Luna: Quick honest thing — a handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. If this show helps you think about your own meetings or your career, that's the reason it exists. Lucas: Yeah, it's a small group, but it keeps us independent and ad-free. So thank you to anyone who's part of that. And back to the meeting: there's one more thing Priya did that I want to mention. Luna: Please. I thought we covered all three. Lucas: She changed the name of the meeting. It was called 'Weekly Team Sync.' She renamed it 'Weekly Decision Forum.' That one word — decision — shifted everyone's expectation. They showed up ready to decide, not just to report. Luna: Language matters so much. It's like when you rename a one-on-one from 'check-in' to 'coaching session.' The whole dynamic changes. Lucas: Exactly. So if you are in your first ninety days and you inherit a meeting that feels like a time sink, you have permission to redesign it. Start with one change. Maybe it's the agenda format. Maybe it's the closing question. You don't have to do all three at once. Luna: And if you try something and it doesn't work, you can iterate. The worst thing is to keep running a meeting that everyone hates because 'that's how it's always been done.' Lucas: Priya's advice was this: 'Your first redesign will not be your last. That's fine. The goal is not a perfect meeting. The goal is a meeting that is better than last week.' Luna: I love that. It takes the pressure off. You're not trying to reinvent the wheel; you're just trying to make the wheel a little less squeaky. Lucas: Exactly. And if you do that consistently, you build a reputation as someone who makes things better, not just someone who manages them. Luna: That is the kind of reputation every new manager should want. Lucas: Alright, that's all for this episode. Next time we're going to talk about something that a lot of listeners have written in about: how to handle the first time you have to give critical feedback to someone who used to be your peer. Luna: Oh, that's a big one. I'm already thinking of examples. Lucas: We'll get into it. Until then, take a look at your team meeting this week and see if one small change could make it better.