It Isn't a Memory Contest
Here is a trouble you'll see in many workplaces.
"I told you that before." "I never heard it." "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.
If it happens once in a while, it may be a simple slip in communication. But a workplace where it keeps happening is in real trouble. These arguments are not only about who remembers better. In most cases the real cause is weak job design:
- Nobody wrote down what was decided.
- It isn't clear who makes the call.
- Nobody knows where the job starts and ends.
- There is no deadline.
- Nobody shared what comes first.
- Work moves forward on a spoken hint and a feeling.
- People later change what they claim they meant, in a way that suits them.
In short, a workplace full of these arguments runs on people's memory. And human memory breaks all the time. So don't fight with memory. Fight with a written record.
What "I Told You" Really Means
"I told you" comes in a few types.
1. They honestly think they said it
In their own head, the message was delivered. They thought about it. They told someone else. They mentioned it briefly in a meeting. They said it vaguely in small talk. Somewhere along the way, that turned into "I told you officially."
There may be no bad intent. But it causes trouble for the listener, because nothing was left in a form they could treat as a real instruction.
2. They don't want to admit they forgot to give the instruction
They never actually said it. But admitting that would mean admitting a failure in managing the work. So they say:
"I told you." "Isn't that obvious?" "I wanted you to think for yourself."
and push the blame onto the other person. This is hard to deal with. It is a kind of blame laundering: a missed instruction, a missing definition, and a lack of checking all get washed into "you didn't understand."
3. They grade the work after seeing the result
Once they see the result, they say:
"What I really wanted was this." "That wasn't what I meant." "I expected you to think of that too."
There was no standard at the start. They are making the standard up after the fact. This puts the other person at a disadvantage however hard they try. It is like changing the exam questions after the exam is over.
"Obvious to Anyone" Is Not Obvious
"Isn't that obvious?" is a risky phrase too. Sometimes a thing really is common knowledge at work. But in most cases, "obvious" lives only in one person's head:
- It's normal for that person's experience.
- It's normal in that team.
- It's normal for that boss.
- But it was never written down.
- And nobody shared how to decide.
If you tell someone "it's obvious" in that state, they are stuck. Work isn't a mind-reading contest. What people need is this kind of information:
- the goal
- the deadline
- the scope
- the priority
- who decides
- what counts as done
- what you won't do this time
- when to check in along the way
If these stay vague, "I told you / you never told me" arguments are likely to come later.
What Workplaces With Many of These Arguments Have in Common
Workplaces with this problem tend to share a few traits.
1. Many instructions are spoken only
Spoken instructions are not bad in themselves. But if they stop at speaking, they're risky. A spoken instruction drifts depending on the wording, the context, the mood of the moment, and how the listener understood it. For work with several people, or work that someone will need to check later, speaking alone is not enough.
2. There are no meeting minutes or confirmation notes
There was a meeting, and there was a talk. But nobody recorded what was decided. Holding a meeting is not the same as reaching an agreement. After a meeting, you should note more than what was said:
- what was decided
- what was not decided
- who does what
- by when
- who to ask
- what was put on hold
3. Responsibility and authority don't match
You hear, "Think for yourself and act." But you don't actually have the authority to decide. If you decide on your own, you're scolded. If you ask, you're told you lack initiative. That is a bad setup: you're given responsibility without authority. When "I told you" and "isn't it obvious" start in that setup, the listener has no way out.
4. Changes keep coming after the fact
No standard was shown at the start, and then small corrections arrive later. This also creates "I told you" arguments. If the conditions had been shown at the start, it could have been avoided. Hearing "what I really meant was this" afterward is hard to accept. The issue is not the worker's understanding. It is that the person who made the request didn't define what they wanted.
The Fix Is Not "Remember Better"
When you are pulled into one of these arguments, you may think:
"Maybe my memory is bad." "Maybe I should have listened better." "Maybe it's my fault for not taking notes."
Taking notes does matter. But that's not the heart of it. What matters is to run your work so that it doesn't depend on human memory. That means leaving a record.
The Strongest Defense: A Short "Let's Make Sure We Agree" Note
The most effective way to avoid "I told you" later is a short written note to confirm that you agree. After a meeting or a spoken instruction, send a brief text. For example:
To confirm our understanding today, I will proceed as follows.
Goal:
To carry out [task]
Scope:
- [item]
- [item]
Not included this time:
- [item]
- [item]
Deadline:
[date]
Who to check with:
[name]
Points that need a decision:
- [item]
If anything is different, please let me know by [date].
Just sending this changes a lot. The key is to write "This is how I understood it." If the other person sees it differently, they can fix it right then. If they say nothing, you at least have proof that you went ahead on that understanding at that time. Later, when someone says "I told you," you can answer:
"In the note we agreed on at the time, I was to proceed this way."
That way you don't have to fight with memories.
What to Write Down After a Meeting
You don't need to write polished minutes. This much is enough:
What was decided:
What was not decided:
Who is responsible:
Deadline:
Who to check with:
Who decides:
What we will do this time:
What we will not do this time:
What to check next time:
The most important line is what you will not do this time. Many problems begin there. If you decide only what to do and not what to leave out, people will say later:
"I thought that was included." "I assumed you'd do that much." "I wanted you to look at that too."
So write down what is included and what is not, as a pair.
How to Answer "I Told You"
If you answer with emotion, it only gets worse. A better way is to go back to the record.
Answer 1: Go back to checking what you agreed
Sorry, in my notes the scope was up to [item].
Did you mean for [other item] to be included this time?
Answer 2: Turn it into a process for next time
To avoid mix-ups, I'd like to write down the scope, deadline, and who to check with in a short text, even for things we confirm in person.
Answer 3: Make the scope clear
If we add [other item] to this job, I'd like to adjust the deadline or the priorities.
Which should I put first?
The key to all three is not to blame the other person. Saying "You never told me, did you?" straight to their face is a punch. Bringing it back to "Let's make sure we agree" is safer.
Keeping a Record Does Not Make You Difficult
Some people worry that keeping records will make them seem difficult. But a work record is not a nuisance. It is a basic way to protect the work:
- It protects the person who asked.
- It protects the person doing the work.
- It protects the team.
- It protects whoever takes over later.
- It gives you something to check when trouble comes.
- It lets you repeat the same job later.
A record is both a defense and a way to improve how the work is done. The more "I told you" arguments a workplace has, the more a record is worth.
But Don't Take Everything on Yourself
There is one warning. A person who keeps records tends to have their work in order, so they can easily become the go-to person:
"Ask her, she'll know." "He'll put it together." "She'll sort it out."
If that goes too far, your load grows again. So when you write things down, don't carry everything. Write down your own part as well:
The person who decides this: [name]
The person who runs it: [name]
The person who updates the documents: [name]
My part this time: sorting out the issues and a first draft
A record is not for taking over everyone else's responsibility. It is for making each person's responsibility clear.
Summary: End "I Told You" With a Written Record
Workplace "I told you / you never told me" arguments are not only about individual memory. In most cases the cause is in how the work is set up:
- Instructions are only spoken.
- Roles are unclear.
- Deadlines are unclear.
- The scope is unclear.
- Nobody knows who decides.
- Changes keep arriving after the fact.
- There are no minutes or confirmation notes.
In that kind of workplace, anyone would end up in arguments. So you don't have to fight with your memory. What you need is a short note to confirm that you agree:
Goal
Scope
Not included
Deadline
Who to check with
Who decides
Date by which to report any difference
Leaving just this goes a long way to protect you. In a workplace full of "I told you," run your work on records, not on memory. Before your work gets thrown into someone else's blame laundering, put a label on it. That is the most realistic way to protect yourself from "I told you / you never told me" arguments.
