A design leader's guide to setting boundaries

I’ve stayed silent when I shouldn’t have. There were moments, more than I’d like to admit, where I knew the right answer was no, but I didn’t say it. Times when I compromised my own ethics to tow the party line. When I kept someone on the team even though I knew they weren’t a good fit, it was because I was afraid of the fallout. When I let poor decisions go unchallenged in leadership meetings, I hoped someone else would speak up, but the funny thing is that very few people are brave in the boardroom.

I've told myself it was the mature thing to do. That I was being diplomatic. But really, I was just afraid.
Afraid of being labelled difficult.
Afraid of the confrontation.
Afraid of what would happen if I chose to tell the truth.
Afraid of losing what I had worked so hard to achieve.
And every time I stayed quiet, the cost was real, morale slipped, trust cracked, and the work suffered.

The Architecture and Design industries are full of contradictions. We ask designers to be visionary leaders and meticulous detailers. We ask them to think big, but stay inside the budget. And most critically, we ask them to guide their clients while constantly deferring to their demands.

Somewhere along the line, saying yes became the default.
Yes to that last-minute change.
Yes to the fourth design option.
Yes to the impossible deadline.

And in doing so, designers and architects have unintentionally trained their clients to see them not as trusted experts, but as responsive assistants.

Why design professionals struggle to say no

Personally, I believe a lot of this stems from deep-rooted issues with self-worth. Architecture school teaches us to accept criticism as currency. Our work is pulled apart, pinned up, and judged publicly, often harshly. Nothing is ever good enough, and that culture of critique becomes internalised. Instead of building creative confidence, the process leaves many designers stuck in a fixed mindset. They learn to seek validation. To wait for approval. And once in the workplace, that mindset transfers to clients, bosses, and peers.

The result? A studio full of well-meaning, talented people who say yes to everything. Who avoid hard conversations. Who try to prove their worth through overwork. And who burn out, silently and predictably.

I’ve worked with some impossibly talented and dedicated people in my career, and more than I’d like to admit, I’ve left the office after hours, scrambling for a deadline, only to see other teams still glued to their desks. Eyes hanging out of their heads, spinning out design changes for unrelenting (and often under-qualified) design managers with superiority complexes, managers who have over-promised to clients or bosses and pushed their people-pleasing problems down on others. So where does the buck stop? Who is meant to stand up and say “enough is enough”? Who is meant to be brave and challenge the status quo? I’d say it’s all of us. Every single one of us has the ability to use a strategic and well-placed no.

The power of a strategic no

And now the challenging part. No matter how you cut it, Boundary setting is essential to effective leadership. A Harvard Business Review article, How to Say 'No' to Extra Work by Vasundhara Sawhney (2023), highlights that people who protect their time and energy are seen as more trustworthy and productive. Similarly, studies from the Centre for Creative Leadership indicate that establishing boundaries directly reduces the risk of burnout and increases team performance.

But let's be real, it's not easy, and there is no perfect science to it. However, it doesn’t mean becoming rigid. It means learning to say no with purpose and clarity. Saying no to protect the quality of the work. Saying no to preserve your team’s capacity. Saying no to earn the right kind of trust, the kind that comes from doing fewer things better.

When to say no: 5 critical triggers for design leaders

Saying no is never easy. It can feel like you’re letting someone down, risking a relationship, or stepping into a conflict you’d rather avoid. I know I’ve ducked out of those moments before, telling myself I was keeping the peace when really I was just afraid. That fear is familiar to most of us; it’s why we often default to 'yes'. But recognising the right moments to push past that fear is what separates reactive professionals from real leaders.

Those moments show up in the mess of everyday practice: when a client keeps pushing scope without acknowledging budget; when a director promises a delivery date the team can’t possibly meet; when a staff member asks for exceptions that undermine fairness across the group; or when you’re already stretched thin and know another yes will tip you into burnout. These are not abstract scenarios; they’re the everyday flashpoints where saying yes quickly erodes trust, quality, and well-being.

Some of the clearest triggers for a strategic no are:

1. When the request compromises safety, compliance, or professional standards (and yes, it happens more than anyone admits).
2. When it risks team burnout or chips away at morale (for example, agreeing to yet another design revision without considering how it compounds the team’s workload).
3. When it undermines the project’s budget, timeline, or quality without a clear benefit (like when a client keeps asking for 'just one more thing' without justification).
4. When it contradicts the vision or values agreed upon with the client (for example, when they return from a trip overseas and insist on adding an idea that completely clashes with the established design).

When my own boundaries (time, energy, values or ethics) are at stake (a lesson that took me far too long to learn, and one where others have sometimes paid the price).

