Derek Sivers, 2009

“If you’re not saying “HELL YEAH!” about something, say no.”

Derek Sivers published this rule in a 2009 essay for people who felt overcommitted or scattered. Saying no by default preserves time and energy for the rare opportunity that deserves wholehearted attention rather than another thin layer of obligation. The rule is a filter for situations with abundant options and limited capacity. It recognizes that a weak yes carries hidden costs: preparation, switching, recovery, and the inability to pursue a later opportunity with the depth it deserves. The business value of the line appears when it changes a real decision. It directs attention toward assumptions that routine can hide and invites a team to examine the system behind an outcome instead of treating the visible result as a complete explanation.

Individuals and small teams can define what an enthusiastic yes must support, delay nonurgent commitments, and keep a visible stop-doing list. When a new project arrives, the decision should include which existing promise will be reduced or removed. Application therefore requires an explicit mechanism: what should people do differently, what signal should move, and when will the team examine the result? Writing those elements down turns general agreement into a testable management practice.

Not every essential responsibility feels exciting, and early-stage learning may require modest experiments before enthusiasm develops. The filter should not be used to neglect care, legal duties, maintenance, or collaborative work that creates value without personal thrill. Context matters because an idea that improves one situation can create harm in another. Leaders need boundaries, dissent, representative evidence, and a way to correct course. Accountability cannot be delegated to the quotation or the tool used to implement it.

AI produces a continuous stream of ideas, drafts, and potential ventures, making possibility far cheaper than sustained attention. The scarce resource is the commitment needed to refine one useful thing, earn trust, and carry it through unglamorous details. A monthly commitment review can classify work as wholehearted, necessary, experimental, or removable, then return capacity from weak discretionary promises to the few projects that merit depth. The review should preserve what was known when the choice was made, document what changed, and share the learning beyond one team. Repeated with discipline, that cycle converts a memorable sentence into better judgment rather than another short-lived management theme. It also makes the cost of assumptions visible, allowing future teams to reuse proven knowledge while recognizing the point at which a different customer, risk, or operating environment requires fresh testing.