Track against records, not against people
The distinction is both ethical and practical. Time logged against a customer, an opportunity or a task produces information about the work. Time logged purely against a person produces information about the person, and invites the behaviour that makes the data useless.
Framing matters for adoption: teams log time far more consistently when the output is visibly about the account rather than about them.
What it makes visible
Two things, mainly. Which accounts consume disproportionate effort relative to what they return, and where capacity actually goes compared to where the plan assumed it would.
Both are uncomfortable and both are useful. The first informs pricing and renewal decisions; the second informs hiring.
- Effort per account, for profitability and renewal conversations.
- Effort per deal, to understand cost of sale.
- Billable hours against tasks, for invoicing and payroll.
- Searchable records for audit or client queries.
Friction determines accuracy
Time data is only worth having if it is roughly accurate, and accuracy collapses when logging is a separate end-of-week chore.
Logging from inside the record being worked on — the task, the deal, the customer — keeps the act close to the work. Weekly reconstruction produces tidy numbers that are largely fiction.
Be clear what it is not for
If a team suspects time data will be used to rank individuals, they will round, batch and pad, and the dataset becomes worse than nothing because it looks authoritative.
Saying plainly what the data is used for, and then using it only for that, is the difference between a measurement system and a compliance exercise.