Why does monitoring backfire?
Software that counts keystrokes, tracks mouse movement, or takes screenshots every few minutes is measuring activity—not real work. A consultant thinking through a solution for an hour looks inactive to that kind of tool; someone using a mouse jiggler doesn’t.
What you measure shapes behavior. If sitting still is marked as ‘idle,’ people start looking busy instead of doing good work. And when people feel watched, they log hours more cautiously: an extra hour on a safe client instead of honestly recording ‘this took longer.’
- Trust. Monitoring tells your team: we don’t trust you.
- Wrong incentive. People optimize for the meter, not the client.
- Noise. Keystrokes and open windows don’t reflect quality, discussion, or thinking.
- Privacy. Under the GDPR, processing personal data needs a clear purpose, should collect only what’s necessary, and people must know what’s happening. Continuous screen monitoring is hard to justify under these rules; if you’re unsure, consult a privacy specialist.
So what should you measure?
Good productivity metrics answer a business question, not just a manager’s. They come from data people enter on purpose: logged hours, budgets, and invoices. That way, you can talk about them without anyone feeling accused.
| Number | Question | Source |
|---|---|---|
| Billable percentage | What portion of our time can we invoice? | Logged hours marked as billable |
| Budget versus actual | Are projects staying within the agreed hours? | Project budgets and logged hours |
| Capacity and utilization | Do we have bandwidth, or are we at capacity? | Available hours versus logged hours |
| Aging | How long does finished work wait before it’s billed? | Unbilled hours, by age |
| Profitability | Are we making money on this client or project? | Revenue from hours versus cost |
How to define billable percentage and where it leaks is explained in Billable hours.
Why measure at the team level?
Most productivity issues are organizational, not individual: too many internal meetings, projects that are always underestimated, or clients who ask for lots of non-billable work. You only see those patterns when you look by team, project, or client.
Individual leaderboards distract from the real causes. They encourage comparisons even though people do different work. Use individual numbers as a conversation starter between employee and manager—ask, ‘what’s getting in your way?’—not as a judgment.
Keep your personal timeline separate from logged hours
Automatic time tracking collects a lot: apps, websites, locations. That helps you remember everything, but those raw signals belong to the employee, not the company. What the company needs is the result: the hours someone logs on purpose. How that works is explained in Automatic time tracking.
This separation is important. As soon as raw activity is counted toward productivity, you’re back to monitoring—just with a friendlier name. The same goes for AI features: which data an assistant can use is explained in Privacy and AI context.
How to get started
You don’t need a fancy dashboard. Start with a few numbers you review monthly, and only add more when there’s a specific question.
- Decide which activities are billable and set an hours budget for each project.
- Agree that everyone logs their hours with a short description, and that raw activity stays private.
- Review by team each month: billable percentage, budget versus actual, and what’s still unbilled.
- Discuss outliers as a question: what’s taking time here, and what can we do about it?
How Half5 does it
In Half5, productivity numbers are based on logged hours, not timeline data. The timeline is end-to-end encrypted: “Only you can read your timeline. Half5 cannot access your timeline.” Admins see numbers for the whole organization, department managers see data for their department and its projects, and everyone else only sees their own.
Reports include “Capacity & utilization,” “Team performance,” “Profitability,” “Project health,” and “Aging.” They show logged hours and amounts, including per employee. Timeline data isn’t included: it’s stored encrypted on the server, so no report or manager can read it. The AI summary for managers only gets counts, like how many entries a review flagged, and no names.
Frequently asked questions
Can I legally monitor employees’ computers?
That depends on your purpose, necessity, and how you inform employees; the GDPR sets requirements for this. It’s a legal question for each situation, so have it checked before rolling out this kind of software.
Is a high billable percentage always good?
Not always. You also need time for training, sales, and internal improvements. Focus on the trend and unexpected drops, not just a single target number.
What’s the difference between capacity and utilization?
Capacity is how many hours a person or team has available. Utilization is the share of that spent on logged work.
Can my manager see my timeline in Half5?
No. The timeline is end-to-end encrypted and only readable on your own devices. No screen, report, or export shows it to your manager. They only see what you log yourself: hours, leave, and trips.
How do I measure knowledge work that doesn’t have a countable output?
Use hours as a tool, not a goal: compare hours spent with budgets and what you can invoice. Talk about the gaps—that’s where the insight is.
