Memory creates arguments
Suppose you say to an employee:
“You're always late.”
They say:
“No I'm not.”
Now what? You have one recollection. They have another. Or you say:
“We've discussed this several times.”
They say:
“I only remember one conversation.”
Again, you are arguing about memory rather than managing the issue. Evidence changes that.
Evidence changes the conversation
If attendance is becoming unreliable, track it. If deadlines are slipping, record them. If commitments are repeatedly missed, capture them. If the same mistake keeps happening, write it down. Then you can say:
“These are the four dates.”
Or:
“These were the five commitments, and three were not completed by the agreed date.”
Or:
“Here are the last eight weeks.”
Now the conversation is grounded in something both people can examine. That usually makes it calmer.
Evidence is not about building a prosecution case
This is important. The objective is not to secretly collect material so you can eventually ambush somebody. Evidence should help both manager and employee understand what is really happening. It may confirm your concern. It may also show that your impression was wrong.
Perhaps you thought the problem happened constantly. The evidence shows it happened twice. Useful. Perhaps you thought performance had not improved. The evidence shows a clear positive trend. Also useful. Evidence should sharpen judgement, not merely support a conclusion you had already reached.
Beware of words such as “always” and “never”
Managers use these words casually.
“You always miss deadlines.”
Really? Every one?
“You never take ownership.”
Never?
“Customers are constantly complaining.”
How many? Broad language invites argument. Specific evidence creates a much better starting point.
Move from impressions to observable behaviour
Another common problem is vague judgement.
“They aren't leadership material.”
What does that mean?
“Their attitude isn't right.”
What behaviour are you seeing?
“They need more ownership.”
What would more ownership look like? Translate the judgement. Perhaps: They repeatedly escalate ordinary decisions despite having authority. They missed four of their last six commitments. They do not raise risks until after deadlines. They have not held agreed one-on-ones. Now you have something that can actually be discussed.
Define the standard first
Evidence is only really useful when you know what you are comparing it with. What was expected? What did success look like? What was the agreed deadline? What was the target? What behaviour was required?
Without that, managers can collect lots of information but still struggle to judge performance fairly. Evidence plus a vague standard is still a vague management system.
Use What Success Looks Like
This is one reason I developed the What Success Looks Like approach. A job description may tell someone their responsibilities. But a manager also needs to be able to say:
“This is what good performance looks like in your role.”
Then future conversations become: What did we agree? What happened? What evidence do we have? Where is the gap? That is far stronger than:
“I just don't think you're doing quite enough.”
Evidence belongs in one-on-ones
One-on-ones should not depend on whoever has the strongest memory of the last month. Come back to previous commitments. What did you say you would do? What happened? What evidence of progress exists? What are you improving? Where are you stuck? Now development becomes visible over time. That allows both people to see movement rather than relying on a general feeling.
Let the employee bring evidence too
This should not all be manager-generated. Ask the employee:
“What evidence can you show me that you're improving?”
That changes the conversation. If they are working on delegation, what has changed? If they are working on follow-through, what commitments were completed? If they are developing somebody beneath them, what can that person now do? Employees should participate in understanding their own performance.
Dashboards are evidence too
A dashboard can be extremely useful. But only if somebody uses it. Revenue. Margin. Conversion. Errors. Complaints. Rework. Deadlines. The data makes patterns visible. But remember: The dashboard does not manage anything. It gives you evidence for a conversation. What is happening? Why? What should we do? Who owns it? By when? Then come back and see whether it worked.
The number is not the verdict
A red KPI is evidence. It is not automatically proof that somebody has failed. Get curious. What caused it? Is this a one-off? A pattern? Something outside the person's control? A system issue? A capability issue? Likewise, green does not automatically mean everything is wonderful. Evidence should trigger thinking, not replace it.
Look for patterns over time
One incident is data. Several similar incidents may be a pattern. That distinction matters. If someone misses one deadline, understand what happened. If they miss six of eight, there is a different conversation to have.
The great advantage of tracking is that you can see when an isolated event becomes a repeated issue. Without evidence, that moment is very difficult to judge.
Track enough, not everything
I am not suggesting managers create enormous surveillance systems. You do not need to document every breath someone takes. Track the things that genuinely matter. Important standards. Significant commitments. Repeated concerns. Development goals. Key results. The purpose is better management. Not paperwork for its own sake.
Record conversations that matter
If you have an important performance conversation, retain a simple record. What was discussed? What was agreed? What needs to change? What support was offered? What commitment was made? When will you review it? Then the next conversation does not have to begin with:
“I think we talked about this a while ago.”
You know.
Evidence protects employees too
This is worth saying. Evidence does not only help management. It protects the employee from vague or unfair criticism. A manager may say:
“Your performance is getting worse.”
The data might show the opposite. A manager may believe someone rarely follows through. The record may show they normally do. That is useful. Good evidence improves fairness because it makes the manager's judgement testable.
Evidence exposes management problems as well
Suppose several employees repeatedly miss the same standard. Perhaps they are all poor performers. Possible. But perhaps the standard is unclear. Perhaps the process is broken. Perhaps training is inadequate. Perhaps the target is unrealistic.
Patterns can reveal problems with management and systems, not merely employees. That is another reason to collect evidence with curiosity.
Stop managing by anecdote
Business conversations are full of anecdotes.
“Customers seem happier.”
“Morale feels better.”
“The team is struggling.”
“Communication has improved.”
All may be true. But ask: What would we expect to see if that were true? Fewer complaints? Lower turnover? Fewer errors? Faster response times? More completed actions? Different employee feedback? Anecdotes can be useful clues. Evidence helps determine whether the story is real.
Separate fact from interpretation
This is one of the most useful disciplines a manager can learn. Fact:
“The report was submitted two days after the agreed deadline.”
Interpretation:
“They don't care.”
Those are not the same thing. Perhaps they don't care. Perhaps something else happened. Start with the fact. Then investigate. Good management becomes much calmer when leaders stop treating every interpretation as though it were evidence.
Use evidence in difficult conversations
A difficult conversation becomes far easier when you can say:
“This is what we agreed.”
“This is what happened.”
“This is the evidence.”
“This is the gap.”
Now ask:
“What do you think is going on?”
That is a much stronger conversation than delivering a long speech about how disappointed you feel.
Evidence reduces surprise
Performance problems should not arrive as a shock at an annual review. If evidence is discussed regularly, both people know where things stand. The employee sees the pattern. The manager sees the pattern. Progress or lack of progress becomes visible. If a harder conversation is eventually required, it has context.
Record commitments, not just problems
Evidence is not only about failure. Track promises. What did someone say they would do? By when? Did it happen? Over time, this reveals something very important: Can their word be relied upon? Reliability is one of the strongest forms of evidence in leadership.
Recognise improvement with evidence
Managers often notice a problem loudly and improvement quietly. Change that. If someone's performance improves, point to it.
“Three months ago this was happening weekly. It hasn't happened for six weeks.”
Or:
“You completed all four commitments this month.”
Or:
“Your team's rework rate has halved.”
That recognition is more powerful because it is specific.
Use evidence to see development
Leadership development is gradual. Without a record, people forget how far someone has come. Ask: What could they not do six months ago? What can they do now? What decisions can they now make? What problems do they no longer escalate? What conversations can they now handle? That is evidence of growth.
Do not weaponise record-keeping
If employees believe every note is being collected merely to punish them, trust disappears. Be transparent. Explain why important commitments or performance measures are being tracked. The objective is clarity and follow-through. Not gotcha management.
Make the system normal
Evidence should not suddenly appear only when someone is in trouble. Use it normally. For everyone. Goals. KPIs. Commitments. Progress. Development. Then evidence becomes part of how the organisation manages, not a special weapon brought out during disciplinary conversations.
Managers need evidence about themselves too
This applies upwards. If you are developing as a leader, ask: What evidence shows you are improving? Are fewer problems being escalated? Are your managers becoming more capable? Are you holding one-on-ones consistently? Are commitments being followed through? Has the team become less dependent on you? Do not exempt yourself from the standard.
A simple evidence-based management rhythm
Try this:
1. Define the standard
What does success look like?
2. Agree the commitment
What will happen, by when?
3. Capture relevant evidence
Not everything. What matters.
4. Review it regularly
One-on-one, meeting or scoreboard.
5. Look for patterns
Improving, declining, recurring?
6. Ask questions
What is causing what we see?
7. Agree action
What needs to change?
8. Follow up
Did it happen?
9. Look at the evidence again
Did the action make any difference? That turns data into management.
Ask the question before making the judgement
The next time you find yourself saying:
“I think...”
pause. Perhaps your judgement is right. But ask:
“What evidence do I actually have?”
If the answer is:
“Not much — I just remember...”
perhaps it is time to collect some. Because evidence changes conversations. It makes patterns visible. It reduces arguments about recollection. It helps employees understand where they stand. It improves fairness. And it gives managers something much more useful than:
“I just have a feeling.”
Evidence beats memory every time.