Productivity does not come from permanent time pressure. It comes from consciously deciding where available time should be spent.
“ASAP,” “as soon as possible,” “highest priority,” or “we actually needed this yesterday.”
Phrases like these have become part of everyday business language. They communicate determination and responsiveness. From a management perspective, they can even feel reassuring. A task is assigned, a deadline is attached, and everything initially appears organized.
The problem begins when genuine exceptions become the permanent way of working.
A recent discussion in Der Spiegel addresses precisely this phenomenon, asking how employees can challenge artificial urgency and push back against deadlines that lack a clear rationale.
From a leadership perspective, however, simply telling employees to resist unnecessary deadlines is not enough.
The deeper issue is this:
Leaders need to understand which activities actually consume time, how changing priorities affect ongoing projects, and whether the perceived workload matches the actual distribution of work.
This turns activity tracking into a management tool.
Not a tool for controlling people, but a foundation for objectively understanding how work is actually being done.
The Dangerous Confusion Between Urgency and Importance
A deadline is not inherently negative.
Projects need schedules. Customers expect results. Contracts contain deadlines. Proposals need to be submitted, systems delivered, and regulatory requirements fulfilled.
The problem begins when the proximity of a deadline is automatically interpreted as the business importance of a task.
Researchers led by Meng Zhu have described this phenomenon as the “mere urgency effect.” Their experiments showed that people tend to favor urgent tasks over more important tasks, even when the supposedly urgent tasks provide less actual value.
Simply putting a time limit on something can influence our attention so strongly that we lose sight of the task's actual importance.
For companies, this effect is highly relevant.
Imagine a strategically important concept for a major client that has two weeks before its deadline.
At the same time, an employee receives an email asking for a relatively unimportant analysis “by this afternoon.”
Psychologically, the second task suddenly has greater presence.
Without conscious prioritization, the deadline wins over importance.
That is where leadership responsibility begins.
Leadership Also Means Filtering Urgency
A leader should not simply pass organizational pressure down the hierarchy.
They need to evaluate it.
Imagine management forwards a request to a department head. The department head passes it to a team leader as “urgent.” The team leader then turns it into an immediate task for an employee.
Within minutes, an ordinary request can become a perceived crisis.
And nobody has stopped to ask why the result is actually needed today.
For me, professional leadership therefore always includes the question:
What actually happens if this task is completed tomorrow, next week, or at the originally planned date?
The answer is often surprising.
For a legal deadline, the consequences may be significant.
The same can be true for a production outage. If an important customer is waiting for a proposal, speed may provide a genuine competitive advantage.
But for many internal requests, the honest answer is:
Practically nothing.
The deadline exists because someone named a date. That date is passed along, gains an appearance of legitimacy, and eventually displaces other work.
A good leader needs to interrupt this mechanism.
The Invisible Problem: Every New Priority Displaces an Old One
In project-based work, time has one particularly important characteristic:
It cannot be allocated to multiple things at the same time.
If a developer spends four hours preparing an urgent special analysis, those four hours are unavailable somewhere else.
If a lawyer suddenly prepares an internal report, they are not working on a client matter during that period.
If an engineer stops a customer project to prepare an unexpected presentation, the development work does not continue during those hours.
Yet new tasks are often treated as if they simply appear on top of existing capacity.
The right management question is therefore not:
“Can you get this done today?”
It is:
“Which other task should we postpone so that this task can be completed today?”
That small difference fundamentally changes leadership.
A new priority now has a price.
And leaders can only evaluate that price if they understand what the organization's available time is actually being spent on.
A Full Workday Says Little About Productivity
Many companies now have excellent project management systems.
They know their tickets, tasks, milestones, budgets, responsibilities, and deadlines.
What is often missing is the connection between these structures and the actual time spent doing the work.
A project can be 80% complete according to the project plan and still be economically off track.
Conversely, a project may be behind its original schedule even though the team is working highly productively because unexpected customer requests or internal special assignments have consumed a significant amount of capacity.
Without an activity dimension, leaders primarily see outcomes.
They do not necessarily see how available capacity was used to produce those outcomes.
This is particularly important in knowledge work.
Microsoft has described a working environment characterized by an exceptionally high number of digital interruptions. Employees in highly communication-intensive environments are frequently interrupted by meetings, emails, and messages.
An organization can therefore appear extremely active while producing surprisingly little focused value.
Context Switching Is Not a Free Resource
Permanent urgency becomes particularly problematic when it creates frequent task switching.
An employee is working with concentration on a project.
A message arrives.
An allegedly urgent issue needs to be resolved.
Then comes a phone call.
Afterward, the employee returns to the original project.
A traditional time-tracking system might record 30 minutes for the interruption.
But the actual organizational impact can be considerably larger.
Research into the phenomenon known as “attention residue” suggests that our attention does not necessarily move completely from one task to the next. Parts of our thoughts remain with the previous task, potentially reducing performance on the new task.
That is why looking at activities can be much more informative than simply looking at attendance time.
As a manager, it is not particularly useful for me to know that someone worked for eight hours.
I want to know whether those eight hours consisted of, for example:
- Six hours of focused project work
- One hour of communication
- One hour of administration
Or whether those eight hours consisted of twenty small activity blocks spread across five different projects, internal requests, emails, and meetings.
Formally, both are eight-hour workdays.
Organizationally, they are completely different.
Our Perception of Time Is Surprisingly Unreliable
There is another problem:
People are not always good at estimating how much time they actually spend on something.
This is not a question of competence. It is a well-documented psychological phenomenon.
The American Psychological Association describes the planning fallacy as the tendency to underestimate the time required for future tasks, partly because we base our estimates on overly optimistic assumptions about how things will unfold.
From a leadership perspective, this is highly relevant.
An employee might genuinely believe:
“These meetings barely take any time.”
An activity analysis may show that several hours per week are being spent on them.
A project manager might believe:
“The customer only asks occasional follow-up questions.”
Over four weeks, those questions can turn into a substantial amount of additional work.
A manager might believe:
“My team spends almost all of its time on our strategic projects.”
An activity analysis may show that administration, internal coordination, support, and short-notice special assignments are consuming a significant proportion of available capacity.
None of these people necessarily have to be deliberately wrong.
Their perception may simply be inaccurate.
That is precisely why structured activity tracking is so valuable.
Activity Tracking Is First a Mirror for the Employee
Time tracking is often viewed exclusively from the company's perspective.
The company wants to calculate project costs, bill services, or document working hours.
But an important benefit is often underestimated:
Recorded activities give employees a more objective view of their own working lives.
That can be extremely valuable.
If someone looks back on Friday and simply feels that they have been busy all week, there is little to learn from that feeling alone.
But if they can see that, for example:
- 35% of their time went to customer projects
- 20% went to meetings
- 15% went to internal coordination
- 15% went to support
- 15% went to administrative activities
they have a completely different basis for reflection.
They can then ask concrete questions:
Does this distribution match my actual responsibilities?
Did I spend my time on the areas I am accountable for?
Which activities took significantly longer than expected?
Which tasks repeatedly interrupted focused work?
Which supposedly urgent tasks were actually important in hindsight?
Where might I have created urgency myself even though it was not necessary?
Activity tracking therefore becomes a tool for personal time management and self-reflection.
For Leaders, a Second Perspective Emerges
The same information serves a different purpose at management level.
Here, the focus is less on an individual workday and more on patterns.
If a project consistently requires significantly more time than planned, the reason could be an inaccurate estimate.
But it could also be changing requirements, excessive coordination, technical problems, or a large number of unplanned additional services.
Without activity data, many of these discussions remain subjective.
The project manager says the customer is generating an unusually high workload.
Sales says the project was correctly estimated.
The employee says they are constantly dealing with follow-up requests.
Management simply sees that the project budget has been exceeded.
Structured analysis of actual activities creates a shared factual basis.
In Project-Based Businesses, Time Becomes an Economic Variable
This point becomes even more important for project-oriented companies.
Project controlling should not begin when an invoice is issued or a project has already been completed.
Leaders need to identify as early as possible whether actual effort and estimated effort are beginning to diverge.
Knowing the total amount of time is not enough.
The structure of that time matters.
Suppose 120 hours were budgeted for a project and 80 hours have already been consumed halfway through the project timeline.
That is an obvious warning signal.
The information becomes even more valuable when you can see why those 80 hours were used.
Were more development hours required?
Were there unexpectedly many customer meetings?
Were services delivered that were not originally included in the scope?
Are internal quality processes more complex than expected?
Or is the project repeatedly being interrupted by urgent tasks from other projects?
Only then can leadership intervene effectively.
Time Tracking Must Not Be Confused With Employee Surveillance
At this point, an important boundary needs to be established.
Good activity tracking must not become a system for evaluating every minute of an employee's day.
The wrong question would be:
“Why did Employee A need 43 minutes for this task while Employee B only needed 31?”
That kind of analysis can quickly create a culture of surveillance and destroy the actual value of the data.
Complexity, experience, quality of work, customer requirements, and different approaches cannot be reduced to individual minute values.
Much more useful questions are:
Why does this type of activity now require 25% more time than it did six months ago?
Or:
Why is the proportion of unplanned work in this team continuously increasing?
Or:
Why has the capacity allocated to a strategic project not been achievable for four consecutive weeks?
Activity data should therefore primarily be used to explain processes, not judge people.
In my view, that is one of the most important conditions for employee acceptance.
Tactile Time Tracking Can Significantly Reduce the Barrier
There is still a practical challenge.
The more complicated time tracking becomes, the less effectively it works in everyday life.
If an employee has to open a program, search for a project, select an activity, and start a timer every time they change tasks, time tracking becomes an additional administrative process.
With frequent task switching, that process quickly becomes disruptive.
This is precisely where TimeSpin takes a tactile approach.
The TimeSpin dodecahedron can be individually configured with activity or project labels. Its different sides can represent customer projects, internal projects, administration, meetings, support, or other relevant activities.
When the activity changes, the user simply turns the cube to the corresponding side.
Time tracking follows the actual action.
The data is automatically synchronized and can then be analyzed.
In my view, the tactile interaction also creates an additional benefit: it makes the activity change conscious.
When someone turns the cube from “Project Development” to “Email / Administration,” they immediately register that a context switch has taken place.
The technology therefore does not merely support later reporting and controlling.
It can also support self-awareness during the working day.
The Weekly Review Matters More Than the Individual Minute
Such tracking becomes particularly valuable when viewed over a week or a month.
Not every individual deviation matters.
Patterns matter.
An employee may discover after four weeks that they spend an average of 12 hours per week in internal meetings.
A team may discover that almost one-quarter of its available project capacity is being consumed by short-notice support requests.
A manager may see that a project is progressing according to plan but requires significantly more coordination than originally estimated.
A CEO may discover that strategic topics are repeatedly being displaced by supposedly urgent operational tasks.
The conversation then changes.
Instead of:
“We don't have enough time.”
the question becomes:
“What are we actually using our time for?”
From a leadership perspective, that is a much better question.
Time Data Can Lead to Better Project Planning
Tracking actual activities also offers a long-term advantage:
It improves future project planning.
If historical data shows that a particular project phase consistently requires 30 hours, even though proposals are repeatedly calculated with 20 hours, the next project should not simply be planned with 20 hours again.
Activity tracking can help counteract the psychologically established planning fallacy.
We have to rely less on assumptions and can instead use historical experience.
Project management research has long highlighted the role of optimism, overconfidence, and the planning fallacy in systematic errors in project forecasting.
Historical activity data provides an external perspective:
How long did comparable activities actually take?
Time tracking can therefore turn historical data into organizational knowledge.
Leaders Also Need to Question Their Own Urgency
Responsibility should not be placed exclusively on employees.
Leaders themselves are often the biggest producers of artificial urgency.
A short message from a CEO may be nothing more than a question from their perspective.
To the recipient, however, it may immediately become the highest priority.
“Could you take a look at this?” can be interpreted by a team as:
“The boss expects this today.”
“We should clarify this soon” can become:
“Do this immediately.”
That is why leaders need to learn to communicate priorities more precisely.
If something is needed by Friday, say Friday.
If something should only be done after other priorities are completed, say that as well.
And if immediate action really is necessary, leadership should simultaneously decide which existing task will be postponed.
Prioritization without deprioritization is not prioritization.
Transparency Also Changes the Conversation About Overload
This insight is particularly important when managing teams.
When an employee says:
“I can't keep up with my workload anymore.”
there are two bad reactions.
The first is:
“Then you need to organize yourself better.”
The second is:
“Then we immediately need more employees.”
Either response could be correct.
But either could also be wrong.
The first step should be understanding what is actually causing the workload.
Perhaps the employee genuinely has too many tasks.
Perhaps they are spending an unusually large amount of time on activities that could be automated or delegated.
Perhaps they are constantly being interrupted by other departments.
Perhaps project budgets were unrealistically calculated.
Or perhaps certain processes have become so bureaucratic that they consume a disproportionate amount of working time.
A transparent activity structure makes these causes visible.
This also changes the quality of the conversation between employees and managers.
The discussion becomes less dependent on subjective impressions and more grounded in information that both sides can understand and evaluate.
Time Tracking Should Not Become an Isolated System
For professional business environments, it is important that activity data does not remain trapped inside a technical silo.
Time tracking creates the greatest value when the data can flow into existing project management, ERP, accounting, practice management, or billing systems.
TimeSpin provides integration capabilities for this purpose. Its API enables external systems to exchange and process time data as part of existing workflows.
For patent and trademark professionals, Genese provides specialized IP management software, and TimeSpin can connect recorded time with relevant Genese case files.
This can turn a simple tactile interaction at the workplace into a continuous information chain:
Activity → Time spent → Project → Controlling → Billing → Management decision
The real value is therefore not the timer itself.
The value lies in the insights generated from the data.
Conclusion: Leadership Needs Less Urgency and More Transparency
Companies do not become more productive by labeling as many tasks as possible as urgent.
They become more productive when employees and leaders can distinguish which activities actually matter and where the limited resource of time is truly being spent.
That requires more than project plans and calendars.
It requires a realistic view of everyday work.
Activity tracking can help on three levels.
For the employee, it creates a more objective basis for self-reflection. Their perception of how they spent the week can be compared with the actual distribution of activities.
For the manager, it creates transparency around capacity, interruptions, project effort, and organizational patterns.
For the company, it creates a data foundation for better project estimates, improved processes, and a clearer distinction between necessary urgency and artificially created urgency.
A simple tactile solution such as TimeSpin can integrate this transparency into everyday work without turning time tracking itself into another administrative burden. Activities can be represented on the sides of the dodecahedron, changes are recorded by simply turning the device, and the data is automatically synchronized.
But ultimately, what matters is how leaders use that data.
The central question should not be:
“Did you document every minute?”
The much more important question is:
“Did we use our shared time for the right things?”
That is where productive leadership begins.
Top comments (0)