Boundaries aren't walls — they're infrastructure for a sustainable UX practice

If you work in UX, content, or design, you've heard some version of these before: "I promised the client you'd be done by [insert unrealistic date]." "We don't have time for testing, just ship it." "Can you just...?"
I recently spoke at Leadership by Design 2026 about why these moments keep happening — and what boundaries actually have to do with fixing it.
Boundaries aren't about saying no
It's true that "no" is a complete sentence. But in most of the work we do, saying no outright isn't always realistic. So instead of thinking about boundaries as walls or "keep out" signs, I offered a different frame, borrowed from architecture: a boundary's real job isn't to block access to a space — it's to define what happens inside it. A retail unit and an apartment can share a building, but nobody expects the same fixtures in both, because the boundary lines tell you what each space is for.
Applied to a UX practice, that reframe changes the question. Instead of "what do we refuse to do," it becomes "what is this space for, and how do we protect that purpose?"
The practice core: culture, systems, and people
Every practice sits inside three layers — the cultural environment it operates in, the systems and ways of working that structure it, and, at the center, the people doing the work. I focused the talk on that center, because a practice is only as strong as the collective expertise of the practitioners inside it. Without people who advocate, educate, and articulate the value of the work, there's no practice to protect in the first place.
Five ways to build boundaries into a practice
I walked through five components that, together, define a healthy practice space:
Self-care. Self-awareness comes first — you can't care for yourself well until you know what you're actually feeling and needing. I leaned on the work of Vivianne Castillo here, who has written about the difference between treating burnout's symptoms and addressing its cultural and systemic root causes.
Vulnerability. Real connection starts with vulnerability — first with yourself, then with a trusted person, then outward to your wider community of practice. Brené Brown's research on courage, compassion, and connection maps almost perfectly onto this progression.
Active listening. Vulnerability only works if people feel genuinely heard — not just heard on the surface, but listened to for the feeling underneath the words. That means being fully attentive, asking open-ended questions, and reflecting back what you've heard.
Pushing back. This is the one that tends to land hardest. Content design leader John Paz put it simply: you can be the bottleneck, or you can be the burnout. For years, "bottleneck" felt like a dirty word to me — content often gets blamed for slowing things down, often unfairly. But choosing to be the intentional bottleneck, on your own terms, is what prevents burnout down the line.
Inclusive boundaries. Here's the twist: the most effective boundaries aren't drawn in isolation. Practice charters, SLAs, and rules of engagement work best when cross-functional partners help shape them — because people respect a threshold more when they understand its purpose going in.
What this looks like in practice
Some of the most practical tools I shared were the simplest:
Organizing your team into a defined practice unit is, on its own, a form of boundary-setting
Get explicit about what your practice won't do before worrying about what it will
Set rules of engagement: how people request design or content support, and how that scales with the size of the ask
Use SLAs to define what you'll deliver and when — which cuts down on the "urgent, need by end of day" messages
If it fits your organization, build a practice charter — and write it with the people it affects, not just for them
The takeaway
Boundaries, done this way, aren't restrictive — they're protective. They ward off burnout, reduce stress, clarify expectations for everyone around you, and build both self-respect and the respect of your collaborators. As one attendee's comment on the talk's core idea put it: boundaries define purpose; they don't prevent access — the same way a good design constraint sharpens the work instead of limiting it.
If you're building or rebuilding a practice and want a structured way to think through where your boundaries need defining—business case, cross-functional relationships, tools, team size, and how you measure success—that's exactly the diagnostic work I do in The Practice Audit.



Comments