How to Recognize Failed Dialogue, Moving Targets, and Empty Work Rituals
1. Conclusion: interpersonal dialogue failure and organizational management failure are structurally similar
Some people do not answer the question in front of them. They simply continue with whatever they wanted to say. Some managers behave in the same way toward work: they do not receive the field’s questions or explanations; they impose their own conclusion, emotion, or preferred form.
The scale differs, but the underlying pattern is similar:
They do not treat the other party’s question, purpose, time, and role as carrying equal weight.
In personal conversation, the question is ignored. In an organization, the purpose and definition of done are ignored. In conversation, one person seizes the agenda. At work, senior leaders keep decision rights while pushing execution and accountability downward.
People then learn that speaking is useless, that completed work may be overturned later, and that thinking deeply only increases the amount of work they may lose. This is not merely a personality mismatch. It is a system that fails to return responsiveness, authority, and stable criteria.
2. A person who ignores questions: inability or unwillingness?
Some people can answer a short sentence but lose the central question when the message contains several premises. They may pick one easy word and use it to launch their own topic. Several explanations are possible:
- limited ability to hold and integrate information
- difficulty linking context and implied premises
- attention already occupied by what they want to say next
- avoidance of an uncomfortable question
- a habit of placing their interests above the other person’s agenda
A single missed question does not justify a judgment about intelligence or character. Being able to handle short messages also does not prove an ability to understand longer ones.
However, when someone genuinely does not understand, a healthy response is to ask, “Which part are you asking about?” or “Could we take it one point at a time?” If the person neither clarifies nor answers, and simply continues talking, the problem concerns not only processing capacity but also their stance toward dialogue.
3. Look at responsive behavior, not nationality, age, or unusual spelling
Unnatural Japanese, old-fashioned number puns, and idiosyncratic notation may reflect age, typing habits, a first language, or online culture. They are weak evidence of intelligence or character.
More useful questions are behavioral:
- Do they answer what was asked?
- Do they request clarification when needed?
- Can they summarize the other person’s point?
- Do they overwrite the conversation with their own topic?
- Can they correct themselves after feedback?
Nationality does not determine reciprocity. A non-native speaker may be highly responsive, while a fluent speaker may use every question as a bridge back to themselves. Responsiveness and correctability are better indicators than identity.
4. The workplace version of ignoring a question: responsibility without authority
The organizational equivalent often looks like this:
A manager orders a document.
The purpose and final form remain unclear.
The employee develops it through discussion.
The employee presents it.
At the end, most of it is deleted and the manager says, “One sentence was enough.”
The creator loses the time spent thinking, drafting, and explaining. The senior person who changes the direction bears little of that discarded cost.
The contradiction becomes sharper when a middle manager is responsible for producing the document but lacks authority to finalize it:
- responsible for delivery
- responsible for the deadline
- responsible for explaining it to the team
- responsible for rework
- but unable to stabilize the purpose, depth, structure, or final decision
That is not delegation. It is the subcontracting of work and accountability while decision power remains above.
Role ambiguity is not merely irritating. A large occupational survey in Japan found that role ambiguity was associated with psychological distress and job dissatisfaction and could amplify the harmful effect of other job stressors.[1]
5. Late reversals are undefined requirements, not necessarily poor understanding
A manager may say “make something first,” without defining the requirement, and then declare that the result is wrong. Repeated often, managerial ambiguity is relabeled as employee misunderstanding.
Purpose, final form, and criteria remain vague
↓
The creator builds a reasonable hypothesis
↓
The decision maker sees the draft and only then discovers a preference
↓
Major deletion or rework
↓
The creator is judged as having failed to understand from the beginning
In reality, the artifact has been used as a prototype that helped the decision maker think. Prototyping is legitimate, but the experimental nature and expected rework should be explicit.
Research on projects treats late requirement discovery and requirement changes as major sources of rework, delay, and added cost.[2][3] Change itself is not the problem. The problem is failing to record who changed what, why, with what impact, and then attributing the cost to the creator’s supposed deficiency.
6. A capable manager does not pass senior leaders’ emotions directly downward
A manager may be demanding and still be easy to work for when they:
- separate emotion from the decision
- define the objective and priority
- explain the decision criteria
- translate senior demands into executable work
- block unnecessary interference
- state exactly what must change and why
Their direct reports experience clarity and can move through logic rather than mind-reading.
Yet the capable manager may personally absorb long lectures, emotional interference, and shifting demands from someone above. The lower level feels rational not because the organization is healthy, but because one person is filtering chaos and converting it into logic.
This is not merely admirable leadership. It is the creation of a human firewall. Continuous emotion regulation and surface compliance constitute emotional labor and may contribute to exhaustion and burnout.[4]
7. Being suited to management does not mean wanting this organization’s middle-management job
A person who can structure ambiguity, define completion, mobilize people, allocate roles, and verify output demonstrates management capability.
A good handover, for example, may include:
- teaching basic and advanced software use
- having the learner operate the software directly
- using a changed rule as a real case
- having the learner record, edit, and submit a deliverable
- arranging coverage for the next day’s recurring task
- leaving written evidence of completion
That combines instruction, delegation, verification, and risk control.
But management aptitude is not the same as willingness to become a powerless buffer. These are different roles:
- designing and improving work
- versus calming senior leaders, absorbing political conflict, translating criterion-free commands, and carrying accountability without authority
Rejecting the second role does not prove inability to lead. It may indicate a clear understanding of which kind of leadership is sustainable.
8. Ignoring a known handover for a month and declaring the final two days an emergency
Organizations sometimes know about a transfer or reassignment for weeks, do little, and then demand that everything be completed in two days. They may even characterize planned leave as unacceptable if the handover is not “finished.”
This is not a sudden emergency. It is delayed planning becoming visible near the deadline.
A reasonable handover is complete when:
- current procedures have been explained
- necessary documents and systems have been shared
- the successor has performed the work
- a representative deliverable has been produced
- recurring and exceptional tasks have been identified
- open items and contacts have been recorded
- coverage has been arranged for absences
Completion does not mean the successor will never ask a future question. If management believes something remains missing, it must identify the missing item. “I still feel uneasy” is not a definition of done.
An employee’s interview, medical appointment, family commitment, or need for rest should not become the resource used to repair a month of managerial delay.
9. Verify understanding through performance and output, not “Do you understand?”
A weak verification is:
“Do you understand?”
“Yes.”
A stronger verification is:
“Please perform the task.”
“Apply it to a new case.”
“Submit the result.”
“Explain where you hesitated.”
When the learner can operate the software, complete the full sequence, and submit an output, there is observable evidence that the core handover occurred.
The purpose of training is not for the trainer to speak for a long time. It is to create a state in which the learner can reproduce the work after the trainer leaves.
10. A signature without verification becomes ritual, not control
Imagine a recurring process in which a person is called twice a week only to sign and drop a document into another department’s box. The signer has no quality-control duty, no right to reject, and no substantive accountability for the content.
What does mandatory personal attendance add?
- interruptions
- walking and waiting
- scheduling dependency
- coverage problems during absence
- complaints from other departments
- anxiety about being scolded
If it does not improve error detection, assurance, fraud prevention, or auditability, it is not stronger control. It is a work ritual.
Modern delivery systems use unattended delivery, photographs, notifications, and digital records so that the process continues when the recipient is absent. Internal processes should also be designed around purpose and evidence, not physical appearance.
A real control specifies:
- what is being verified
- who has verification authority
- whether delegation is allowed
- who covers absences
- the deadline and destination
- the evidence retained
Adding steps is not the same as strengthening governance.
11. Seeing waste does not create an obligation to rescue every process
People who are good at improvement can often see the next failure:
- Who substitutes when the person is absent?
- Who responds when the signer does not appear?
- Who handles complaints from the receiving department?
- Why must this exact person attend when the signature carries no substantive authority?
But once an employee has explained the risk, completed the handover, and management chooses another direction, that employee does not have to keep rescuing the process.
I consider the process inefficient.
If leadership chooses it, leadership also chooses its operating cost.
This boundary matters. Seeing a problem and owning it are different. When capable people constantly repair every gap, the organization fails to learn and turns them into human infrastructure.
12. Minimum conditions for healthy work design
| Element | Question to answer |
|---|---|
| Purpose | Why is this work being done? |
| Deliverable | What must be submitted? |
| Definition of done | What result ends the task? |
| Authority | What may the owner decide? |
| Information | What context is required? |
| Support | Who helps when the work is blocked? |
| Evaluation criteria | What counts as acceptable? |
| Priority | How does it rank against other work? |
| Deadline | When is it needed? |
| Change control | Who changed what, and why? |
| Coverage | How does the process continue during absence? |
| Record | Where is completion and rationale documented? |
Without these conditions, “show initiative” becomes a demand to guess the manager’s private answer.
Conclusion: return responsiveness, authority, and criteria
A person who ignores questions and an organization that overturns work after the fact may appear unrelated. The shared failure is this:
The other party’s question, time, judgment, and role are not received as equal realities.
Healthy dialogue answers the question.
Healthy management pairs responsibility with authority.
Healthy handovers use performance and deliverables as evidence.
Healthy control designs purpose, authority, coverage, and records instead of repeatedly summoning people.
Capable people do not need to rescue everything. They need to identify the structure, repair the reasonable scope, document what was done, and refuse to carry the cost of inefficiency selected by others.
