Negative Thought Record

Your client has received feedback that they interrupt or talk over colleagues in meetings, especially in disagreement. They don't experience themselves as doing this - they feel they're just trying to contribute. The behavior is creating friction and threatening a key relationship, but the client has no internal record of the thought chain that precedes it.

Introduce after they've described a specific recent incident, not in the abstract. 'Let's slow that meeting down. Walk me through the last time it happened - not what you said, but what you noticed yourself thinking right before you spoke.' Most clients in this position haven't separated the situation from the thought from the behavior. The table gives them columns that make that separation physical on the page. Some clients will resist Step 2 because naming the judgment feels like admitting they were wrong. Frame it differently: 'Examining a thought doesn't mean the thought was wrong. It means we're checking whether it was useful.'

Watch the Judgment column in Step 1. Clients who write situational descriptions instead of actual thoughts ('she was taking over the conversation') haven't found the thought yet. The thought is usually the interpretation underneath the situation: 'She doesn't respect my expertise.' Keep returning to that column until they name an actual judgment. In Step 2, watch the third column - 'What changes if I release this judgment?' Short answers ('I'd be less reactive') haven't done the work. Look for specificity about what they would actually do or say differently.

Start with the rows where Step 2 was left short or blank - those are the judgments with the most grip. Ask: 'Read me what you wrote in the Judgment column for this row.' Then: 'What would have to be true about that situation for this judgment not to apply?' This moves from defending the thought to examining the conditions it requires. If more than three rows have the same judgment in different words, name the pattern explicitly: 'This same story shows up in four different situations. That's useful information.'

Your client is technically strong and valued, but when they receive critical feedback - even mild, constructive feedback - they disengage for days. They stop contributing in meetings, pull back from collaboration, and do only what's required. Their manager has noticed and it's starting to affect how the client is perceived at a senior level. The client is aware of the pattern but hasn't examined what drives it.

Introduce as a pattern tracker, not a feelings diary. 'This isn't about processing how bad the feedback felt. It's about identifying what you told yourself about the feedback - and whether that interpretation was accurate.' Clients who are used to high performance often resist frameworks that feel like they're about emotional management. The clinical table format tends to work for this client type because it feels analytical. Assign Step 1 about the most recent specific feedback incident, not feedback in general.

Watch the Judgment column for absolutist language: 'My work isn't good enough,' 'They don't trust me,' 'I don't belong at this level.' These all-or-nothing interpretations are the ones most worth surfacing in Step 2. In Step 2, watch whether the client can write genuinely in the third column or whether they produce hedged language like 'I might be less defensive' - language that avoids committing to a specific change. Real Step 2 work looks like: 'I'd actually respond to the feedback instead of going silent. I'd ask a follow-up question in the same meeting.'

Start at the Emotion column, not the Judgment column. Ask the client to name which emotion in which row felt most disproportionate to the actual situation. That's usually the entry point to the most productive judgment. Then move to the Judgment column for that row and spend time in Step 2 on it specifically. The question that tends to open this up is: 'What would a colleague who respects your work - and has given you positive feedback - think is true about this situation?'

Your client is in ongoing tension with a peer - a colleague at the same level, a co-founder, or a board member. They're convinced the peer is deliberately working against them: taking credit, excluding them from conversations, or misrepresenting their contributions. The client has brought this up in multiple sessions and the story hasn't changed, which suggests the judgment driving the reaction is fixed.

Introduce gently and specifically: 'You've described this situation a few times now. I want to try something different - not to relitigate what happened, but to look at the thought you're carrying about it and examine what it's doing to you.' Clients who've been replaying a conflict for weeks or months often have high investment in the accuracy of their interpretation. The risk is that they complete the tool as confirmation of the judgment rather than examination of it. Name this upfront: 'The goal isn't to decide whether the judgment is right. It's to notice what it costs you to carry it.'

Watch whether the Judgment column entry changes between Step 1 and Step 2 or stays identical. If the client copies the Step 1 judgment word-for-word into Step 2 without any examination, they've done the accounting without the work. In Step 2, watch the 'What changes if I release this judgment?' column specifically - clients who cannot write anything in this column are not yet able to imagine the alternative, which is itself significant data. Also watch for sarcasm or minimizing in that column: 'Nothing would change, they'd still be doing it.'

Start with the third column of Step 2 - not the judgment, but the imagined release. Ask: 'Read me what you wrote about what changes.' If it's sparse, that's the conversation: 'What would have to be true about this situation for you to be able to write something in that column?' This sidesteps the question of whether the peer is actually undermining them and focuses on what the client can influence. The question that often opens this up: 'Regardless of whether your interpretation is accurate, is carrying this thought helping you navigate the relationship?'

Your client spends disproportionate time preparing for routine meetings - sometimes hours for a 30-minute check-in. They know it's excessive but can't stop. They describe it as 'being thorough' or 'I don't like surprises.' The behavior is affecting their capacity and their ability to operate at the strategic level their role requires.

Introduce as a trigger tracker, not a time audit. 'We're not going to look at how long you prepare. We're going to look at what you tell yourself will happen if you don't.' The over-preparation is the behavior in the Outcome column - the automatic thought driving it is what Step 1 is designed to surface. Assign between sessions and ask them to track the thought at the moment they sit down to prepare, not in retrospect.

Watch the Judgment column for catastrophic or evaluative thoughts: 'I'll be exposed,' 'They'll think I don't know what I'm doing,' 'I can't afford to be wrong in front of this person.' These are different in character from perfectionistic content ('I need this to be complete') and worth distinguishing. In Step 2, watch the Emotion column - clients who list only one emotion for every row may not be differentiating the emotional experience well. More precision there typically produces more precision in the examination.

Start with the Outcome column. Ask: 'When you over-prepare and the meeting goes fine - what happens to the thought in the Judgment column? Does it update, or does it stay in place for the next meeting?' For most clients in this pattern, the thought doesn't update because the over-preparation feels like it caused the good outcome. That loop is the coaching conversation. Then move to Step 2 and the release question: 'What would be different about how you went into meetings if you weren't carrying this thought?'

Your client has identified delegation as a development priority in multiple sessions. They've made commitments and returned without having delegated. They describe wanting to delegate but finding reasons not to in each specific instance: the task is too important, the team member isn't quite ready, this one is easier to just do themselves. The pattern is behavioral - the commits don't transfer to action.

Introduce specifically around one recent delegation that didn't happen. 'Walk me through the last thing you could have delegated and didn't. When you got to the moment of handing it off, what happened in your head?' The tool is useful here because the failure-to-delegate loop has a specific thought triggering it that the client hasn't named. The table gives it a place to land. Some clients resist this framing because they've been told delegation is a 'skill gap' - naming a thought underneath feels more exposing than accepting a skill label. Acknowledge both: 'There's skill involved and there's also a judgment that's interfering.'

Watch whether the judgment named is about the task, the team member, or themselves. 'This task is too complex to delegate' is a task judgment. 'She's not ready' is a team member judgment. 'If I hand this off and it goes wrong, it reflects on me' is a self-judgment. The third type is usually the real driver but gets disguised as the first two. If the first five rows all use task or team member language and none uses self-referential language, ask directly: 'What do you tell yourself about your own reputation in that moment?'

Start by asking the client to count how many different judgments appear in their Step 1 rows. Most clients expecting to find a single pattern are surprised by the variety. Then identify the most common judgment type and move to that row in Step 2. The release question - 'What changes if I let go of this judgment?' - often surfaces the real fear: 'I'd have to trust that someone else's version is good enough, and I don't know if I believe that.' That's the coaching conversation.