--- title: "The scope creep that arrives dressed as a quick favour" date: 2026-07-17T00:00:00Z updated: 2026-07-11T08:21:29Z tags: ["Career", "Communication", "Visibility", "Stakeholder Management", "Judgment", "Scope Creep"] canonical: https://bianca.codes/blog/the-scope-creep-that-arrives-dressed-as-a-quick-favour/ --- # The scope creep that arrives dressed as a quick favour _Every 'while you're in there, could you just...' is small enough to say yes to and invisible enough to never get credit for._ The message shows up right after you've delivered something, usually with a compliment stapled to the front of it. "This is great, by the way, while you're in there could you also just add a filter for last quarter?" It's never framed as new work. It's framed as a footnote to the work you just finished, which is exactly why nobody, including you, treats it as work at all. Say yes to enough footnotes and you've picked up a second job. Not the kind with a ticket and a deadline, the kind that's just a running tab of ten-minute favours that never shows up on a roadmap, never gets estimated, and never makes the list when someone asks what you did this quarter. Four or five of these in a week is two or three hours easily, and two or three hours a week for a year is a project nobody signed off on and nobody remembers agreeing to. The obvious fix is to just say no to the extra asks, and that advice is correct and useless in the same breath, because any single one of these requests really is small. Refusing a five-minute favour doesn't read as boundary-setting. It reads as difficult, and you already know that, which is exactly why you keep saying yes. ## Why "just say no" doesn't survive contact The request smuggles in its own defence before you've had a chance to object to it. "While you're in there" isn't just a phrase, it's an argument: you're already positioned to do this, the marginal cost to you is basically nothing, so refusing looks like you're being precious about five minutes rather than protecting anything real. Arguing against that framing means arguing against your own competence and proximity, which is a much harder sell than arguing against the merits of an actual new request. The other half of the problem is that none of this gets logged anywhere. A ticket has a title, an owner, a status. A "while you're in there" has none of those, so there's no artefact anyone, including you, can point at six months later to prove the pattern existed. That's the same blind spot [this arc has already covered](/blog/when-your-work-is-invisible-because-it-just-works/): work that runs quietly and gets done fast reads to everyone outside it as work that costs nothing, which is exactly what makes it safe to keep asking for more of. ## What actually helps Name the ask out loud, in writing, every time, without refusing it. "Sure, noting that as a second thing so it doesn't get lost" costs you nothing and does the one thing silent compliance never does: it puts the request somewhere other than your memory. You're not declining. You're refusing to let it stay invisible. Keep a running tally somewhere you'll actually see again, not a mental note you're trusting yourself to remember under deadline pressure. A pinned message to yourself, a plain text file, whatever's frictionless enough that you'll actually use it. The point isn't record-keeping for its own sake, it's that the day you need to show someone the pattern, you have five dated examples instead of a vague sense of being tired. Attach a rough cost even when you're not asking for anything back. "Happy to, that's about twenty minutes" reframes the favour from free to counted without costing you the relationship or making you sound like you're keeping score. Most people genuinely don't clock how much these add up to until someone puts a number next to them. ## This week Next time a "while you're in there" message lands, don't just do it. Reply with the acknowledgment line first, then do it. One sentence, no confrontation: "Sure, that's a second thing on top of the original ask, happy to knock it out." Naming the ask is the easy version of this problem. The next post in this arc is about the harder one: the request where the honest answer is actually no, and how to give it without sounding like you can't do the job. ## Frequently Asked Questions ### **Isn't narrating every small favour going to make me look difficult?** Not if you do it while still saying yes. The line isn't a refusal, it's a receipt. "Noting that as a second thing" reads as organised, not obstructive, because you're doing the work either way. What makes someone look difficult is refusing small asks outright, not acknowledging that they exist. ### **What if my manager genuinely doesn't care about a ten-minute favour?** Then the record isn't for this week, it's for the conversation three months from now when you're explaining why your actual project slipped. One favour is not evidence of anything. Fifteen dated ones in a doc is a pattern, and patterns get taken seriously in a way vague fatigue never does. ### **Does this apply to favours from peers, or just from managers and stakeholders?** Both, though the phrasing shifts. With a peer it's less about protecting your review and more about not becoming the default answer to "who can just fix this quickly." The tally still matters either way, because your time doesn't know the difference between who asked for it. ### **I've already said yes to a bunch of these without tracking them. Is it too late to start?** No. Start today and don't try to reconstruct the last six months from memory, you'll undercount and second-guess yourself. The pattern is just as visible going forward as it would have been in hindsight, and it's a lot less work to prove. ### **Isn't this just complaining about workload with extra steps?** Complaining is vague and unfalsifiable: "I'm so busy." A tally is specific and checkable: "here are eleven unscoped requests in three weeks, averaging fifteen minutes each." One of those gets you sympathy. The other gets you a conversation about what actually gets deprioritised. ### **What if the favour really is trivial and genuinely not worth mentioning?** Then don't mention it, that's a judgment call and you're allowed to make it. The problem was never any single favour. It's the ones that quietly aren't trivial that get waved through on the same "it's basically nothing" logic as the ones that are, because nobody stopped to check which category they were actually in.