WOOP for Organizations: Institutionalizing a Personal Technique into Organizational Decisions
This article was generated by AI. The accuracy of the content is not guaranteed, and we accept no responsibility for any damages resulting from use of this article. By continuing to read, you agree to the Terms of Use.
- Intended readers: Strategy leads, PMs, and corporate-planning staff who design strategy formulation, project kickoffs, or quarterly reviews
- Assumed background: The basic concept of “Designing Paired Negative”
- Reading time: Full read about 15 minutes / skim about 5 minutes
Overview
WOOP (Wish → Outcome → Obstacle → Plan) is a personal motivation framework Gabriele Oettingen established through two decades of empirical research1. It starts from the counter-intuitive finding that “positive fantasy impairs achievement,” and it builds in a discipline of looking the Obstacle in the face.
This article extends the WOOP introduced in STEP 1-D of the sister piece “Implementation Guide for Organizational Context Supply Capability” into a design for organizational decision-making. It covers application patterns for strategy formulation, project kickoffs, and quarterly reviews, along with the most common failure mode (escaping into external Obstacles).
Why WOOP works for organizations
Oettingen’s central finding: positive fantasy — comfortably imagining the desired future as if it had already been achieved — actually reduces energy and effort and impairs real-world achievement1. The effect replicates across weight loss, job search, romantic relationships, and academic performance. Her alternative is WOOP, which deliberately incorporates looking the Obstacle in the face.
At the organizational level, exhortations like “let’s paint a big vision” or “let’s stay positive” share exactly the structure of positive fantasy. When strategy formulation collapses into beautiful vision statements, achievement recedes. WOOP for organizations is a structural countermeasure to that trap.
The WOOP framework
1
2
3
4
Wish: The wish to achieve (kept short)
Outcome: The best outcome of a world in which the wish is achieved
Obstacle: The biggest obstacle inside yourself / the organization (focus on internal, not external)
Plan: "if X then Y" actions prepared for when the Obstacle appears
Personal version vs. organizational version
| Element | Personal | Organizational |
|---|---|---|
| Wish | Personal goal | Strategic goal / project goal |
| Outcome | Best outcome for the individual | Best outcome for all stakeholders |
| Obstacle | Personal habits / psychology | Internal organizational structure / culture / dynamics |
| Plan | If-then personal action | If-then organizational process / decision rights |
The defining feature of the organizational version is that the Obstacle is organizational structure, not individual psychology. “When priorities shift, we run out of people,” “our coordination with sales is weak,” “executive approval is slow,” “burnout occurred on the last project of this kind” — these are the kinds of organizational obstacles you write into Obstacle.
Application pattern 1: WOOP in strategy formulation
Use a WOOP template in quarterly, semi-annual, and annual strategy formulation:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
## Strategy WOOP (Q3 2026)
### Wish
[Concrete strategic goal. 1-2 sentences]
### Outcome (the world in which it is achieved)
- For customers:
- For team members:
- For shareholders / leadership:
### Obstacle (top 3 internal obstacles)
1. [Structural / organizational obstacle]
2. [Cultural / dynamics obstacle]
3. [Resource / capability obstacle]
* External factors (market, competition, regulation) do NOT belong here. Put them in a separate section.
### Plan (if-then form)
- If Obstacle 1 appears, execute X (Owner: __, Trigger: __)
- If Obstacle 2 appears, execute Y
- If Obstacle 3 appears, execute Z
The “don’t escape into external factors” discipline
The biggest trap in organizational WOOP is escaping the Obstacle field into external factors. Teams tend to write things like “if the market cools,” “if regulation changes,” “if a competitor moves” — but these aren’t avoidable obstacles, so no Plan can be built against them.
Refocus on internal factors instead: “If the market cools, how many months until our cash runway hits the danger zone, and have we agreed on what to cut before then?” “If regulation changes, how many person-months does compliance take, and can our current team absorb it?”
External factors are triggers; the actual Obstacle is your organization’s inability to respond to them.
Application pattern 2: WOOP at project kickoff
At the start of a new project, combine WOOP with a Pitch document (Shape Up2):
1
2
3
4
5
6
7
8
9
10
11
12
13
## Project Kickoff WOOP
### Pitch (Shape Up)
- Problem / Appetite / Solution / Rabbit holes / No-gos
### WOOP layer
- Wish: project goal
- Outcome: ideal post-launch state
- Obstacle:
- Failure patterns from past projects of this kind
- Structural weaknesses of this team
- Past coordination friction with adjacent teams
- Plan: "if-then" processes for each Obstacle
This pairs naturally with Klein’s premortem technique3 (asking, from a future in which the project failed, what went wrong and working backward). Premortems develop the imagination of failure; WOOP prepares the actions for failure. Combining them gives you the organizational version of Defensive Pessimism4.
Application pattern 3: WOOP in quarterly reviews
In quarterly reviews, revisit the previous period’s Plan:
1
2
3
4
5
6
7
8
9
10
11
12
## Quarterly Review WOOP
### Achievement against last quarter's Wish
[Achieved / partially achieved / not achieved]
### Obstacles that actually showed up
- Showed up as predicted → did the Plan work?
- Showed up unexpectedly → why couldn't we predict it?
- Predicted but didn't show up → keep / modify / drop the Plan
### This quarter's updated Wish and Obstacle
- ...
This isn’t just a “retrospective meeting”; it’s a mechanism for growing Obstacle prediction capability at the organizational level. Gollwitzer’s research on implementation intentions5 shows that the “if-then” form sharpens recognition of concrete triggers and shortens response time.
Anti-patterns
| Pattern | Why it backfires |
|---|---|
| Escaping into external factors (market, competition) | No Plan possible; turns into blame-shifting |
| Writing Obstacles abstractly (“lack of resources”) | No concrete trigger to recognize, so Plan never fires |
| Writing Plan as wishful intent (“we’ll try harder,” “we’ll be careful”) | Lacks “if-then” specificity |
| Ritualizing WOOP | Form is preserved but the Obstacle-confrontation discipline drains away |
| WOOP sessions that are “fun” | A workshop that’s only fun is avoiding Obstacle confrontation |
| Listing only one Obstacle | Single-point focus leaves blind spots |
WOOP as a higher-order process for paired negative
WOOP is Defensive Pessimism for individuals, institutionalized into a decision-making process. In the same way, while paired negative (sister article) handles individual acts of pointing out problems, WOOP handles whole strategies and projects. They differ only in scope; the philosophy is the same:
- Paired negative: pairing a problem call-out with a direction for response, in a single utterance
- WOOP: pairing a Wish + Outcome + Obstacle + response Plan in a single decision
An organization that practices paired negative day-to-day shifts naturally into organizational WOOP, and vice versa.
Summary
- Positive fantasy (comfortable imagination of achievement) reduces effort and impairs achievement
- WOOP is an empirically-validated framework that builds in Obstacle confrontation
- The key to organizational WOOP: a discipline of keeping the Obstacle on internal factors
- Applicable to strategy formulation, project kickoffs, and quarterly reviews
- Combined with premortems, it forms the organizational version of Defensive Pessimism
- It sits as a higher-order process above paired negative
Related articles
- Implementation Guide for Organizational Context Supply Capability: From Facing Problems to Repair — Parent article
- Designing Paired Negative: How It Differs from Solo Negative, and Why It Moves Organizations — The individual-action version of WOOP
- Implementation Guide for ADR / Pitch / Kickoff Memos — Document design that incorporates WOOP
References
Rethinking Positive Thinking: Inside the New Science of Motivation — Gabriele Oettingen, Current / Penguin Random House (2014). ISBN: 9781617230233. Underlying empirical paper: Oettingen & Mayer (2002) JPSP 83(5). [Reliability: High] ↩︎ ↩︎2
Shape Up: Stop Running in Circles and Ship Work that Matters — Ryan Singer, Basecamp (2019). [Reliability: Medium-High] ↩︎
Performing a Project Premortem — Gary Klein, Harvard Business Review (September 2007). The premortem technique. [Reliability: High] ↩︎
Defensive Pessimism: Harnessing Anxiety as Motivation — Julie K. Norem, Nancy Cantor, JPSP, vol. 51, no. 6 (1986). DOI: 10.1037/0022-3514.51.6.1208. [Reliability: High] ↩︎
Implementation Intentions: Strong Effects of Simple Plans — Peter M. Gollwitzer, American Psychologist, vol. 54, no. 7 (1999). DOI: 10.1037/0003-066X.54.7.493. The effect of “if-then” plans. [Reliability: High] ↩︎