Absorbing Scope Teaches the Org That Scope Is Free

In most engineering orgs, scope creep has a face, and it usually outranks you.

Here’s what I got wrong for years. A new requirement would land mid-sprint, I’d absorb it, and I’d quietly eat the schedule. It felt like competence. What I was actually doing was training people.

When a change costs nothing, you get more changes. Nobody’s being malicious about it. The price just never shows up on a receipt, so it gets paid somewhere nobody’s looking: the team’s nights, and the defect count six months later that everyone will pin on the developers.

Saying no doesn’t really work. You spend your credibility and the requirement lands anyway. So don’t say no. Send the receipt instead. “Sure, and this is now more important than X?” Then follow it with an email: here’s the reordered list, and here’s the new date on the thing that just slipped. You still said yes. You just didn’t hide the bill.

Do that a few times and the asks get fewer and sharper, because now they cost the person making them something real. All you’ve done is put the price tag back on something somebody quietly peeled it off of.

The same thing happens with whole jobs, not just tasks. Every org has a job nobody funded. Somebody wrote the requirement, so now they review the mockups. Then they own the ship date. Then they’re the one checking whether the docs got written, chasing QA, and answering sales when the date moves. Nobody ever named that job, but it exists anyway. A role you refuse to fund still gets built, one duty at a time, on whoever happens to be standing closest.

That cost never hits a budget line either. It shows up as the senior engineer whose real work slipped a quarter, and as the gaps nobody covers because the person absorbing all of it is already full. Leadership looks at the org chart and doesn’t see a hole, because somebody is quietly standing in it.

There are two ways out of that one. You can keep absorbing it, which teaches everyone the job is free. Or you can hand the whole stack to one person on purpose, in the open, so the missing role becomes impossible to argue with. The second one hurts, and honestly, the hurting is the point. Pain spread thin across five people is invisible. Concentrate it and it turns into a hiring decision.

Either way, the work was never free. Somebody was just paying for it where the person ordering it couldn’t see. So who in your org is doing a job that isn’t on the chart?