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 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.

I’ve had to fix my own version of that. The receipt assumes I know the impact on the spot, and often I don’t. So now it goes more like this: “You added requirement X. We stopped and scoped that. The stopping and scoping costs us X, and here is the updated schedule with your new item added and its impact to other work.” The scoping is a cost too, even when the new thing turns out to be small.

Do that a few times and the asks get fewer and sharper, because now they cost the person making them something real.

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 and answering sales when the date moves. 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 somebody on purpose, in the open, so the missing role becomes impossible to argue with. I took the second one. We had no product-owner role, so I decided engineers would own products, with a senior engineering leader going first so the team could see what good looks like. I told people plainly: “Everyone will feel the pain when devs own it. But the work gets done.” And I wanted the costs said out loud, not quietly absorbed.

That pain is part of how it works. Spread thin across five people, it’s invisible. Concentrate it and it can turn into a hiring decision, though only if somebody’s watching. If leadership just gets used to it, I’ve only moved the hole.

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?