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 it's late July 2026, and I keep hearing from new managers that the thing nobody warned them about isn't managing former peers or giving feedback — it's scope creep. The quiet expansion of what the team is supposed to deliver, one tiny ask at a time. Luna: Yeah, the death by a thousand paper cuts. I've been there. It's especially brutal when you're new and you don't want to be seen as difficult. Lucas: Exactly. And I want to anchor this in a real case. There's a product design team at a mid-sized B2B SaaS company — they had a solid roadmap for Q2 2026. Three features, measured in story points, the whole thing. Luna: Sounds like a dream. Lucas: It was — until about week three. That's when the head of sales came by with a 'quick request' — could they mock up a new onboarding screen for a demo? Should take a day, he said. Then the CEO's admin asked for a slide deck for an investor meeting. Then a senior engineer wanted a design tweak on an internal tool. Luna: And none of those were on the roadmap. Lucas: Zero. By the end of the quarter, the team had lost three weeks — three entire weeks — to unplanned work that had seemed small in isolation. The core features shipped late, the team was exhausted, and the manager felt like she'd failed. Luna: And she probably internalised it as a personal failing, when really it was a structural problem. Lucas: Exactly. And that's where the 'Scope Budget' framework comes in. I learned about it from an engineering manager at a fintech company — he used it to cut unplanned work by 40 percent in two sprints. Luna: Forty percent — that's huge. How does it work? Lucas: The core idea is simple: treat your team's capacity like a fixed dollar budget. You have, say, one hundred story points per sprint. That's your budget. Every request — no matter who it's from — has a cost in story points. You have to approve the expense before work starts. Luna: So it's a mental model shift. Instead of just saying yes to every 'quick ask,' you literally have to ask: what are we not doing to make room for this? Lucas: Right. And the framework has three rules. Rule one: every unplanned request gets a story point estimate before discussion. No estimates, no conversation. That alone kills most of the vague asks. Luna: Because people tend to underestimate when it's just a verbal 'how long?' Lucas: Exactly. Rule two: every request has to be approved against the budget. The manager literally says 'we have 20 points left this sprint. This request is 5 points. Do you want it more than the bug fix we scheduled for Thursday?' Luna: That forces a trade-off conversation. And it makes the requestor own the priority. Lucas: Yes. And rule three: the manager tracks all unplanned work in a separate column on the board — we called it the 'tax' column. At the end of each sprint, you look at how many points you spent on tax. If it's more than 15 percent of your budget, something's off. Luna: So you can't hide it. It becomes visible. I like that. Lucas: The manager I mentioned started doing this in March 2026. First sprint, unplanned work was 28 percent of his budget. Second sprint, he enforced the rules — unplanned dropped to 17 percent. By the end of Q2, he was under 10 percent consistently. Luna: What was the biggest pushback he got? Lucas: From the head of product, actually. She initially felt the framework was too rigid — like he was hiding behind process. But he showed her the data: the team's velocity had actually increased because they weren't context switching. Luna: So the process became a shield. "I'd love to help, but here's what we'd have to drop. You okay with that?" Lucas: Exactly. And that's the thing — most senior stakeholders actually appreciate the transparency. They just don't want to hear 'no.' They want to hear 'here's the cost of yes.' Luna: But what about a new manager who doesn't have the political capital yet? They're two months in, and the VP of Sales asks for something. It's hard to say 'let me estimate that first.' Lucas: It's harder, for sure. But the framework actually helps with that, because it depersonalises the refusal. It's not you saying no. It's the budget saying no. You can literally say 'I use a capacity model to protect the team's commitments. Let me check what we'd need to defer.' Luna: That's smart. It makes it a system, not a personality thing. Lucas: Right. And one more thing — the three-question test. Before you say yes to any unplanned request, ask yourself: Does this serve the current sprint goal? Can it wait until next sprint? And if we do it now, what known commitment suffers? Luna: Simple but powerful. I'm going to use that in my next backlog grooming. Lucas: I think that's the real takeaway — scope creep isn't inevitable. It's a management failure only if you don't have a system to handle it. And the system can be as simple as a budget metaphor and three questions. Luna: Speaking of systems — and this is something we don't talk about often — the reason we can keep making episodes like this one, ad-free and focused on practical tools, is that a small number of listeners chip in monthly. Lucas: Yeah, it's literally listener-funded. A handful of people who find value in the show support it through buy me a coffee dot com slash fexingo. That's what keeps the lights on and lets us drill into topics like this without worrying about sponsors. Luna: If you've ever used a framework from this show — the Scope Budget or anything else — and it's saved you time or stress, that's exactly the kind of impact those supporters make possible. Lucas: So, back to the three-question test — I think the real power is that it trains your brain to think in trade-offs. After a few weeks, you stop reflexively saying yes. You start seeing every request as a resource allocation decision. Luna: And that's the skill that separates a new manager from a great one, honestly. Lucas: Absolutely. So next time someone drops by with a 'quick ask,' remember: it's not quick. It's a line item in your team's budget. And you're the one who signs off.