Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Say No to Their Teams
Transcript
- Lucas: So we get a lot of questions from new managers about how to handle requests from their team. But there’s one that’s trickier than it seems: how do you say no to a direct report without damaging the relationship? Luna: Yeah, it’s one of those things that sounds simple but feels awful in practice. I’ve seen managers say yes just to avoid the discomfort. Lucas: Exactly. And the problem is, saying yes too often can actually hurt your team more than a well-placed no. I want to use a specific example from a mid-size SaaS company I’ve been following. A team lead there named Priya had a senior engineer come to her and ask for access to a production database to run some ad hoc queries. Luna: And I’m guessing she didn’t just say yes. Lucas: Right. She knew that giving blanket access would bypass their security protocols and create a precedent. But she also didn’t want to seem like she didn’t trust him. So she paused and used a four-step framework that I think is really useful for any new manager. Luna: Okay, I’m listening. What’s step one? Lucas: Step one: don’t answer immediately. Priya said, ‘Let me think about that and get back to you by end of day.’ That buys you time to evaluate the request without pressure. Luna: That seems obvious, but in the moment it’s easy to feel rushed. Especially if the person is senior or you’re new. Lucas: Exactly. Step two: clarify the underlying need. When she came back to him, she asked, ‘What specific data are you trying to get, and what decision will it inform?’ It turned out he wanted to analyze customer churn patterns to decide which features to prioritize. Luna: So the real need was a churn analysis, not database access per se. Lucas: Right. Step three: explain your no clearly and tie it to a principle. She said, ‘I can’t give you direct production access because we have a policy to protect customer data and prevent accidental changes. But I can help you find another way.’ That last part is critical. Luna: Because you’re not just blocking; you’re redirecting. Lucas: Exactly. Step four: offer a concrete alternative. She connected him with the data engineer who could run a scheduled report with the exact fields he needed. The engineer got his analysis done within a week without the security risk. Luna: So the no wasn’t really a no to his goal. It was a no to the method. That’s a big distinction. Lucas: And that’s the frame I want new managers to adopt. Saying no isn’t about closing a door; it’s about opening a better one. If you just say no without an alternative, you look like a blocker. If you explain the why and offer a path, you look like a leader. Luna: I think a lot of new managers also worry about losing their team’s trust. Like, if I say no too often, will they stop coming to me? Lucas: That’s a real fear. But research from Google’s Project Aristotle shows that psychological safety is built on consistency and fairness, not on saying yes. If you say no to everyone equally and explain your reasoning, people actually trust you more because they know the boundaries are clear. Luna: So it’s like setting a fence. People feel safe inside a well-marked perimeter. Lucas: Exactly. And here’s another angle: sometimes the most dangerous yes is the one you say to a senior leader overruling your team’s capacity. Say your VP asks your team to take on a new project, and you know your engineers are already overloaded. Saying yes to the VP means saying no to your team’s wellbeing. Luna: That’s a really hard position. How do you handle that? Lucas: You use the same framework. Pause. Clarify the VP’s priority. Explain the trade-off: ‘We can do this, but it means delaying the current feature sprint by two weeks. Are you okay with that?’ Often the senior leader didn’t realize the impact. You’re not saying no; you’re showing the cost. Luna: And if they still push, then you escalate with a clear rationale. Lucas: Right. And that protects your team from feeling like you’re just a mouthpiece for higher-ups. Luna: You know, this reminds me of something I read about how Pixar’s leaders handle feedback. They have a concept called ‘plussing’ — you always build on an idea before criticizing it. Lucas: That’s a great parallel. Saying no with an alternative is like plussing in reverse: you take the request and improve the approach. Luna: Exactly. Let’s give listeners a script they can use tomorrow. Lucas: Sure. When a direct report asks for something you can’t approve, say: ‘I appreciate you bringing this to me. I can’t say yes to because. But I can help you achieve your goal by. Let’s set up time to work through that.’ Luna: That’s clean. And it acknowledges their initiative, which is important. Lucas: Absolutely. And if you’re the one receiving the no, it also helps to recognize when a manager is doing it well. It builds a culture where no is just part of healthy prioritization. Luna: I want to circle back to the guilt piece. A lot of new managers feel guilty saying no, especially if they’re managing former peers. Lucas: That’s a huge issue. You used to be equals, and now you’re setting boundaries. But here’s the thing: your former peer doesn’t need you to be their friend; they need you to be their manager. A clear no that helps them focus is more valuable than a fuzzy yes that leads to overwork and resentment. Luna: And if we’ve helped you think through a moment like that — maybe you’ve used a script we gave, or you’ve felt more confident setting a boundary — then honestly, if today was worth a coffee to you, that’s the link. Buy me a coffee dot com slash fexingo. Lucas: Yeah, that’s a small way to keep this ad-free and focused on real tools. We appreciate anyone who finds value and wants to chip in. Luna: And we’re back to the topic because I think this connects: the best managers I’ve seen don’t just say no to requests; they also say no to themselves. They resist the urge to micromanage or take over a task. Lucas: That’s a great point. Saying no to yourself is maybe the hardest part. When you see a team member struggling, your instinct is to jump in and fix it. But that’s a yes to control and a no to their growth. Luna: So the no becomes a developmental moment. ‘I’m not going to solve this for you, but I’ll help you think through it.’ Lucas: Exactly. And that’s the kind of no that builds a stronger team over time. It’s not a rejection; it’s an investment. Luna: Alright, let’s wrap with one concrete takeaway. Lucas: Sure. Next time you’re about to say yes to something you shouldn’t, stop. Ask yourself: what’s the real need, and can I redirect this to a better outcome? If you can’t, then say no with a clear principle. Your team will thank you for it. Luna: And if you’re a listener who’s managed to say no well recently, we’d love to hear about it. Until next time, take care.