Last week, I had a conversation with a client.
At one point, we touched on a topic that remains sensitive in many organisations: time tracking.
More specifically, why some high-performing professionals become frustrated with timesheets. Why they sometimes start getting creative with their hours. Why they question how they are rewarded. Or why they begin wondering why they should work faster in the first place.
The conversation stayed with me.
Because what appears, at first glance, to be a discussion about hours is actually about something far more fundamental: how organisations define value.
Let me clear up a common misconception straight away.
Most cognitively strong professionals do not automatically expect higher pay because they are smarter.
That is rarely the issue.
The issue arises when they realise that the system primarily rewards time.
Not impact.
Not expertise.
Not results.
But time.
And that is where the tension begins.
So, let us take two consultants as an example.
They are given exactly the same assignment. The first needs eight hours to analyse the problem and develop a solution. The second identifies the root cause within two hours, develops the solution, and ultimately delivers the same result. Or an even better one.
What happens then?
In many organisations, an uncomfortable situation suddenly emerges. The manager looks up and asks:
"Why were you finished so quickly?"
"Are you sure you investigated everything thoroughly?"
"Well, if you have some time left, perhaps you could take on a few additional tasks?"
And then comes the awkward question.
"How many hours are you going to record?"
Because the system – or the client – expects eight hours. Not two.
People begin recording hours that do not necessarily reflect the time they actually worked.
Not out of bad faith. But because the reality of their work no longer aligns with the logic of the system.
The result?
Some people add extra hours because otherwise questions will be asked. Others deliberately take longer than necessary. A third group struggles with the three minutes here and the half-hour there, filling the gaps with small pieces of "busy work".
And then something remarkable happens. The focus shifts.
Away from solving the problem.
Towards filling in timesheets correctly.
Towards finding explanations.
Towards justifying efficiency.
Towards making eight hours of work look as though it genuinely took eight hours.
The outcome is simple.
Speed and efficiency are no longer advantages.
They generate additional administration.
Additional explanations.
Additional justification.
In other words, precisely the things an efficient employee is trying to avoid.
A traditional manager sees a discussion about timesheets. A cognitive leader sees something different.
They see an employee struggling with a fundamental sense of fairness and accuracy. Because from that employee's perspective, the equation simply does not add up. The client is not paying because someone spent eight hours on a task. The client is paying because a problem was solved.
Because expertise was applied.
Because someone knew what they were doing.
Because the right solution was found.
Why should speed become a disadvantage? Why should expertise mainly result in additional work? Why would someone invest in learning faster, building deeper expertise, and finding better solutions if the end result is simply more work? And why is efficiency not valued?
A cognitive leader therefore does not focus on the hours. They focus on the outcome. They understand that performance is not always linear.
The task that takes two hours today may take eight tomorrow. And vice versa.
That is why they focus not on the time required, but on the value created.
This may be one of the most difficult lessons for organisations. For decades, we have built systems around presence. Around working hours. Around effort.
Organisations have traditionally measured value through working time, attendance, and visible effort. And for many roles, that still works perfectly well.
But once you start working with knowledge workers, specialists, and cognitively strong professionals, the model begins to show its limitations. Because their greatest contribution often does not lie in the number of hours they work.
Their greatest contribution lies in what they see.
In the connections they make.
In the mistakes they prevent.
In the solutions they find more quickly than others.
And that kind of value is incredibly difficult to capture in a timesheet.
Perhaps we should spend less time discussing how many hours someone worked. And more time considering what that person actually contributed.
Not because time no longer matters. But because time and value are not always the same thing.
Those who practise cognitive leadership recognise that distinction. They understand why some high-performing professionals become frustrated in systems that primarily measure visibility, completed spreadsheets, and physical presence. They understand why efficiency is sometimes penalised. And they also understand that these discussions are rarely about money.
They are about recognition. They are about fairness. And they are about a much bigger question: What contribution does an organisation truly value?
If you recognise this in someone on your team - someone who delivers fast, thinks differently, and is slowly disengaging - that is worth a conversation. I work with leaders who want to understand what keeps their strongest people motivated, and what makes them leave.
One intake is often enough to see clearly. Send me a message if you'd like to talk.
Cognitive Leadership Review explores how cognitive differences influence the way people, teams, and organisations function. I'm Leticia Vandemeersche and I write about cognitive leadership, hidden potential, and the tension between high-performing professionals and systems that were not always designed with them in mind.
.svg)