Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How Managers Kill Innovation With Perfect Processes
Transcript
- Lucas: I have been noticing a pattern in the feedback we get from first-time managers, and it is not about delegation or giving tough feedback. It is about the sheer volume of meetings they schedule just to keep people aligned. They treat their calendar like a project management tool, filling every hour with syncs, check-ins, and status updates, assuming that visibility equals control. Luna: Right, because if you are not in the room, you feel like you are losing grip on what is happening. But does that actually create clarity or just noise? Lucas: It creates noise, and worse, it destroys the capacity for actual work. I was reading a case study from a mid-sized software company where the average engineer spent nearly thirty-five percent of their week in meetings. That leaves barely enough time for coding, let alone thinking through complex architectural problems. The manager thought they were being proactive, but they were effectively suffocating the team's output. Luna: So the manager is working harder to manage, while the team works less because they are constantly interrupted. Is there a way to measure when that line is crossed? Lucas: Yes, and the metric is surprisingly simple: look at the ratio of synchronous to asynchronous work. When a manager relies on meetings to convey information that could be written down, they are misallocating high-cost human attention. The key is distinguishing between decisions that require debate and updates that merely require documentation. Luna: That makes sense. But many managers struggle to write clear updates. They default to talking because it feels faster in the moment. Lucas: Exactly. Writing is harder, so they avoid it. But writing scales. A well-structured memo can be read by ten people in twenty minutes total, whereas a twenty-minute meeting involves ten people sitting still for twenty minutes each. The time cost multiplies instantly. The trick is teaching teams that brevity is a feature, not a bug. Luna: So we are really talking about discipline in communication styles rather than just cutting meetings arbitrarily. How do you convince a nervous new manager to trust that silence? Lucas: You give them a framework for what replaces the meeting. If you cancel the daily stand-up, you must implement a daily written update. If you remove the weekly review, you need a shared dashboard that updates automatically. The manager needs to see that removing the meeting does not mean removing visibility; it means shifting visibility to a passive channel. Luna: And that passive channel has to be easy to access. If the information is buried in an email thread no one reads, the manager will just reinstate the meeting out of panic. Lucas: Precisely. The alternative workflow must be better than the meeting. If the dashboard is messy or the doc is outdated, the meeting comes back as a band-aid. We saw this at a marketing agency last year where they tried to go fully async but used a cluttered Slack channel. People missed context, got frustrated, and went back to weekly status calls within three weeks. Luna: So the failure wasn't the concept of async, it was the poor execution of the tooling. What tools actually work for this shift? Lucas: It rarely matters which tool you use, whether it is Notion, Confluence, or even a shared spreadsheet. What matters is the protocol. One successful firm implemented a rule where any request for status had to be answered via a pre-formatted template in their project management tool. No emails, no chats, just structured data entry. It took two days to set up, but saved four hours per person per week thereafter. Luna: That structural constraint forces the behavior. It removes the ambiguity of whether to write or talk. Do managers ever push back against this level of structure? Lucas: Some do, especially those who pride themselves on being flexible. But flexibility without boundaries usually turns into chaos. You want flexibility in how the work gets done, not in how it gets reported. The reporting should be rigid so the thinking can be free. Luna: I like that distinction. Rigid reporting, flexible execution. It sounds like a lot of managers confuse the two. They make the process rigid and the expectations vague. Lucas: That is a common trap. They micromanage the process because they are unsure of the outcome. By tightening the reporting loop, they think they are securing the outcome, but they are actually just increasing friction. The goal is to reduce cognitive load for the team, not add another layer of administrative overhead. Luna: How do you help a manager identify which meetings are actually value-add versus just habit? Most of them don't realize they are part of the problem. Lucas: We suggest a calendar audit. Have them mark every recurring meeting with a color code: green for decision-making, yellow for brainstorming, red for pure status updates. You will usually find that sixty percent of their calendar is red. Those are the candidates for elimination or conversion to async. Luna: That visual is powerful. Seeing the sea of red blocks probably scares a manager into action faster than any lecture on productivity. Lucas: It does. And once they start canceling those red meetings, they need to handle the anxiety. Team members might ask why the meeting is gone. The manager has to confidently direct them to the new protocol. If they hesitate, the old habits return immediately. Luna: So leadership here is about enforcing the new norm, not just announcing it. It requires follow-through. What happens if someone complains that they missed info because the meeting was canceled? Lucas: That is a test of the system. If the information was truly critical, the async channel failed. The manager then fixes the channel, not the calendar. Never revert to a meeting because the tool is bad. Fix the tool. Meetings are expensive; tools are cheap. Luna: Right. You wouldn't buy a broken hammer and blame yourself for not hitting the nail. You replace the hammer. Same logic applies here. Lucas: Exactly. And over time, this builds a culture of respect. When you protect your team's deep work time, they notice. They feel trusted to deliver results without constant supervision. It shifts the dynamic from policing to partnership. Luna: That trust is huge for retention. High performers hate having their time wasted on low-value syncs. Removing those is a quick win for morale. Lucas: Absolutely. And it frees up the manager to do the things that actually require their presence: coaching, strategy, and removing blockers. Those are high-leverage activities. Status updates are low-leverage. Good managers spend their energy on leverage. Luna: So the takeaway is to audit, eliminate the red meetings, and build a better async system. It is a practical, actionable step for anyone feeling overwhelmed by their calendar. Lucas: Yes. Start small. Pick one recurring meeting that everyone admits is useless and kill it. Replace it with a brief doc. See how it feels. You might be surprised by how much clearer things become. Luna: If today helped you rethink your own calendar, consider supporting the show. Buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Lucas: Your support keeps these episodes ad-free and allows us to dig deeper into these operational details. Thank you for helping us stay independent. Luna: It really does make a difference in the quality of research we can bring you. Back to the topic, though, what about remote teams where the lack of physical presence makes managers even more anxious to schedule calls? Lucas: That anxiety is amplified in remote settings. Without hallway conversations, managers feel blind. But the solution is not more Zoom; it is better digital transparency. You need a single source of truth that is always live, so the manager never has to guess the status of a project. Luna: A living document that reflects reality in real-time. It sounds simpler in theory, but building that habit is hard. How do you get a distributed team to commit to keeping it updated? Lucas: You tie it to recognition. Make the person who maintains the most accurate project board the go-to expert for that area. Or integrate it into performance reviews. If the work isn't documented, it didn't happen. That incentives the update behavior naturally. Luna: Incentivizing documentation over talking. It flips the script entirely. I think a lot of managers would find that liberating once they realize they don't need to be the central hub of information. Lucas: They don't. They need to be the filter, not the router. Routing information is a bottleneck. Filtering insight is value. Shift the mindset, and the calendar follows.