Spot the Drag-In and Refuse to Take On the Responsibility
What this article is about
What tires you out at work isn't just a heavy workload.
What really grinds down your nerves is situations like these:
- Questions land on you even though you're not the department in charge
- You're told to handle something you have no authority to decide, just because you're the one on the ground
- Someone says "just five minutes," and suddenly you've been stuck there for 20 or 30
- Something said out loud turns, later, into "that's something you're supposed to handle"
- You passed a message along as a favor, and somehow you became the person in charge
- The pressure is different when other people are around and when it's just the two of you
This isn't a personality flaw where you're "bad at saying no."
Structurally, it's a pattern where someone skips the person actually in charge, the person with the authority, and the official channel, and pushes decisions and responsibility onto whoever happens to be nearby doing the hands-on work.
In this article, I'll call that being "dragged in."
And the trick to refusing without burning out isn't turning cold.
Stay friendly. But don't accept the responsibility.
That's it.
People who struggle to say no are often the ones who are good at their jobs
The people who get dragged in at work aren't low performers.
It's usually the opposite. They tend to be seen like this:
- Looks like they'll listen
- Looks like they understand the actual work
- Looks like they'll sort it out on the spot
- Looks like they can connect you with other departments
- Isn't a boss, so it's easy to lean on them
- Probably won't make a fuss if they say no
- Has done it for you once before
In other words, someone who gets dragged in a lot has been detected as a "handy place to dump things."
If you help out of pure goodwill, you'll be thanked at first. The danger comes afterward.
Once you accept even one request, it gets translated like this from then on:
Just happened to help once
↓
They did it last time
↓
Just ask this person
↓
This seems like their job
↓
This person is holding it up
↓
Why isn't this moving?
This is workplace goodwill laundering.
You built a bridge out of kindness, and later you're made the bridge's maintenance company.
First, sort it out: is this request really your job?
The first step in avoiding the drag-in isn't saying no on emotion.
First, sort the request.
There are only four things to check.
1. Is it my job?
2. Can I decide it within my own authority?
3. Is it coming through the official request channel?
4. Will there be a written record?
If even one of these four is missing, don't take it on right away.
The combination to be especially careful about is this:
It's not my job
+
I have no authority to decide it
+
It's being said out loud
+
They're saying "just a little"
That's pretty dangerous.
It may look like casual chat or a quick consultation, but later it can be converted into "something you heard," "something you're supposed to act on," or "something you're holding up."
Not "refusing," but "sending it back to the proper channel"
People who find it hard to say no tend to think that refusing means rejecting the other person.
But what you need at work isn't rejection.
What you need is to send it back to the person actually in charge, the person with the authority, and the channel that leaves a record.
Say another department's paperwork turns out to be wrong.
Here's the bad response.
I'll check on it from our side.
I'll contact them for you.
I'll ask about it.
It looks helpful. But at that moment, you start turning from a "go-between" into the "person who handles inquiries."
Here's the good response.
I'll send you the scanned data, so please contact the department in charge from here on.
You're still cooperating here. But you haven't become the person in charge.
Hand over the information. Don't hand over the responsibility.
Keeping those two apart is what matters.
The basic forms for saying no without wearing yourself out
To say no without burning out, don't try to improvise every time.
Turn your phrasing into templates.
1. Stop at "outside my authority"
Sorry, I can't make a decision on that, so please go through my department head.
That would be a call for my supervisor, so I can't act on it myself.
That's outside what I can decide, so please check through the official channel.
The point is not to over-explain your reasons.
If you explain at length why you can't, that's where they'll press you.
The strongest line is quite simple.
That's outside my authority.
This isn't a cold thing to say. It's the correct stopping line, organizationally speaking.
2. Send it back to the department in charge
I can't decide this here, so please check with the department in charge.
I'll share the data, so please work with the department in charge from here on.
The point of contact is the XX department.
What matters here is not saying "I'll check on it."
"I'll check on it" is a handy phrase, but a dangerous one.
Once you're the person who checks, you're next the person who gets chased for updates.
3. Move it from spoken word back to Teams or email
Things get dropped when they're just said out loud, so if it's needed, please send it on Teams.
I want to be sure I've got the details right, so could you send it on Teams?
Please send it to my supervisor so the people involved can see it too.
Requests made only out loud tend to change shape later.
Something that started as a "consultation" can turn into a "request," and then into "your assignment."
That's why you bring it back to a written record.
This isn't about suspecting the other person. It's about protecting your understanding and theirs.
4. Cut off long conversations
Sorry, I have something to check after this, so I need to go.
I can't break away from this task right now, so please use Teams if you need to.
I have something scheduled after this, so right now isn't a good time.
Be extra wary when someone says "just five minutes."
If it really takes five minutes, they can write the key points on Teams.
If it won't finish in five minutes, you shouldn't take it on the spot.
Here's an easy phrase to use.
I don't think this will take five minutes, so please send it on Teams.
If that feels a bit strong, you can soften it.
It's hard to give you an accurate answer right now, so it would help if you sent it on Teams.
How to handle people who corner you one-on-one
Some people at work are all smiles in front of everyone, then suddenly lean on you once it's just the two of you.
This type behaves like this:
- Jokey when others are around
- Turns into lecturing or interrogating when it's one-on-one
- Says "just five minutes" and holds you for a long time
- Presses the person on the ground about things that should be settled between bosses
- Wants to get their way but won't go through the official channel
- Watches your reaction to gauge how far they can push
The countermeasure for this type isn't clever talking.
It's not being alone with them.
- If you spot them in the hallway, pretend you just remembered an errand and walk off
- If they're about to catch you at your desk, don't keep your eyes off your screen for too long
- If a conversation is about to start, cut it off with "I have something to check after this"
- If it's important, make it "Teams, please"
- If it's about a decision, send it back with "please go through my department head"
- If it looks like it will physically drag on, move to a place where there are other people
Getting away isn't rude.
If the other person is skipping the official channel, you're just returning things to the official channel.
Separate your "smile" from your "responsibility"
When you say no at work, it gets easier if you separate your attitude from your responsibility.
Attitude: friendly is fine
Responsibility: don't accept it
This is the approach that wears you down the least.
On the other hand, these two patterns are the risky ones.
Tough attitude
Reject the responsibility too
This one easily leads to conflict.
Kind attitude
Accept the responsibility too
This one turns you into the office handyman.
What you're aiming for is this.
Soft attitude
Send the responsibility back to the official channel
For example, you can say it like this.
Oh, you're right, that's not correct.
I'll send you the data, so please check with the department in charge.
Sorry, I can't decide that, so please go through my department head.
Thank you. If you need to, please send it on Teams.
Don't show hostility toward the other person. But don't take on the responsibility.
That's not cold. It's sound work design.
Ways of saying no that wear you out, and ways that don't
Even when you're saying no either way, some ways wear down your nerves and some don't.
The way that wears you out
Sorry, but, um, I kind of feel like I shouldn't be the one doing this, and, well, I get the situation, but still...
This is exhausting.
The reason is that you're trying to convince the other person.
But someone who drags people in isn't necessarily talking in order to be convinced.
Sometimes they just want to hand it to somebody, anybody.
The way that doesn't wear you out
That's outside my authority.
Please check with the department in charge.
If you need to, please send it on Teams.
It's short. It's sorted. The route is clear.
This way, you're less likely to end up replaying it in your head afterward.
That's because it's already been processed on your end.
Something feels off
↓
Match it against the labels
↓
Use the template response
↓
Log it
↓
Done
If you can get into this flow, your nerves don't get worn down as easily.
Danger phrases you shouldn't say
People who get dragged in a lot use danger phrases without realizing it.
Danger phrase 1: "I'll take care of it on our side"
This is the doorway to being made the person in charge.
Say this instead.
I'll share the data you need, so please go to the department in charge from here on.
Danger phrase 2: "I'll check on it"
This is the doorway to being made the go-between.
Say this instead.
Please check with the department in charge.
Danger phrase 3: "I'll try asking, just in case"
This is the doorway to "you're the contact point."
Say this instead.
Please send it on Teams so you can check directly with the people involved.
Danger phrase 4: "I'm fine" / "It's okay"
Depending on the situation, the other person may take it as having received permission.
Say this instead.
It didn't hurt. Just in case, please tell me out loud from now on.
Or don't force a reply, and let it pass with the smallest possible reaction.
How to run a day when you're being dragged in all over the place
Some days, for whatever reason, you get dragged in several times in one day.
On a day like that, it's no longer a day for being nice to people.
It's a day for dodging the barrage of drag-ins.
Narrow down what you do.
1. Don't go looking for new tasks to pick up
2. Don't make another department's problem your own
3. Avoid one-on-one grilling by advisors and higher-ups
4. Send spoken requests back to Teams
5. Anything outside your authority goes through your department head
6. Scan files and share data if needed, but don't become the inquiry contact
What matters in this state isn't "being cold."
Smiling is fine. A nod of greeting is fine. Minimum cooperation is fine too.
Just don't take it on.
Hand over the information.
Don't take on the responsibility.
Don't make the decision.
Don't become the point of contact.
Just this makes a big difference in how much your nerves get worn down.
Keep a log: a shield so it doesn't turn into a problem for you
You don't need to start a fight right now.
But when something feels off, it's good to jot down a simple log.
A log isn't an attack. It's a record that protects your own sense of things.
This template is enough.
Date:
Time:
Place:
Person:
Others present:
What happened:
What was asked of me:
How I responded:
What happened afterward:
What felt off:
For example, you'd write it like this.
Date: June 10, 2026
Place: Inside the department
Person: Someone at the advisor level
Others present: Other team members were there
What happened: After tapping my shoulder several times, they said things like "this could count as power harassment" to the people around.
What was asked of me: Nothing clear. However, in the past I've been grilled one-on-one about hiring and decisions at the boss level.
How I responded: Only a minimal reply and a nod.
What felt off: Their attitude may differ between when others are around and when it's one-on-one.
That much is enough.
What matters is that you don't later think, "maybe it was all in my head."
A log is a shield for your future self.
Saying no doesn't break the work
Plenty of people feel guilty about saying no.
But at work, the people who are really in danger aren't the ones who say no.
The dangerous state is this:
- Nobody knows who's in charge
- Nobody knows who makes the decisions
- Nobody knows where the scope of this particular job ends
- It was all spoken out loud and there's no record
- The person who acted out of goodwill is made responsible afterward
- Someone puts pressure on a person nearby instead of going through the official channel
If you leave this state alone, the work of the whole organization starts to break down.
So saying no isn't slacking off.
It's the act of sending the work back to the right channel.
Wrap-up: not wearing yourself out is a matter of design, not personality
People who say no without wearing themselves out aren't mentally tough.
They aren't bouncing people off with sheer willpower every time, either.
What they do is quite simple.
Detect the drag-in
↓
Check whether it's my job and my authority
↓
If not, send it back to the proper channel
↓
If it was spoken, bring it back to Teams or email
↓
If needed, just keep a log
↓
Once it's over, stop thinking about it
In other words, the skill of saying no isn't the skill of getting angry.
It's the skill of sorting.
And the strongest person at work is someone like this:
Stays friendly.
But doesn't take it on.
Hands over the entry point.
Doesn't become the person in charge.
Stops at "outside my authority" when it's outside their authority.
Once you can do this, even on days when you get dragged in a lot, your nerves aren't worn down as easily.
You don't have to fight the dark arts of the workplace head-on.
Just send things back to the official channel before the spell goes off.
Quick one-liners you can use right away
Sorry, that's outside my authority.
Please go through my department head.
I can't decide this here, so please check with the department in charge.
I'll share the data, so please work with the department in charge from here on.
Things get dropped when they're just said out loud, so please send it on Teams.
I can't break away from this task right now, so please use Teams if you need to.
I have something to check after this, so I need to go.
It's hard to give you an accurate answer right now, could you put it in writing?
I can't decide that, so please have your supervisors check with each other.
The point of contact is XX / the XX department.
