Scope is a moral choice, not a planning one

Every plan has a line through it. Above the line, what ships. Below it, what waits — which, if you’ve built anything before, you know usually means what never comes at all. We draw that line in the language of planning. Capacity, velocity, what’s realistic for the quarter. The whole vocabulary is logistics, as if we’d been packing a truck and simply ran out of room before everything fit.

But look at what’s actually sitting on either side of it. Above the line is a set of people whose problem you’ve decided to solve. Below it is a different set of people whose problem you’ve decided, for now, they get to keep having. That is not a logistics call. It’s a choice about who counts enough to be served this time, wearing the costume of arithmetic. A product’s real values don’t live in its mission statement. They live in its cut list.

Here’s the mechanism worth being precise about: the logistics framing launders the decision. “We didn’t have the bandwidth” sounds like something that happened to you — a fact about the calendar, weather you were caught in. “We chose not to build the thing that would have made this usable for people on slow connections, or on a screen reader, or on a tighter budget” sounds like what it actually is: a decision, with a beneficiary and a casualty. Same line, same plan, same Tuesday. The first phrasing just lets you skip noticing that you chose at all.

Consider the most common form the deferral takes: “we’ll add it later.” Later is not a time. Later is the place plans go when you want the comfort of not having said no. A feature promised for “later” has roughly the survival odds of a New Year’s resolution — real intent, no mechanism, and every subsequent quarter it gets outrun by whatever’s newer and louder. Deferral feels kinder than rejection because it costs nothing to say and hands the other person some hope to hold. That’s exactly what makes it the less honest of the two. A clean no lets someone go find another answer. A soft “later” keeps them waiting on you for one that isn’t coming.

The objection is real and I want to state it at full strength, because a caricature would be too easy to wave off. You cannot build everything. Pretending scope isn’t constrained is its own dishonesty. Focus is not optional; a product that tries to serve everyone ends up serving no one; ruthless cutting is the only reason anything ships at all. All of that is true and none of it is in dispute here. The claim isn’t that you should cut less. It’s that when you cut — and you must — you should know you’re making a choice about people, and make it with your eyes open. Pick who you’re not serving on purpose, for a reason you’d be willing to say to their face, instead of letting the reason quietly default to “they weren’t in the room when we prioritized.” The cut is unavoidable. The self-deception about what the cut is — that part is optional, and it’s the part to drop.

There’s a practical edge to this and not only a matter of conscience. Because scope encodes who you serve, the pattern of your cuts compounds. Trim the same kind of person’s needs three quarters running and you have, in effect, decided what your product is and isn’t for — whether or not anyone ever wrote that decision down. The omissions add up into a shape, a personality of what’s included and what’s missing that users feel even when they can’t name it. Owning scope as a values decision is how you get to author that shape on purpose, instead of discovering it a year later in your churn.

So the next time the line goes through the plan, don’t only ask what fits. Ask who’s below it, and whether you’d tell them, to their face, why. If you would, cut with a clear conscience — that’s what focus is. If you wouldn’t, you haven’t found a capacity problem. You’ve found a decision you were hoping the calendar would make for you, so you wouldn’t have to.