I don’t always get it right, and neither will you. Sometimes fatigue or pressure clouds my judgment, and I say yes when I should have said no. But keeping these triggers in mind helps me recognise the danger signs. It’s a reminder that one uncomfortable no in the moment can save months of stress, rework, or disappointment down the track. Saying no is an art form, but it can be learned, and every time you practice it, you give yourself and your team permission to work with more clarity and less fear.

How to say no without damaging client relationships

Most people aren’t afraid of the word “no.” They’re afraid of the conflict that might follow. I understand, we all want peace and harmony. But peace rarely comes from avoiding the hard moments. I’m not suggesting you gear up for battle with clients or colleagues, but moments of tension can prevent bigger problems, set boundaries, or protect a teammate. Too often, we shy away when what we actually need are more people willing to step into the discomfort with honesty. The real question is: how do we handle conflict without turning it into combat?

1. Use frameworks, not feelings

This approach redirects the conversation from emotions to facts, which are harder to argue with. For example:

• "To keep the project compliant, we can't reduce the corridor width. It breaks the fire code."
• "This material doesn’t meet safety standards, so we can’t specify it, but here are two compliant alternatives."
• "Because approvals were delayed on your side, we now need to hold to the revised program dates. Compressing the schedule further would compromise quality and cost.

Why it works: facts depersonalise the decision, make boundaries clear, and help both clients and colleagues see that the no is about protecting outcomes, not about resistance.

2. Redirect with options

Offering alternatives helps maintain momentum while protecting quality. It shows you’re not shutting the door, just pointing to a better path. For example:

• "We can’t add that extra level, but we could look at reworking the mezzanine to add space."
• "We can’t redesign the whole façade, but we could explore adjusting the entry sequence to create more impact."

Why it works: clients and colleagues feel heard, and you avoid being seen as obstructive.

3. Protect the team out loud

A leader’s role is to voice the “no” that the team may not feel safe to say themselves. Strong leaders set that example with phrases like:

• "The team won't be available this weekend, but we can schedule a session first thing Monday morning."
• "We can’t take on that extra design change right now, but we can revisit it once the team has capacity in two weeks."

Why it works: it sets healthy boundaries in plain sight, shows the team they are supported, and normalises rest as part of sustainable performance.

4. Name the impact

Being explicit about consequences helps people understand why “no” is necessary, while also creating space for resolution. For example:

• "If we say yes to this extra revision, it will push delivery back two weeks and put the opening date at risk. If keeping that date is the priority, we need to hold the line here."
• "Reducing the budget in this area would mean cutting safety features. That’s not negotiable, but we can explore trimming costs in finishes or non-critical elements."
• "Because approvals have been delayed, the program has already slipped by three weeks, which pushes completion back. To recover, we need timely sign-offs going forward; without them, the revised completion date will need to be extended."

Why it works: it connects the “no” directly to project outcomes and then pivots toward a constructive path forward, making the decision easier to respect and act on.

5. Build systems that say no for you

The most effective way to reduce conflict is to design processes that clearly define expectations up front. For example:

• Using Programa's Project Management milestone tool, helps set the pace and gives you the visibility over how mich time this will delay us by.
• Establishing a client communication portal via a Client Dashboard on Programa sets up a clear approvals process to which locks deadlines after approvals, or client approval workflows that prevent moving forward without sign-off.
• Programa Schedules help set clear expectations around budgets and that more expensive marble that needs to squeeze into the same budget.

Why it works: It shifts the 'no' from being personal to being part of the system, which protects both the team and the relationship.

Building systems that protect your boundaries

Saying no is uncomfortable, but it is also one of the clearest signals of leadership. Every well-placed no protects the quality of the work, the well-being of the team, and the trust of the client. The real measure isn’t whether you avoid conflict, but whether you handle it with honesty and respect. Next time you feel the pull to say yes against your better judgment, pause and remember: the strength of your leadership is often defined not by what you take on, but by what you choose to protect.

One way to make this easier is by tightening the systems that support you. With Programa, that might mean simplifying client approval workflows so that delays and scope creep don’t spiral into late nights and missed deadlines. At Third Principle Co., it’s about building the operational backbone that gives studios the confidence to protect their people and their process. Both approaches transform saying no into a positive act of stewardship, one that is less about confrontation and more about safeguarding the work and the team behind it.

The best "no" Is the one you never have to say

Many conflicts in design practice stem from unclear expectations at project kickoff. That's why boundary-setting should start before the first sketch. Ready to build systems that protect your team and your work?

Your studio deserves structure that supports sustainable, high-quality work.