WOOP Goal Setting

Client arrives with a goal that is technically appropriate but slightly smaller than what they actually want. The stated goal is manageable, professionally reasonable, and unlikely to require them to confront anything difficult. The real goal — the one with the pull — is one level up from what they wrote. When the Wish field is filled with the safe version, everything downstream is also safe: the Outcome is modest, the Obstacle is organizational rather than internal, and the Plan avoids any behavioral change that would expose them. The WOOP framework only works when the Wish is genuine.

Frame the Wish step as the place where ambition is tested, not announced. 'The first box is about what you actually want — not what seems reasonable to say out loud. Before you write anything, I want to ask: is the goal you have in mind the one with the pull, or a slightly smaller version of it that feels safer to commit to?' The resistance here is self-protective — the client has learned that naming ambitious goals invites scrutiny and accountability. Name it: 'Naming a goal that is slightly smaller than the real one means the plan you build will also be slightly smaller. The framework only closes the right gap when the Wish is the real wish.'

Watch the Wish field for language that hedges commitment: 'improve,' 'work on,' 'begin to,' 'explore.' These phrases describe a direction, not a goal — and a direction cannot be planned for or evaluated. Also watch for the Obstacle field naming organizational or situational constraints ('my manager doesn't create space for this,' 'the team culture isn't there yet') when the actual obstacle is the client's own reluctance or fear. The external obstacle is often true and also not the most useful thing to plan around.

After all four fields are complete, read the Wish back to the client and ask: 'Is this the goal with the pull, or did you write a version that felt safer?' If they confirm it is the safe version, ask what the real one would be — and whether the Plan they wrote would still apply to that. Then turn to the post-tool prompt: 'If this wish came true, what would you have to give up to maintain it?' The giving-up question is the final test of whether the goal is real — a goal the client is unwilling to pay for is aspirational, not actionable.

Client is action-oriented and finds the first three WOOP steps preliminary. They want to write the plan. When they complete the worksheet, the Wish is vague, the Outcome is minimal, and the Obstacle is named but not examined — because all of the client's energy went into the Plan field. The resulting plan is detailed and decisive but is built on an unexamined obstacle and motivated by a lightly imagined outcome. When the obstacle actually arrives, the plan has no connection to anything motivating enough to sustain it.

Frame the sequence as load-bearing, not decorative. 'The four steps build on each other — the Plan is the last step, and it only does what it's supposed to do if the first three are done carefully. The research behind this framework shows that skipping to the Plan is the most common failure mode: you build a good plan for a poorly understood obstacle.' The resistance from action-oriented clients is that the Wish and Outcome steps feel like motivation exercises they have done before. Name it: 'The Outcome step is not about enthusiasm — it is about building the motivational fuel you will need when the obstacle actually shows up. A Plan with no Outcome attached is a task list, not a commitment.'

Watch for the Outcome field being completed in one sentence while the Plan field has three or four detailed items. That asymmetry signals where the client's energy went. Also watch for the Obstacle field naming the obstacle correctly but the Plan not addressing it — the Plan instead describes a positive routine that the client will follow in the absence of the obstacle, rather than a specific response to the obstacle when it appears. 'If I feel overwhelmed, I will review my goals' is not a plan; it is an intention to intend.

After all four fields are complete, read the if-then logic back explicitly: 'Your obstacle is [what they wrote]. Your plan when that obstacle appears is [what they wrote]. If that obstacle showed up tomorrow — does this plan actually address it, or does it address a version of it that isn't quite as difficult?' The question stress-tests the plan against a real scenario. Then ask the post-tool prompt: 'Is your obstacle something external or something internal? If you treated it as internal — what would change about the plan?'

Client arrives with a goal that is not new. They have tried to move on it before. They are not starting fresh — they are trying again, usually with some awareness that the previous attempt failed without being fully clear on why. Working through WOOP on a goal with history requires the coach to use that history: the obstacle they name should be checked against what actually happened before, and the Plan should be tested against the previous attempt's failure point. A standard WOOP pass on a repeated goal misses the most important information available.

Frame WOOP as a retrospective tool as much as a prospective one. 'You've had some version of this goal before. Before we work through the four steps, I want to know: the last time you pursued this — what actually stopped it? We'll use that as a reference point for the Obstacle step.' The resistance from clients in this situation is often shame about the repeated attempt. Name it: 'Most goals that don't hold the first time have a specific failure point that a plan could have addressed. The fact that you're here working on it again means you have more information than you did the first time. We're going to use that.'

Watch the Obstacle field to see whether the client names the same obstacle that derailed the previous attempt — or whether they name a different, safer-sounding one. If the obstacle that stopped them before was avoidance of difficult feedback, and they write 'my schedule becomes unpredictable,' the new plan will fail in the same place for the same reason. Also watch for the Plan being a repetition of what the client tried before with minor adjustments. If the previous plan involved accountability check-ins and it didn't hold, a new plan that also involves accountability check-ins will produce the same result.

After all four fields are complete, ask: 'Does the obstacle you named match what actually stopped the previous attempt — or is it different?' If different, the previous obstacle is still the most useful one and the plan should address it. Then: 'If you had executed this exact Plan the last time — would it have held?' The question requires the client to test the plan against their own experience before the obstacle appears again. Close with the post-tool prompt: 'What would you have to give up to sustain this goal if it succeeds this time?'