You Don't Need Time Tracking
"What gets measured gets managed." It is the most quoted line in management, printed on posters, slide decks, and boardroom walls for decades. And Peter Drucker, the person everyone attributes it to, never actually said it. The original idea, traced to V.F. Ridgway's 1956 paper, was a warning: quantitative measures of performance tend to distort the very processes they claim to monitor.
You probably did not expect that. And you probably did not expect a time tracking company to tell you that you might not need time tracking. But here we are. There are situations where tracking every hour does more harm than good, and recognizing them is the first step toward using this tool wisely.
When Metrics Become Targets
British economist Charles Goodhart observed something in 1975 that reshaped how we think about measurement: any observed statistical regularity tends to collapse once pressure is placed upon it for control purposes. Anthropologist Marilyn Strathern later distilled this into a cleaner formulation, now known as Goodhart's Law: "When a measure becomes a target, it ceases to be a good measure."
Time tracking is a textbook case. When billable hours become the primary success metric, people start optimizing for the metric rather than the outcome. Software teams measured by hours write verbose code because refactoring (which reduces output) looks like negative productivity. Agencies that reward billed time see creative work suffer as people pad timesheets instead of solving problems.
This is not hypothetical. In Big Law, associates chasing 2,200 billable-hour targets end up working over 3,000 total hours annually. Over 65% report negative mental health effects from this pressure. The metric meant to ensure diligence instead drives burnout and attrition.
History offers a vivid analogy. During British colonial rule in India, authorities placed a bounty on dead cobras. Enterprising locals started breeding cobras for the bounty. When the government canceled the program, breeders released their now-worthless snakes, making the cobra problem worse than before. Replace cobras with billable hours, and you have a portrait of what happens when a well-intentioned metric creates perverse incentives.
The McNamara Fallacy
There is a lesser-known but equally important concept for anyone considering mandatory time tracking: the McNamara Fallacy. Named after Robert McNamara, U.S. Secretary of Defense during the Vietnam War, it describes the trap of making decisions based solely on what you can quantify while ignoring everything you cannot.
Sociologist Daniel Yankelovich described the descent in four steps:
- Measure whatever can be easily measured.
- Disregard what cannot be easily measured, or give it an arbitrary value.
- Presume that what cannot be measured easily is not important.
- Conclude that what cannot be easily measured does not exist.
Time tracking measures hours. It does not measure the quality of ideas, the trust between teammates, the creative breakthrough that came from an "unproductive" afternoon of thinking, or the mentoring conversation that kept a junior team member from quitting. When hours become the only lens through which work is evaluated, these unmeasurable contributions quietly disappear from the organizational radar. Not because they stopped mattering, but because nobody is counting them.
The Real Cost of Tracking Everything
Beyond the philosophical concerns, there are practical problems with mandatory time tracking backed by data.
Productivity Theater
A 2023 Visier survey found that 83% of employees engage in at least some form of productivity theater: performing work for the sake of appearing busy rather than creating value. At companies using surveillance and tracking tools, the problem is five times worse. 61% engage in performative work, compared to 12% at companies that do not monitor. Tracking does not just fail to improve productivity. It actively incentivizes faking it.
The Autonomy Tax
Decades of research in Self-Determination Theory by psychologists Edward Deci and Richard Ryan show that intrinsic motivation depends on three things: autonomy, competence, and relatedness. Their meta-analysis of 128 controlled experiments confirmed that external controls (surveillance, imposed deadlines, pressured evaluations) reliably undermine intrinsic motivation. Mandatory time tracking triggers several of these at once. It is surveillance. It creates implicit deadlines. And it imposes external evaluation on work that was previously self-directed.
As Daniel Pink put it in Drive: "Control leads to compliance; autonomy leads to engagement." If you want your team to do the minimum, track every minute. If you want their best work, think carefully about what you are signaling.
Flow Destruction
Paul Graham's influential essay Maker's Schedule, Manager's Schedule explains why knowledge workers struggle with interruptions: "You can't write or program well in units of an hour. That's barely enough time to get started." Research by Gloria Mark at UC Irvine puts a number on this: after any interruption, it takes an average of 23 minutes to return to the original task. Stopping to log time, classify a task, or switch a timer is an interruption. A team of ten developers losing 15 minutes each to daily time tracking overhead burns over 50 hours of development time per month, and the hidden cost of context switching makes the real toll much higher.
The Classification Dilemma
"Should I log this meeting under project A or project B?" "Is reading documentation research or development?" These questions seem trivial, but they add up. The mental energy spent on categorization is energy not spent on actual work. And the anxiety of potentially miscategorizing time creates a low-level cognitive tax throughout the day. If people need a decision tree to categorize their time, something has gone wrong.
When Time Tracking Actually Helps
Despite everything above, time tracking remains valuable in specific contexts. The key distinction is whether you are measuring to learn or measuring to control.
Client Billing and Transparency
When clients pay for your time, tracking it is not optional. But even here, the goal should be transparency and trust-building, not squeezing maximum billable hours. Honest timesheets and clear reports build the kind of long-term client relationships that billable-hour maximization destroys.
Understanding Reality
Many teams are shocked when they first see where their time actually goes. That "quick" task that keeps eating entire afternoons. The recurring meeting that accomplishes nothing every week. Time tracking as a diagnostic tool, used periodically rather than perpetually, reveals patterns that are invisible to intuition. Track for a few weeks, identify the bottlenecks, act on what you learn. You do not need to track forever to get the insight.
Capacity Planning
How many projects can your team realistically handle next quarter? Without historical data, you are guessing. Time tracking provides the foundation for sustainable workloads and realistic commitments, the kind that prevent the crunch cycles that burn teams out.
Personal Awareness
Some individuals find tracking their own time genuinely useful. Not because someone demands it, but because it helps them understand their patterns, protect focus time, and make conscious choices about priorities. The difference is voluntary versus mandatory. Freely chosen tracking supports autonomy. Imposed tracking undermines it.
Doing It Right
If you decide time tracking makes sense for your situation, here is how to avoid the pitfalls.
Measure outcomes, not hours. Track time as an input, but evaluate success by what gets delivered. Jason Fried, co-founder of 37signals, put it simply: "I have no idea how many hours my employees work. I just know they get the work done."
Start with appetite, not estimates. The Shape Up methodology replaces "How long will this take?" with "How much time is this worth?" Instead of tracking hours against an estimate, you define a time budget and shape the work to fit it. The budget becomes a creative constraint, not a surveillance mechanism.
Keep categories simple. Three to five categories beat thirty. If your categorization system requires a training session, simplify it.
Make it frictionless. The less tracking interferes with actual work, the better the data. Tools that stay out of your way produce more honest data than tools that demand constant attention, because people actually use them.
Review trends, not timestamps. Look at weekly patterns, not whether someone started at 9:01 or 9:03. Micromanagement destroys the very productivity you are trying to improve.
Question the practice regularly. Time tracking should prove its value continuously. If you cannot articulate what decisions it improves, you probably do not need it.
The Bottom Line
Time tracking is a tool, not a virtue. Like any tool, it works well for some jobs and poorly for others. The worst outcome is not failing to track time. It is tracking time religiously while falling into the McNamara Fallacy, where the hours on the spreadsheet feel like certainty while the things that actually matter go unmeasured.
Use time tracking when it serves a clear purpose: client billing, diagnostics, capacity planning, personal awareness. Abandon it when it drifts toward surveillance and control. And whatever you do, never let the measure become more important than the work itself.
At Sandtime.io, we built a time tracker designed for teams that want insight without micromanagement. Simple categories, minimal friction, focus on what matters. Because the best time tracking is the kind you barely notice.