Time Tracker

---
name: time-tracker
description: Track where your time actually goes: manual vs. automatic tracking, categorization, analysis, and turning data into better schedules. Use when diagnosing time leaks or building an honest picture of your workweek.
category: productivity
---

# Time Tracker

## Overview

Most people's sense of their time is fiction: we overestimate deep work, underestimate meetings and context-switching.

Time tracking replaces stories with data. The skill: low-friction tracking, sensible categories, and acting on findings.

Two approaches: manual (start/stop timer — accurate, needs discipline) and automatic (software logs apps/sites — effortless, needs categorizing).

Best systems combine both: automatic capture for the raw record, a 5-minute daily tidy for meaning.

The analysis is one comparison: planned allocation vs. tracked reality. The gap is the entire insight.

## When to use

- Feeling busy but unsure what you're actually producing
- Preparing for a schedule redesign, role change, or negotiation
- Billing clients or justifying headcount with evidence
- Diagnosing why deep work never happens despite 'having time'
- Quantifying meeting load for yourself or a team

## Core concepts

- **Track everything for 2-4 weeks.**
  A short complete sample beats a year of partial data. Two weeks is usually enough to redesign a schedule.
- **Categories over projects.**
  6-10 broad buckets (deep work, meetings, messaging, admin, learning) reveal patterns better than 40 project tags.
- **Automatic capture + manual meaning.**
  Software logs the timeline; you spend 5 min each evening assigning categories. Manual-only dies within days.
- **Actual vs. intended.**
  Planned allocation vs. tracked reality, per category. Don't analyze raw hours in isolation — compare against intent.
- **Deep vs. shallow.**
  Separate value-creating time from overhead, whatever your frame. Overhead past 50% is the classic finding.
- **Fragmentation tax.**
  Ten scattered 15-min tasks cost far more than 150 minutes — each switch has refocus cost. Track switches and longest focus blocks.
- **Privacy by design.**
  Time data is sensitive. Keep it local or trusted, aggregate before sharing, never surveil others without consent.
- **Baseline before optimizing.**
  Track two weeks without changing behavior. Premature optimization corrupts the data you need.

## Practical workflow

1. **Define categories first.**
   6-10 covering your week, including 'uncategorized' — its size signals tracking quality.
2. **Set up capture.**
   Automatic tracker on work devices; simple manual timer for offline work, walks, thinking time (which counts).
3. **Run a 2-week baseline.**
   Observe without intervening. Resist the urge to 'be good' — you need the truth first.
4. **Do the 5-minute daily tidy.**
   Categorize each evening while memory is fresh. Next-week reconstruction is fiction.
5. **Analyze weekly, one page.**
   Hours per category, deep-work per day, meeting load, switches per day, longest focus block. Written findings.
6. **Redesign one thing.**
   Single lever from the data: batch meetings, protect mornings, cap email windows, kill a recurring meeting. Then re-measure.
7. **Re-track quarterly.**
   One week per quarter keeps the picture honest without permanent overhead.
8. **Count offline work.**
   Thinking, walking, whiteboarding count. If only screen time is tracked, deep thinking looks like 'idle.'

## Common pitfalls

- **Tracking with no analysis.**
  Data nobody reviews is self-surveillance. No weekly analysis planned? Don't track.
- **Too-granular categories.**
  30 categories collapse within days. Start broad; split only categories that surprise you.
- **Manual-only tracking.**
  Start/stop discipline dies under real workload — exactly when data matters most. Automate capture.
- **Optimizing during baseline.**
  Changing behavior while measuring defeats the purpose. Observe first, intervene after.
- **Ignoring context switches.**
  Hour counts without fragmentation miss the biggest killer. Twelve 20-min blocks is not '4 hours of work' — it's mush.
- **Data as weapon.**
  Guilt spirals for yourself, micromanagement for others. Time data informs design; it doesn't punish humans.
- **Analysis paralysis.**
  Hours building beautiful dashboards instead of pulling the one obvious lever. First analysis usually reveals one big fix.
- **Forgetting the why.**
  Tracking without a question ('where does deep work go?') produces numbers nobody acts on. Start from the question.