Activity Value Log

A client who is a VP of marketing at a consumer goods company consistently reports feeling misaligned - she describes her work as 'not what I should be doing' but cannot name what she should be doing instead. She spends significant time on campaign reporting and vendor management, which she frames as necessary but not meaningful. Three to five days of activity logging with the 'How I Feel' and value rating columns produces the concrete data to examine the gap between what she says matters and what she actually does.

Position the log as a data-collection tool rather than a reflection exercise: 'You've been describing a sense of misalignment, but we've been working with your memory of how you spend time, which tends to be approximate. This log tracks what you actually do, how you feel doing it, and how much value it produces - logged in real time or close to it, not reconstructed at the end of the week. Three to five days of honest data will show us what your work actually looks like rather than what you think it looks like. Bring it completed and we'll look at the patterns together.' The distinction between memory-based and logged data is accurate and motivating for analytically-oriented clients.

Watch for the 'How I Feel' column being left blank or populated with uniform neutral ratings - this is the column most clients shortchange but also the one that carries the most diagnostic information. Ask: 'You've rated most entries as medium value and left the feeling column sparse. I want you to go back to two entries - the one you felt best during and the one you felt worst during - and describe those in more detail.' The specific contrast often unlocks what the uniform ratings suppressed. Also watch for the value ratings being completed based on organizational priority rather than the client's own judgment of value - entries rated high because they are on her boss's priority list rather than because they feel meaningful.

Start with the patterns rather than individual entries: 'Looking across the full log - what activities appear most frequently with low value ratings? What is the most common feeling state in the log overall?' The frequency question identifies structural misalignment; the feeling question identifies the emotional texture of her current week. Then ask: 'Is there anything in the log that surprised you - something that felt higher value than you expected, or something that felt worse than you would have predicted?' Surprises in the log are often the most useful data. Close by asking which of the three action items at the bottom of the log - eliminate, schedule for peak energy, minimize task-switching - would make the biggest difference if she acted on it this week.

A client who is a chief of staff at a healthcare system knows that his best thinking happens in the morning but schedules meetings throughout the day including first thing in the morning because his role requires it. He describes afternoons as 'written off' and frequently ends the day having done reactive work rather than the strategic work he intended to do. Three to five days of logging reveals the specific pattern: which activities actually land in which energy states, and where the day's energy architecture is creating consistent interference with the work that matters most.

Frame the log as an energy architecture tool: 'You already know you're better in the morning. What we don't know is exactly what is filling that window versus what you intend it to hold, and what the high-value work that is being displaced is costing. This log tracks both - activity and how you feel during it - so we can see the actual pattern rather than your general sense of it. Five days of logging, including the feeling column. Bring it and we'll map the energy architecture of your actual week.' The 'actual versus intended' distinction is accurate and creates productive tension for clients who already have a theory about their own peak hours.

Watch for the client logging activities during a meeting-heavy week that is not representative of his typical week. Ask: 'Is this week representative, or was it unusually meeting-heavy/unusually free? I want to make sure the log reflects a normal week before we draw conclusions from it.' Also watch for the 'How I Feel' column describing task completion (finished, pending, waiting for input) rather than energy state (energized, depleted, flat, focused). The log needs energy data, not status data. If the client has logged status rather than energy, ask him to re-rate two or three entries before the debrief proceeds.

Map the log against time-of-day: 'Looking at the entries from before 10 AM versus after 2 PM - what value ratings and energy states appear in each window? Is there actually a pattern, or is it more variable than your general sense of it?' Some clients find the log confirms their peak hours; others discover the pattern is less consistent than assumed. Then examine the displacement question: 'What is the highest-value activity on this log, and what time of day did it actually happen? Was that your peak window?' If the highest-value work is consistently displaced from the peak window, the action item is specific: protect a morning block from meeting scheduling. Close by asking what one structural change would most reliably move the highest-value work into the window where he is most capable.

A client who is a director of client success at a professional services firm has been managing a weekly status report for eighteen months that he believes no one reads. His manager has never commented on it, no client has ever referenced it, and he spends approximately three hours per week producing it. He has been hesitant to raise the question of eliminating it because he is uncertain whether it actually matters. Five days of logging that includes this activity alongside his genuinely high-value work produces the data to either build the case for elimination or discover a use case he was not aware of.

Position the log as evidence gathering: 'You have a hypothesis about the status report - that it costs three hours per week and produces nothing visible. Before you bring that to your manager, you need data rather than a hunch. Log your actual work for this week, including the status report, with honest value ratings. If the pattern across the log supports the hypothesis, you'll have the full picture: what the report costs in your week relative to what your high-value work produces. That's a more concrete conversation than 'I think no one reads it.'' The evidence-gathering framing converts a hesitant hypothesis into a data collection mission.

Watch for the client rating the status report as medium rather than low value as a defensive hedge against the question he is reluctant to ask. Ask: 'You rated the status report as medium value. What is the medium value it produces?' If he cannot name what value it produces, the medium rating is a hedge. Also watch for the log excluding the status report entirely if the client finds it easier to not document the thing he already wants to eliminate - the omission itself is informative. Ask at the debrief: 'I want to make sure the status report is in the log. Is it there?'

Start by locating the status report entry in the log: 'Where is the status report entry? What did you rate it and how did you feel during it?' Then ask the elimination question with the log as evidence: 'Looking at this entry compared to the three highest-value entries on the same log - is there a case for keeping it at the same priority level?' If the answer is no, the next step is the manager conversation. Ask: 'What would you need to know before bringing this to your manager, and is there a way to find out without making the conversation bigger than it needs to be?' The manager conversation is a separate coaching focus that the log data prepares him for.