Time audit: log waking hours in 30-min blocks for one…
Log how you spent your waking hours in thirty-minute blocks for one week, then categorize every block by domain and calculate the percentage of discretionary time each priority actually received.
Why This Is a Rule
Your stated priorities and your time allocation tell different stories. You say "product launch is my top priority" — but your time log shows 4 hours on it and 20 hours on email, meetings, and administrative tasks. The time log reveals your actual priorities through revealed preferences (Audit your last seven days of behavior against stated…): whatever gets the most time is what you actually prioritize, regardless of what you say.
The 30-minute block resolution is the Goldilocks granularity: fine enough to capture meaningful patterns (a 30-minute meeting shows up distinctly) but coarse enough to be sustainable for a full week (nobody can maintain minute-by-minute logging). One week provides enough data for pattern recognition while being short enough to maintain logging discipline.
The "discretionary time" calculation is critical. Not all time is available for priority work — sleep, commuting, meals, and non-negotiable obligations consume hours that were never available for priorities. Calculating percentages of discretionary time (the hours you actually control) produces an honest assessment of allocation. "My top priority got 10% of my discretionary time" is the real metric, not "I spent 4 hours on it this week."
When This Fires
- Before designing any time management system — measure current state first (Instrument before executing — drift detection requires… baseline before intervention)
- When stated priorities don't seem to be advancing despite effort
- Quarterly, to verify that time allocation matches priority ranking
- Complements Log every task AND its trigger for one full day — then… (reactivity audit) with the broader time-allocation measurement
Common Failure Mode
Estimating rather than logging: "I spend about half my time on important work." Estimates are systematically biased toward stated priorities. Logging reveals the truth: the "about half" is often 15-25%, with the rest consumed by categories you'd never intentionally prioritize.
The Protocol
(1) For one full week, log every 30-minute block of waking time: what you did, categorized by domain (priority 1 work, priority 2 work, meetings, email, admin, personal, etc.). (2) At week's end: calculate total hours per category. Calculate discretionary hours (total waking hours minus non-negotiable obligations). (3) For each priority: hours spent ÷ discretionary hours = percentage of discretionary time received. (4) Compare percentages to priority rankings: does priority #1 get the highest percentage? Does the ranking order match the allocation order? (5) Mismatches reveal revealed preferences that contradict stated priorities. Address the mismatch through structural changes (Block Q2 tasks on the calendar with specific day+hour…, Group weekly tasks under parent objectives, allocate best…), not through willpower to "spend more time on priorities."