Introduction: Workplaces that do not watch people often ask “Why?” only when they leave
In some workplaces, a person’s work is not properly observed while they are there.
Their workload is not measured.
Their automation is not understood.
Their education work becomes permanent support.
Their improved efficiency becomes room for more undefined tasks.
Then, when they decide to leave, people ask:
Why are you leaving?
That is such a waste.
This work has value.
Everyone relies on you.
Can you keep doing it?
This sounds like recognition.
But there is a structural problem.
If the work had value, why was it not designed as formal work earlier?
Why were scope, workload, priority, successors, and evaluation not defined?
This article calls this pattern “the laundering of explanation responsibility for resignation.”
The conclusion is simple:
If the work has value, do not run it on goodwill. Design it.
1. “Why are you leaving?” can become shifted responsibility
Asking why someone leaves is not always bad.
A constructive exit interview can help an organization learn.
But the problem appears when the workplace:
did not observe the person’s workload
did not reduce work
did not define the role
kept adding work to the person’s efficiency gains
asks only when the person leaves
Then “why are you leaving?” becomes a way of shifting explanation responsibility to the employee.
The organization should also ask itself:
Why did we not notice the load earlier?
Why did we not define the valuable work as formal work?
Why did we keep relying on one person?
Why did we add more work after they automated the old work?
2. “It has value, so keep doing it” is a dangerous phrase
When someone tries to let go of work, they may hear:
This work has value.
Everyone benefits from it.
Only you can do it.
Please continue.
The phrase sounds appreciative.
But value and personal ownership are different things.
If the work truly has value, the organization should:
make it formal work
define the scope
estimate the workload
reduce other work
set priorities
create successors
reflect it in evaluation or compensation
create manuals, scripts, and checklists
A bad workplace instead says:
It has value
↓
so do it with goodwill
↓
so do not leave
↓
so explain why
↓
so you should continue
That is not design.
It is personal dependency.
3. People who automate work can look falsely available
People who use RPA, VBA, templates, manuals, scripts, and checklists may look less busy.
But they are not necessarily free.
They have made the work lighter.
they do not repeat manual work
they do not think through the same task every time
they do not repeat the same explanation
they automate, standardize, and script the work
If others misunderstand this, they may say:
You seem available.
You are fast.
You can handle this too.
This is dangerous.
Efficiency gains are not infinite free capacity.
They are safety margins created by work design.
A useful response:
The work may look lighter because RPA, VBA, and standardization have reduced manual steps.
If additional work is added, please clarify what should be lowered, along with priority and scope.
Shorter:
Automation reduced the workload, but that does not mean unlimited capacity.
4. Before adding work, decide what to reduce
This is one of the most important principles of work design.
Before adding work, decide what to reduce.
When new work is assigned, also decide:
what will be reduced
what will stop
what will be delayed
which priority will go down
who decides exceptions
when the scope will be reviewed
Without this, work only increases.
Bad pattern:
add new work
↓
do your best
↓
look around
↓
cooperate
↓
read people’s feelings
↓
if it fails, coach the person
↓
if they burn out, treat it as their problem
This is not assigning work.
It is stacking load.
Response:
I can review the request.
If additional work is expected, please clarify what should be reduced and confirm the priority and scope.
Shorter:
If we add this, please also decide what we reduce.
5. Do not turn educators into permanent support windows
Even with a high-level educator, skills will not spread unless the organization makes it safe to receive them.
Educators burn out when this happens:
You do this training too.
You taught it, so support it forever.
If the trainee is confused, ask you.
If an exception appears, ask you.
Next training is also yours.
This is not education.
It is making the educator into human infrastructure.
Roles should be separated:
Educator:
initial understanding, materials, scripts, standardization
Operator:
daily operation and normal questions
Manager:
formal ownership, scope, priority, reduction of existing work, responsibility for failures
Place an exit condition at the beginning:
The purpose of this training is initial understanding and standard procedure sharing.
Post-training operation, daily questions, exception handling, and formal ownership should be handled by the responsible owner or manager.
The educator is not assumed to become the permanent support window.
Shorter:
Conducting training and becoming the ongoing operational owner or support contact are separate matters.
6. Make it safe to receive work
If people refuse to receive new skills or tasks, it is not always because they lack motivation.
They may be defending themselves.
If I say I understand, I become the owner.
If I say I can do it, everything is handed over.
If I ask a question, it becomes my job.
If I fail, I get blamed.
The previous owner leaves, but I receive no authority.
My existing work does not decrease.
In this situation, education will not spread.
People will say:
I still do not understand.
This is difficult.
I cannot do that yet.
I cannot take that much.
This can be a defense reaction.
The solution is to design responsibility transfer before skill transfer.
separate understanding from ownership
watch → do together → do a small part → do with supervision → formal ownership
reduce work before adding work
separate normal processing from exception judgment
define how failures are handled
do not make the educator the permanent support window
create a reversible review route
reflect received work in evaluation
Education is not just transferring skill.
It is creating a structure where the receiver does not need to defend themselves.
7. “Let’s all cooperate” can become a search for the next easy person
When someone leaves or work increases, workplaces often say:
Let’s all cooperate.
Let’s do our best.
Let’s support each other.
Cooperation itself is not bad.
But cooperation without design is dangerous.
In reality, work does not go to everyone equally.
It flows to the easiest person to ask.
no formal owner
no reduced work
no rule
but help if someone is struggling
the easiest person absorbs it
This is not cooperation.
It is natural load flow.
Real cooperation requires design:
who owns what
who decides
what is reduced
how far each person goes
where exceptions return
when to review
Response:
I agree that cooperation is necessary.
However, unless we define who owns what, who decides, the priority, and what work is reduced, the load will concentrate on specific people.
Shorter:
To cooperate properly, we should first define roles and scope.
8. Do not turn work-design ability into a “personality problem”
People who can design work may be seen as “difficult” in weak organizations.
They may:
identify undefined work
separate responsibility scopes
confirm decision-makers
reduce work
create scripts
standardize
automate
turn training into systems
return responsibility to the right place
avoid filling structural holes with goodwill
This is not a personality flaw.
It is an organizational capability.
A workplace that calls this “a trait problem” may be pathologizing the very ability it needs.
What the organization needs is not more people who absorb everything with goodwill.
It needs more people who can act according to the proper design.
A useful response:
I would like to treat this not as a personality issue, but as a work design, role definition, and operation rule issue.
Shorter:
I understand this as an issue of scope and decision-making, not personality.
9. Manager-level turnover is a strong organizational signal
When a manager or department head leaves, it can be a strong signal.
They often have:
income
status
internal relationships
discretion
information
influence
If such a person leaves, the organization should look at the structure.
Especially if the person was:
reliable
receiving heavy issues
able to teach
able to manage
working late
constantly consulted
Ask:
Were heavy decisions concentrated on one person?
Was the middle management layer thin?
Were supervisors already overloaded?
Was the decision route after the manager’s departure undefined?
Were “do you know a little about this?” requests leaking to surrounding people?
Do not only look at the resignation.
Look at the structure that collapses when that person leaves.
10. If the workplace ends with “I wonder why,” it inherits goodwill laundering
When key people leave, some workplaces only say:
I wonder why they left.
That is unfortunate.
It was sudden.
What should we do about the successor?
Let’s all cooperate.
If it ends there, the organization does not learn.
It should ask:
Why was heavy work concentrated on that person?
Why did judgment stop without them?
Why was there no successor?
Why did educators become permanent support contacts?
Why did we add work to efficiency gains?
Why did valuable work remain informal?
If these questions are not asked, the load flows to the next easy person.
Goodwill laundering is inherited.
11. Do not push all explanation responsibility onto the person leaving
If a workplace asks why someone is leaving, it should also examine its own structure.
Why did we not notice the load?
Why did valuable work remain informal?
Why did automation gains become more work?
Why did educators become permanent support?
Why did we use “cooperation” instead of role design?
Did we turn a work-design issue into a personality issue?
If the organization does not examine these, the same problem will repeat.
12. Practical phrases
“This work has value, so continue”
I recognize that the work has value.
However, continuing it requires the company to define scope, workload, priorities, and handover structure.
I do not think it is sustainable to keep absorbing it through individual goodwill or automation.
Shorter:
Precisely because it has value, it should be designed as formal work rather than dependent on one person.
Additional work
I can review the request.
If additional work is expected, please clarify what should be reduced and confirm the priority and scope.
Misreading automation as free time
The work may look lighter because RPA, VBA, and standardization have reduced manual steps.
If additional work is added, please clarify what should be lowered, along with priority and scope.
Training becoming permanent support
Conducting training and becoming the ongoing operational owner or support contact are separate matters.
Post-training operation, daily questions, and exception handling should be organized by the responsible owner or manager.
“Let’s all cooperate”
I agree that cooperation is necessary.
However, unless we define who owns what, who decides, the priority, and what work is reduced, the load will concentrate on specific people.
When the issue is framed as personality or traits
I would like to treat this not as a personality issue, but as a work design, role definition, and operation rule issue.
When asked why you are leaving
I recognize that there is valuable work.
At the same time, continuing it requires work volume, role scope, priority, and handover structure to be designed by the organization.
I judged that long-term continuation is difficult in a personally dependent form.
13. Final takeaway: If it has value, do not make it personal dependency
The conclusion is simple.
If it has value, make it formal work.
If it is formal work, define the scope.
If you define the scope, estimate the workload.
If you estimate the workload, decide what to reduce.
If you want it to continue, create successors.
If you train people, do not make the educator a permanent support window.
If you ask people to cooperate, define roles and decision-makers.
If automation made work lighter, do not fill the margin with undefined tasks.
Before calling it a personality issue, examine the work design issue.
Asking “why are you leaving?” after the fact is too late.
The better questions are:
Why did we not see this before the person left?
Why did we not design the valuable work?
Why did we run it on goodwill?
Why did we add work without reducing work?
Why did we treat work-design capability as a difficult personality trait?
Final line:
The more valuable the work is, the less it should depend on goodwill. It should be designed.
