What does it mean that boundaries are not walls?

Boundaries are not about shutting people out — they are about defining the terms of engagement. A wall blocks everything. A boundary filters selectively.

Example: A software engineer joins a new team where the culture is to respond to Slack messages within minutes, regardless of the hour. She feels the pull to comply — the messages keep coming at 9 PM, at 11 PM, on weekends. Her first instinct is to wall off completely: turn off notifications, stop checking Slack after 5 PM, refuse all after-hours communication. But that creates a different problem — she misses a production incident that genuinely needed her expertise, and her team loses trust in her reliability. She recalibrates. She sets a boundary, not a wall: she communicates that she checks Slack once at 8 PM for emergencies flagged with a specific emoji, and everything else waits until morning. She is not blocking the channel. She is filtering it. The team adapts. Trust holds. Her evenings return. The boundary did what the wall could not — it preserved connection while protecting her capacity.

Try this: Draw two columns on a page. Label the left column "Wall" and the right column "Boundary." Think of three relationships or contexts where you currently feel drained, overextended, or resentful. For each one, write what walling off would look like (complete withdrawal, cutting off communication, refusing all requests) and then write what a selective boundary would look like (specific limits, clear communication, defined terms of engagement). Notice the difference in what each approach preserves and what it destroys. For at least one of the three, draft the actual language you would use to communicate the boundary — not the wall. Time: 15-20 minutes.