Decline with three components: what you're declining, which priority you're protecting, and an alternative — never just 'I''m busy'

Why This Is a Rule

"I'm busy" is the most common and least effective way to decline a request. It communicates nothing about what you're protecting, invites "when you're less busy" follow-ups, and positions you as overwhelmed rather than strategic. The three-component decline converts refusal from a personal failure ("I can't handle more") into a professional decision ("I'm protecting a specific priority").

What you're declining: specificity prevents ambiguity. "I can't take on the market research project this quarter" is clear. "I'm too busy" is vague and invites renegotiation. Why (the priority being protected): naming the priority demonstrates strategic reasoning. "I'm protecting my capacity for the product launch" shows you're making a deliberate trade-off, not just overwhelmed. This is Frame professional boundaries as quality commitments, not capacity confessions — 'protecting the review' beats 'I have too many meetings''s quality framing applied to declines. Alternative when appropriate: offering an alternative preserves the relationship and demonstrates helpfulness within your constraints. "Could Sarah handle this, or could we schedule it for Q2?" redirects rather than simply blocking.

This structure respects both parties: the requester gets a clear answer with reasoning, and you maintain your priority protection without appearing inflexible or capacity-limited.

When This Fires

• When any request arrives that conflicts with your current priorities
• When the instinct is to say "I'm too busy" without specifying what you're protecting
• When declining feels uncomfortable — the three-component structure provides a professional framework
• Complements Acknowledge, boundary, alternative — this three-part structure preserves connection while maintaining limits (acknowledge-boundary-alternative) and Surface trade-offs with forced-choice: 'I can do X or Y this week — which matters more?' instead of silently absorbing both (forced-choice trade-offs) for the specific decline context

Common Failure Mode

Vague decline: "I wish I could but I'm slammed right now." This communicates: temporary capacity issue that might resolve soon. The requester returns next week. Structured decline: "I'm unable to take on the market research this quarter because I'm focused on the product launch. Could we revisit in Q2, or would you like me to suggest someone who might be available now?" This communicates: strategic decision, clear timeline, and a path forward.

The Protocol

(1) When declining a request, state three components: What: "I'm declining [specific request]." Be precise about what you're saying no to. Why: "To protect [specific priority I'm working on]." Name the priority — this demonstrates strategic reasoning, not capacity limitation. Alternative: "Here's what I can offer instead: [different timing, different person, modified scope]." (2) Keep it concise — one to three sentences total. Over-explanation signals guilt and invites negotiation. (3) If no alternative exists: "I'm declining [request] to protect [priority]. I don't have an alternative to suggest, but I wanted to be straightforward about the trade-off."