The Worry Jar

An executive describes effective problem-solving under actual conditions but a persistent background of worry about scenarios that haven't materialized. They can make clear decisions when the situation is present, but spend significant cognitive load on 'what if' territory. The worry doesn't prevent functioning but it depletes capacity and has started affecting sleep. They describe it as their mind refusing to 'let the problem go' even when no action is required.

Position this as a triage exercise, not a reassurance tool. 'The point isn't to convince you the scenarios won't happen. It's to sort the worry by what it's attached to - because worries that are attached to things you can act on right now are different from worries that require you to wait, and those are different from worries where no action is possible at all. The two columns map that.' Some clients resist this because sorting feels like dismissing real concerns. Name it: 'We're not deciding whether the worry is valid. We're deciding what it requires from you.'

Watch the 'Possible Solutions' column for entries that don't actually address the worry in the left column. Clients who are highly action-oriented sometimes generate solutions to adjacent problems rather than the one named. 'That solution - which worry on the left does it address?' is the question that makes the column honest. Also watch for worries in the left column that are really combinations of several concerns collapsed into one. 'Is this one worry or three?' Disaggregating often makes the 'Possible Solutions' column more tractable.

Start by asking the client to place each worry in one of three categories: requires action now, requires waiting, or no action possible. Ask them to read the 'no action possible' entries aloud and then ask: 'What would you actually do differently if you stopped spending time on this one?' That question often reveals whether the worry is functioning as preparation or as rumination. Then move to the 'requires action now' column: 'Of the solutions you've written, which one would you actually do this week?' Close by asking: 'After sorting these, which ones feel smaller, and which ones feel more real than they did when they were undifferentiated?'

A professional in the middle of a career transition, a personal financial decision, and an organizational change at their current employer describes being unable to prioritize which concern to address first. The worries are interconnected - each one seems to affect the others - and the interconnection has made them feel unmanageable as a set. They're not paralyzed but their decision-making has slowed significantly, and they're aware the delays are compounding the situation.

Use the two-column structure to separate the worries from each other before addressing interconnection. 'The interconnection is real, but the first step is to give each concern its own row. Once they're separate, we can see what each one actually requires. Right now they're compounding each other in your head because they're not separated on paper.' Some clients resist this because they believe separating them misrepresents the reality - everything does affect everything. Name it: 'We're not ignoring the connections. We're just making each one visible before we look at how they interact.'

Watch whether the client writes interconnected worries as one compound entry ('if the job situation doesn't resolve, then the financial decision becomes impossible') rather than as separate rows. If compound entries appear, gently disaggregate them: 'That's two concerns. Give each its own row.' Also watch the 'Possible Solutions' column for entries that are conditional on the other worries resolving first ('once I know what's happening at work, then I can address the finances'). Conditional solutions aren't solutions - they're a sequencing preference. Ask: 'What could you do with this one right now, independent of how the others resolve?'

Start with the 'Possible Solutions' column and ask the client to identify which solutions require no other worry to resolve first. Those are the actionable ones. Then ask: 'Of your worries, which one, if addressed, would make the others smaller?' That question surfaces the leverage point. Close by asking the client to commit to one specific action from the solutions column before the next session - and to name what they'll do if the interconnected worries make that action feel blocked. 'What's your plan if worry B makes you want to delay action A?'

A team leader describes constant low-level worry about whether their team members are performing adequately. They check in more than they intend to, catch themselves reviewing others' work at hours they've decided they won't, and describe a persistent background anxiety that something is being missed. They acknowledge the behavior is affecting team trust but can't stop it because the worry feels legitimate - there are real performance risks on the team.

Position the worksheet as a way to audit which specific worries are actionable. 'The worry about the team isn't irrational - there are real performance concerns. What we're sorting is which of those concerns have something you can do right now versus which ones require waiting, and which ones are outside your control entirely.' Some clients in management worry that sorting their concerns means letting their guard down. Name it: 'Sorting the worry doesn't mean stopping monitoring. It means understanding which monitoring is actually necessary and which is running beyond what the situation requires.'

Watch the left column for worries about individual team members' futures rather than current performance - 'will this person succeed long-term,' 'am I developing them enough.' Those worries can't be addressed through current-state monitoring and tend to drive the over-checking pattern. Also watch the 'Possible Solutions' column for solutions that look like increased oversight. If solutions consistently involve more monitoring, the worksheet may be reinforcing the behavior it's meant to interrupt. 'That solution - does it address the worry, or does it temporarily soothe it?'

Start by asking the client to categorize their worries by whether a solution actually resolves the concern or just manages it. Then ask: 'Which of your worries would still be present even if the team were performing above target?' Those worries are operating independently of performance data - they're not information-processing; they're a default state. Close with the most actionable entry: 'What one concrete action would actually reduce this concern rather than temporarily reassure you?' That distinction - resolving versus soothing - is the key frame for this scenario.