The Employee Productivity Guide: Measuring Task Work Without Distorting It

• Task count. Rewards whoever splits their work into the most items. Within a month you will have more tasks and the same output.
• Hours logged. Measures presence and the diligence of timesheet completion, which are not correlated with either effort or results.
• Message and activity volume. Measures how much someone communicates about work, which is often inversely related to doing it.
• Composite scores. A single number with a hidden formula cannot be argued with, cannot be learned from, and will be gamed as soon as its inputs are guessed.
• Anything a person can inflate in five minutes. If they can, eventually they will, and you will have taught them to.

The pair worth looking at first is completion time against turnaround. A team with a 90-minute completion time and a six-hour turnaround does not have a speed problem — it has four and a half hours of queue. Pushing people harder cannot recover time nobody was working.

These are exactly the four figures TaskIt computes, from stored task timestamps, with nothing estimated or scored. A duration is only averaged when both ends exist, so an incomplete record shrinks the sample rather than counting as zero — which matters more than it sounds, because the alternative flatters whoever has the messiest data.

• Assigned, accepted, started, completed. Four counts that together show where work is accumulating.
• Pending and in progress. What someone is currently holding. This is the number to look at before adding to it.
• Overdue and blocked. Blocked is the more useful of the two: it is a deliberate statement with a reason, not just a date that passed.
• Completion rate. Completed against assigned. Only meaningful above a minimum sample — someone who finished their only task should not outrank someone who finished eighteen of twenty.

Be careful with counts across people. They are only comparable when tasks are roughly comparable in size, which they usually are not. A count is a description of a person’s week, not a league table position.

The common rule — and the one TaskIt uses — is to attribute a task to its current assignee. That has one very good property: because a task has at most one current assignee, per-person counts summed across the company can never exceed the company total. Reports that break that invariant are the ones that eventually produce a figure nobody believes.

The cost is a blind spot. Someone who did 80% of a job and then handed it over earns nothing in the per-person figures, and someone who joined a collaborative task at the end earns the completion. That is not a flaw to be argued away — it is a limitation to be compensated for by reading handover history and collaboration reports alongside the numbers.

1. 01Measure time to accept. If it is hours, work is waiting to be picked up. Nobody is being slow; the work is not reaching anyone who is free.
2. 02Compare completion time with turnaround. A large gap is queue. A small gap with a long completion time is genuinely the work itself.
3. 03Check the workload distribution. One person holding eleven tasks while two hold three explains most overdue lists without any reference to effort.
4. 04Count blocked tasks and read the reasons. Repeated external blockers — waiting for a customer, waiting for approval, material not available — are process problems wearing a performance costume.

The fixes for queueing are structural: route work to a department queue rather than to a named person, notify the channel people actually read, and rebalance a queue you can now see. None of them require a conversation about anyone’s performance.

Show the working

A figure someone can trace back to specific tasks invites a correction; a score cannot be corrected, only resented. "Your average turnaround is eleven days" is an accusation. "These four tasks account for most of it — two were blocked waiting on the supplier" is a conversation.

Ask about the outliers, not the average

Averages hide the interesting cases. The three slowest tasks in a month usually contain the actual finding, and it is usually structural — an approval that took a week, a customer who went quiet, a dependency nobody owned.

Never measure what you have not explained

If people do not know that acceptance time is being looked at, some of them will not accept tasks promptly and will be measured badly for a behaviour nobody asked them to change. Say what you are looking at, and why, before you look at it.

Do not automate the judgement

A ranking is a starting point for a question, not an output. The person at the bottom of a completion-rate ranking is sometimes the one being handed everything difficult, and no formula will tell you that.

Screen capture, keystroke logging, idle-time detection and location tracking all measure presence rather than outcomes, and they change the relationship between a manager and a team in ways that are difficult to reverse. They also tend to produce their own distortions — people learn to look busy, which is a skill of no value to anyone.

Task-derived measurement is different in kind: the events being recorded are things people did to the work — accepted it, updated it, handed it over, finished it — and they are recorded because the work needed recording anyway. TaskIt deliberately has no timer, timesheet, effort log or activity monitor of any kind, which is a design choice rather than a gap.

1. 01Overdue and blocked. Start with what is currently wrong, and read the blocked reasons rather than counting them.
2. 02Workload. Who is holding what. Rebalance before adding anything new.
3. 03Time to accept, per department. The single most actionable figure most teams have, and the one that responds fastest to a structural change.
4. 04The three slowest tasks of the month. Not to attribute them — to find out what they had in common.