Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Master The Art Of Saying No
Transcript
- Lucas: The hardest part of your first promotion isn't learning the new tools or even the new metrics. It's realizing that everyone now looks to you for answers, and you have exactly zero bandwidth to give them all. I call it the inbox vacuum. You get promoted, suddenly every Slack message and email lands on your desk because people assume you're the bottleneck, and you spend three hours a day just triaging other people's problems. Luna: That sounds exhausting. Did you find yourself saying yes to everything at first? Lucas: Guilty as charged. In my early days as a team lead, I thought being accessible meant being available. I answered emails within minutes, jumped on calls for minor decisions, and tried to personally review every deliverable. By month two, I was drowning, and my team was stagnating because they were waiting for my approval on things they could easily handle themselves. Luna: So what changed? How did you break that cycle without looking like you were checking out? Lucas: I had to implement a strict decision matrix. I categorized tasks into three buckets: those only I could decide, those where my input was valuable but not required, and those entirely within my team's scope. For the third bucket, I stopped responding unless there was a crisis. It felt unnatural at first, like I was ignoring work, but within weeks, my team started making faster decisions and came to me with more strategic questions instead of operational ones. Luna: Did anyone push back? Some team members might feel neglected if you stop replying instantly. Lucas: A few did initially. One senior engineer kept tagging me in threads for trivial code reviews. I had to sit him down and explain that while his work was excellent, I wasn't adding value by approving it myself. Instead, I empowered him to approve junior devs' code, which actually boosted his confidence and freed up my calendar. It was about shifting from gatekeeper to enabler. Luna: That makes sense. Shifting the burden of ownership upward seems healthier than hoarding it. Lucas: Exactly. And here is the thing about October 2026 and the current market climate. Teams are leaner. Margins are tighter. If you are a new manager trying to do everything yourself, you become the single point of failure. That is a risk no executive wants to take. So learning to say no to operational noise is actually a fiduciary responsibility, not just a personal boundary. Luna: Right. And saying no doesn't mean doing nothing. It means redirecting energy. Lucas: Precisely. I started using a simple rule called the 'two-minute delay'. If an email didn't require an immediate response, I waited two hours before replying. Often, the issue resolved itself, or someone else answered it. If it didn't, I had more time to craft a thoughtful response rather than a reflexive one. This small change alone gave me back five hours a week. Luna: Five hours is huge. But what about the anxiety of missing something important during that delay? Lucas: Valid concern. To mitigate it, I set up automated alerts for keywords related to critical incidents or client escalations. Everything else went into the batch processing pile. This way, I wasn't ignoring urgent matters, I was just deprioritizing the non-urgent ones. It taught my team to label their requests clearly, which improved communication across the board. Luna: So clear labeling becomes a new norm. That's a nice side effect. Lucas: It is. And it forces people to think about why they are reaching out. Are they asking for permission, for information, or for support? When they have to categorize their request, they often realize they don't need my input at all. It empowers them to solve the problem independently. Luna: I like that. It feels like teaching your team to fish instead of giving them the fish. Lucas: Metaphorically speaking, yes. But there is a practical tool that helps here. I use a shared dashboard where my team tracks ongoing projects and blockers. If they are stuck, they update the dashboard. If I see a blocker that requires my intervention, I step in. If not, I leave it. This transparency reduces the need for status updates via email, which is another huge time sink. Luna: Does that dashboard create pressure on the team to always look busy? Lucas: Initially, some worried about visibility. I reassured them that the dashboard was for alignment, not surveillance. We agreed on a cadence for updates—daily for active projects, weekly for maintenance. This reduced micromanagement fears and kept the information fresh without requiring constant check-ins. Luna: Okay, so we have boundaries, decision matrices, and dashboards. What happens when upper management comes knocking with urgent requests? Lucas: That is the real test. Upper management often doesn't see the daily grind. They see results and assume capacity is infinite. My strategy is to show, not tell. When a VP asks for something extra, I pull up our current workload map. I show them what is already in motion and ask, 'If I take this on, what should go off the plate?' This shifts the conversation from refusal to prioritization. Luna: Brilliant. You make them choose the trade-off, not you. Lucas: Exactly. It preserves your relationship while protecting your team's focus. Nobody likes being told no, but everyone understands resource constraints. By framing it as a resource allocation issue, you speak the language of leadership, not just complaint. Luna: I can see how that builds credibility. You aren't just complaining; you are managing. Lucas: Yes. And it teaches your stakeholders how to work with you effectively. Over time, they learn to bundle requests, to respect your calendar, and to come prepared with clear objectives. It changes the culture of interaction, not just your personal workflow. Luna: What about the emotional toll? Sometimes saying no feels like letting people down. Lucas: That guilt is real. But remember, your primary obligation is to the team's success, not to individual convenience. If you say yes to everything, you end up saying no to quality, depth, and innovation. You are trading long-term value for short-term compliance. Is that really what you want for your career? Luna: Definitely not. Short-term wins rarely build lasting legacies. Lucas: Correct. So, embrace the discomfort. Your team will respect you more for protecting their time than for indulging every whim. And honestly, most people prefer a manager who sets clear expectations over one who is perpetually overwhelmed and reactive. Luna: That's a strong reframe. Clarity is kindness. Lucas: It is. And it scales. As your team grows, these systems become essential. Without them, chaos ensues. With them, you have a machine that runs efficiently even when you are not in the room. Luna: I love that vision. A self-sustaining team. Lucas: That is the goal. But let's pause for a moment. If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo — that's F. E. X. I. N. G. O. Luna: Yeah, thanks for keeping the content sharp and free. I appreciate it. Lucas: Back to the topic. Let's talk about feedback loops. Once you have established these boundaries, how do you ensure your team knows they are on the right track? Luna: Do you rely on formal reviews or informal check-ins? Lucas: A mix. Formal quarterly reviews are necessary for HR and compensation, but they are too infrequent for course correction. I hold bi-weekly one-on-ones focused solely on professional development and roadblocks. These are sacred. No operational updates, no status reports. Just growth and guidance. Luna: That sounds intense to prepare for. Do you have an agenda template? Lucas: I do. Three questions: What went well? What got in the way? What do you need from me? Simple, effective, and it puts the ball in their court. It also prevents me from dominating the conversation with my own concerns. Luna: Putting the ball in their court encourages ownership. Lucas: Exactly. And it creates a safe space for honest dialogue. If they know you are listening for their needs, they are more likely to share challenges early. Early detection of issues saves countless hours of firefighting later. Luna: Proactive rather than reactive. Again, a shift in mindset. Lucas: Mindset is everything. Tools help, but the underlying belief that your role is to enable others, not control them, drives the behavior. When you internalize that, saying no to noise becomes easy because you know what truly matters. Luna: So it starts with clarity of purpose. Lucas: Always. And as you navigate your first ninety days, remember that every 'no' is a 'yes' to something else. Choose wisely. Luna: I wonder if there are cases where saying no is actually wrong. Lucas: Rarely. Usually, it's about timing or delivery. But if the answer is genuinely no, owning it firmly is better than a hesitant maybe. Clarity builds trust faster than ambiguity ever will. Luna: So, final thought. How do you measure success in this new role? Lucas: When your team succeeds without you, you win. If you are indispensable, you are not leading; you are holding. True leadership is creating a environment where others can shine. Luna: That's a powerful standard to aim for. Lucas: It is. And it keeps you humble. Because the credit belongs to them, not you. But the responsibility for enabling them is yours. Luna: I'll keep that in mind as I navigate my next project. Lucas: Good luck. And remember, the inbox vacuum is a choice. You can fill it with noise, or you can leave it empty for clarity. Luna: Empty for clarity. I like that. Lucas: See you next time.