The Real Reason Scope Breaks
Our portable dishwasher broke. My wife asked if we could get a permanent one installed instead of replacing it. I said I would take a look.
The house was built in the 1920s. In an old house, every time you peel something back you find something else underneath. So I started working and thinking. A permanent dishwasher needs a dedicated outlet. New outlet means reworking the plumbing run and redoing the counter section. New outlet also means opening the wall.
The wall was old plaster. Wouldn't it be easier to just replace that section with drywall? Well, if I was replacing that section, wouldn't it be easier to do the whole wall? While the wall was open I noticed the wiring was old knob and tube. Better update it while I had access. And if I was updating the kitchen wiring, shouldn't I do the rest of the electrical in the kitchen too? That meant opening the other walls. If the other walls were open, I might as well replace that plaster with drywall as well. And if the walls were open, shouldn't I look at the ceiling? And while the walls were open, I should insulate. If I was going to insulate, I could also replace the old drafty windows while I was at it.
Should I go on?
My wife asked for a dishwasher. She did not ask for a kitchen renovation. Nobody planned one. It happened one "while I'm in here" at a time. Each decision was logical. Each one felt like a natural extension of the last. And none of them were ever named as scope.
That is exactly how scope breaks on real projects. Not in one big decision. In a chain of small ones, each reasonable on its own, with nobody stopping to ask what they all add up to.
The Four Forces That Break Scope
After years of leading large programs, I see the same four forces show up again and again. I saw all four of them in my kitchen.
1. The Pressure to Please
My wife asked for a dishwasher. I wanted to say yes. Leaders want to say yes to stakeholders, respond to executives, and show momentum. Saying no feels difficult. Saying yes feels helpful. So we say yes before we understand what yes actually means.
2. The Fear of Missing Out
Once I saw the knob and tube wiring, I could not unsee it. The logical thought was: I should fix this while I have the chance. On real projects this looks like a competitor launching a feature, or a new idea surfacing mid-sprint. Leaders try to fit it in rather than name the cost of doing so.
3. The Illusion of Small
Every step in my kitchen story felt small. Replacing a section of plaster is small. Insulating one wall is small. The problem is that small decisions chain together. Almost every scope change on a real project begins with the same phrase: "it is just a small update." Small is rarely small. Small is usually a placeholder for "I have not thought through the impact."
4. The Absence of a Shared Definition of Done
My wife and I never defined what done looked like. She said dishwasher. I heard opportunity. When quality and completion are not defined upfront, leaders fill the gap with their own assumptions. Teams fill it with theirs. Both end up building different things.
These forces are not signs of weak leadership. They are signs of unexamined leadership. I know because I walked through all four of them in my own kitchen.
The Cost of Breaking Scope
My kitchen project cost more than a dishwasher. It cost more than the walls. It cost time I had not budgeted, money that was not planned, and weeks without a functional kitchen. My wife had not asked for any of that. She had asked for a dishwasher.
On real programs, the cost pattern looks the same. Delivery dates slip because the work grew. Quality erodes because the team is stretched across more than they planned for. Budgets inflate because each small decision carries a price that was never added up. Teams burn out because the ground keeps shifting and nobody names it as a problem until the damage is already done.
The most dangerous part is that none of it feels like a crisis in the moment. Each step feels manageable. It is only when you look back at the whole chain that you see what happened.
Scope drift is like pulling a thread. Each pull seems small. By the time you notice the problem, the whole seam is gone.
How to Stop Breaking Scope
What I needed in my kitchen was someone to ask one question before I touched the second wall: what does done actually look like? I never asked it. That is why a dishwasher turned into a renovation.
Stopping scope drift is not about being rigid. It is about being honest before the chain starts, not after it is already three steps deep.
1. Make trade offs explicit
If you add work, something else must adjust. Time, cost, resources, risk, or quality. There are no exceptions. In my kitchen, adding insulation meant adding time. I just never said that out loud.
2. Use the Pack of Six
Time, Cost, Scope, Resources, Risk, and Quality. If one moves, the others move. This model gives leaders and stakeholders a shared language for what any change actually costs.
3. Define the end state early
If you cannot describe what done looks like in plain language, you cannot protect it. My wife's definition of done was a working dishwasher. Mine kept expanding. Neither of us ever compared notes.
4. Treat quality as a fixed constraint
When quality is left undefined, scope becomes infinite. The knob and tube wiring bothered me because I had a quality standard in my head that nobody else knew about. Define the quality bar upfront so scope changes cannot quietly lower it.
5. Slow down the yes
I said I would take a look before I understood what I was looking at. A fast yes creates slow delivery. A thoughtful yes creates predictable delivery. The pause is not weakness. It is the job.
6. Name the chain before you pull it
Every scope change has a chain behind it. Ask what comes next. Ask what it touches. Ask what changes if this one thing moves. Do not approve anything until you can see at least two steps ahead.
These habits do not restrict leaders. They give leaders something to stand on when the pressure to add just one more thing arrives.
The Leader as a Scope Protector
In my kitchen story, I was both the person who broke scope and the person responsible for delivering the work. That is an unusual case. On most real programs, those are different people.
A stakeholder makes a commitment. A salesperson promises a feature. An executive adds a priority. None of them are the ones who have to build it. The team absorbs what leaders agree to. That is why scope protection is a leadership responsibility and not something you can delegate to the team.
Teams cannot protect scope. They can flag it. They can escalate it. But they cannot stop a leader from saying yes to something that changes the work underneath them. Only leaders can do that.
Protecting scope does not mean protecting the team from new ideas. It means making sure that every new idea carries its real cost with it when it enters the room. When you protect scope, you protect team capacity, delivery quality, budget integrity, and the trust that comes from delivering what you said you would deliver.
In one line
Scope does not break in Jira. It breaks in the moment someone says yes without asking what that yes will cost.
When leaders understand the forces that pull scope apart, they stop treating scope drift as something that just happens and start treating it as a problem they created and can solve. The kitchen eventually got finished. It took longer than expected, cost more than planned, and required a lot of explaining. The dishwasher works great, though.
How this insight supports different learners
R Readers
Follow the four forces that cause scope drift and see how each one showed up in a single kitchen renovation that started as a dishwasher installation.
L Listeners
Connect with the kitchen story and recognize the same chain of logic in your own projects. The "while I'm in here" moment is one every experienced practitioner has lived through.
D Doers
Take six habits directly into your next project: make trade offs explicit, define done early, treat quality as fixed, and name the chain before you pull it.
O Observers
See how a leader who has broken scope themselves thinks about scope protection differently. The honesty is the point.
Questions this insight answers
- Why do leaders break scope even when they know better?
- What is scope drift and how does it start?
- How do you recognize when scope is expanding unintentionally?
- What habits protect a project from scope drift?
- How do you say no to additions that each seem reasonable on their own?