Break repetitive thought loops by mapping what’s really driving the issue across key life areas, using a structured coaching reflection framework.
This structured reflection moves from situation to thoughts to core problem to possible solutions - would working through a current challenge using that sequence be a useful way to prepare for our next session?
A senior product manager has been describing a conflict with a peer for three sessions. The story is consistent: what the peer did, why it's frustrating, what he has tried. Nothing has changed. He is clearly thinking about it carefully, but the thinking is going in circles. He describes the situation accurately and then restates it. No new information is entering the loop.
'I want to try something different with this situation. This worksheet separates the situation - what an observer would report - from your thoughts about it. Those are different things, and you've been treating them as one. Write the situation in 'Situation' and only the observable facts. Save everything else for the next field.' The instruction to separate facts from interpretation is often the useful disruption for someone in a loop.
Situation fields that contain interpretation ('he clearly doesn't respect the process') rather than observable events ('he sent the proposal directly to the VP without telling me'). The separation between those two levels is the exercise. Watch for the 'Thoughts' field to be skipped quickly in favor of 'Problem' - the interpretive layer is the one clients most want to bypass, but it's where the constraint usually lives. If Thoughts is thin, the Reflections field will be thin too.
Read his Situation field aloud: 'Is there anything in here that is actually your interpretation of events rather than what happened?' That question often immediately produces 2-3 revisions. Then move to Thoughts: 'Which of these interpretations is doing the most work in how this situation feels?' That's the question that locates the constraining story. The Solutions section comes last, and only after those two fields have real content.
A client whose Reflections section consistently defaults to 'I don't know what I'm missing' - not as a placeholder, but as a genuine response - may be in a situation where outside perspective is structurally absent. Severity: low. The reflections field is meant to simulate that outside view. If he can't access it, ask directly: 'What would someone who knows you well but isn't involved in this situation notice about how you're framing it?'
A COO brings well-structured problems to sessions. She describes situations clearly and arrives with solutions already in hand. She moves through the space between problem and solution very quickly - often too quickly. Her solutions are reasonable but occasionally miss the actual constraint because the problem definition was assumed, not examined.
'Before you take me to the solution you have in mind, let's use this structure to map the problem first. I'm going to ask you to stop at each section before moving to the next. The constraint often isn't in the Solution field - it's in Thoughts or Reflections.' The instruction to stop between sections is literal. Don't let her complete the full worksheet in one pass; pause at Thoughts and Reflections.
Problem fields that are crisp and clear but appear before the Situation and Thoughts fields have been adequately populated. The problem definition often smuggles in the solution direction - 'the problem is we need a better process for X' already points toward a category of solution. Watch for the Reflections field to confirm the existing solution rather than genuinely question the framing: 'I might be missing some context' instead of naming a specific assumption.
After the worksheet is complete, compare Problem to Situation: 'Is the problem you named actually supported by the situation you described, or did the problem definition come from somewhere else?' That question tests whether the sequencing did its work. Then go to Reflections: 'What assumption in your Problem field would change your solution most if it turned out to be wrong?'
A leader who produces detailed solutions in the Solutions field that bear no relationship to what appeared in Reflections may have a practice of treating Reflections as an obligatory step rather than a genuine one. Severity: low. Rather than flagging this directly, try asking her to write the Reflections field as if she were advising a colleague rather than herself. That distance sometimes produces a more honest read.
A director of customer success describes workplace situations in careful detail but rarely includes his own perspective on what they mean. He reports what happened, what others said, what the outcome was. When asked what he thinks about it, he tends to answer with what other people think. He has strong situational awareness and limited access to his own interpretive layer.
'This worksheet has a field that most people rush past, called Thoughts. It asks what you're telling yourself about the situation - not what's objectively true, not what others think, but the story you're running about it. I want you to spend as long on that field as you do on Situation. That's where the work is for you.' Name the specific field and the specific invitation before he starts.
Thoughts fields that read like a continued Situation field ('he said X, and then Y happened') rather than an interpretive layer ('I'm telling myself this means he doesn't trust me to handle it'). Watch also for Thoughts to be framed as other people's thoughts about the situation ('my manager thinks I should have caught this earlier'). The field asks for his interpretations. The confusion between his thoughts and others' thoughts is itself a signal.
Start with the Thoughts field. Read it back to him and ask: 'How many of these are actually your read on the situation versus someone else's?' Then: 'Which one is the interpretation that has the most hold on how this feels?' That question asks him to rank the interpretations by influence, which requires him to own them as his. Then move to Reflections with: 'Given that interpretation - what might you be getting wrong?'
A client who consistently cannot populate the Thoughts field with genuine first-person interpretations across multiple uses of this tool may have a pattern of external attribution that is significant enough to warrant direct exploration. Severity: low to moderate. Surface it: 'I notice this field tends to be hard for you in a specific way - it seems easier to describe what others think than what you think. What's that like to notice?'
A client anxious about a specific goal or situation and wants a behavioral map
LifeClient describes feeling 'bad' or 'off' but cannot name the emotion with any specificity
LifeClient has strong self-knowledge but struggles to act on what they know
