Never Say No, Say Not Now¶
Definition¶
A flat "no" to a stakeholder's idea reads as political refusal and invites conflict; "not now" reframes the same refusal as a scheduling fact. The mechanism: hold a current, explicit business objective, and when a new idea arrives, ask whether it serves that objective more than the work already in flight. If not, it waits — not because it's a bad idea, but because something else currently outranks it. If it genuinely would invalidate the current objective, the team replans; otherwise, in the book's words, "the problem will go away by itself."
In the Book¶
Chapter 10 opens with a team paralyzed by eight stakeholders in different countries continuously dumping "blue-sky ideas" into an inexperienced product owner's backlog, with no shared objective to test them against — the plan degenerated into "a stream of consciousness," the team was overloaded with low-value stories, and stakeholders, seeing slow progress, kept reshuffling priorities, which caused the very delay they were reacting to. The proposed fix routes every new proposal through the current business objective (maintained via a hierarchical backlog such as an impact map or story map): does this new idea serve the objective already being pursued? If yes, fold it in; if no, offer to postpone the objective itself for something more critical, which most requesters decline once framed that way, or defer the new idea. The book flags the recurring failure mode directly: without discipline, every new idea gets declared "critical enough to change the objective," recreating the original stream-of-consciousness problem — so the objective itself must be genuinely fixed, not up for silent renegotiation on every request.
Why It Matters¶
Most rejected-idea friction is really unresolved disagreement about priority, not about the idea's merit — restating a "no" as "not now, because we're currently pursuing X" makes the tradeoff explicit and gives the requester a real lever (argue X should change) instead of a dead end. It works anywhere flexible scope meets multiple stakeholders with no shared ranking: product backlogs, resourcing requests, or any setting where saying "no" outright costs more politically than the decision itself warrants.