How to Set Boundaries as a Manager

Why managers find limits so hard to set

The word "boundaries" makes many managers uncomfortable. It sounds like something from a therapy session rather than a management conversation. But the discomfort runs deeper than vocabulary. Most people who become managers were promoted partly because they were responsive, helpful, and willing to go the extra mile. Those habits served them well as individual contributors. As a manager, the same habits can become a trap.

Being always on feels virtuous when you are new to management. You are proving yourself, building trust, showing the team you care. But there is a ceiling. Past a certain point, availability without limits sends the wrong signals: that your team cannot make decisions without you, that every problem requires your attention, and that your role is to absorb everything that comes your way.

There is also a cultural dimension. Some organisations reward availability over outcomes. If the norm is responding to messages at all hours and never saying no, setting any kind of limit feels career-limiting. But managers who protect their thinking time and operate with clearer limits typically produce better outcomes over time, and they model the kind of sustainable working habits their teams need to see. Read more in our guide on managing your energy as a manager.

The four limits every manager needs

Limits come in different forms. Most managers need to address all four, though the urgency varies depending on role and context.

• Time limitsManagers often have no focused work time because every calendar slot is available for booking. Block at least one or two meaningful windows per week where you can think, prepare, and process without interruption. This is not a luxury. It is where your best decisions get made.
• Availability limitsA message sent at 9pm is not necessarily an emergency. Being explicit about your availability, with your team and your own manager, removes the guilt of not responding immediately. The key is having a clear escalation path so people know what to do if something is genuinely urgent.
• Scope limitsSome things will come your way that are not yours to own. Requests that belong to another team, decisions that should sit elsewhere, work that has been escalated because it is easier than owning it. Saying no to the wrong work is not unhelpfulness. It is clarity. See also our guide on delegation, because scope limits and delegation often go hand in hand.
• Emotional limitsManagers often become emotional containers for their team. Someone is anxious about a deadline. Someone is frustrated with another team. These are real concerns and worth taking seriously. But there is a difference between listening and supporting, and making someone else's anxiety your own. You can hold space without carrying it with you for the rest of the day.

How to communicate limits without losing trust

The practical question is how to set limits without your team feeling abandoned or your organisation seeing you as unhelpful. The answer is straightforward: communicate proactively, give your team what they need to work independently, and be consistent.

If you are protecting certain mornings for focused work, tell your team. "I am not in meetings on Monday mornings. That is my planning time. If you need me urgently, send me a message and I will respond. Everything else I will see after lunch." People adapt quickly when expectations are clear. The problem is when limits are invisible and people interpret your silence as disinterest.

Most ad-hoc interruptions happen because people are uncertain. They do not know how to decide, or they lack context, or they have never been given the authority to act. Use regular catchups to pre-empt issues before they become urgent messages, and make clear in Actions what each person owns and is empowered to resolve. When people have context and authority, they interrupt less.

Consistency matters as much as clarity. A limit that disappears whenever someone pushes back is not a limit. If you protect Monday mornings but then book a meeting there whenever someone asks, you have communicated that the limit is negotiable. Consistency helps your team internalise the rhythm and plan around it rather than probing for gaps.

Finally, model what you expect. If you tell your team to leave on time and protect their recovery, but you are sending messages at 11pm and booking Friday afternoon slots, the message is mixed. What you do matters more than what you say. If burnout is already a concern on your team, our guide on addressing burnout covers the warning signs and what to do next.

Putting it into practice

The best time to set limits is before you feel you need them. Once you are already overwhelmed, every limit feels like adding friction to an already difficult situation. Start small and be explicit about the changes you are making.

• Name the limitDo not just behave differently. Tell people what you are doing and why. "I am protecting my mornings for focused work from now on" is clearer and more respectful than going silent and hoping people notice.
• Build the rhythm firstRegular catchups and clear Actions reduce the need for ad-hoc contact more than any availability policy. When people know they will see you on Tuesday, they save questions for Tuesday instead of messaging on Monday evening.
• Say no to scope creepWhen a request lands that is not yours to own, say so clearly and redirect it. "That sits with the X team, I would recommend speaking to Y" is a complete answer. You do not need to apologise for not absorbing work that is not yours.
• Review after four weeksCheck in with yourself and your team. Are the limits holding? Are there unintended consequences? Adjust where needed, but resist rolling them back entirely under pressure. Small calibrations beat starting over.