Celebration and Wins Log

A client who produces strong results consistently but experiences almost no satisfaction from them. They complete a project, note that it went well, and immediately orient to what's next. In sessions, wins from the previous month are described in one sentence and then set aside. They describe themselves as 'always looking forward,' which feels like a strength to them but functions as a pattern that prevents them from building confidence from their own track record.

Frame this as a data-collection tool before it's a reflection tool. 'Before we can understand what's actually producing your results, we need to document the results. Most of what you know about what you're doing well lives in your short-term memory and disappears.' The enabling factors column is the most important field: it shifts the tool from a victory lap to an analytical exercise, which is more acceptable to clients who resist celebration as self-indulgence. 'What made this possible?' is less threatening than 'celebrate this.'

Watch the enabling factors column for attribution patterns. Clients who consistently attribute wins to circumstances ('the client was easy to work with'), team effort ('we got lucky with timing'), or external conditions rather than their own competence are using the log to document outcomes without claiming agency over them. The wins column is less important than what the client writes after 'what made this possible' - that column reveals self-concept more reliably than any direct assessment. If the enabling factors column is consistently blank or vague, that's the coaching conversation.

Start with the enabling factors column, not the wins. 'Look at what you wrote here - what pattern do you see across your wins this month?' Most clients haven't looked at their wins as a dataset before. The question that typically shifts the conversation: 'If someone who didn't know you read these enabling factors, what would they conclude about what you're good at?' Clients who minimize their wins often accept this framing more readily because it's hypothetical. Move from the log to the next session: 'Which of these wins tells you something about what you should pursue more of?'

A leader who experienced a visible professional failure - a product launch that missed, a team conflict that became organizational, a presentation that went badly at an important moment. They've intellectually processed the failure but their confidence in their own competence has been shaken in a way they haven't recovered from. They continue to perform well by external measures but they no longer trust their own judgment the way they used to.

Position this as counter-evidence documentation, not positivity practice. 'Your brain is currently running a bias toward confirming the story the failure told about you. This tool creates a competing dataset.' The wins need to be specific and named, not general - 'handled the Q3 client situation well' is less useful than 'caught the scope creep on the Chen account before it became a problem and renegotiated the timeline in one conversation.' Specificity is what makes the evidence weighty enough to compete with the failure narrative.

Watch for the client logging wins that occurred before the failure but not since. Some clients build the log backward, documenting historical wins rather than current ones, because the current ones don't feel as real. If the log is populated but the client still can't point to a recent example of something they handled well, ask directly: 'What happened this week that you'd put on this list if you were logging it?' Resistance to logging recent wins may mean the failure narrative is still running stronger than the recovery evidence.

Start with recency: the most recent entry on the log is more important than the oldest. 'What did you log this week that you almost didn't include because you didn't think it counted?' That question surfaces the self-editing pattern. If the log has entries that span before and after the failure event, place them side by side: 'Your log shows you doing X three months before [the failure] and Y two weeks after it. What does that tell you?' The goal is to get the client to see the failure as an event in a pattern of competence, not as a revelation of incompetence.

A professional who consistently undersells their contribution in performance reviews because they can't recall specifics under pressure. They know they did strong work but by the time the review arrives, the specific examples have evaporated. Their written evaluations don't reflect what they actually produced. They want to be able to represent their work accurately, not just feel good about it.

Frame this as evidence collection with a specific end use. 'We're building the raw material for your performance narrative. Every entry in this log is a potential example you can use in a review conversation - but only if it's specific enough to stand alone as evidence.' The enabling factors column doubles as a leadership evidence column: 'I identified the scope gap early and renegotiated before it became a delivery problem' is more useful in a review than 'delivered the project.' Coach the client to write entries as if the reviewer won't know any context.

Watch for entries that are too abstract to be useful in a review context. 'Handled client relationship well' is not usable evidence. 'Stepped in when the account team escalated and resolved the billing dispute in one call by finding the contractual misunderstanding' is. If the client's entries are consistently abstract, they're writing for the feeling of having logged wins, not for the utility of the data. Ask them to rewrite one entry in each session using specifics. The habit of specificity takes a few sessions to build.

Start by asking the client to pick the three entries they'd most want a senior leader to see and explain why those three. The explanation reveals how the client narrates their own contribution - whether they lead with impact, with process, or with relationship. If they consistently choose impact entries, ask what entries related to process or relationship were left off the list. Close by asking: 'Which entry here surprised you most? What does it tell you about what you're actually good at that you don't usually say out loud?'