When Managers Take Credit and Pass Blame: How Responsibility, Skill and Results Get "Laundered"

• The five types of employees a company said it didn't want
• The company sports day: a debate that started from the number
• Raising concerns constructively isn't "armchair criticism"
• Laundering responsibility, skill and results all at once
• Criticism from above gets turned into pressure on subordinates
• Why it keeps going even when everyone sees through it
• The minimum conditions for stopping it
• Summary

The five types of employees a company said it didn't want

At one company's training session for newly promoted staff, the president listed five traits of the kind of employee he didn't want people to become.

1. Clinging to past successes
2. Acting first and inventing the logic afterward
3. Shifting responsibility onto others
4. Handling things they don't understand as if they did
5. Playing the armchair critic while their own work is poor

Read from the other side, what the company really wants is people who update their thinking based on today's facts, act with a purpose and a hypothesis, own their decisions, treat the unknown as unknown, and turn feedback into actual implementation.

Yet sometimes the middle managers who are supposed to teach these values are the ones who reenact all five on the job.

Certifications, past departments, salary and job title are all part of a person's background. But if someone uses them in place of answering the issue at hand ("I hold the qualification," "I used to work in that specialist department, so I know," "I'm a manager, so I'm right"), that background stops being evidence and becomes a shield against being checked.

A title can justify the authority to decide, but it doesn't prove the decision is correct. Past experience is the same: if you can't explain how it connects to today's problem, it's just a display of credentials.

The company sports day: a debate that started from the number

A group of young employees took the lead in planning a company sports day. Having young staff speak up and bring others along was valuable for the organization in itself.

Behind the plan was the idea that "if people make friends at work, fewer of them will quit." Chances to socialize can raise a sense of belonging and may help people stay for a while. But that alone doesn't make the real reasons people leave disappear: overtime, how the work is set up, the relationship with their boss, and whether they feel able to speak up.

In a meeting, one manager firmly demanded, "Give me a number for how many working hours the sports day will save." But no one had designed how the sports day would be linked to productivity, over what period it would be measured, what it would be compared against, or which metric would be used.

The young employee pushed back with questions like these:

• If we put out a half-baked number, won't that hurt the credibility of the whole plan?
• Productivity is a side benefit, so why put it front and center as a number?
• Of the several side benefits, why single out productivity?
• If a number is needed, what exactly would we measure, and how?

These weren't acts of defiance. They were legitimate quality-check questions: confirming the purpose, the cause and effect, the way of measuring, and the criteria for choosing a metric.

But when the manager was asked for a concrete proposal, he said, "That's something we should all think about together." The person demanding a metric had no hypothesis about how to measure it.

It later came out that the department's policy included "improving work efficiency," and that the manager himself was struggling to produce a number for hours saved that he could report. People who took part came to share a suspicion: he wanted to manufacture an efficiency figure out of the sports day and fold it into his department's results.

We can't state his motive as fact. Still, the order of his actions looks like this:

Decide the purpose of the event → choose the effects → design the metric

is not what happened. What happened was:

I want a number I can use in my report → attach work efficiency to the event → leave the reasoning and the way of measuring to my subordinates

This isn't "logic first, then action." It's a KPI added after the fact, with the desired conclusion placed first. (A KPI is a numerical target used to judge whether something is working.)

Raising concerns constructively isn't "armchair criticism"

Another employee responded to this plan by first saying:

I think it's a really good thing that young staff speak up and bring others along. Since you asked for opinions, though, I'd like to share my concerns up front so the plan doesn't get shot down later.

Then they explained the limits:

• Friends at work can act as a short-term brake on people quitting
• But in an environment with 100 hours of overtime a month, friends alone won't keep people
• If raising a work problem with your boss gets it brushed off with "that's just the job," there's no point in speaking up
• In fact, having trusted friends could encourage people to leave together ("let's quit as a group")
• So we need to look not only at forming friendships but also at workload, discretion, how bosses respond, roles, psychological safety, and so on

This isn't commentary from the outside rejecting the plan.

A real armchair critic would say "a sports day is pointless" or "the plan is shallow" and stop there. This employee acknowledged the activity's value, narrowed the range of its effects, laid out the conditions for it to work and its side effects, and tried to lower the risk of the plan collapsing later.

In other words, it's criticism, but it doesn't stop at criticism. It's closer to a plan review, an audit of assumptions, a premortem (imagining in advance why a project might fail), or risk analysis.

Careful thinking doesn't mean agonizing for a long time. It means checking assumptions, breaking cause and effect into parts, considering other explanations, anticipating secondary effects, trying something small, and updating based on the results. People who get to a conclusion quickly may have a thought process that is hard for others to see. But a thought process you can't see isn't the same as no thinking at all.

Laundering responsibility, skill and results all at once

In a different task, documents addressed to a particular person had been sent back to the administrative department several times. But the fact of the first return was never passed on to the person in charge.

Believing the first document had arrived, that person sent the next one as a follow-up. They wrote the recipient, department and name clearly, indicated where to look, and added a clear process: "If there's a problem, return it with the reason; if not, throw away this cover sheet." The main document reached the intended person.

The person in charge had a staged plan:

1. Make the recipient and handling instructions clear on paper
2. See whether it actually reaches the person
3. If it doesn't, talk directly with the people involved and check the route
4. Track the follow-up date and the check date on a calendar

