At work, there's sometimes one person who always seems to be in a bad mood.
At first, you might think:
"Maybe they just take things the wrong way." "Maybe we just don't click." "Maybe it's their skills or their attitude."
But if you watch for a while, you may start to see something different.
The person before them got worn down the same way. Their replacement burned out fast. There was a stretch when the pressure was on you. When you pulled back, the load slid onto someone else. And now that person is getting short-tempered too.
At this point, it's no longer about one particular person.
It's a structure where vague, undefined work keeps flowing to whoever will take it.
Fuzzy Work Is Only Defined Inside Someone's Head
Every workplace has fuzzy requests.
"Pull together where we are and what the issues are." "Tidy this up, make it look good." "Can you take a look at this?" "Just make it work somehow." "Give me the big picture." "It's not that the share is going up, it's more like..."
The person saying it may feel like they know exactly what they mean.
But for the person receiving it, there's no way to tell.
Who is this for? What decision is it meant to support? How far should I take it? What counts as done? Who makes the final call? What am I not supposed to do? How detailed should the summary be?
The work arrives with all of that left undefined.
So the receiver has to work out the requirements on their own.
In other words, the receiver is doing the defining work that the requester never did.
If it were just 1 request, that's fine. But when it happens every time, people burn out.
The Load Piles Up on the "Mom Type"
Fuzzy requests don't land on everyone equally.
For some reason, they drift toward the people who look like they'll catch them.
People who read between the lines. People who can turn a vague idea into actual tasks. People who don't stir up trouble. People who are good at filling in the gaps. People who can't help looking after others. People who end up absorbing everyone's feelings too.
Work keeps flowing to people like this.
On a good day, you could call them "caring and dependable." On a bad day, they're the dumping ground for undefined work.
Once requesters start learning, without quite realizing it:
"This person will pick up on what I mean." "This person won't get angry and will take it." "This person will figure something out." "This person will turn it into real tasks."
the load concentrates on that one person.
And then that person nears their limit.
Someone who started out responding kindly gradually begins to ask:
"Who said this?" "What outcome are you hoping for?" "Who is this for?" "What exactly do you mean by 'how'?" "How far should I go with this?"
This isn't rebellion.
They've simply stopped accepting something undefined as it is.
Ask for Requirements, and the Requester May Get Irritated
Checking the requirements is normal, of course.
Who is it for? What's the goal? How far do we go? What takes priority? What's off limits? Who decides?
If you don't check these, the work gets overturned later.
But if the person throwing out the fuzzy request doesn't realize their own request is undefined, being asked these questions can feel like being cross-examined.
"Why don't you get it?" "Why are you asking about so many details?" "Anyone would understand this." "That's not the point." "That's not what I meant."
And so the irritation and pressure show up.
In other words, the receiver isn't the problem.
By starting to define the requirements, the receiver just exposed what the requester hadn't defined.
A fuzzy request only works because the receiver fills in the gaps. Once they stop, the requester's undefined thinking is right there in the open.
If getting irritated is the response to that, the structure is in pretty bad shape.
When One Person Steps Back, It Moves to Someone Else
The scary thing about this structure is that it keeps going just by switching who catches the work.
The load piles up on the previous person. They quit. It piles up on their replacement. They wear down too. Then it moves to someone else. That person starts replying with requirement questions. And the pressure shows up again.
Seen like this, it's pretty clear.
The problem isn't any particular person.
Fuzzy, undefined work is flowing to whoever happens to be willing to take it at that moment.
So when you step back, it moves to someone else. That person starts to burn. And the people around them get gradually more irritable.
This isn't about anyone's personality. It's about how the work flows.
The Moment You Realize "It's Not Just How You Take Things"
While you're the only one being worn down, it's hard not to doubt yourself.
Am I overthinking this? Is my attitude the problem? Am I just not good enough? Do I just not click with this person?
But once the same pattern shows up with other people, things look different.
The previous person went through it. The temp who filled in went through it. You went through it. Now someone else is going through it.
By this point, it's happened often enough to be a pattern.
So it's quite likely this was never "your problem." It was a structure that makes one person carry what's undefined.
Realizing this makes it easier to protect yourself.
It wasn't your fault. You were simply being used as the catch-all. So you stepped back. And when you did, it flowed to the next catch-all.
Seen this way, you don't have to shoulder it all as your own responsibility.
Even Kindness Burns When It Turns Into Work
In workplaces like this, even kindness is risky.
Say a new hire did a task well.
"The scan came out clean." "It was straight and easy to read." "There wasn't even a shadow." "I'd like to tell them that." "If you don't mind, it might help to share it, optional of course."
Normally, that's a nice thing.
You praise what's good. You give the person a small win. You give everyone else a useful example.
But once it goes through a manager or a boss, the kindness can change shape.
"Optional sharing" becomes a de facto work order. "What went well" becomes a checklist item. "Praise" becomes a basis for comparison. "A reference" becomes standardization. "It might help to share it" becomes "whoever suggested it owns it."
When that happens, you've added to the new hire's workload. You meant to praise them, and the burden lands on them. Kindness gets laundered into duties and accountability.
That's why, in an unpleasant workplace, you have to choose carefully how your kindness travels.
Give praise directly to the person. Give managers only a completion report. Leave standardizing and sharing until time, roles, and responsibility have been formally decided.
Sometimes protecting kindness means not handing it over to the organization.
"Optional" Isn't Optional When It Comes Through the Boss
You might think that writing "optional" makes it safe.
But the moment it passes through a boss or a senior colleague, it may not look optional to the person receiving it.
"My boss told me to." "My senior said so." "It feels like I should do it." "Saying no would look bad." "Isn't this basically an order?"
For new hires and junior staff especially, an "optional" request that comes from above weighs a lot.
Who it came from matters more than whether the wording says optional.
So even with good intentions, you need to be careful.
"It might help to share this." "It'd be nice if you could do this, optionally." "If you'd like, put it together."
Phrases like these can sometimes just create more work.
Praise meant for someone's benefit becomes a burden on them. That's best avoided.
Set the Scope Before You Take On Training
Training is the same.
"Teach the new person." "Keep an eye on them, you know, nicely." "Get them up to speed." "Make sure they can actually be useful."
Requests like these are risky.
How well do they need to be able to do the job? Who decides whether they've passed? How much do I teach? Where do I stop and let them handle it themselves? What are they not allowed to do? By when do they need to be able to do it?
If you take on training with all of that left undefined, the trainer burns out.
And later you might hear:
"You didn't need to have them do that much." "I wanted you to teach them more." "Why can't they do it yet?" "Isn't this just dumping it on them?"
So when you're asked to train someone, the first thing to say back is this:
"What level of ability should be the goal?" "How far should I teach?" "Who should I check with when a judgment call comes up?" "I'd like to agree on what's left to them and what I'll oversee."
This isn't passing the buck.
It's defining the requirements for training.
What a Healthy Workplace Looks Like, and What an Unhealthy One Looks Like
The same kind gesture flows differently in different workplaces.
In a healthy workplace, it goes like this:
"The new person's scan was really clean." "Nice. I'll let them know." "If there's room, I'll use it as a reference later."
And that's the end of it.
Praise arrives as praise. An observation stays an observation. Sharing stays optional. If it does turn into extra work, someone properly decides the time, roles, and who's responsible.
In an unhealthy workplace, it goes like this:
"Then let's standardize it." "Then share it with everyone." "Then let's make it a checklist item." "Then who's going to manage it?" "Then whoever brought it up can handle it." "Then have the new person write it up too."
Kindness gets converted into a management metric or extra work.
If that keeps happening, people stop offering kindness. They stop praising. They stop making suggestions. They stop improving things.
If trying to make the workplace better makes you burn out, nobody will try.
Switch to Observer Mode
Once you can see this structure, you don't have to force yourself to rescue anyone.
Of course, when you see someone struggling right in front of you, you want to help. But if you step in, you become the catch-all again.
Instead, switch to observer mode.
Who got the fuzzy task? What was undefined? Who replied with requirement questions? At what point did the requester get irritated? When did the receiver start to tire out? Is the reason the work isn't moving the worker, or the fact that it was never defined?
Just watch all of this, calmly.
This isn't gossip. It's a structure log.
If people are getting irritable one after another, that's very valuable observation data.
How to Write a Structure Log
If you're going to keep records, it works better to write down the structure rather than your feelings.
For example, like this:
Date:
Who:
What came in:
What was undefined:
What the receiver asked:
How the requester reacted:
Result:
Impression:
In practice, it might look like this:
Date: 6/__ (June)
Who: Person A
What came in: Asked to summarize the current situation and issues
What was undefined: Unclear who it's for, what the goal is, and how detailed it should be
What the receiver asked: "Who is this for?" "What outcome do you want?"
How the requester reacted: Somewhat irritated, nitpicked the exact wording of the questions
Result: The working conditions never got clarified, and the receiver was left dissatisfied
Impression: Looks less like a personal issue and more like undefined work piling up on one catch-all person
Written like this, it's an observation rather than just a complaint.
What matters isn't "who got annoyed." It's which undefined thing flowed to whom, and how.
The Point of Keeping Records Is Defense, Not Attack
You don't keep a structure log to attack anyone.
You keep it to protect yourself.
Once you can see the same pattern happening again and again, you no longer have to blame yourself. The next time a similar request comes in, you can answer with requirement questions. You can tell which tasks you shouldn't take on. You can keep yourself from sliding back into the catch-all role. It can also help you decide whether to change jobs or departments.
With records, you can look at the structure instead of your emotions.
Instead of "something just feels off," you can say: "The undefined parts keep getting pushed onto the receiver every time." "When we ask for requirements, the requester gets irritated." "When the catch-all person changes, so does the target of the pressure."
That's quite powerful.
Not Rescuing Is Also a Necessary Kind of Defense
When people around you are burning out, you want to help.
"You could sort it out this way." "I'll do it for you." "Let me put it together once." "I'll teach the new person too."
But if you keep doing that, you become the handyman again.
The translator of the undefined. The trainer. The firefighter. The go-between. The person who owns whatever they suggested.
And then you burn out too.
So if you do help, you need to set limits.
"I can do that much." "Once the goal is set, I can sort it out." "If you name who decides, I can move it forward." "Beyond that, please have someone above decide."
That's enough.
Don't rescue everything. Don't carry everything. Support only the part where requirements have been given.
That's what defense looks like.
People Don't Get Irritable Because They're Weak
When someone gets irritable, they can get labeled "emotional."
But if you keep taking on undefined work, getting irritable is natural.
Every time, you guess what the other person means. Every time, you fill in the background. Every time, you build the working conditions yourself. Every time, you brace for changes after the fact. Every time, you get picked apart over details. Every time, another fuzzy task shows up.
Anyone would get tired of that.
Someone who started out asking politely gradually sounds tenser. Their questions get sharper. Their expression darkens. Their replies slow down. They start to pull away.
That doesn't mean their character got worse.
The structure is wearing them down.
Summary: If People Keep Burning Out in Turn, Look at the Structure
When someone at work is irritable, it's best not to put it down to their personality or attitude right away.
If the same kind of irritability is showing up in other people one after another, it's probably the structure.
The previous person burned out. The stand-in burned out. You burned out. Someone else is starting to burn out.
Then the thing to look at isn't any individual.
Who is the undefined work flowing to? Who is taking over the job of defining requirements? Who is absorbing the emotions? Who is dealing with changes after the fact? Whose kindness is being turned into work?
Look there.
And make sure you don't become the catch-all yourself.
Give praise directly to the person. Report only what's necessary to managers. Take on training only after the scope is set. Don't route optional sharing through the boss. Answer undefined requests with requirement questions. If you help, help only within a defined scope. Watch the burning structure from the side, and keep a record.
This isn't cold.
It's a very practical way of working that protects your own life and time.
