Figure out what's actually eating your time before you optimize your calendar
Audit where the time really goes instead of guessing and reorganizing the wrong thing.
- Use it for
- Anyone who feels busy all the time but can't say specifically where the time goes.
Most productivity advice optimizes a calendar built on a guess about where time goes, and the guess is usually wrong in a specific, predictable way: people underestimate context-switching, low-value recurring meetings, and the gap between "time spent near work" and "time spent actually working." Reorganizing a calendar based on the wrong diagnosis produces a nicer-looking calendar and the same actual problem. The fix isn't a better schedule, it's actually looking at where the time went first.
This prompt works from a real time log, not a guess, and pushes past the generic "you're in too many meetings" answer to what's specifically true for you.
When not to use this
Needs an actual log of how you spent your time — a rough calendar export, a few days of honest notes — not a vague sense of being busy. Without real data this just produces generic time-management advice you could have gotten anywhere.
Fill in
Here's a log of how I actually spent my time over {{period}}:
{{log}}
Don't give me generic time-management advice. Analyze what's actually
here:
1. **Where the time really went**, categorized honestly — not just
"meetings" and "work," but specific enough to act on (e.g., recurring
status meetings vs. actual collaborative work vs. context-switching
between unrelated tasks).
2. **The biggest surprise** — something that's eating more time than I'd
have guessed, or a pattern I probably don't consciously notice because
it happens in small pieces throughout the day.
3. **What's actually discretionary** versus what's genuinely fixed —
be honest about which categories I could realistically change versus
which are structural constraints I'm stuck with.
4. **The specific highest-leverage change** — not "reduce meetings
generally," but the one specific thing that, if changed, would free
up the most time for the least disruption.
Base this entirely on the log, not on generic assumptions about how
people spend time.Why it works
Starting from a real log rather than a self-report is what makes the diagnosis trustworthy. People are reliably bad at estimating their own time allocation from memory — meetings and context-switching in particular get underweighted because they don't feel like "using up" time the way a long focused task does, even though they often cost more in aggregate. A real log surfaces that gap instead of inheriting it.
Separating discretionary from structural time is what keeps the output actionable instead of just diagnostic. Knowing you spend twelve hours a week in meetings is only useful if you also know which of those you could actually decline — otherwise it's just a more precise version of feeling busy.
Common mistakes
- ×Logging only work hours and missing the full picture of context-switching between work and non-work interruptions, which is often where the real leak is.
- ×Reconstructing the log from memory a week later instead of logging in the moment or pulling from a real calendar. Memory smooths over exactly the small recurring leaks this is meant to surface.
- ×Treating every "discretionary" category as something to immediately cut. Some discretionary time is doing real work you value — the point is an honest choice, not maximum reduction.
Follow-ups
- If I could only change one thing this log shows, which would you pick and why that one over the others?
- What would this look like if I tracked it for another week — what should I specifically pay attention to that this log might be missing?
Did this work?
You can name a specific time sink you hadn't consciously noticed, with enough detail to actually do something about it — not a generic "you should time-block more."
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.