Introducing Time Tracking to a Team That Does Not Want It

Resistance to time tracking is usually not obstruction. It is a reasonable inference from what time tracking has meant in most people's previous jobs.

Which means the rollout has to answer that inference, and no amount of tooling does it.

For a vendor-side perspective on employee PC activity tracking, see learn more from Monitask.

What people are actually assuming

Worth naming, because addressing it directly works better than pretending it is not there.

That it is about them. That the numbers will be compared, and that somebody's will be worst.

That it will be used later for something else — a performance review, a redundancy list, a target.

That honest recording will be punished. Log four hours of real focused work and look lazy; log eight and be safe.

That it will not change anything. Record the problem for months, watch nothing happen.

Every one of these is a correct description of some previous rollout, which is why the assumption is rational rather than paranoid.

What to say, in order

Say what it is for

One purpose, specifically. "We do not know what our projects actually cost, and we are quoting badly as a result."

Not a list of six. A list reads as evasion. See what time tracking is for.

Say what it will not be used for

Explicitly, and in writing. Not compared between individuals. Not in performance conversations. Not to set targets.

Vague reassurance does not work because people have heard vague reassurance before. Specific commitments can be checked.

Say what changes as a result

"If this shows that approvals are costing us two days a week, we will change the approval process."

Naming the thing you are prepared to change is the strongest single signal that this is not about people.

Say what you expect the numbers to show

"I expect this to show fewer billable hours than we assume, and that is fine — that is what we are trying to find out."

This inoculates against the month-two problem described below.

Then ask them to design the categories

With you, not for them. They know what kinds of work actually happen, and the list will be better and shorter.

And it converts the exercise from something done to them into something they built.

What to do practically

Make recording take seconds, from where they already work. The single strongest determinant of whether it survives. See why time tracking fails.

Include non-productive categories — waiting, blocked, admin, rework — and say explicitly that recording them is welcome.

Let people correct their own entries without asking anyone.

Report at the level of work, not per person. What your first report looks like will be read very carefully.

Give people their own data.

And do not introduce a target at the same time. Tracking and a target in the same meeting guarantees the first months are protective, and you never see an honest baseline.

What happens in month two

Recorded productive time comes out lower than everyone assumed.

Because waiting, admin, rework and interruptions are now visible instead of absorbed into project hours.

This is the system working. It is also the moment where rollouts get reversed, because someone reads it as a productivity decline.

Say it in advance. Then when it happens, point back at having said it.

The moment that decides everything

Someone senior will ask for a per-person report.

Not out of malice — because it is an obvious question and the data appears to answer it. For broader independent background, see ICO guidance on monitoring workers.

What happens next determines whether the policy is real. If you produce it, every commitment you made is void, and the team will know within a day.

Have the answer ready: what the aggregate data shows, why individual comparison is not valid given the work differs, and what question they are actually trying to answer — which usually has a better route.

And if you are overruled, say so openly. Quietly complying is worse than the honest version. See what time data must never be used for.

Reporting back

Monthly, brief, to everyone who records.

One thing that changed because of it. This does more for compliance than any reminder, and its absence does more damage than any missing feature.

If nothing changed, say that too, and say why. People can accept a slow month; they cannot accept silence.

For a small team

Same principles, and the informality makes it easier to skip them.

Three people means aggregate reporting is individual reporting. Be honest about that rather than pretending otherwise.

And you are more likely to be asked directly what you are going to do with it. Have the answer.

The short version

Resistance is a correct reading of previous rollouts, not obstruction.

State one purpose, state what it will not be used for, and name the thing you are prepared to change.

Let the team design the categories.

Warn in advance that recorded productive time will look lower — that is the month-two reversal point.

And the first request for a per-person report is the test. Everyone is watching what you do.