Time Management Audit

A client logs 55-60 hour weeks and cannot account for where the time goes. They describe feeling constantly behind despite constant effort. Their work output doesn't reflect their hours. They've attributed this to their role being genuinely demanding, to organizational inefficiency, or to difficult colleagues — not to patterns in how they spend their own time.

Position as a diagnostic before any redesign. 'Before we talk about what to change, we need to know what's actually happening. The weekly time log is the starting point — keep it for one real week, including the meetings you didn't choose and the things that just appeared.' The client may be tempted to log a representative week rather than the messy actual week. Push for the actual: 'The representative week is usually the week you wish you had. Log the one you're actually living.'

The actual vs. ideal column in the category analysis is the most useful piece of this tool. Watch specifically for categories where actual time significantly exceeds ideal — these are the places where demand is overrunning intention. Also watch for categories where actual time is dramatically lower than ideal: the client who says they need to spend more time on strategy but logs zero strategy hours is revealing an execution pattern worth examining.

Start with the single largest gap between actual and ideal. 'This is where you're spending the most time beyond what you intended. What's driving that?' Then move to the time thieves table — ask the client to read each item they've identified. The question that tends to open this up: 'Of everything on this list, which one are you most responsible for — not the organization, not other people — you?' The self-generated time thieves are where redesign leverage lives.

A director-level client can articulate their priorities clearly in a session. They know what matters most. They plan their weeks with their priorities in front of them. By Wednesday, the week has been consumed by reactive work and the priorities haven't been touched. The client experiences this as an organizational problem — the environment doesn't allow focused work. The audit is designed to surface whether this is true or whether the client is making choices that produce the pattern.

The log is the starting point, but frame it specifically around the priority question: 'For each time block you log this week, mark whether it was planned or reactive. At the end of the week, we'll know the actual split.' This modification of the basic log creates a planned/reactive ratio the client can see. Some clients are shocked by how low the planned percentage is for work they describe as self-directed.

Watch for whether 'reactive' is used to describe genuine interruptions or as a label the client applies to anything that wasn't in the calendar at the start of the week. A meeting the client scheduled on Tuesday is not reactive — but clients who default to reactive framing will categorize it that way. Push for precision: 'When did this first appear in your schedule? Who initiated it?'

Start with the planned/reactive split if you're using the modification above. 'This ratio is what your week actually looks like. What would need to change to shift that by 10 percentage points in the direction of planned?' Then move to the redesigned week: 'Which of the reactive items on your actual log could have been handled differently — batched, delegated, declined, or moved?' Work through that list specifically rather than in principle.

A recently promoted manager continues to spend most of their time on technical work they're comfortable with rather than the management and strategic work their new role requires. They're skilled at the technical work, it feels productive, and the management work feels ambiguous and uncomfortable. The time log will likely show significant time in the former IC category and near-zero time in management activities.

Frame explicitly around role transition. 'The question isn't whether your time use was good before — it was, for that role. The question is whether the same pattern fits what this role actually requires.' Introduce the tool before they've had time to construct a narrative about how they're doing in the new role, ideally in the first month of the transition.

In the category analysis, watch for how the client populates the categories. IC-to-manager clients often don't have natural categories for people management, team development, or strategic planning — these may not appear on the log at all. If management activities are absent from the actual time log, it's not because the client deprioritized them: it means they didn't happen. That absence is the coaching conversation.

Start with the categories that appear in the ideal column but have zero hours in the actual column. 'You said you want to spend time on X. The week shows zero. What happened?' Then move to the time thieves table with one specific question: 'What on this list is work you should be delegating rather than doing?' The transition from IC to manager is partly a time-use transition — the audit makes the current state visible before the redesign can happen.