Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Ask Their Boss for Resources
Transcript
- Luna: So Lucas, I want to talk about something that I think keeps a lot of new managers up at night. Lucas: What's that? Luna: Asking their boss for more resources. Headcount, budget, tools, time. It feels like you're admitting you can't handle the job. Lucas: Yeah, it's a huge mental hurdle. And it's funny because as an individual contributor, nobody expects you to ask for resources on behalf of a team. But the moment you become a manager, that's literally part of your job description. You're the one who has to go upstairs and say, 'We need X to deliver Y.' And if you've never done it, it feels like begging. Luna: Right. And most new managers either don't ask at all and just try to make do, or they ask in a way that comes across as whining. 'We're so overloaded, we need help.' That's not a proposal, that's a complaint. Lucas: Exactly. So let's talk about a specific case. I was talking to a friend of mine—let's call her Priya. She's about six months into her first management role at a mid-size SaaS company. She's a product manager, and she has three developers on her team. Her boss is the VP of Product. Priya's team was tasked with building a new feature that's critical for a Q4 customer launch. But about a month in, she realized the timeline was impossible with just three devs. She needed at least one more developer, ideally two, to hit the deadline without burning everyone out. Luna: And she was terrified to ask. Lucas: Terrified. She told me she felt like she was failing. She thought her boss would say, 'You can't manage a simple project? I hired you to figure this out.' So she sat on it for two weeks, tried to squeeze more hours out of her team, and morale started dropping. Luna: That's the classic trap. You try to solve it yourself because you think asking is a sign of weakness. But actually, not asking is the real failure. Because you're putting the whole project at risk. Lucas: Totally. So I walked her through a simple three-part framework. First, anchor the request in business impact—not in team stress. Second, give a concrete ask with options. Third, anticipate objections and have a fallback. Luna: Let's break that down. What does 'anchor in business impact' look like in Priya's case? Lucas: Instead of walking into her boss's office and saying, 'We're overwhelmed and we need another dev,' she started the conversation with the customer launch. She said, 'I've been reviewing the Q4 timeline for the new feature, and I want to make sure we hit the launch date with high quality. With our current capacity, I see two scenarios: we either delay the launch by six weeks, or we bring on an additional developer to keep the original date. I recommend the second option, and here's why.' Now she's framed it as a business decision, not a personal plea. Luna: That's smart. She's showing she's thinking about the company's revenue, not just her team's workload. Lucas: Exactly. And the second part—concrete ask with options—she didn't just say 'I need a dev.' She said, 'If we can get one senior backend engineer for the next eight weeks, I'm confident we hit the launch date. If we can get two, we can also add the performance optimization work that's been deprioritized. What's possible from your side?' She gave her boss a spectrum. That makes it easier for the boss to say yes to something. Luna: And the third part—anticipating objections. What did she think her boss would say? Lucas: She knew the VP would probably push back on budget or headcount freeze. So she had a fallback ready. She said, 'If we can't get a full-time person, could we bring in a contractor for the eight weeks? Or could we borrow a developer from another team that's in a slower period?' She had three levels of ask: ideal, good, and acceptable. That way, even if the boss says no to the first, the conversation doesn't end. Luna: So what happened? Did she get the resource? Lucas: She got one contractor for six weeks. Not the full eight, not a full-time hire, but it was enough. And her boss told her later, 'I appreciated that you came to me with a clear analysis, not a complaint. That's what I need from my managers.' So she actually strengthened her reputation by asking. Luna: And I think that's the key insight. Asking for resources, when done right, signals that you're strategic and that you care about the outcome. It's not a sign of weakness. Lucas: Right. And you know, this ties into something we talk about a lot on this show—the idea that being a good manager means serving your team. Part of that service is going to bat for them. If you don't ask for what they need, you're not doing your job. And if you've been finding value in these kinds of conversations, I want to mention something quickly. Luna: Go ahead. Lucas: This show is ad-free and listener-supported. If you've gotten something useful from an episode like this one, you can support us at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. It helps us keep making content that's focused on real, practical advice for new managers. Luna: Yeah, and honestly, even a small contribution makes a difference. It's how we know we're hitting the mark. Lucas: Alright, back to the resource ask. So once you have the framework, the next challenge is actually delivering the message. Let's talk about language. What words trip up new managers? Luna: I think a big one is starting with 'I think we need' or 'I'm worried that.' That sounds tentative. Instead, lead with the data. 'Based on the project plan, we need X to hit the deadline.' It's factual. Lucas: Yeah, and avoid the word 'overwhelmed.' That's an emotion word. It doesn't land in a business conversation. Instead say 'capacity constrained.' Or 'the current team size creates risk for the timeline.' Same reality, but framed as a business risk. Luna: What about when the boss says no? Because that happens a lot. Lucas: It does. And how you handle a 'no' is almost as important as how you ask. First, don't get defensive. Say 'I understand, that makes sense given the constraints.' Then pivot to your fallback. 'Could we explore a contractor for a shorter period?' If even that is a no, then ask for guidance. 'Given that we can't add capacity, what would you suggest we deprioritize to keep the launch date?' That puts the ball back in the boss's court and forces them to make a trade-off decision. Luna: That's powerful because it shows you're still trying to solve the problem, you're just working within new constraints. Lucas: Exactly. And sometimes the boss will say, 'Let me think about it and get back to you.' That's not a no. But you need a follow-up plan. Before you leave the room, say, 'When would be a good time to check in on this? I want to make sure we don't lose momentum.' Set a specific date. Luna: I want to push back on something though. There's a lot of advice out there that says 'just be confident.' But confidence isn't the issue for most new managers. It's that they don't know the right structure. They don't know how to build a business case. So they avoid the conversation entirely. Lucas: That's a really good point. Confidence is a byproduct of preparation. If you've done the work—mapped out the scenarios, quantified the impact, prepared your fallbacks—you'll naturally feel more confident. The problem isn't that new managers lack courage, it's that they lack a template. So let's give our listeners one. Luna: Yes, please. Lucas: Here's a simple script you can adapt. First sentence: 'I want to discuss the timeline on Project X. I've reviewed the plan and current capacity, and I see a risk that we won't hit the deadline with the current team size.' Second sentence: 'To mitigate that risk, I recommend adding one developer for the next eight weeks. This will allow us to deliver on time and maintain quality.' Third sentence: 'If that's not possible, I have a couple of alternatives we can discuss. Can we talk through what might work?' That's it. Three sentences. Luna: And if the boss asks why you didn't come sooner, what do you say? Lucas: Good question. You can say, 'I wanted to first understand the scope fully and see if we could adjust internally. After analyzing the workload, it became clear that we need additional support to meet the commitment.' That shows you were proactive, not reactive. Luna: I think one more thing that helps is to remember that your boss also has a boss. They have their own constraints. If you can frame your ask in a way that helps them make a case upward, you're more likely to get a yes. Lucas: Exactly. So instead of saying 'I need a developer,' say 'Adding a developer will ensure we hit the Q4 revenue target that's in your quarterly goals.' You're connecting your ask to their metrics. That's a huge lever. Luna: Let's talk about the non-financial resources too. Sometimes what you need isn't headcount, it's time. Like asking for a deadline extension. Lucas: Same framework applies. Anchor in business impact. 'If we extend the deadline by two weeks, we can deliver a more robust feature that will reduce support tickets by an estimated twenty percent.' Concrete ask with options. 'I'd recommend a two-week extension, but if that's not possible, we could deliver a stripped-down version by the original date and add the rest later.' And anticipate objections. 'I know this impacts the marketing campaign, but I've spoken with the marketing lead and they said a two-week delay is manageable if we give them a firm date.' Luna: So it's really about preparation and empathy. Understanding what your boss needs and showing them how giving you what you need helps them get what they need. Lucas: Exactly. And I think that's the meta-skill here. As a new manager, you're learning to think in terms of trade-offs and priorities. That's what leadership is. You're not just executing tasks anymore, you're making decisions about where to invest limited resources. And that includes the resource of your boss's attention and budget. Luna: I want to circle back to Priya's story. She got the contractor, the launch happened on time, and her team didn't burn out. But she told me the biggest win was that she now has a template for future asks. She's no longer afraid to have that conversation. Lucas: That's the goal. Because the first time is the hardest. After that, you realize it's just a business conversation. And your boss actually respects you more for it. So if you're a new manager listening, and you've been putting off that resource conversation, take this as a nudge. Prepare your three sentences, pick a time, and have the talk. Your team will thank you. Luna: And if you've already had that conversation and it didn't go well, that's okay. You can always circle back with a more structured approach. It's not about getting it perfect the first time, it's about learning to advocate effectively. Lucas: Yeah, and we'd love to hear how it goes. You can always reach out to us. Until next time, keep leading.