Latest / Manager Mondays with Fexingo: People Management, Team Leadership, and First-Time Managers / How to Manage Scope Creep Without Killing Initiative
Transcript
- Lucas: You have a designer — let's call her Priya — who consistently delivers work that's better than what you asked for. The problem is it's also 30 percent more than what you asked for, and it shows up two weeks late. Luna: I've managed that person. It's infuriating because you can't be mad at the quality. Lucas: Right. The instinct is to praise the extra effort, but then you realize the whole team's timeline just shifted. And next sprint, Priya does it again. So today I want to talk about a specific type of scope creep — the kind driven by genuine initiative, not by confusion or laziness. Luna: Because punishing initiative is how you create a culture of doing the bare minimum. Lucas: Exactly. But neither can you let it slide. I saw a great framework from a product leader at a mid-size SaaS company — they called it the 'one extra' rule. When a team member proposes adding something beyond the original spec, the manager acknowledges it, then asks: 'What are you willing to deprioritize to make room?' Luna: That forces a trade-off. But what if Priya says nothing needs to be deprioritized because she'll just work evenings? Lucas: Then you have a sustainability conversation. Because scope creep that's absorbed by unpaid overtime is still scope creep — it burns people out. And as a manager, you're responsible for that, even if the employee volunteers. Luna: So the frame isn't 'stop doing extra work.' It's 'let's make the extra work visible and intentional.' Lucas: That's the core of it. And here's a specific number that comes from a study of software teams at Carnegie Mellon: projects where scope creep exceeded 25 percent of the original estimate had a 70 percent likelihood of missing the deadline by at least a month. Priya's 30 percent puts you right in that danger zone. Luna: Oof. So the cost isn't just her time — it's the downstream impact on everyone waiting on her deliverable. Lucas: Right. So what do you do? Step one: diagnose the motive. Is Priya adding scope because she's unsure about the original spec? Because she's bored with the core task? Because she wants to impress you? Each requires a different response. Luna: Let's take the 'unsure about the spec' case first. Lucas: That's the easiest to fix. It means your requirements weren't specific enough. If you say 'design a landing page,' Priya may interpret that as 'design a landing page with animations and a micro-interaction.' You meant 'a static page that converts.' The intervention here is to write tighter specs — include explicit scope boundaries: what's in, what's out, and what a stretch goal looks like. Luna: But that can feel micromanaging if you over-specify every detail. Lucas: There's a difference between specifying outcomes and specifying methods. You don't tell Priya which font to use. You tell her the page needs to load under two seconds and include three form fields. The 'how' is hers. Luna: Okay, what about the second case — Priya is bored with the core task? Lucas: That's trickier because the work still needs to get done. One approach is to explicitly allocate 'innovation time' — say, 10 percent of her sprint capacity — where she can explore new ideas. But that time is tracked, and the core deliverables are protected. You're basically saying: 'I see you want to stretch. Here's a container for that.' Luna: And the third case — she's trying to impress you? Lucas: That's the one that requires the most emotional intelligence. Because if you correct her too harshly, she'll think you don't value excellence. The move is to separate the person from the behavior. Say: 'Priya, I love the ambition in this. But for this project, the goal is speed and precision. Can we cut the extras and ship the core on time? I want you to save those ideas for our next planning session.' Luna: You're redirecting her energy instead of shutting it down. Lucas: Exactly. And if she still struggles, you might need to look at your own behavior. Are you ever rewarding scope creep with praise? If every time Priya overdelivers you say 'wow, this is amazing,' you've trained her to keep doing it. Luna: That's a good point. We're on a careers show, and one of the things we talk about a lot is how managers can create the conditions for their team to do their best work. And we don't run ads on these episodes because we think that kind of honest, practical advice should be freely available. If you find value in that, and you want to support the show staying ad-free, the link is buy me a coffee dot com slash fexingo. Lucas: It genuinely helps. And it's a small gesture that keeps us independent. So, back to Priya — there's a fourth case I want to cover. Luna: What's that? Lucas: Priya adds scope because she's anxious about failure. She thinks the core work isn't good enough, so she layers on extras to distract from that fear. That one requires a coaching conversation about perfectionism. Luna: That's a different intervention entirely. You're not managing scope anymore — you're managing psychology. Lucas: Right. And you can't solve that with a process change. You have to talk about what 'good enough' looks like, and help her trust that delivering on time is more valuable than delivering a masterpiece that's late. Luna: Let me ask a practical question. Suppose you've had the conversation, you've set boundaries, and Priya still delivers scope creep. What then? Lucas: You escalate consequences. Not punishment — but clear cause and effect. Next time, you push back the delivery date of the entire project and name why: 'Because the spec was exceeded, we lost two weeks. Going forward, if scope expands beyond what we agree, I'll reset the timeline publicly so everyone sees the impact.' That's accountability without shame. Luna: And if it keeps happening, it might be a fit issue. Some people are just not wired to work within constraints. Lucas: That's the hardest conclusion, but sometimes true. There are roles where scope creep is an asset — R&D, exploratory design, strategy. If you're managing a tight delivery team, you may need to move Priya to a role where her instincts are an advantage instead of a liability. Luna: I like that reframe. It's not about breaking her spirit — it's about finding the right container for her talent. Lucas: Exactly. One last thing: there's a simple preventive measure I've seen work. Before every project, ask the team: 'What does minimum awesome look like?' Define the smallest version that would still feel great to ship. Then anything beyond that is explicitly a stretch goal. Luna: That sets a shared baseline. So when Priya adds her extras, the team can see they're deviating from the agreed minimum. Lucas: Right. And it takes the pressure off you as the sole enforcer. The team becomes the guardian of scope. Luna: That's a good note to end on. Next week we're going to talk about something that came up in our listener survey — how to manage a team member who's technically brilliant but socially awkward. Lucas: That's a tough one. See you then.