The Three Questions That Kill Scope Creep

A founder brings me an idea. I don't argue about whether it's good — most of the time it is. I ask one question instead: do you have more budget, more people, or more time to give it?

Almost always, the answer is no. And that single question does more for how a founder relates to priorities than any argument I could make. It's not a rejection. It's a test, and it's the same test every time, which is exactly why it works — the founder starts running it themselves before I even ask.

Do you have more budget, more people, more time? Almost always, the answer is no.

The test only has three levers

There are exactly three ways to add real capacity to a plan: more money, more people, or more time. If a founder can point to one of those, the idea gets added — genuinely added, not squeezed in. If they can't, the idea isn't dead. It just can't sit on top of everything already agreed. It has to trade for something.

This is where most scope creep actually comes from. Not from bad ideas — from good ideas that skip the test. Someone gets excited, the idea sounds urgent, and it gets waved onto the roadmap without anyone asking what it's displacing. Do that enough times and the roadmap stops being a plan. It becomes a wish list with a due date.

Agreeing an idea matters is not the same as doing it now

People who are good at this work — sizing tasks honestly, saying what they will and won't do — tend to make founders uncomfortable in a specific way. Founders who are used to handing something off and having it disappear don't love hearing "not yet." It reads as friction, even when it's accuracy.

So I separate two things that get treated as one. Agreeing an idea is worth doing, and agreeing to do it right now. I do the first one immediately and out loud — the idea gets acknowledged, written down, given a real shape with implementation steps, not just a name on a list. Then the three-question test decides the second one.

That separation matters more than it sounds like it should. A founder who hears "yes, this belongs on the roadmap" and a founder who hears "no" are having two completely different conversations, even when the actual scheduling outcome is identical.

We overestimate the day, underestimate the quarter

Run the test consistently and something else becomes visible: we're much worse at judging a day than a quarter. A founder will swear they have more ideas than any team could get through. Then you lay those same ideas out — week by week, three months at a time — and one of two things turns out to be true. Either there's less real work than three months' worth. Or half of it isn't actually a task yet, just a wish with no shape, and it needs the founder to sit and think before the test can even apply to it.

Either way, the panic was never really about volume. It was about everything competing for attention in the same moment, with no lever to sort it.

The test is the discipline, not the roadmap itself

The roadmap is just where the answer lives. The test is what keeps it honest. Without it, "flexible" quietly turns into "unlimited," and a roadmap that accepts everything isn't protecting anyone's priorities — it's just deferring the collision.

With it, ambition stays exactly as large as it should be. The founder keeps bringing ideas, all of them, without hesitation — because they know the test will sort what's real from what's not yet, without anyone having to argue about it.

The test isn't there to say no. It's there so nobody has to argue.