Latest / New Manager Conversations with Fexingo: First 90 Days, Managing Former Peers, and Leadership Basics / How New Managers Can Protect Their Team From Scope Creep
Transcript
- Lucas: So here's a situation that I think almost every new manager encounters within the first few months, and it rarely shows up in the official training. Your team is humming along on a project, you've got a clear roadmap, everyone knows their tasks. Then an email comes in from a director in sales: 'Hey, could your team just add this one small report by Friday? It's just a pivot table.' And then a product manager pings you about 'a quick data pull.' And before you know it, your team is working nights to deliver things they never agreed to. Luna: Right — the classic death by a thousand small requests. And as a new manager, you feel like you can't say no because you're still building relationships. You want to be seen as helpful and collaborative. Lucas: Exactly. And letting that accumulate, it's not just about burnout. It erodes your team's trust in you. They start thinking, 'My manager doesn't protect us.' And once you lose that, it's really hard to get back. So today I want to talk about a specific tool I've seen work well: something I call the 'three-question test' for every incoming request. Luna: Okay, I want to hear this. But first — you mentioned a real company example. Do you have one that illustrates the damage? Lucas: Yeah. There's a mid-size SaaS company called BuildRight. They're in the construction project management space, about three hundred employees. A new engineering manager named Priya came in to lead a team of five. She was super eager to prove herself. Within her first month, she said yes to four cross-functional requests that each seemed small. Individually, they were maybe a day or two of work. But they all hit the same two senior engineers. By week six, those engineers were working weekends. One of them — a top performer — started looking for other jobs. Luna: That's the nightmare scenario. You lose your best people because you didn't protect their time. And it's not malice — it's just inexperience. Lucas: Right. So Priya eventually realized she needed a system. She created what she called a 'scope check-in' — a fifteen minute slot every Monday where the team would list every request that came in the previous week, who asked for it, and how much time it actually took. She found that forty percent of their sprint capacity was being consumed by unplanned work. That's huge. Luna: Forty percent — that's almost half the team's energy gone to things that weren't on the roadmap. And I bet a lot of those requests, if someone had pushed back, they would have just disappeared. Lucas: That's the thing — many requests are urgent to the requester but not actually critical to the business. So Priya started using the three-question test. Before she or her team said yes to anything, they'd ask: one, does this align with our current quarterly objective? Two, does it need to be done this week or can it wait until next sprint? And three, is the requester willing to trade something off our roadmap in exchange? Luna: That third question is the killer. Because when you say, 'Sure, I can get this done by Friday, but that means the new user onboarding feature slips by a week,' suddenly the urgency changes. They often say, 'Oh, it's not that critical,' or they escalate to their boss. Lucas: And that's healthy escalation. It forces a real priority conversation. So the three-question test gives the new manager a framework that doesn't feel like they're being difficult. They're just asking clarifying questions. It's hard for anyone to argue with 'Can you help me understand how this ties to our Q2 goal?' Luna: I want to push back a little though. This works well in a company with clear quarterly objectives. But what if you're in a startup where priorities shift weekly? Or a smaller team where cross-functional collaboration is the whole point? Isn't there a risk of building a silo? Lucas: Fair point. And I think the answer is that the framework needs to match the culture. In a fast-moving startup, the three-question test might be too rigid. But the principle still applies: you need a visible way to track and trade off requests. One startup I know uses a shared Trello board called 'The Ask Wall'. Every request goes there, and the team votes on which ones to tackle. It's transparent, and it makes the trade-offs visible to everyone. Luna: The Ask Wall — I like that. It takes the burden off the manager to be the sole gatekeeper. The team sees the full picture and can advocate for their own capacity. Lucas: Exactly. And that brings up another point: the best tool I've seen for preventing scope creep is something called a 'team capacity agreement'. It's a one-page document that the new manager co-creates with their key stakeholders. It says, 'Here's what we can commit to this quarter. Here's how many unplanned hours we can absorb per week. And here's the process for requesting something new.' Luna: That sounds like a contract. And if stakeholders sign off on it, they can't later complain that the team isn't being responsive. Lucas: Right. And Priya at BuildRight did exactly that. After the scope check-in revealed the forty percent drain, she scheduled a meeting with the heads of sales, product, and customer success. She walked them through the data and said, 'Look, we want to support you, but we need to be realistic. Let's agree on how much unplanned work we can take on without breaking our commitments.' They ended up agreeing on a ten percent buffer — about half a day per person per week. Luna: That's reasonable. And it's better than the alternative — which is everyone being exhausted and nobody delivering well. Lucas: So for new managers listening: your job isn't just to manage the work your team is assigned. It's to manage the work that tries to sneak in through the side door. And the earlier you set those boundaries, the easier it is. If you wait until week twelve, you already have a reputation as someone who always says yes — and then saying no feels like a betrayal. Luna: Yeah, I think that's the key takeaway. You have to establish the norm early — like, from day one — that you're going to be thoughtful about what your team takes on. It's not about being difficult; it's about being transparent about capacity. Lucas: And on that note — if this kind of practical advice has been helpful to you as you navigate your own leadership journey, it's actually because of listeners like you that we can keep this show ad-free and focused on real tools. If you've gotten value from episodes like this one, you can support the show at buy me a coffee dot com slash fexingo. That's buy me a coffee dot com slash fexingo. Even a small contribution helps us keep doing deep dives into the everyday challenges new managers face. And we really appreciate it. Luna: Absolutely. It's listeners who keep this conversation going. And speaking of conversations — let's get back to the team capacity agreement. Lucas, how do you actually get stakeholders to sit down and agree to that? Isn't there a fear that they'll see it as the team being inflexible? Lucas: There can be. But Priya found that framing it as a partnership helps. She said, 'I want to make sure we can say yes to the most important things. To do that, I need your help understanding what's truly urgent versus just convenient.' She also brought data — the forty percent number was powerful. Stakeholders didn't realize the cumulative impact of their small asks. Luna: Data really is the neutral language. When you say 'we spent twelve hours on requests from your team last week,' it's not personal. It's just a fact. Lucas: Right. And once the agreement is in place, the new manager should also model the behavior. If they themselves get pulled into meetings or asked to do things outside their scope, they should use the same framework. Your team watches what you do, not what you say. Luna: So the manager has to be the first one to say 'I need to check my capacity agreement before I commit.' That's a good point. You can't preach boundaries and then violate them. Lucas: Exactly. And the final piece is that the agreement should be revisited. Priya's team did a quarterly review where they looked at whether the ten percent buffer was enough. Sometimes it was, sometimes they needed to adjust. The point is that it's a living document, not a one-time exercise. Luna: That makes sense. Because as the team's reputation grows, more requests will come in. The buffer might need to increase, or you might need to push back harder. Lucas: Exactly. So to recap for new managers: first, track the unplanned work — just for two weeks. You'll likely be surprised by the volume. Second, create a simple decision framework, like the three-question test, to evaluate requests. Third, co-create a capacity agreement with your stakeholders. And fourth, revisit it regularly. Luna: And do all of this early. Your team will thank you, and your stakeholders will respect you more for being honest about what you can deliver. Lucas: Yeah. And if you're listening and you've tried something like this — or if you've got another approach that works — we'd love to hear about it. You can always reach out to us. But for now, I think that's a solid framework to start with. Luna: Agreed. Thanks, Lucas. And thanks to everyone for tuning in. We'll be back next week with another conversation about the real challenges of being a new manager.