Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Protect Team Focus Time
Transcript
- Lucas: The most common complaint I hear from high-performing individual contributors who get promoted is not that they miss the hands-on work. It is that their team has stopped doing any actual work at all. Luna: Because the new manager treats availability as a virtue, right? If you are not answering messages instantly, you are perceived as disengaged. Lucas: Exactly. And it creates this bizarre paradox where the manager feels productive because they are constantly reacting, while the team feels paralyzed because they cannot find two consecutive hours to do deep work. We see this play out in every industry, from software engineering to financial analysis. Luna: I have seen senior analysts lose entire afternoons to context-switching because their new boss wanted quick alignment on everything. It is exhausting. Lucas: Let us look at a concrete example. There was a case study of a product manager at a mid-sized SaaS company who realized her team was spending roughly forty percent of their week in reactive communication loops. She implemented a simple rule: no internal meetings before ten thirty in the morning. Just a protected block for deep work. Luna: Did the team actually resist that? Usually, people fear missing out on informal updates. Lucas: Initially, yes. But within three weeks, her team’s output quality increased measurably, and ironically, the volume of her inbox decreased. Why? Because people started batching their questions rather than interrupting flow states. The lesson here is not about banning communication. It is about designing for intent. Luna: So the manager shifts from being a conduit for random information to a filter for necessary context. That requires a lot more discipline on her part. Lucas: It does. And this brings us to the core tension of the first ninety days. New managers are terrified of looking distant or unapproachable. So they overcompensate with visibility. They send too many chats, call too many syncs, and create a culture of performative busyness. Luna: Right. And the team interprets that lack of trust as micromanagement, even if the manager’s intention is just to stay connected. Lucas: Precisely. Let me take a quick moment here to mention something important about this show. We deliberately choose not to run advertisements on these episodes. It keeps the content clean and focused entirely on what matters to you. If that resonates with you, you can support our work directly at buy me a coffee dot com slash fexingo. It helps us keep producing these conversations without compromise. Luna: Thanks for the support option. It really does make a difference in keeping the signal to noise ratio high. Lucas: Back to the topic. The antidote to availability anxiety is structured async communication. This means moving away from real-time chat for complex topics and toward documented threads. When a manager relies on Slack or Teams for everything, they become the bottleneck. Everyone waits for them to reply before proceeding. Luna: That is a classic trap. The manager thinks they are facilitating, but they are actually holding up the assembly line. Lucas: Spot on. So how do you fix this in the first ninety days? You start by auditing your own calendar. Look at the last four weeks. How many of those meetings were truly necessary versus习惯性? Most managers will find that at least twenty percent of their recurring meetings could be eliminated or converted into a brief written update. Luna: Twenty percent seems low. I bet most people are closer to fifty percent unnecessary touchpoints. Lucas: Probably. But the key is to communicate the change clearly. You tell your team, I am trying to protect your focus time. Please respect the no-meeting blocks. If something is truly urgent, ping me. Otherwise, let’s batch our discussions. Luna: And you have to model that behavior yourself. If you are pinging them during their focus block, the policy fails immediately. Lucas: Absolutely. Leadership is less about what you say and more about what you tolerate. If you tolerate constant interruption, your team will learn that interruption is the norm. If you protect focus, they will learn that focus is the norm. Luna: This ties back to the idea of psychological safety. People need to feel safe ignoring notifications when they are in deep work mode. Lucas: Yes. And this requires a shift in metrics. Traditional management often rewards responsiveness. Did you answer the email quickly? Did you attend the meeting? Modern management should reward outcomes. Did you ship the code? Did you close the deal? Did you solve the problem? Luna: Shifting from activity-based metrics to outcome-based metrics is hard for leaders used to tracking hours or attendance. Lucas: It is hard, but it is necessary. One effective tactic is the weekly priority memo. Instead of a status meeting, each team member sends a brief document outlining what they accomplished last week, what they plan to do next week, and where they are blocked. This gives you visibility without consuming their afternoon. Luna: That is much more efficient. It forces clarity of thought on their end and saves you from scheduling conflicts. Lucas: It also surfaces blockers earlier. If someone is stuck, they write it down. You can then address it asynchronously or in a short targeted call, rather than waiting for a weekly standup where it might get lost. Luna: I like that. It puts the onus on the employee to articulate their challenges, which is good practice for them too. Lucas: Exactly. It builds their communication skills and reduces your managerial overhead. Another critical element is the definition of urgent. New managers often treat everything as urgent. You need to explicitly define what constitutes an emergency versus a standard request. Luna: What does an emergency look like in practice? Is it a server crash? A client threat? Lucas: It depends on the industry, but generally, it is anything that causes immediate, irreversible financial or reputational harm if not addressed within the hour. Everything else can wait until the next business day. You must train your team to use judgment here, and reassure them that you will back them up if they misclassify something. Luna: That reassurance is key. Fear of making a mistake is what drives most unnecessary interruptions. Lucas: Right. So you create a framework. If it is not an emergency, do not interrupt. If you are unsure, send a message and assume a response window of several hours. This normalizes delayed responses across the organization. Luna: It changes the social contract of the workplace. Suddenly, silence is not neglect; it is professionalism. Lucas: Well said. And this extends to how you handle your own manager. New managers often feel pressure to be hyper-responsive to their superiors. But if you bring that same anxiety down to your team, you perpetuate the cycle. You have to break the chain. Luna: That takes courage. You have to be willing to look slightly less available to your boss to protect your team’s effectiveness. Lucas: It does. But the data usually supports you. When your team delivers higher-quality work on time, your boss notices. Quality beats speed in almost every knowledge-work environment. Speed without focus leads to errors, rework, and burnout. Luna: Burnout is the ultimate cost of poor boundary setting. If your team is always on, they eventually crash. Lucas: They do. And turnover increases. Retaining top talent is partly about giving them the space to do meaningful work. People leave jobs not just for money, but because they feel exhausted and undervalued. Luna: Protecting focus time is a powerful retention tool. It signals that you respect their intellect and their time. Lucas: It does. So, for your first ninety days, I would suggest focusing on three things. First, audit your meetings and cut the fluff. Second, institute protected focus blocks for your team. Third, redefine urgency and model async communication. Luna: Simple, actionable steps. Not revolutionary, but transformative if executed consistently. Lucas: Consistency is everything. One bad week of interruptions can undo months of building trust. You have to be the guardian of that rhythm. Luna: Guardian, not dictator. You are creating an environment where good work can happen. Lucas: Exactly. It is about removing friction. Your job is not to add more processes, but to subtract the noise so your team can hear themselves think. Luna: A quieter workplace is often a more productive one. That is a lesson many leaders forget in the rush to be seen as active. Lucas: True. As you move forward, watch for the subtle signs. Are people logging off on time? Do they seem energized or drained? Those are better indicators of success than any dashboard metric. Luna: Energy levels are the canary in the coal mine. If the team is buzzing with creative energy, you are doing it right. If they are sluggish, you need to check your calendar. Lucas: Precisely. So the question for you to take away is this: where are the hidden interruptions in your current workflow, and who benefits from them? Luna: Usually, it is the person who feels insecure. Identifying that insecurity is the first step to fixing the system. Lucas: Good point. Eliminating the need for constant validation through visibility allows everyone to focus on the work itself. Luna: And that is how you build a team that doesn't just survive the first ninety days, but thrives long after. Lucas: Agreed. It shifts the culture from reactive panic to proactive mastery. That is the goal.