Intro: You start using the very method you hated
The scariest thing at work isn't just having a bad person around.
The scarier part is that bad habits get taught even though nobody ever trains you in them.
Say someone is being blamed by their boss for something that isn't their fault.
They vent about it like this:
Here we go again, blaming me.
Why am I the one getting the blame?
So far, fair enough.
It may well be unreasonable.
But a little later, in a different situation, the same person does this:
You took forever to pick up the phone.
What were you doing?
The high school student couldn't go home, you know.
The person on the other end wasn't in charge this time.
They had simply happened to notice where the key was, and shared it because someone asked.
If anything, they were the one who helped.
And still, the arrow of blame points at them.
In that moment, you can see it.
Ah, they've inherited it.
This person is now using the very "blame-shifting playbook" they hated, only on someone else.
They may not have learned the actual procedures yet.
But they've already learned how to blame, how to corner someone, the habit of catching people by phone, and the habit of pushing responsibility onto whoever is easiest to push it onto.
In this article, I'll call this inheriting the blame-shifting operating system.
1. It's not only work procedures that get inherited
At work, "inheriting" something usually has a positive meaning.
- Following the way your predecessor did things
- Carrying over existing rules
- Repeating a past success pattern
- Sticking to standard work practices
That's important.
But in real workplaces, things that aren't written in any manual get inherited too.
For example, things like these:
- When in trouble, catch people by phone
- Don't put requests in writing
- Ask whoever happens to be nearby
- Tell whoever is easiest to tell
- Blame the last person who touched it
- Treat the person who helped you as the one in charge from now on
- When you're about to get blamed, send the arrow toward someone else
- Say "let's take ownership ourselves" while never looking at your own side's gaps in how things are run
None of these are written down.
But people watch them closely in everyday conversations, scoldings, phone calls, meetings, and one-on-one talks.
And people learn what they watch.
2. What is the blame-shifting operating system?
The blame-shifting operating system is a way of thinking: when a problem happens, you look for a place to put the blame before you sort out the causes or how things are actually run.
Normal root-cause analysis goes like this:
What happened
Whose area of responsibility is it
Which step was missing
Where did the information get stuck
How can we prevent it next time
The blame-shifting operating system goes like this instead:
Who touched it last
Who didn't pick up the phone
Who knew about it
Who is easiest to say it to
Who can I tell to make this all go away smoothly
This isn't cause analysis.
It's moving the blame around.
What's especially dangerous is the pattern where the person who helped ends up being treated as the one responsible.
Happened to know
↓
Shared it because someone asked
↓
The problem got solved
↓
For some reason, treated as "the slow one"
This is the classic case of what I call "good-deed laundering," where someone's act of kindness gets turned into their fault.
3. Case study: how blame got swapped over a lost locker key
Let's take the locker key incident as an example.
How responsibility should have been divided
Issuing and handing over the locker key
→ The person in charge of issuing keys
Keeping the key safe after it's handed over
→ The person who received it
Handling the high school student, confirming identity, deciding whether they can go home
→ The on-site staff who host the students
Searching for and checking on a lost key
→ The person themselves + the on-site staff
Reissuing after the key is officially confirmed lost
→ A request to the person in charge of issuing
Divided like this, it makes sense.
The person in charge of issuing keys issues them and hands them over.
The person who receives the key looks after it.
The on-site staff check with the high school student and decide whether they can go home.
Once the loss is confirmed, a reissue is requested.
But with the blame-shifting operating system, it goes like this:
The high school student lost the key
↓
Can't go home
↓
Called the person in charge of issuing
↓
They didn't pick up
↓
The person in charge of issuing is slow
No, that's wrong.
The person in charge of issuing keys isn't someone who constantly monitors the student's pockets, the work site, places they went out to, desks, and piles of cardboard boxes.
If you say "you issue the keys, so you're responsible for tracking where they are after handover," the scope of responsibility grows without limit.
Lost it at the work site
Lost it while out somewhere
Took it home by mistake
Left it on someone's desk
Buried under a pile of papers
It's unreasonable to make all of that the issuer's responsibility.
So the problem isn't the key itself.
The problem is a mindset that tries to load onto the person who issued it everything else: managing the key after handover, handling things on site, deciding whether the student can go home, and being instantly reachable by phone.
4. "If you saw it, you should have checked" is the "whoever found it owns everything" bug
In workplaces like this, you sometimes hear:
If you saw it, why didn't you look into it back then?
This is dangerous logic too.
Seeing something and being obligated to investigate it are two different things.
Saw it
≠
Obliged to find out whose it is
Saw it
≠
Becomes the person who manages it
Saw it
≠
Becomes the person in charge of lost items
If you say "if you see anything, check it all," then everything in the workplace is fair game.
- Papers on a desk
- A key left lying around
- Abandoned cardboard boxes
- Something someone forgot
- Items in shared spaces
- Documents from other departments
If everyone started doing that, no work would get done.
So the correct way to put it is this:
When I saw it, no one had told me it was lost or asked me to check.
So I didn't think of it as something I needed to look into, such as whose key it was.
After I was contacted, I shared the place where I happened to have seen it.
That's enough.
5. Why do people do the very blame-shifting they hate?
This isn't just a matter of personality.
At work, people learn not only procedures but also how to behave.
New hires and junior staff watch not only how the work gets done but also
- who you ask
- who you have to tell to get things approved
- who it's "OK" to blame in the current atmosphere
- how to avoid taking responsibility
- when the boss gets angry
- what way of talking is less likely to become a problem
In other words, in a bad workplace, even things like these get taught:
A culture of catching people by phone
A culture of settling things verbally
A culture of leaving no record
A culture of pushing blame onto whoever is easiest to push it onto
A culture of correcting people in front of everyone, then making it about their attitude when they push back
Whether the person realizes it or not, it gets copied as workplace culture.
That's why someone who suffers from being blamed by their boss may do the same blame-shifting to someone else in another situation.
It's ironic, but it happens quite often.
6. Seen as social learning, it's pretty natural
In psychology, there's the idea that people watch what others do, see the results, and take those behaviors into their own repertoire.
It's generally called social learning or observational learning.
The same goes for the workplace.
Suppose a boss gets things done by
Speaking forcefully
Catching people by phone
Correcting people in front of everyone
Turning it into a question of attitude when someone pushes back
Leaving the scope of responsibility vague and dropping it on those below
and it isn't punished, and in fact works, then the people around them learn.
I see, so this is how people get moved around here.
Of course, not everyone copies it.
But when people are short on time, in a hurry, or about to be blamed themselves, they tend to reach for a familiar pattern.
That's why blame-shifting gets inherited.
7. It's not just policy that trickles down
In organizations, all kinds of things flow from top to bottom.
- Policies
- Goals
- Wording
- Criteria for decisions
- How meetings are run
- How to scold people
- Where to put responsibility
Bad management styles can flow from top to bottom too.
A boss puts pressure on a subordinate.
The subordinate takes that pressure.
Then, in another situation, that subordinate uses the same pattern on someone even easier to push around.
Blamed by the boss
↓
Feels like the victim
↓
In another situation, pushes the blame onto someone easy to say it to
↓
Blame-shifting gets reproduced
This is what it means to pass down the blame-shifting operating system.
8. Using "own it yourself" to blame others
What makes it even more troublesome is when "take ownership yourself" is used to blame others.
At work, you often hear lines like these:
Let's think of it as our own responsibility.
That's blaming others, you know.
Originally, taking ownership means finding the part you can actually change yourself.
But when someone with the blame-shifting operating system uses it, it turns into this:
Demands that others take ownership
Doesn't look at the gaps in how their own side runs things
When the arrow points at them, sends the blame to someone else
This isn't taking ownership.
It's blaming others while using the language of ownership.
In a case like this one, there's plenty that should have been looked at:
- Was the person managing their own key?
- Did the on-site hosting side confirm the student's identity?
- Did anyone search the surrounding area?
- How tidy was the desk area where the key was lying? (the Japanese workplace habit of keeping things sorted and in order, known as "2S")
- Did anyone put the request in a chat message instead of settling it only by phone?
- Did the whole thing go beyond the issuer's scope of duties?
Without looking at any of that, saying
It's the fault of the person who didn't answer the phone
isn't taking ownership.
It's just looking for a place to park the blame.
9. The pattern: scolded in front of everyone → you push back → "bad attitude" → a meeting
In a workplace with the blame-shifting operating system, this sequence tends to happen:
Scolded in front of everyone
↓
You respond with the facts and who is in charge of what
↓
Seen as talking back
↓
Told you have a bad attitude
↓
Suddenly called into a meeting
The problem here is that the original issue disappears.
What it should have been about was
- how the phone call was handled
- how the key was managed
- how the high school student was hosted
- the scope of the person in charge of issuing
- what the scope of duties was under your predecessor
But the moment you push back, it gets swapped for an evaluation of your character or attitude:
- You're not being receptive
- You have a bad attitude
- You can't think logically
- You're being defiant
That's why you shouldn't fight it out in front of everyone.
On the spot, say this:
If I answer only verbally here, we might end up with a misunderstanding, so I'll sort out the facts and the scope of what I handled and share them in chat later.
That's all you need.
10. How to stop the inheritance
10-1. Take it from spoken word back to chat
The blame-shifting operating system is strong in spoken conversation.
That's because it's easy to mix up the issues when you talk.
Didn't pick up the phone
The high school student couldn't go home
Key person
If you saw it, you should have checked
Do it properly from now on
All of these get mixed together at once.
So bring it back to chat.
To avoid misunderstandings, I'll write up the timeline and the scope of what I handled and share it.
10-2. Separate the issues
Even when it looks like a single matter, it actually contains several separate issues.
Handling the phone call
Issuing the key
Looking after the key after handover
Hosting the high school student
Searching when it's lost
Deciding whether they can go home
Reissuing
How things were run under your predecessor
Just separating these makes blame-shifting much weaker.
10-3. Lay out the timeline
A timeline is powerful.
16:25 Missed call
16:36 Missed call
16:39 Picked up and shared the place where I'd seen the key
Written like this, it becomes clear that framing the one-hour delay in getting home as caused by a slow phone response doesn't hold up.
10-4. Check how things were run under your predecessor
When your scope of responsibility is about to be suddenly expanded, check how it was handled under your predecessor.
Under my predecessor, too, I'm not aware that the person in charge of issuing also handled tracking where the key was after handover, dealing with the student when a key was lost, or deciding whether they could go home.
This is powerful.
Even if the other person says "well, you're the key person," you can turn it back:
Then did my predecessor do all that too?
Is that officially defined as part of the role?
Do I have the authority, the procedures, and the time for it?
10-5. If they still twist things, share it with the relevant people on CC
At first, sort it out between the two of you.
If they keep distorting it verbally, bring in the people involved.
This isn't an attack.
It's preventing misunderstandings.
To all concerned,
Regarding the locker key matter, I'm sharing the timeline and the scope of what I handled to prevent any misunderstanding.
In this form, it's not about personal feelings. It's a check on how things are run.
11. Templates you can use
11-1. When it first comes up verbally
Because this might lead to a misunderstanding if we only talk about it verbally, I'll write up the timeline and the scope of what I handled and share it.
If I could give just one answer right now, the scope of what I handle is issuing the locker key and handing it over.
My understanding is that looking after the key after handover is up to the person who received it, and handling the high school student, confirming their identity, and deciding whether they can go home are up to the on-site side.
I'll share the details in chat.
11-2. The message to send first
Regarding the locker key, I'd like to lay things out to avoid any misunderstanding.
The first contact to me was at 16:25. I picked up at 16:39 and shared the place where I had happened to see the key.
As a result, the key was found, and my understanding is that the high school student was able to go home.
For locker keys, the scope of what I handle is issuing and handing over.
My understanding is that looking after the key after handover is up to the person who received it, and handling the high school student, confirming their identity, and deciding whether they can go home fall within the on-site and hosting staff's scope.
So describing this as "the student couldn't go home because I didn't pick up the phone" doesn't match my understanding, either in terms of the timeline or the scope of duties.
From now on, in cases like this, it would help if you could leave the request in chat as well, not only by phone.
Once I can check, I'll reply within the scope of what I handle.
11-3. Version with relevant people on CC
To all concerned,
Regarding the locker key matter, I'm sharing the timeline and the scope of what I handled to prevent any misunderstanding.
[Timeline]
・16:25 Missed call to me from the on-site leader
・16:36 Missed call to me from a team member
・16:39 I picked up and shared the place where I had happened to see the locker key
・After that, the key was found, and my understanding is that the high school student was able to go home
[My understanding of the scope of duties]
For locker keys, the scope of what I handle is "issuing" and "handing over."
I understand that looking after the key after handover is the responsibility of the person who received it.
I also understand that hosting the high school student, checking with them, searching for a lost key, and deciding whether they can go home fall within the on-site and hosting staff's scope.
If a reissue is formally needed, I'm happy to handle it once I receive a request for reissuing.
In this case, I shared the place where I had happened to see the key after being told it was lost.
So describing it as "the student couldn't go home because I couldn't answer the phone" doesn't match my understanding, either in terms of the timeline or the scope of duties.
Going forward, to prevent misunderstandings, I'd appreciate it if requests like this could be left in chat or similar as well, not only by phone.
Once I can check, I'll reply within the scope of what I handle.
11-4. When the issuer's responsibility is stretched without limit
Being in charge of issuing doesn't mean I understand myself to be fully responsible for tracking where a key is after handover or for the first response when it's lost.
If that counted as the issuer's responsibility, it would extend to keys lost at the work site, while out somewhere, or while in the person's own possession, so the scope of responsibility would grow without limit.
My understanding is that my scope is issuing, handing over, and reissuing after a formal request.
11-5. If they still put the responsibility on the issuer
If you want to run things so that dealing with a loss after handover, confirming identity, and deciding whether someone can go home are all part of the issuer's responsibility, the scope would extend beyond issuing work, so I'd like to ask you to change the setup so that the on-site side handles issuing and managing locker keys itself.
Please sort out my scope as issuing, handing over, and reissuing after a formal request.
11-6. When it gets turned into a question of attitude
Rather than an impression of my attitude, I'd like to confirm which part of my work you're pointing to.
11-7. When it becomes a meeting
Is this about how the phone call was handled?
Is it about managing the locker key?
Is it about hosting the high school student?
Or is it about the scope of duties from when my predecessor was in the role?
First, I'd like to separate the issues and confirm them one by one.
12. Good inheritance and bad inheritance
Inheriting things isn't bad in itself.
Good inheritance looks like this:
Keep the procedures
Make roles clear
Define each person's scope
Decide the conditions for escalating
Leave a record in chat
Make sure the next person doesn't get lost
Thank the person who helped you
Bad inheritance looks like this:
Catching people by phone
Cornering people verbally
Mixing up who is responsible for what
Blaming the last person who touched it
Making the person who helped the cause of the delay
Correcting people in front of everyone, then making it about their attitude when they push back
Aiming the blame you had pinned on you at someone else
Good training gets people to inherit procedures.
Bad training gets them to inherit blame-shifting.
That difference is huge.
13. Wrap-up: The people who notice get worn down. But they're also the ones who can build the fence.
If you can't see blame-shifting being inherited, you can't see it.
Most people only look at the trouble right in front of them.
No key
Can't go home
Called
No answer
In trouble
Slow
They stop there.
But people with strong self-awareness (the ability to watch your own thinking from the outside) look deeper.
Isn't it up to the person to manage it?
Isn't it up to the on-site side?
Isn't this outside the issuer's scope?
Wasn't it run differently under my predecessor?
Aren't we blaming someone who just happened to help for the delay?
Isn't this the same pattern of blame-shifting the boss uses?
That's why they notice.
And because they notice, they get worn down.
But you don't have to try to educate everyone about all of it.
There's only one thing to do.
Turn it into a fence.
Keep the timeline
Separate the scope of duties
Separate the person's own responsibility from on-site handling
Bring it back from the phone to chat
Check how things were run under your predecessor
If they still twist things, share it with the relevant people on CC
That's enough.
Left alone, a bad workplace culture gets inherited.
So we change what gets inherited.
Instead of blame-shifting, let them inherit
timelines, roles, records, and boundaries.
That is the defense against good-deed laundering.
