Daily Gratitude Tracker

A senior product manager runs fast, ships consistently, and rarely stops to acknowledge what's working. Their attention is consumed by what's behind, what's at risk, and what needs fixing. The low points feel louder than the wins, even when the wins are real.

Frame this as a data-collection exercise, not a positivity exercise. 'You track metrics for everything else - this is a week's worth of data on what's actually going right. Three specific entries a day, end of day, before you close your laptop.' Clients who dismiss gratitude as soft are more willing to engage when the frame is observational rather than emotional.

Vague entries are the signal. 'Good collaboration' means the client is filling boxes to complete the task. 'Tariq caught the API issue before it hit production and didn't wait to be asked' means the exercise is working. Check specificity: if most entries are categories rather than named events, the client is going through the motions. Also watch the Sunday read-back - clients who say 'it was fine, mostly similar things' have not looked for patterns.

Start by asking them to read three entries aloud - not summarize, read. The act of saying them out loud changes the register. Then ask: 'What themes showed up more than once?' Patterns in a seven-day log are often more informative than the individual entries - relationships that appear repeatedly, times of day that generate better entries, areas of work that never show up. The question that tends to open things up: 'What surprised you about what made the list?'

A director has come through a rough stretch - a failed product launch, a team conflict, or a personal loss - and is functionally back at work but carrying residual low-level demoralization. They are executing but their baseline is flat. The standard 'what's going well' question gets thin answers.

Introduce this with explicit permission for the exercise to feel hard at first. 'Some days the three items will come easily. Other days you'll sit there for a few minutes. Both are useful. The ones you have to work for tell you something about where your attention has been living.' Don't promise it will feel different after a week - say it will give you both something concrete to look at.

Entries that mix what went well with what went wrong ('I finished the deck, but the feedback wasn't great') indicate the client is editing positive entries before writing them. Watch also for blank days or days where entries are completed retroactively (several days at once). The pattern of when entries get made is as informative as what they contain.

Start with the last two or three days, which are freshest. Ask: 'Were there entries that surprised you - things you wouldn't have noticed if you hadn't been looking?' Then move to the full week: 'What's here that you wouldn't have named if I asked you how the week went?' The gap between their verbal summary and what's actually on the page is often significant and worth naming.

An executive director at a nonprofit is highly attuned to team recognition - sends notes, acknowledges effort publicly, names wins in all-hands meetings. When asked what's going well for them personally, they deflect immediately. Their own wellbeing is a blind spot maintained by relentless outward focus.

Name the asymmetry upfront: 'You're good at noticing this for your team. This week, the exercise is about noticing it for yourself - specifically, what you appreciated about your own work and your own life.' Some clients in this profile will treat the exercise as another giving practice. Redirect: 'These entries are private. No one else reads them. They don't have to be useful to anyone else.'

Entries that are about others ('my team handled the funder call well') rather than about the client's own experience. The tracker is designed to surface the client's positive attentional field, not their recognition of others. If three or more entries per day are other-focused, name it in session without judgment: 'I notice most of your entries are about other people. What shows up when you try to name something specifically about you?'

Ask them to read the self-appreciation entries - the ones that are clearly about them, not others. Then ask: 'How did those feel to write?' The answer is usually 'awkward' or 'strange.' That awkwardness is the coaching conversation. 'What makes it easier to notice this in your team than in yourself?' - that question tends to open the real territory.