The manager, however, didn't properly check the plan, or the fact that he hadn't shared the information about the first return. He judged that the employee "doesn't grasp the current situation," "lacks problem-solving skills," and "needs to be trained as a leader from the basics." Then he declared that he would make them revise the materials 15 or even 20 times until they were done.

Three kinds of laundering can happen here.

Type	Before	After
Responsibility laundering	The manager's failure to share information	The subordinate's failure to grasp the situation
Skill laundering	Careful thinking and staged planning the subordinate already had	Skill the manager supposedly built from the basics
Results laundering	The plan, numbers and outcomes the young staff created	The manager's record of coaching and department policy achieved

Failures and shortfalls flow down to the subordinate, while the subordinate's skills and results are collected by the boss. It's a one-way filter.

"Laundering of responsibility, skill and results" is an analytical term I'm using in this article to explain how the workplace functions; it is not an established academic term. It does connect, however, to the self-serving bias (the tendency to credit success to your own ability and blame failure on outside factors) and to research on how destructive leadership affects subordinates.

Criticism from above gets turned into pressure on subordinates

Suppose the five problem behaviors the president described actually applied to a particular manager. What's needed then is self-examination.

But sometimes criticism from above gets turned into a problem the manager should teach subordinates, not something they themselves need to fix.

Leadership points out problem behaviors → Admitting it as my own problem would open up past management failures too → Redefine it as "my subordinates lack problem-solving skills" → I stay in the position of teacher, not someone who needs to improve → Make the subordinate revise things over and over, then claim it as the result of my coaching

This is a hypothesis. We can't state an individual's motives as fact from the outside. It isn't necessarily deliberate manipulation; the person may be defending themselves unconsciously.

Still, if someone concludes "you can't do it" before even hearing the subordinate's explanation, and doesn't change their premise when facts that contradict it come out, then the purpose of that exchange probably isn't to assess ability. The goal has become fixing the roles of teacher and student in place, rather than having a dialogue.

In this way, the philosophy the president offered as a prompt for self-examination is turned by a middle manager into a weapon for straightening out subordinates. Giving authority to teach to someone who runs against the philosophy becomes a breeding ground for the very behavior the company wants to prevent.

Why it keeps going even when everyone sees through it

This kind of laundering doesn't necessarily fool the people around it.

• The young employee pointed out, during the meeting, that the logic was added after the fact and that there was no hypothesis for measuring
• Other employees guessed at the fixation on the number and its link to the department's policy results
• The person in charge recognized the structure in which a failure to share information was converted into a lack of ability
• The president himself had described similar behavior as a trait of the "undesirable employee"

In other words, the pipes of the laundering process are quite transparent.

It still doesn't stop, because being seen through and being held accountable are two different things. As long as the same manager holds the power to evaluate, the power to train, and the power to control who gets what information, the practice can continue even when everyone around can see the structure.

A large meta-analysis (a study that combines many studies) on psychological safety has shown that it is linked not only to ordinary job performance but also to voluntary cooperative behavior. It has also been reported that people who are more sensitive to their environment may be affected more strongly by workplace stressors and by leadership.

So when people who think and act on their own hold back extra proposals and cooperation, it isn't necessarily a lack of ability or sense of responsibility. In an environment where speaking up gets your idea shot down after the fact and only the results get taken, limiting your discretionary contributions is a rational way to protect your resources.

The minimum conditions for stopping it

It's hard to stop this problem with values training alone. At a minimum, these practices are needed.

1. Record the decision process
   Keep a record of who decided what, based on which facts.

2. Make responsibility for sharing information clear
   When necessary information didn't reach the person in charge, don't treat it only as their failure to keep up.

3. Design metrics from the purpose
   Don't decide on the number you want first and attach it to the plan afterward. Don't force a precise number onto side benefits that can't be measured.

4. Diagnose before you coach
   Before deciding "you can't do it," ask what the person thought, what they did, and what information they had.

5. Separate where results come from
   Don't blur the contributions of the planner, the implementer, the decision-maker and the supporter, so that a manager can't collect everything as their own coaching result.

6. Make managers subject to multi-rater feedback too
   Beyond evaluation from their own boss, check with subordinates, peers and related departments how they handle information sharing, defining requirements and taking responsibility.

7. Don't turn the person who raised the issue into a "troublemaker"
   Treat questions about purpose, cause and effect, and how to measure as quality assurance that protects the plan, not as an act of sinking it.

Summary

Even if a company says it wants employees who think carefully, take responsibility and execute, if the following is what happens on the ground, a different kind of person is what actually gets nurtured.

• Thinking carefully gets you labeled "slow"
• Questioning assumptions gets you labeled "defiant"
• A manager's failure to share information becomes a subordinate's failure to understand
• A subordinate's results become the manager's coaching record
• The desired number is decided first, and the logic is attached afterward

The people who adapt to this environment are not those who think deeply about problems, but those who guess the answer in the evaluator's head, avoid responsibility, and keep dissent to themselves. The ideal the company advertises and the kind of person who survives on the ground end up reversed.

Whether an organization truly changes isn't decided by whether it talked about problem behavior in training. It's decided by whether you can trace who held back information, who made the decision, who took the blame for failure, and whose results it was recorded as.

Seeing through it is only the first step. To stop transparent laundering, you have to change the system of authority, evaluation and records, not just the stated values.

---