For a long time, I believed that disappointing someone was a sign that I had done something wrong.
If someone asked me to take on one more responsibility, I tried to make it work. If a request made me uncomfortable, I searched for a way to say yes. If I sensed that someone wanted a different answer, I softened my own position until it was barely recognizable.
This habit can look like kindness from the outside. Sometimes it is simply fear wearing a pleasant expression.
Recently, I found myself struggling with a task at work that had been added to my responsibilities some time ago. The process placed me between a client who wanted a problem solved quickly and an outside contractor who needed increasingly detailed information before taking action. I was expected to absorb the urgency from one side and the questions from the other.
The more I tried to make the process work, the more stressful it became. Eventually, I was thinking about quitting my job, even though I need to continue working for a few more years before retirement. That reaction helped me recognize that this was not just an unpleasant task. It was a poorly defined process that placed ownership and pressure in the wrong place.
When discomfort is trying to tell us something
We are often encouraged to push through discomfort. Sometimes that is exactly what growth requires. A new responsibility may feel awkward at first, and learning a new skill can be frustrating before it becomes familiar.
But not all discomfort is a sign that we need to try harder. Sometimes it is information.
A process may be missing a clear handoff. A responsibility may have been assigned without the authority or resources needed to carry it out. We may be asked to promise an outcome that depends on people we do not manage. We may be standing in the middle of two groups, expected to satisfy both while having control over neither.
When that happens, the solution may not be becoming more tolerant of stress. It may be clarifying where our responsibility begins and ends.
The boundary I needed to set
I had tried to communicate that this task was causing me significant stress. I hinted that it was affecting my ability to continue comfortably in the role. But hints are easy to misunderstand, especially when the other person is focused on keeping the existing arrangement in place.
I realized I needed to be specific. My responsibility could reasonably end with writing up the service ticket, documenting the incident, and assigning it to someone else to contact the contractor and arrange service for the client.
That was the point where my ownership ended. Continuing to manage every interaction between the client and the contractor was not a natural extension of documenting the problem. It was a separate responsibility, one that needed to be assigned clearly to someone with the time, authority, and expectations to manage it.
Writing this boundary down was difficult. I worried that my manager would be disappointed. I worried that she would interpret it as unwillingness to help. I worried that I would be pressured into backing away from what I had said.
Those fears were not imaginary. In previous conversations, I had found myself compromising my needs before I had fully explained them. A verbal conversation could quickly become a negotiation in which the other person reached a conclusion before I had finished making my point.
So I put the boundary in writing.
Why written boundaries can help
A written boundary is not automatically better than a conversation, and it should not be used to avoid every uncomfortable discussion. But writing can provide space for clarity.
When we write, we can separate the facts from the fear. We can describe the current process, explain its impact, define what we can take responsibility for, and identify what needs to happen next. We can reread our words before sending them. We do not have to respond to pressure in real time.
Writing also creates a shared reference point. Instead of relying on what each person remembers from a tense conversation, there is a clear statement of what was requested and why.
The goal is not to build a case against someone. The goal is to make the situation easier to understand.
Disappointment is not an emergency
What frightened me most about setting the boundary was not necessarily the boundary itself. It was the disappointment I imagined it would cause.
We often act as though another person’s disappointment is a problem we must immediately solve. We explain more than necessary. We apologize for having a limit. We offer alternatives we cannot sustain. We take back the no and replace it with a reluctant yes.
But disappointment is a normal human response. It does not automatically mean that we have been unkind, unfair, or irresponsible. Someone can be disappointed by our answer and still be treated respectfully.
That distinction has been freeing for me: I am responsible for communicating honestly and doing my part. I am not responsible for preventing every uncomfortable feeling my honesty may create.
The other person gets to decide what their disappointment means. They may need time to adjust. They may need to rethink a process. They may disagree with the boundary. Those are real possibilities, but they are not proof that the boundary was wrong.
A boundary is not an attack
There is a difference between setting a boundary and punishing someone.
“You are impossible to work with, and I refuse to deal with this anymore” is an attack. “I can document and assign the service ticket, but I cannot manage the contractor relationship after that point. We need a clear handoff for those follow-up interactions” is a boundary.
A boundary describes our participation. It does not require us to diagnose the other person, assign blame, or demand that they agree with our feelings.
Healthy boundaries can include a brief explanation, but they do not need a courtroom presentation. The more we argue for the legitimacy of our needs, the more opportunities we may create for someone else to debate them.
The responsibility that remains
Setting a boundary does not mean we get to abandon every difficult responsibility. At work, we still need to understand our role, communicate professionally, meet reasonable expectations, and remain open to solutions.
A boundary might lead to a conversation about priorities, staffing, timing, or compensation. It might reveal that a responsibility really is part of the job and that expectations need to be clarified. It might also reveal that the process needs to be redesigned.
We cannot control which of those outcomes occurs. What we can do is stop silently accepting an arrangement that is causing serious and sustained harm, then calling our distress a personal failure.
Disappointing people more often
I recently heard someone say that we need to disappoint people more often. The point was not to become careless or cruel. It was to understand that disappointment is sometimes the unavoidable result of telling the truth about what we can and cannot do.
That idea challenged me because I have spent much of my life trying to be easy to work with. I wanted to be dependable. I wanted people to know they could count on me. But dependability does not mean unlimited availability, and being cooperative does not mean giving away ownership of my time, energy, or peace.
Sometimes the most dependable thing we can do is state a limit before resentment or exhaustion makes the decision for us.
Letting the boundary stand
After I sent my message, I had to wait. The timing was not ideal. I sent it just before beginning a week-long vacation, so there was no immediate response or resolution. That gave my mind plenty of room to revisit the situation.
But the delay also gave my manager time to consider the boundary and think about a workable solution. I did not need to keep explaining myself from the middle of my vacation. I had said what I needed to say.
That is the practice I am working on now: allowing a clear boundary to exist without immediately rushing in to soften it. Letting another person think. Letting them be disappointed. Letting the next step belong partly to them.
We are not required to make everyone happy in order to be good people. We are not required to say yes in order to prove that we care. And we do not have to take responsibility for every feeling that follows an honest, respectful no.
Sometimes peace begins when we decide that someone else’s disappointment is not ours to carry.
0 comments