A system boundary defines what people should expect from you in a professional role: how you interact, when you are available, and where work ends. For an engineering manager, blurred boundaries can make feedback harder to accept, delay decisions, and damage work–life balance. section 3.3.3 section 3.3.4
When friendliness weakens accountability
An engineering manager became overly friendly with former teammates and did not clearly separate friendship from professional responsibility. Two team members then took constructive feedback less seriously, and one delayed responding to a work request. A one-on-one conversation clarified expectations and restored the boundary. section 3.3.3
Practical boundaries protect both relationships and delivery:
- Separate personal friendship from supervisory responsibilities; remain humble and assertive when giving feedback. section 3.3.3
- Protect working hours by avoiding late-night work messages, using Send Later, or marking messages for reading the next day. section 3.3.4
- Say no to demands that overcommit the team, explain likely effects on timelines, and offer constructive alternatives. section 14.2.4
- Reduce unnecessary meetings by clarifying involvement, using the RACI matrix, and sharing minutes with people who only need information. section 14.2.4
- Review boundaries regularly, manage stress and emotions, and base difficult decisions on objective data rather than immediate reactions. section 3.3.4
A boundary is not a refusal to help. It makes commitments visible, gives others a reliable way to work with you, and creates room to protect team well-being while meeting professional responsibilities. section 3.3.4 section 14.2.4
