Latest / Work-Life Balance with Fexingo: Boundaries, Time Management, and Avoiding Career Overload / The Shrinkage Principle How Scope Creep Steals Your Time
Transcript
- Lucas: So Luna, I want to start with a question. Have you ever been asked to do something at work that sounded simple, and then it turned into this massive, sprawling project that ate your entire week? Luna: Oh, absolutely. Last year, my manager asked me to 'tidy up the team's documentation.' Three weeks later, I was building a whole knowledge management system. Lucas: Exactly. That's scope creep in its purest form. And it's one of the biggest silent contributors to career overload. We've talked about energy audits and digital declutters, but today I want to drill into this specific phenomenon because it's so common and so preventable. Lucas: The term comes from project management, but it applies to every job. You're asked to do one thing, but because the request is vague or because you keep adding little improvements, the work expands until it fills all the time you have. Parkinson's Law meets a vague ask. Luna: Right. And it's not just about the time — it's the mental load. You're constantly renegotiating what you're supposed to be doing, which is exhausting in its own way. Lucas: So today, I want to introduce what I'm calling the shrinkage principle. It's a simple mental model for catching scope creep before it starts. The idea is to always ask: what's the smallest version of this that actually solves the problem? Luna: I like that. So instead of trying to do the perfect job, you define the minimum viable outcome first. That's like the MVP of your task. Lucas: Exactly. And it's a two-step process. First, you need to notice when a request is vague. Second, you need to ask the right clarifying questions before you start. Most of us skip both steps because we're busy and we want to be helpful. Lucas: Let me give you a concrete example. A marketing manager gets an email from their boss that says, 'Can you refresh the company website?' That's it. If they just start, they'll end up redesigning the whole brand. But if they apply the shrinkage principle, they'd ask: 'What's the main goal? Is it to update the homepage or fix the contact page?' Luna: So you're cutting the scope down before you even begin. That's smart. But isn't there a risk of looking like you're not a team player if you ask too many questions? Lucas: There is, but the trick is in how you ask. You don't say 'This is too vague, be more specific.' You say something like, 'I want to make sure I'm focusing on what matters most to you. Is the priority the homepage or the whole site?' That frames it as you being thorough, not difficult. Luna: Yeah, that's a great script. And it's not just about the initial request. Scope creep can happen later too, when someone adds 'Oh, while you're at it, can you also...' Lucas: That's the second trap. You're halfway through, and suddenly there's a new requirement. The shrinkage principle applies there too. You have to go back to the core definition and ask: does this new thing belong in the original scope? If not, it's a separate task. Lucas: I read about this software developer who was asked to fix a bug in the login system. During the process, he noticed the password reset flow was clunky, so he decided to improve that too. Then he thought the account settings page needed a redesign. Two weeks later, he'd built a whole new user profile system, and the original bug fix was still unfinished. Luna: That's a cautionary tale. And it's so easy to fall into that trap because you're trying to do a good job. You see something that could be better, so you fix it. But you're not being paid to fix everything. Lucas: Right. And that's why the shrinkage principle is so powerful. It forces you to define success in advance. If the boss says 'refresh the website,' success is a new homepage, not a rebrand. Once you have that definition, anything outside of it is scope creep, and you can politely push back. Luna: I think the hardest part is when the scope creep comes from you, not from someone else. You're self-imposing extra work because you want to do a great job. How do you catch that? Lucas: That's a great point. One technique is to write down the original goal on a sticky note and keep it on your monitor. When you feel the urge to improve something unrelated, look at the note and ask: does this serve the goal? If not, write it down on a separate list for later. Lucas: That's the 'parking lot' method. You acknowledge the idea, but you don't act on it now. You literally park it. And that prevents it from derailing your current task. Luna: That's a concrete tactic. But I also think there's a cultural element. Some workplaces reward people who go above and beyond, so if you stop doing that, you might feel like you're losing points. Lucas: True, but the key is to go above and beyond on the right things. You can still exceed expectations within the defined scope. What you're trying to avoid is doing a million random tasks that don't actually move the needle. That's how burnout happens. Lucas: Let's talk about a specific example from the news. A few years ago, there was a story about a city government project that was supposed to build a simple bike lane. But because of constant scope creep—adding landscaping, redesigning intersections, changing the route—the project took five years and cost ten times the original estimate. Luna: Wow, that's bureaucratic scope creep. But it happens in our own careers too, just on a smaller scale. You end up spending five extra hours a week on stuff that was never really asked of you. Lucas: Exactly. And those five hours, over a year, add up to more than a month of wasted time. That's a month you could've spent on a promotion-worthy project or actually leaving work on time. Luna: So how do you push back when a boss explicitly asks you to take on something outside your scope? I mean, you can't always say no. Lucas: You're right, you can't always say no. But you can say yes, and then have a conversation about priorities. Something like: 'I'm happy to take this on. Should I deprioritize the quarterly report, or can we move that deadline?' Lucas: That way you're not refusing, you're forcing a trade-off. And that's a key skill—making the cost of scope creep visible to the person who's creating it. Luna: I love that. It's like you're bringing the hidden cost to the surface. And often, when the boss realizes something else will slip, they'll reconsider the request. Lucas: Exactly. And that's the essence of good boundary-setting. It's not about being abrasive; it's about being clear about the impact on your time and the team's goals. That's a professional skill that separates the people who are just busy from the people who are effective. Luna: Before we go deeper, this feels like a good moment to mention something. If you're getting value from these conversations, a couple of dollars a month genuinely helps keep this show ad-free. You can support us at buy me a coffee dot com slash fexingo. Lucas: Yeah, we really appreciate that. It's listeners like you who make this possible. And it's a small way to give back if you've gotten something from these episodes. But let's get back to scope creep. Lucas: So another angle is the role of technology. We all have tools that make it easier to add to a project—like project management software where you can just attach a new task to an existing one. But that ease of adding is also an invitation to scope creep. Luna: Right, it's like one click to expand your workload. You don't even have to talk to a person; you just add it to the board. Lucas: And that's why it's even more important to have a clear definition of done. I always ask my team: what does 'done' look like? If they can't tell me, we're not ready to start. Lucas: Let's wrap up with a practical challenge. For the next week, before you start any task, take thirty seconds to write down what 'done' means. And when you feel the urge to add something extra, write it in your parking lot list instead. I bet you'll find you're getting more done and leaving work earlier. Luna: That's a great challenge. And I'd add: if you notice a colleague is clearly suffering from scope creep, maybe share the shrinkage principle with them. It could be the most helpful thing you do this month. Lucas: That's a nice note to end on. Because this isn't just about protecting your own time—it's about creating a culture where we all do our best work without burning out. And that's something we can all contribute to.