Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Push Back Without Burning Bridges
Transcript
- Lucas: So you're three months into your first management role. Your VP emails you at 6:47 PM on a Tuesday with a new project that needs to ship in two weeks. Your team is already at capacity. What do you do? Luna: I'm guessing the answer isn't reply-all with a list of reasons it can't be done. Lucas: Right. But the instinct for a lot of new managers is to go one of two extremes. Either they say yes and burn out their team, or they say no in a way that sounds defensive or adversarial. Neither works long-term. Luna: There's a middle path. Lucas: There is, and it's a skill you can learn. I've been thinking about this because a listener named Priya wrote in. She's a first-time engineering manager at a midsize SaaS company, about eighty people. Her VP asked her team to build a new reporting dashboard in three weeks. She knew it would take at least five. She didn't want to be seen as difficult, but she also didn't want to set an impossible expectation. Luna: What did she do? Lucas: She used a three-part framework that I've seen work really well. First, she acknowledged the objective. She started the conversation by saying: I understand why this dashboard is important for the Q3 sales kickoff. That shows you're aligned with the business goal, not just protecting your turf. Luna: That's key. If you lead with the problem, you sound like you're not a team player. Lucas: Exactly. Then step two: share the constraint. She said: My team currently has fifteen story points of committed work over the next two sprints. A three-week timeline would require us to drop two existing commitments or cut corners on testing. She gave specifics. Numbers. That's not whining, that's data. Luna: And then step three is the alternative. Lucas: Yes. She offered: If we push the dashboard to week five, we can deliver the full scope with proper QA. Or, if three weeks is firm, we can deliver a stripped-down version with one core metric and add the rest later. Which would you prefer? She gave her VP a choice, not a problem. Luna: It's almost like she's managing the decision, not just the task. Lucas: Exactly. And the VP chose the stripped-down version. The dashboard launched on time, it wasn't perfect, but it was useful. And Priya built credibility because she was proactive and solution-oriented. Luna: There's actually some research behind this. Harvard Business Review published a study in 2023 on managerial assertiveness. They found that managers who used this kind of 'yes, and' framing were seen as more competent and more collaborative than those who just said no flat out. Lucas: The key insight is that most new managers swing between compliance and defiance. Compliance gets you a reputation as a pushover. Defiance gets you labeled as difficult. The sweet spot is collaborative pushback. You're not saying no to the goal, you're saying no to the path. Luna: I saw this play out in a completely different setting. A friend of mine runs a small manufacturing plant. He had a regional director who kept adding rush orders. My friend learned to say: I can prioritize this order, but it means order X will slip by two days. Is that okay? Usually the director would say no, keep order X on track. So he'd ask: What if I split the rush order across two shifts and add overtime? That costs 15 percent more. Can you approve that? Lucas: He's making the trade-offs visible. When you do that, you're not being difficult, you're being transparent. And most bosses appreciate transparency more than a fake yes that blows up later. Luna: The challenge is that new managers often feel they don't have the authority to push back. They think: I just got promoted, I should be grateful, I can't question my boss. Lucas: I've felt that too. But here's the thing: your job as a manager isn't to be a yes-person. It's to deliver results sustainably. If you say yes to everything, you'll eventually fail at everything. Pushing back, done right, is part of your responsibility. Luna: Let's talk about the language. What are some specific phrases that work? Lucas: Sure. One I like: I want to make sure we set this up for success. Can we talk through the timeline? That's non-confrontational. Another: To hit that date, we'd need to deprioritize X. Are you comfortable with that? That puts the decision where it belongs. Luna: And if the boss says yes, deprioritize X, you've done your job. You've documented the trade-off. Lucas: Exactly. The worst case is when you take the hit silently and then miss the deadline. That damages trust more than a respectful pushback ever would. Luna: There's another scenario: what if the request is coming from a peer, not your boss? Like another manager asking your team to help on their project. Lucas: That's actually harder in some ways because you don't have the same hierarchy. But the same principle applies. You say: I'd love to help. Right now my team is focused on X and Y. If we take this on, which of those should we pause? Let me check with my boss to make sure we align. Luna: That brings your boss into the loop without throwing anyone under the bus. Lucas: Right. And it protects your team from being overcommitted by a peer who doesn't see your full plate. Luna: One thing I've noticed: new managers sometimes worry that pushing back will make them seem less capable. But actually, the opposite is true. Leaders who know their limits and communicate them clearly are seen as more self-aware and trustworthy. Lucas: Yeah. And if you're worried about how it will land, you can always soften it with a time-bound ask. Like: Can I have 24 hours to look at the team's capacity and come back with a realistic timeline? That buys you time to think, and it shows you're taking it seriously. Luna: That's a great tactic. Because the pressure often comes from a sense of urgency. But most deadlines can flex by a day or two if you ask. Lucas: Absolutely. And if they really can't flex, at least you've had an honest conversation. Your team will appreciate that you fought for them, and your boss will appreciate that you're realistic. Luna: I think the underlying skill here is actually strategic thinking. You're not just pushing back, you're prioritizing. You're showing that you understand the bigger picture. Lucas: That's a great way to put it. And it's a skill that only gets more valuable as you move up. The higher you go, the more you have to say no to good ideas so you can say yes to great ones. Luna: You know, if today's episode gave you a practical framework you can use, that's exactly the kind of thing that makes this show worth supporting. Lucas: Honestly, if it helped you think through a career move or a tough conversation, that's the link. Buy me a coffee dot com slash fexingo. No pressure, just a way to keep this ad-free and focused on what matters. Luna: And we're back to your playbook. Step one: acknowledge the objective. Step two: share the constraint. Step three: offer an alternative. Lucas: Let's leave listeners with a quick cheat sheet. Next time your boss drops something on your plate, take a breath. Say: I want to make sure we do this well. Let me check the team's capacity and come back with options. Then actually do it. You'll be amazed how often that simple pause changes the outcome. Luna: And remember, the goal isn't to win an argument. It's to get the best result for the business, your team, and your own sanity. Lucas: Exactly. That's the sweet spot. Thanks for listening, and we'll see you next time.