Use natural consequences, not punitive ones — 'if scope…

When This Fires

• When designing consequences for boundary statements (Three components of an effective boundary)
• When the instinct is to threaten emotional consequences ("I'll be upset") rather than describing reality
• When the boundary needs to be professional and relationship-preserving
• When the consequence needs to be inarguable rather than negotiable

Common Failure Mode

Emotional consequences: "If you keep interrupting my deep work, I'm going to be really frustrated." This makes your emotional state the consequence, which the other person might not care about or might dismiss. Natural alternative: "If deep work is interrupted, the deliverable will be delayed proportionally." Now the consequence is a business reality that affects them, not an emotional state that affects you.

The Protocol

(1) For each boundary, write the consequence first as it naturally comes to mind (often punitive/emotional). (2) Convert to natural: "What actually happens — in reality, not as my imposed penalty — when this boundary is crossed?" (3) Common natural consequences: timelines extend (more work → more time). Quality decreases (less focus → worse output). Availability shrinks (energy spent here → unavailable there). (4) State the natural consequence alongside the boundary: "If [boundary violation] occurs, the natural result will be [what actually happens]." (5) The consequence should be something that occurs naturally from the violation, not something you artificially impose. "I'll need to push the deadline" → natural. "I'll be disappointed in you" → punitive.