Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage an Employee Who Keeps Asking for More Resources
Transcript
- Lucas: You've been a manager for about four months. One of your senior engineers, Priya, is your best performer. But every week, she comes to your one-on-one with another request: we need a junior developer, we need a data analyst, we need an additional cloud budget, we need a dedicated QA person. And she's not wrong — the project is complex. But your budget is frozen until Q3. So what do you actually say? Luna: Right, because if you say 'no' flat out, you risk demotivating your strongest player. But if you say 'yes' or even 'maybe,' you're setting false expectations. Lucas: Exactly. And this is the dilemma of Resource Request Management — it's one of the most common blind spots for first-time managers. You're trained to advocate for your team. But there's a difference between advocating and rubber-stamping. Today I want to walk through a specific case and three scripts you can use. Luna: Before we go deep — something quick. If this show has helped you navigate a sticky manager moment, a handful of listeners chip in monthly at buy me a coffee dot com slash fexingo. It's what keeps this ad-free and focused on real scenarios like this one. Lucas: Yeah, genuinely appreciate everyone who does that. It lets us spend time on these detailed cases instead of chasing sponsors. So — back to Priya. The case I'm thinking of comes from a mid-size SaaS company, about 300 employees. Their VP of Engineering shared this with me off the record. Luna: What was the specific ask? Lucas: Priya wanted to ship a new feature — a real-time dashboard for enterprise clients. She estimated it would take six months with her current team of three. She said if she got two more engineers and a dedicated QA, she could do it in three months. That's a 40 percent headcount increase for one feature. Luna: Forty percent — that's a huge ask. And the manager, let's call him Mark, had no budget. So what did he do? Lucas: Mark did something smart. He didn't say no. He said, 'Let me understand what you'd drop to make this work.' He asked Priya to rank every project on her plate — not just the dashboard — and identify which ones she'd pause or kill to free up her existing team's time. Luna: That's a great reframe. Instead of 'can I have more,' it becomes 'what am I trading off?' Lucas: Exactly. And that's Script Number One: Validate the ask, then ask for trade-offs. You say, 'I hear you — this feature is important. Help me understand: if we don't get additional headcount, which of your current commitments would you deprioritize to make room?' That forces the employee to think like a manager. Luna: And it also reveals if they're willing to make hard choices. If they say 'I can't drop anything,' then the request is really about capacity, not priority. Lucas: Right. In Priya's case, she initially said everything was critical. But Mark pushed back gently — 'if everything is critical, nothing is.' He asked her to bring a ranked list to their next one-on-one. She came back with two lower-priority maintenance tasks she could defer. Luna: That's progress. But the dashboard still needed more hands. What was Script Number Two? Lucas: Script Number Two is about reframing the resource ask as a time to market trade-off. Mark said, 'If we can't add headcount, what's the minimum viable version of the dashboard you could ship in four months?' That changed the conversation from 'what I need' to 'what I can do with what we have.' Priya realized she could ship a simplified version with just two of the five planned features — and iterate later. Luna: So the MVP approach. That's a classic product management technique, but it's surprising how often engineers don't think that way when they're in execution mode. Lucas: Exactly. And Mark didn't just accept the MVP — he made Priya own the scope decision. He said, 'You're the expert on what's essential. I trust you to define the cut line.' That gave her autonomy and reduced her frustration. Luna: What about the third script? Lucas: Script Number Three is for when the resource request is actually valid and you need to escalate — but you want to do it in a way that doesn't make the employee feel like you're just passing the buck. Mark eventually agreed that a real-time dashboard needed more QA. So he said, 'I can't approve a new hire, but I can negotiate a shared QA resource from another team for two sprints. Would that help?' That's a creative middle ground. Luna: So he found a temporary solution instead of a permanent one. And Priya felt heard. Lucas: Exactly. And when that temporary resource didn't fully solve the problem, Mark escalated to his VP — but he did it with data. He said, 'Priya's team is shipping 20 percent slower on the dashboard than originally planned because we're sharing QA. Here's the impact on the enterprise client launch date. Do you want to reprioritize or approve a contract QA person?' He framed it as a business decision, not a complaint. Luna: That's key — you're not just asking for more; you're showing the cost of not getting more. Lucas: Exactly. And the VP approved a three-month contract QA. So Priya got what she needed, but through a different path. And Mark built trust with his leadership by being data-driven, not emotional. Luna: There's a broader point here. A 2023 study from the University of Zurich looked at 150 software teams and found that teams with moderate resource constraints actually outperformed teams with abundant resources on innovation metrics — because scarcity forces prioritization. Lucas: That's fascinating. So the constraint isn't always the enemy. The enemy is unclear priorities. Mark's approach basically forced Priya to clarify priorities — which made her a better engineer and eventually a better manager herself. Luna: What about the manager who feels guilty saying no? I think a lot of first-time managers worry they're being unsupportive. Lucas: That's a real fear. But there's a difference between being unsupportive and being a responsible steward of resources. I tell new managers: Your job isn't to get your team everything they want. Your job is to help them do their best work with what they have — and to fight for them when the data supports it. Luna: So it's about being a translator between the team and leadership. Lucas: Exactly. And the best way to avoid resentment is to be transparent. Mark told Priya, 'Here's the budget reality. Here's what I can control. Here's what I can't. Let's work together on what's possible.' That honesty builds more trust than a vague 'I'll see what I can do' that goes nowhere. Luna: What if the employee still pushes back after you've used all three scripts? Lucas: That's when you need to have a career conversation. Say, 'I understand this is frustrating. If you feel strongly that this project can't succeed without more resources, then we need to talk about whether this is the right role for you.' That sounds harsh, but it's actually respectful — it acknowledges their standards might not align with the company's reality. Luna: So it's a last resort, but it's honest. Lucas: Exactly. And in practice, most employees won't push that far if they feel you've genuinely listened and explored creative options. The problem is usually not the 'no' — it's the feeling of being dismissed. Luna: So recap: Script one — ask for trade-offs. Script two — reframe to MVP. Script three — find creative middle grounds, then escalate with data. Lucas: That's the framework. And I'll leave you with this: Every resource request is an opportunity to teach your team how to think strategically. If you just say yes or no, you lose that teaching moment. If you walk through the trade-offs together, you build better decision-makers. Luna: And that's the real job of a manager, isn't it? Not just allocating resources, but growing people who can allocate them wisely themselves. Lucas: Exactly. Next episode we'll talk about managing an employee who always says 'that's not my job' — which is a related but different beast. Thanks for listening.