The short version
What wears you down at work isn't simply having a lot to do.
What really wears you down is having no authority to decide anything, yet getting stuck with the messaging, the blowback, and the cleanup.
A boss or senior colleague leans on you and says, "Do it this way." But they won't explain it to the other department themselves. So you pass the message along. The other department pushes back. And suddenly it's "You explained it badly."
When this keeps happening, it's easy to start wondering, "Is it my delivery? Am I just weak?" But look at it as a structure and it's a very different picture.
The problem comes before your delivery. The decision-making, the responsibility for running things, the responsibility for explaining, and the responsibility for passing the message on are sitting in the wrong places.
This article walks through why people who get pushed around end up looking like "cheap people to move," why the colleagues who listen to you still can't fix the root problem, and how to become someone who tidies things up without soaking up everyone else's responsibility.
1. What was actually going on
The usual chain of events goes like this.
The pushy person makes the decision
↓
They tell you, "Go tell them" or "Call them"
↓
You pass it on to the other department
↓
The other department raises practical concerns
↓
Instead of "my instruction was bad," the pushy person says "you explained it badly"
↓
You become the one who takes the blame
This isn't a simple "miscommunication."
It's a setup where the messenger ends up carrying the responsibility, like a carrier pigeon blamed for the letter.
The person who decided is someone else. The people who run it day to day are someone else. Yet the person stuck in the middle somehow ends up absorbing all the friction and all the blame.
It would be harder not to get worn down in that position.
2. Why it makes you so angry
The reason is simple.
You're thinking, "Then say it yourself."
If someone leans on you and says "do this," they should be the one to explain it to the other department. If the other department pushes back, they should be the one to answer for it.
In reality, though, they pass the pressure down to you and never take the pushback themselves.
Say you warn them in advance:
If we send it out as is, it'll probably cause a problem with XX.
And they respond:
Did I ask you to bring that up? Just say it. Hurry up and call them.
Then the pushback comes, just as you predicted, and they say:
You explained it badly.
This is a structure where your risk warnings get shut down, only the job of carrying it out is handed to you, and responsibility for the result is stuck onto you afterward.
3. Where is the manager?
Stopping this kind of structure is supposed to be the manager's job.
Here's what a manager should be sorting out:
- Who decides
- Who is responsible for running it
- Who gets the other department to agree
- Who explains when there's pushback
- Whether the person under them is being left with the blame and nothing else
When that isn't working, the person in the middle on the front line becomes the shock absorber.
People who use pressure come on strong with those who are easy to lean on. But with difficult people, or people more powerful than themselves, they don't push directly.
As a result, the person who received the pressure gets stuck standing between the other department or the customer and the boss.
This isn't "tough coaching." It's closer to picking a target and sending the pressure down to them.
4. Plenty of people will listen, but none of them can fix the root problem
Sometimes coworkers or bosses will hear you out.
That sounds rough. Are you okay? That must be hard. Don't push yourself too hard.
That helps. It's a valuable place to let your feelings out.
But it won't solve the root problem.
That's because the root problem isn't feelings. It's how responsibility is assigned.
What you actually need to settle is:
- Who takes responsibility for the pushy boss's instructions
- Who explains when the other department pushes back
- How to stop soaking up the messenger's share of the blame
- How to fix the gap between who decides and who is responsible
You can't count on the people around you to change all of that. So the only option is to change how you operate on your side.
Instead of treating the people you confide in as problem-solvers, use them for these three roles.
1. A reality check
Ask them something like:
This isn't only about how I put it, right? This setup is just prone to blowing up?
2. A witness
Keep them casually in the loop:
I got this instruction, and these are the concerns, so I'm going ahead this way.
3. A place to vent
Let out the anger, the exhaustion, the "ugh, I'm done."
If you expect your confidant to fix the root problem, you'll only wear yourself down further. It's safer to limit your expectations to a reality check, a witness, and emotional release.
5. Why you end up looking like a "cheap person to move"
From the point of view of the person applying pressure, a track record like this makes you look cheap to move:
- You act the moment you're told
- You don't say no
- You don't push back
- You clean up afterward
- You absorb responsibility even though you aren't the one in charge
- A verbal request is enough to get it handled
- You even take on the annoying cross-department coordination
That isn't really a personal weakness. It's partly the result of your past self-protection habits being learned by the other person.
For example, maybe it used to go like this:
You get a long, nagging lecture
↓
Arguing back only drags it out
↓
You get blamed even more
↓
So you say "Yes..." to end it quickly
↓
You move right away
↓
You clean up afterward too
In the short term, that's a reaction that protects you.
But from the other side, here's what gets learned:
Apply pressure
↓
The other person moves
↓
Even if there's friction, they clean up the mess
↓
Fine to throw it at them next time too
In other words, your defensive reaction becomes a success story for them.
To get out of this, it works better to change the signals the other person sees than to try to change your personality.
6. Logs alone won't make it costly enough for them
From your side, it feels like you're already doing something about it.
- You keep a written log
- You escalate things upward
- You send the troublesome ones back
- You warn them about possible pushback
- You're no longer moving cheaply
Even so, to them it can still look like "if I push, it moves."
Why?
Because you and they define "cost" differently.
Your wear and tear isn't a cost to them. And if they aren't the ones answerable for the explanation, you writing a log is still cheap for them.
What actually costs them something is things like:
- Nothing moves forward unless they decide
- They have to explain to the other department under their own name
- Pushback from the other side comes straight back to them
- Their superiors and others involved are copied, so everyone can see the instruction
- They're forced to choose the priorities themselves
- A vague instruction can't pass through as vague
So more important than just writing logs is handing the decision back.
7. The old pattern and the new pattern
The old pattern
You get a long, nagging lecture
↓
"Yes..."
↓
You move right away
↓
It turns into a conflict
↓
You clean up
↓
It gets thrown at you again next time
This is extremely convenient for the person applying pressure.
The new pattern
"Understood."
↓
"I'll pass this to them as a request."
↓
"I'll check their concerns and the conditions for doing it."
↓
"If they object or set conditions, I won't decide on my own. I'll bring it back."
↓
"After the call, I'll share what was said in writing."
Done this way, you are still doing the work. But you aren't absorbing the responsibility.
That's the key point.
8. The basic rule: "I'll move, but I won't absorb"
Here's the basic rule going forward.
I'll move, but I won't absorb. I'll tidy things up, but I won't decide. I'll pass things along, but I won't make promises. I'll write it down, but I won't stand in for the person in charge.
Put even more briefly:
I'll tidy things up, but I won't blur who is responsible for what.
That's it.
What you want them to think is:
If I talk to this person, they'll sort things out. But they won't blur the line of responsibility.
You go from "the person who'll do everything if asked" to "the person who handles things fast but doesn't absorb responsibility."
9. When you go to another department, turn the "order" into a "request"
If you carry the pressure over as is, things blow up.
Here's the bad version:
XX says to do this, so please take care of it.
This makes you look like the one giving orders. It's more likely to draw pushback from the other department. And once the pushback comes, it's easy for them to say "you explained it badly."
Here's the safe version:
On the HR side, we'd like to move in the direction of XX. That said, your department would be the one running it, so please let us know about any concerns or conditions. If it's difficult, we'd like to find out how far you can go.
That isn't an order. It's a check-in.
You respect the other department's area of responsibility while still making your request.
10. How to respond to the pushy person
Don't over-explain to someone who applies pressure. Some people simply don't listen to risk predictions.
The basic wording can be this:
Understood. I'll tell them it's a request from HR and check their practical concerns and the conditions for doing it. If they object or set conditions, I won't decide on my own. I'll bring it back to you.
If they tell you to call, do this:
Understood. I'll call them. To avoid misunderstandings, I'll send their answer by email after the call.
So you make the call. But anything said out loud goes back into writing.
11. A sample log after a call
Write it up right after the call.
About the matter you asked about, I called the XX department. Their answer was as follows.
- XX is fine
- YY is difficult in practice
- As an alternative, ZZ would work
Could you please decide on the next step?
What matters here is not turning it into your own decision.
Instead of "I think we should...," split it into:
- What the other side answered
- What concerns they raised
- Their alternative
- Who makes the next decision
12. A phrase for handing priorities back
When more work is about to be shoved onto you, ask:
I can do that, but which should take priority, A or B, which I'm working on now?
Or:
If I do this right away, which should I push back, A or B?
If you just say "I'll do it," you've absorbed it. If you make them choose "what do we drop if we do this," the responsibility for priorities goes back to them.
13. A phrase for handing decisions back
When a decision is about to be pushed onto you, reply like this:
If I make a promise on my own judgment, we'll end up with a mismatch later, so I'll take anything that needs a decision back to XX for confirmation.
To the other department, you can say:
If I decide on my own, it may not line up later, so could you also talk to XX? I'll share it from my side too, but please have XX confirm the final decision.
This isn't running away.
You're simply handing the decision back to the person who has the authority to make it.
14. Separate light coordination from heavy decisions
You don't have to send everything back upward.
Light coordination you can handle yourself:
- Scheduling
- Tidying up the wording of messages
- Gathering the other department's concerns
- Sorting out conditions
- Simplifying procedures
- Writing the log
Heavy decisions go back:
- Anything involving the other department's responsibility for running things
- Promises likely to cause trouble later
- Cases where another department is pushing back
- Changes to priorities
- Anything that needs the responsible person to explain
- Anything you have no authority over
In short:
Do the light coordination. Send the heavy decisions back.
This is how you set the boundary of responsibility straight again.
15. Keeping your distance matters a lot
The biggest reason you stopped getting worn down isn't just that you got better at the work.
Cutting down on contact made a big difference.
A dangerous person doesn't wear you down with one-off instructions alone.
- Pressures you verbally
- Doesn't listen to concerns
- Later turns it into a problem with how you explained
- Decides what's going on inside your head
- Won't state their criteria for judging
- And still loads the responsibility onto you
Contact with someone like that piles unfinished tasks up in your head.
So the basic policy can be this:
Don't get close. When something comes, convert it calmly. Hand decisions back. Keep a record. Don't carry it.
Keeping your distance isn't just avoiding someone because you dislike them.
It's practical self-defense:
- Closing the input channel with the highest accident rate
- Reducing blame-shifting through verbal pressure
- Reducing material for rumination
- Weakening their learned belief that "if I push, it moves"
16. Not "running away" but "putting responsibility back where it belongs"
Sometimes you send troublesome matters back to the person who decides or is responsible.
You might feel like that's "running away." But structurally, it isn't.
It's putting the scope of responsibility back where it belongs.
What's actually dangerous is taking everything on just because you're capable.
- The other department's complaints
- The pushy person's sloppy instructions
- Responsibility for running things
- Last-minute corrections
- Responsibility for how it was explained
If you absorb all of this, you become the office fixer. And you only hear about responsibility when something goes wrong.
So it's fine to operate like this:
Organize what you can decide yourself. Send back what you can't take responsibility for to the decision-maker. Leave the other department's responsibility for running things with that department.
17. What it means that you're avoiding the pushy boss too
People who use pressure tend to get avoided by those around them.
- People don't pick up the phone
- Replies get slower
- They'd rather settle things by email
- "Oh, it's that person again"
- People avoid dealing with them directly
Sometimes you find you're doing the same thing with that person yourself.
That doesn't mean there's something wrong with your character.
When you deal with them directly, you get more friction, last-minute changes, and blame-shifting than actual sorting-out of information, so you're lowering the cost of contact.
It's a natural defensive reaction toward someone you don't trust.
However, if you avoid them completely, you risk being written off as "slow to respond" or "not reporting, contacting and consulting" (the Japanese workplace habit of keeping your boss in the loop).
So instead of
Responding instantly because of trust,
go for
Minimum contact backed by a paper trail.
Don't run away from the work itself. But anything said out loud, any blame-shifting, and any vague instruction goes back into the log.
18. The "tidy up, but don't blur who's responsible" approach
This is where I've ended up.
I tidy things up. But I don't overreach on decisions. I don't over-promise. I don't blur the line of responsibility. Anything said out loud goes back into the log.
This is different from moving people with pressure.
The pressure type goes like this:
Apply pressure while staying vague. If the person moves, it's a success. If there's a conflict, it's about how it was explained.
The tidying-up type goes like this:
Separate the request, the concerns, the conditions, who decides, and who is responsible for what. Make the likely sticking points visible. If a decision is needed, send it back.
That's a big difference.
19. Research notes: related fields
This isn't just a story about personality. It's close to research on organizational psychology, workplace bullying, psychological safety, and organizational learning.
Workplace bullying and workplace harassment
In workplace bullying research, features such as repetition, duration, escalation, imbalance of power, and difficulty defending oneself are treated as important.
What matters here is not only a single harsh remark, but the target being pushed into a position where defending themselves is hard.
Abusive supervision
Abusive supervision is a research field that deals with sustained hostile behavior and unfair treatment by a supervisor.
Behaviors such as insults, blame-shifting, hostility, bringing up past failures, and undermining trust are described as harming employees' job satisfaction and stress levels, raising their intention to quit, and fueling resistance behavior.
Psychological safety
Psychological safety is a state in which raising questions, concerns, mistakes, or opposing views doesn't carry an excessive interpersonal risk.
In this case, without psychological safety, it goes like this:
If I push back, it drags on. If I voice a concern, I get yelled at. So I just say "Yes..." and deal with it.
In other words, low psychological safety speeds up the process of becoming someone who moves cheaply.
Organizational citizenship behavior and citizenship fatigue
Helping beyond your formal duties can benefit an organization. But when it's demanded as pressure, or goes on without reward, it leads to exhaustion.
When a "capable person" keeps taking on extra coordination, cleanup, and responsibility absorption, the holes in the organization end up being filled with that person's stamina.
Single-loop learning and double-loop learning
Single-loop learning means fixing only the surface without changing the underlying assumptions. Double-loop learning means reexamining the assumptions, goals, and criteria for judgment themselves.
When their methods stop working, pressure-type people tend to think:
The other person is weak. Young people these days. They've got their heads full of AI and internet stuff. This is how I've always done it. So I'll push harder.
That's not reexamining assumptions. In other words, they haven't reached double-loop learning.
20. Don't chalk up your breakdown to "weakness" alone
If your health got worse in the past, you got flagged on a mental health check, or you gained weight, that was most likely not weakness but your body sending out danger signals.
If you're exposed for a long time to pressure outside your area of responsibility, last-minute changes, and blame-shifting, of course you'll be worn down.
At the time, your survival strategy may have been:
- If I push back, it drags on
- It's faster to just move right away
- If I absorb it, things calm down
- I have no choice but to clean up afterward
But if you keep that up, the other person learns that "this person moves if I push."
So what you should do now isn't blame yourself.
It's to stop making up the difference.
21. Why you're not worn down now
The reason you're not worn down now isn't that your mind suddenly turned to iron.
It's that you changed the structure.
- You don't carry the pushy boss's pressure as it is
- You turn it into a request, a concern, and a check on conditions
- Whatever needs a decision goes back to the boss or the other department
- You don't hold onto it yourself
- You cut down on verbal accidents
- You keep logs
- You don't go out of your way to get involved
- You reduce contact
Because of this, your brain can now judge:
This isn't something that costs me my own life.
Before, whenever you received pressure, it went like this:
I have to push this through. What if they push back? But I can already see they'll push back. They won't listen. If it fails, it'll be my fault.
Now it goes like this:
That's the other department's call. That's the pushy boss's call. That isn't a responsibility I carry. Anything troublesome goes upward. My part ends at sorting out the conditions.
That's why you're not worn down.
This is recovery, it's learning, and it's a redesign of the boundary of responsibility.
22. A template collection for real-world use
When you get pressured
Understood. I'll tell them it's a request from HR and check their practical concerns and the conditions for doing it. If they object or set conditions, I won't decide on my own. I'll bring it back.
When you're told to call
Understood. I'll call them. To avoid misunderstandings, I'll send their answer by email after the call.
When checking with another department
On the HR side, we'd like to move in the direction of XX. That said, your department would be the one running it, so please let us know about any concerns or conditions. If it's difficult, we'd like to find out how far you can go.
When the other side objects
About the matter you asked about, I checked with the XX department. They raised the following concerns.
- XX
- XX
As an alternative, they said ZZ would work. Could you please decide on the next step?
When handing priorities back
I can do that, but which should take priority, A or B, which I'm working on now?
When handing a decision back
If I make a promise on my own judgment, we'll end up with a mismatch later, so I'll take anything that needs a decision back to XX for confirmation.
When asking another department to consult the decision-maker
If I decide on my own, it may not line up later, so could you also talk to XX? I'll share it from my side too, but please have XX confirm the final decision.
When confirming your own scope of responsibility
I'll sort out and confirm what I can, but anything that needs a decision goes back to the responsible department or the decision-maker. To avoid misunderstandings, I'll keep a written record of what was confirmed.
23. Final conclusion
The essence of this problem isn't personality.
It's a problem of where responsibility sits.
People who use pressure look like they can move people in the short term. But in reality, they're often teaching people to defend themselves.
- Not picking up the phone
- Replying slowly
- Settling things by email
- Avoiding direct dealings
- Sending requests to whoever can coordinate
These are the side effects of pressure.
What you need to do isn't change the other person.
I tidy things up. But I don't blur the line of responsibility. I move, but I don't absorb. I pass things along, but I don't promise. Anything said out loud goes back into the log. If a decision is needed, it goes back to the decision-maker. I cut down on contact.
That's enough.
You don't have to fill the hole left by a missing manager with your own body.
Your part is to sort out the structure. Don't absorb the place where responsibility sits on your own.
That's the practical line for getting out from under people who move you with pressure.
A note before publishing
This article draws on workplace material, and it's risky to publish wording that could remind readers of real people or organizations as it stands.
If you publish it, the following is recommended:
- Replace in-group nicknames with "pressure-type boss" or "pressure-type manager"
- Blur the timing, department, and job details
- Don't name real companies, individuals, or specific cases
- Shape it as structural analysis, recurrence prevention, and self-management rather than a vent
- Keep it separate from your own specific situation regarding resignation, transfer, or job change
Candidate internal links
- The structure of "why-why-why" grilling and blame-shifting
- Boundaries for not getting worn down in a workplace without psychological safety
- A template collection for avoiding the fixer trap by handing decisions back to the decision-maker
- Why do people who move others with pressure get avoided by those around them
- How to normalize the scope of responsibility instead of "running away" at work
Research and theory keywords
- Workplace bullying
- Abusive supervision
- Psychological safety
- Organizational citizenship behavior
- Citizenship fatigue
- Single-loop learning
- Double-loop learning
- Defensive reasoning
- Role clarity
- Boundary management
- Responsibility diffusion
- Blame shifting
