Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Simple Change Cut Meeting Time 40 Percent
Transcript
- Lucas: So a mid-size tech company — about eight hundred employees — decided they were drowning in meetings. The average employee was spending twenty-three hours a week in meetings, and the CEO, who was a data guy, had actually pulled that number from their calendar system. Luna: Twenty-three hours? That's more than half the work week in just meetings. No wonder everyone was complaining about not getting actual work done. Lucas: Right. And the crazy part is, the CEO didn't just complain about it. He made one single policy change that cut that number by forty percent across the whole company in six months. Luna: Forty percent? So from twenty-three hours down to about fourteen? That's huge. What was the change? Lucas: It was elegantly simple. He changed the default meeting length from sixty minutes to twenty-five minutes. And he required that every meeting invite include an agenda — not a long one, but at least three bullet points. That's it. Luna: Twenty-five minutes? That seems oddly specific. Why not thirty? Lucas: Good question. He wanted a buffer. Twenty-five minutes of actual meeting time, then a five-minute break before the next meeting. That way people weren't back to back all day. Also, by making it an odd number, it broke the mental habit of 'one hour equals one meeting slot.' Luna: I love that. And the agenda requirement — three bullet points. That's almost like forcing people to think about why they're meeting in the first place. Lucas: Exactly. The agenda didn't have to be long — just enough to show that the meeting had a purpose. 'Discuss Q2 budget, review marketing timeline, assign action items.' That kind of thing. If you couldn't come up with three bullets, maybe you didn't need a meeting. Luna: But I imagine there was pushback. People are used to their hour-long slots. Did they get resistance? Lucas: Oh, definitely. The first month was rough. A lot of senior managers argued that their projects were too complex for twenty-five minutes. The CEO's response was, 'If it needs more time, schedule two back to back slots, but then you have to justify why to your team.' That killed a lot of unnecessary extensions. Luna: So they forced transparency. If you needed a whole hour, you had to explain it. That probably weeded out a lot of vague 'status update' meetings. Lucas: It did. And here's where it gets interesting. They tracked the impact using calendar analytics. After six months, the total meeting hours across the company dropped by forty percent. But they also ran anonymous pulse surveys asking about meeting effectiveness. That actually improved too — people felt the meetings they did have were more focused. Luna: So it wasn't just less meetings, but better meetings. That's the ideal outcome. Lucas: Yeah. The saved time translated into roughly twelve thousand person-hours per quarter. That's the equivalent of adding six full-time employees without hiring anyone. They redirected that time into deep work — coding, strategy, customer research. Luna: And honestly, if today's episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Smallest possible ask, but it keeps the show ad-free and focused on exactly these kinds of case studies. Lucas: Yeah, no pressure at all. But if you've ever saved an hour by cutting a meeting short, maybe throw a coffee our way. Anyway, back to the case — what's interesting is that the policy didn't just affect internal meetings. They eventually applied it to client meetings too. Luna: How did clients react? Usually clients expect an hour, right? Lucas: They tested it. They told clients, 'We've found our most productive meetings run twenty-five minutes. We'll cover the key points and follow up with a written summary within an hour.' Most clients actually appreciated it. They were in the same boat — too many meetings. Luna: So it became a competitive advantage. 'We respect your time.' That's a powerful message. Lucas: Absolutely. And the whole thing hinges on a concept called Parkinson's Law — work expands to fill the time available. If you give someone an hour, they'll use the whole hour. Give them twenty-five minutes, and they'll find a way to get it done in twenty-five. Luna: But isn't there a risk of cutting too much? Some meetings genuinely need more time — like a strategy offsite or a deep technical review. Lucas: Sure. The policy had exceptions — all-hands meetings, quarterly reviews, workshops. Those could be longer, but they had to be explicitly approved by a department head. The default was twenty-five, not the maximum. And exceptions were tracked, so you could see if someone was abusing it. Luna: So the data itself became a check. If one manager had ten two-hour meetings a week, that would show up in the analytics. Lucas: Exactly. The CEO reviewed a dashboard every month showing meeting hours per person, per team. He didn't name and shame, but he'd ask teams why their numbers were high. That kind of gentle accountability kept everyone honest. Luna: And the three-bullet agenda — what if people just wrote vague things like 'budget'? Did they enforce quality? Lucas: The policy only required three words or more, but the culture shifted. After a few months, people started writing better agendas because they saw that good agendas led to shorter, more productive meetings. The tool they used — a calendar plugin — also let attendees upvote agenda items, so the most important topics got discussed first. Luna: That's smart. Prioritization within the meeting itself. So if you only get through two of three items, the third gets cut, not the first. Lucas: Right. And the remaining item would automatically carry over to a follow-up, which then had its own twenty-five-minute slot. That way nothing fell through the cracks, but the meeting ended on time. Luna: I'm curious — did they measure any downstream effects? Like employee satisfaction or retention? Lucas: They did. Employee satisfaction scores related to 'time for focused work' went up twenty-two percent in the first year. Voluntary turnover dropped about five percent. People cited 'respect for their time' as a top reason for staying. That's a huge return on a simple policy change. Luna: So the cost was basically zero — just changing a default and adding a text field. The benefit was millions in saved salary cost and better retention. Lucas: Exactly. And it's replicable in almost any organization. The key is having leadership model the behavior. The CEO personally moved all his one-on-ones to twenty-five minutes and published his calendar publicly so everyone could see he was living the policy. Luna: That's the thing about defaults — they're powerful because they're passive. Most people will just accept whatever the system gives them. Change the default, change the behavior. Lucas: And the best part? The tool they used to enforce the agenda requirement was a simple integration with their calendar system. It auto-rejected any meeting over twenty-five minutes unless it had an approved exception. That removed the friction of having to manually decide every time. Luna: So the system did the heavy lifting. That's a good lesson — don't rely on willpower; build the constraint into the process. Lucas: Yeah. And they eventually open-sourced the integration. Other companies have adapted it. One law firm I know uses a thirty-minute default with a similar agenda rule and cut their billable-hour leakage by eight percent. Luna: I think a lot of listeners are probably looking at their own calendars right now and wondering if they could do this. What's the first step if someone wants to try? Lucas: Start with your own calendar. For one week, change all your meetings to twenty-five minutes and write a three-bullet agenda. See what happens. Most people find that 80 percent of their meetings can be compressed. Then, if you're a manager, share the data with your team and propose a trial. Luna: And if you get pushback, you can always run a pilot in one department first. That's what this company did — they tested it in engineering before rolling out company-wide. Lucas: Exactly. The engineering team was skeptical, but after three months, their productivity metrics improved and they voted to keep the policy. That made the rollout to other departments much easier because they had internal success stories. Luna: It's almost like the change itself became a case study inside the company. And now it's a case study for us. Lucas: It's one of those rare changes that costs nothing, saves money, and makes people happier. The only investment is a little courage to break the one-hour habit. And maybe a calendar plugin.