Question
What goes wrong when you ignore that saying no to protect capacity?
Quick Answer
Saying no once, feeling the discomfort of the other person's disappointment, and resolving never to do it again. The failure is treating the no as an event rather than a practice. One declined request does not protect your capacity — a consistent pattern of capacity-based decision-making protects.
The most common reason fails: Saying no once, feeling the discomfort of the other person's disappointment, and resolving never to do it again. The failure is treating the no as an event rather than a practice. One declined request does not protect your capacity — a consistent pattern of capacity-based decision-making protects your capacity. If you say no to one request and then say yes to the next three out of guilt, you have not changed your system. You have had an isolated moment of discipline followed by a return to the default. The practice only works when it becomes the default, and the default only changes through repetition, not through a single act of courage.
The fix: Identify the next request you receive — professional or personal — that would push your C/C ratio above 0.85 (or further above 1.0 if you are already overcommitted). Before responding, write out three things: (1) your current ratio, (2) what the ratio becomes if you accept, and (3) a capacity-based counter-offer that includes either a later start date, reduced scope, or an explicit trade-off ('I can do X if I stop doing Y'). Deliver the counter-offer using the format: 'My capacity is committed through [date]. I can take this on starting [date], or I can start sooner if we [specific trade-off].' After the conversation, write down the other person's reaction. In nearly every case, the reaction will be more positive than you feared.
The underlying principle is straightforward: Declining new commitments when at capacity is not selfish — it is responsible.
Learn more in these lessons