Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Say No Without Burning Bridges
Transcript
- Lucas: So it's July 2026, and I've been talking to a friend who got promoted to engineering lead at a mid-sized SaaS company back in March. First management role. Smart, well-liked. And she is drowning — not because she can't do the technical work, but because she cannot stop saying yes. Luna: That is such a classic new manager trap. You want to prove you're helpful, you want to be seen as collaborative, and suddenly you're the bottleneck on four different initiatives. Lucas: Exactly. She told me: 'Lucas, in my first month as manager, I said yes to every cross-functional request that came my way. Data team needed access? Sure. Marketing wanted a quick feature toggle? No problem. My old boss — who is now my peer — asked me to cover a deployment on his team's behalf because someone was out sick. And I said yes to that too.' By week six, her own team's roadmap was slipping, and she was working weekends just to keep up. Luna: And I bet nobody told her that saying yes to everything actually makes you look like a less effective leader, not a more helpful one. Your team can't count on you to protect their focus. Lucas: Right. So today I want to drill into the specific skill of saying no — or more accurately, declining a request — in a way that preserves the relationship and actually clarifies priorities. Because the truth is, most new managers say yes because they're afraid of looking difficult or letting people down. But the cost is real. Luna: Speaking of cost — and this ties in — a lot of listeners have told us that this show has helped them navigate those first awkward months as a manager. And I know Lucas and I both feel strongly about keeping these episodes free of ads and paywalls. So if you've gotten some value out of New Manager Conversations, one simple way to keep it going is to throw a few dollars toward the show. It's at buy me a coffee dot com slash fexingo. Even a couple of bucks a month genuinely makes a difference in covering hosting and production. No pressure, just if it's helped you. Lucas: Yeah, seconded. And it really does help us keep the lights on. Alright — back to the 'no' problem. Let's start with a framework that my friend ended up using after we talked. Luna: What did she land on? Lucas: She realized that the core issue wasn't that she didn't know how to refuse. It was that she had no way to quickly evaluate whether a request was actually a priority. So she created a simple three-question filter. First: Does this directly serve our team's current quarterly objective? Second: Is there someone on my team who could own this instead of me? And third: If the answer to both is no, what's the cost of saying yes — in hours, focus, or team morale? Luna: I love that third question. It forces you to be concrete about the trade-off. Because 'I'm too busy' sounds vague and defensive. But 'Saying yes to this means my team's Q3 feature launch slips by two weeks' — that's a real, discussable cost. Lucas: Exactly. So when marketing came back with a second request in the same quarter, she used that language. She said: 'I'd love to help, but here's the trade-off. My team is committed to delivering the new dashboard by end of August. If I pull anyone onto this, that date moves. Can we talk about which is more important to the company right now?' Luna: And how did marketing respond? Lucas: They actually paused and said, 'Oh, we didn't realize that was the priority. Let's revisit.' Because she framed it as a business trade-off, not a personal refusal. That's the key move: you're not saying no to the person, you're saying no to the prioritization. Luna: And I think this is especially hard when the request comes from someone who used to be your peer — or even your boss. There's a history there. You don't want to seem like you've changed. Lucas: That was her second big challenge. Her old boss — now peer — asked her team to cover a deployment. And her instinct was to say yes because she'd always said yes before. But she realized that if she kept doing that, her team would see her as someone who still reports to him. Luna: So what did she do? Lucas: She said: 'I know in the past I would have just handled this, but I'm trying to be more disciplined about protecting my team's focus. Can we look at the deployment schedule together and find a swap that works for both teams?' She offered a solution, not a wall. Luna: That's smart. She acknowledged the relationship, explained the change in her own behavior without apologizing, and proposed a collaborative alternative. That's a masterclass in saying no to a former boss. Lucas: And here's the thing — he actually respected her more for it. He told her later: 'I was a little taken aback at first, but honestly, I wish I'd had that discipline when I was a new manager.' Luna: So one of the barriers is just the fear that saying no will damage the relationship. But often it does the opposite — it signals that you have clear priorities and that you take your leadership role seriously. Lucas: Exactly. And I think there's another layer here: saying no to your own team. New managers sometimes feel like they have to be available for everything their direct reports ask for. But that's a recipe for micromanagement and burnout. Luna: Right. If a team member comes to you and says 'I need you to review this before I send it,' you can say no — or rather, you can say 'Let's talk about what you need from me, and whether there's a way for you to build confidence in your own judgment.' Lucas: That's coaching versus rescuing. And that's a whole other episode. But for today, the takeaway is that saying no is a skill you build deliberately. Start with a simple filter. Use trade-off language. Offer alternatives. And remember that a clear no is often kinder than a hesitant yes that you later have to walk back. Luna: I want to push back just a little though. Isn't there a risk that new managers overcorrect and start saying no too quickly, or in a way that seems rigid or unhelpful? Lucas: Absolutely. That's the other side of the coin. If you say no reflexively, you'll be seen as a silo-builder. The goal isn't to never say yes — it's to say yes to the right things. My friend had to learn that sometimes the right answer is 'Yes, but on this timeline,' or 'Yes, if we deprioritize something else.' Luna: So it's about framing, not just refusing. A conditional yes can be just as powerful as a no. Lucas: Exactly. And the best way to do that is to come back to your team's priorities. If you've done the work of clarifying what matters most in the current quarter, you have a north star. Every request becomes easier to evaluate against that. Luna: So let's say a listener is in week two of a new management role and they're already feeling overwhelmed by requests. What's the one thing you'd tell them to do tomorrow? Lucas: I'd tell them to block thirty minutes and write down every standing request they've said yes to in the past two weeks. Then categorize each one: essential to my team's goal, nice to have, or something I should never have agreed to. Then, for the ones that don't belong, go back to the requester and have the trade-off conversation. You can always renegotiate a yes. Luna: That's actionable. And I think it takes the pressure off being perfect from day one. Lucas: Exactly. You're not admitting failure by revisiting a commitment. You're showing that you've gotten clearer on what matters. That's leadership. Luna: Alright, so next time someone asks you to do something that doesn't fit, remember: pause, check your filter, and name the trade-off. Lucas: And if you're still unsure, ask yourself: would saying yes to this make me a better leader for my team, or just a busier one? That usually answers the question. Luna: Great note to end on. Thanks, Lucas. Lucas: Thanks, Luna. Talk to everyone next time.