It is not just a memory problem
A common workplace conflict sounds like this:
“I told you that already.”
“No, you didn’t.”
“That’s not what I meant.”
“I thought it was obvious.”
“I wanted you to think for yourself.”
This is the classic “I told you / you never told me” argument.
When it happens repeatedly, the real problem is often not individual memory.
The problem is weak work design.
- Decisions are not documented
- Responsibilities are unclear
- Deadlines are vague
- Priorities are not shared
- The decision maker is unknown
- Instructions are given only verbally
- Evaluation criteria change after the fact
In other words, the workplace is being operated by human memory.
And human memory is unreliable.
The three patterns of “I told you”
There are several common patterns.
1. The person genuinely believes they said it
They thought about it.
They mentioned it vaguely.
They told someone else.
They touched on it briefly in a meeting.
In their mind, that becomes “I already communicated it.”
But for the receiver, it was never documented as a clear instruction.
2. They do not want to admit an instruction gap
Sometimes the instruction was never given clearly.
But admitting that would mean admitting a management failure.
So the responsibility is shifted to the receiver with phrases like:
“I told you.”
“You should have known.”
“I wanted you to think for yourself.”
This is responsibility laundering.
3. The evaluation criteria are created after the result
After seeing the output, someone says:
“That’s not what I wanted.”
“I expected you to consider that too.”
“That was the intention from the beginning.”
But if the criteria were not shared at the beginning, this is not fair feedback.
It is post-hoc grading.
The solution is not better memory
The solution is not simply to remember everything better.
The solution is to stop relying on memory.
Use logs.
After a meeting or verbal instruction, send a short confirmation message.
Just to align our understanding, I will proceed with the following:
Purpose:
Scope:
Out of scope:
Deadline:
Person to confirm with:
Decision maker:
Open questions:
Please let me know by [date] if anything differs from your understanding.
This protects both sides.
If something is wrong, it can be corrected early.
If no correction is made, you have a record of the shared understanding at that time.
What to document after meetings
A perfect meeting note is not necessary.
At minimum, record the following:
What was decided:
What was not decided:
Owner:
Deadline:
Decision maker:
Scope:
Out of scope:
Next confirmation point:
The most important item is often “out of scope.”
Many conflicts happen because people decide what to do, but not what not to do.
How to respond to “I told you”
Do not turn it into an emotional fight.
Return to the log.
According to my understanding memo, the agreed scope was up to this point.
Did you intend to include this additional item as well?
Or:
To prevent future misunderstandings, I would like to document scope, deadline, and confirmation points after verbal discussions.
This shifts the conversation from blame to process improvement.
Conclusion
“I told you / you never told me” arguments are often not personal problems.
They are process problems.
When roles, deadlines, scope, and decisions are unclear, people will inevitably disagree later.
Do not fight with memory.
Use logs.
Document:
- purpose
- scope
- out of scope
- deadline
- decision maker
- confirmation point
This is the simplest way to protect yourself and your team from unnecessary workplace conflict.
Codex向け実装メモ
- 記事カテゴリ：仕事術 / 業務改善 / 職場トラブル / マネジメント
- 後出し指摘が多い職場の記事
- 責任転嫁する上司への対処法
- 会議後の認識合わせメールテンプレート
- 仕事のメモ術・議事録術
- 便利屋化を防ぐ仕事の範囲設定
- 認識合わせメールテンプレート
- 会議後確認メモテンプレート
- 業務改善・標準書作成アプリへの導線
- 画像案：
- 「言った」「言ってない」で向かい合う2人
- 口頭指示からログ化への流れ
- 責任ロンダリング猿を軽くデフォルメした比喩イラスト
