How to Apply the Woop (wish, Outcome, Obstacle, Plan) Method to Visualize and Plan Your Goals (Future Builder)

Use the WOOP Method

Published By MetalHatsCats Team

How to Apply the WOOP (Wish, Outcome, Obstacle, Plan) Method to Visualize and Plan Your Goals (Future Builder)

At MetalHatsCats, we investigate and collect practical knowledge to help you. We share it for free, we educate, and we provide tools to apply it. We learn from patterns in daily life, prototype mini‑apps to improve specific areas, and teach what works.

We open with a short scene: it is 08:12 on a Wednesday, coffee cooling beside a small notebook, a calendar with three crossed‑out dates and one circled. We can feel the tug of a big goal — run a 10 km race, finish a draft, clear a backlog of 40 emails — and the same tug of small, familiar frictions: a meeting that runs long, a kitchen that needs cleaning, the couch that knows our name. WOOP offers a structured, lightweight way to turn that tug into an immediate, testable action. Today we will practice it, and we will log it.

Hack #190 is available in the Brali LifeOS app.

Brali LifeOS

Brali LifeOS — plan, act, and grow every day

Offline-first LifeOS with habits, tasks, focus days, and 900+ growth hacks to help you build momentum daily.

Get it on Google PlayDownload on the App Store

Explore the Brali LifeOS app →

Background snapshot

WOOP began as an evidence‑based self‑regulation technique developed by Gabriele Oettingen and colleagues in the early 2000s. It combines mental contrasting (imaging a desired future and the obstacles standing between you and it) with implementation intentions ("if X occurs, then I will do Y"). Common traps include being too vague about the wish (we say “get healthier” instead of “walk 25 minutes four times a week”), imagining outcomes only in a pleasant, relaxing way (which reduces urgency), and making plans that are too abstract to use in real situations. When people change outcomes, they usually: (a) specify exact behavior, (b) identify a small, realistic obstacle with a one‑step plan, and (c) rehearse the plan. Studies show that WOOP increased goal attainment by roughly 10–30% across varied settings; in one quasi‑controlled set of trials, people using WOOP were around 1.2–1.5 times more likely to complete intended tasks over four weeks. The technique often fails when people skip the "O" (Obstacle) or write plans in conditional language rather than implementing "if–then" triggers.

What WOOP is, in one sentence: wish a clear outcome, visualize the best result, surface the internal obstacle you actually expect, and write a simple if–then plan to act when that obstacle appears. What WOOP is not: a long motivational speech, a distant affirmations ritual, or a deep therapy substitute.

We begin with a practice promise: by the end of the day, we will carry out a single WOOP cycle for one concrete wish, enter it in Brali LifeOS, and perform a three‑question check‑in tonight. We will not perfect everything, but we will make a measurable, repeatable start.

Why practice first? Our first priority is to move you from thinking to doing. The WOOP method is designed for quick iteration—one minute to set the wish, three minutes to form the if‑then plan, and one follow‑up check‑in in the evening. If we can get a quick success today, we increase the chance of repeating it tomorrow. Small wins compound. We will show several micro‑scenes across typical days so you can copy the moves.

The structure of this long read

We will move through lived micro‑scenes: choosing a wish, imagining the outcome, naming the obstacle, making the plan, recording the plan in Brali LifeOS, executing a micro‑task, and learning from one pivot. Along the way we will provide sample scripts, exact wording for if–then plans, numbers, and a Sample Day Tally for a typical target. We will end with check‑ins, risks and limits, a simple alternative for ≤5 minutes, a Mini‑App Nudge, and the Hack Card. We assume you will use Brali LifeOS to track tasks, check‑ins and a short journal entry; the link again is: https://metalhatscats.com/life-os/woop-goal-planner

SECTION 1 — Choosing the Wish: a deliberate, small, measurable start We choose a wish that is meaningful and doable within weeks. Too big a wish (publish a book) creates fog. Too small a wish (drink water now) is trivial. We aim for the sweet spot: specific, challenging but attainable in 2–8 weeks, and behavior‑linked. Example wishes:

  • "Walk 25 minutes, 4 times per week, for the next 4 weeks." (behavior, frequency, duration)
  • "Write 300 words on the article draft every weekday evening for 10 weekdays." (count & schedule)
  • "Clear the email inbox to 10 items by Friday and keep it below 15." (numeric target & deadline)

Concretely, we pick one and commit to one day of practice. Choose now. We'll walk through a micro‑scene: we sit with the notebook. We write one line: "Wish: Walk 25 min ×4/week." It takes 20–30 seconds.

Why this formulation works: it specifies the action (walk), the dose (25 minutes), the frequency (4 times weekly), and a timeframe (for the next 4 weeks). If we had said "get fit", we would drift. If we had said "do more exercise", the brain would ask "what counts?"

Practice task—right now Take a piece of paper or open Brali LifeOS and write one wish in the precise form: verb + metric + frequency + timeframe. Spend two minutes. If you cannot decide, use the "default WISH": "Complete one 25‑minute session of the target behavior today." This default keeps urgency and reduces planning paralysis.

SECTION 2 — Outcome: visualize the best concrete result We close our eyes for 30 seconds and imagine the best outcome. Not abstract praise; specific sensory detail. If our wish is "Walk 25 min ×4/week", what does success look/feel/sound like?

Micro‑scene We imagine finishing the 25‑minute walk: shoes slightly damp with evening steam, cheeks flushed 1.5 points warmer on a 1–10 scale, breathing easy, the playlist at track 8, a small note in our Brali journal reading "25/25 min — felt energized." We focus on three things: bodily feeling, immediate benefit (energized, clearer), and a short social or identity sentence: "I am someone who walks regularly."

Quantify the outcome. If the outcome is a race finish, give a time (e.g., finish 10 km in 60 minutes). If it is weight loss, be specific (lose 2 kg in 6 weeks). If it is email, specify a number. Numbers anchor the imagination and make planning actionable.

Practice task—today Write the outcome in one sentence in Brali LifeOS or the notebook. Include the sensory detail and one numeric statement. Example: "Outcome: After 25 minutes of walking, I feel 3/10 less tired and have completed 1 of 4 weekly walks." This takes 60–90 seconds.

SECTION 3 — Obstacle: find the realistic, personal barrier This is the critical pivot in WOOP. The obstacle is not "traffic" or "lack of time" unless that directly maps to our internal decision. We search for the internal action tendency that will stop us: "I will procrastinate after work, saying I'll do it tomorrow", or "I will wait until I feel like it", or "I will choose to scroll instead." Those internal triggers are the ones we can plan for.

Micro‑scene We imagine coming home at 18:30. The couch looks soft, our laptop hums. The internal voice says, "You deserve to rest; walk later." We write: "Obstacle: I feel tired and convince myself it'll be OK to skip." That is a precise, internal obstacle. It usually takes 1–2 minutes to find it.

Common internal obstacles and typical if‑then pivots (examples)

  • Obstacle: "I will forget." Plan: "If it is 18:00 and I haven't put on shoes, then I will set a 3‑minute timer and put my shoes on during it."
  • Obstacle: "I will tell myself I need more time." Plan: "If I talk myself out of the walk, then I will commit to 10 minutes, not 25 (start small)."
  • Obstacle: "I will do one more email." Plan: "If I open emails after 17:30, then I will close the laptop and walk immediately."

We assumed X → observed Y → changed to Z We assumed "people will be stopped by external obstacles" → observed "most people are stopped by internal rationalizations and excuses" → changed to "framing obstacles as internal decision points and naming those internal voices in the plan."

Practice task—today Spend 2 minutes noting one internal obstacle that will likely stop the wish. Keep the language first‑person and present tense: "I will [specific mental move]."

SECTION 4 — Plan: create a short if–then implementation intention This is where WOOP moves from imagination to action. The plan should be compact, clear, and immediately usable in a real moment. The structure is: "If [situation/trigger], then I will [specific behavior]." Keep the "then" action to 1–2 steps, each step taking under 2 minutes. The plan should not be "be more disciplined" or "try harder."

Micro‑scene We write: "If it is 18:30 and I feel like delaying, then I will put on my walking shoes and step outside for at least 10 minutes." That plan anticipates the internal hurdle and gives a concrete, low‑barrier action.

Concrete wording patterns that work

  • If I notice I am saying 'I'll do it later', then I will set a 10‑minute timer and start the session.
  • If it's raining and I would skip, then I will do a 20‑minute indoor march and play my walking playlist.
  • If I see messages after work, then I will silence notifications for 45 minutes and put my phone in the kitchen.

Practice task—today Write one if–then statement that you can use immediately. Enter it into Brali LifeOS as a task and set the time window or condition. Use exact words; it's okay to sound slightly awkward. The fidelity of language matters for automatic retrieval.

SECTION 5 — Entering WOOP in Brali LifeOS: translate thinking into trackable tasks Brali LifeOS is not a magic pill — it is the scaffold where tasks, reminders, and short journaling meet. We will use it to hold the wish, outcome, obstacle, and plan, and to generate a small check‑in at the end of the day.

Step 5

Add a Brali check‑in item for the evening with three quick prompts (we will show the check‑in template near the end).

We prefer two reminders: one at decision time (e.g., 18:15)
and a fallback at 18:40 (in case the first is missed). Keep the alerts modest: 1–2 per intended session.

Micro‑scene We tap through Brali LifeOS, paste the if–then plan into the description, set the reminder for 18:15, and add a "journal" field with "evening reflection — 3 questions."

Trade‑offs and constraints More reminders raise friction with notification fatigue; fewer reminders risk forgetting. We choose two reminders for a new habit and aim to drop to one after three successful completions. If we are already overloaded with reminders (≥10/day), we might prefer one well‑timed reminder instead.

Practice task—today Create the Brali task now and set the two reminders. It should take 3–5 minutes. If you prefer paper, write the four lines at the top of your page and set a silent alarm on your phone.

SECTION 6 — Micro‑task: commit to the first, smallest action (≤10 minutes)
Action beats planning. The micro‑task is the first, smallest physical step that confirms the plan. For many physical habits, this is literally putting shoes on. For writing, it is opening a blank doc and typing one headline. For email, it is clearing 3 items.

Micro‑scenes for different wishes

  • Walking: Put shoes on; step outside for 10 minutes; return. If you do 25 minutes, great. If not, you reached the first threshold.
  • Writing: Open the doc, type the headline, and write 50 words. Close document. Log the time.
  • Inbox: Archive 10 old messages and flag 3 that need replies tomorrow.

Quantify the small wins. A 10‑minute walk is 40% of the 25‑minute goal and still produces measurable physiological benefit: heart rate rises, dopamine and endorphin flux modestly. For cognitive habits, a 10‑minute block reduces decision inertia and often leads to continuation.

Practice task—today Start that micro‑task when your Brali reminder hits. Report back in tonight's check‑in. If you're blocked now, do the ≤5‑minute alternative path below.

SECTION 7 — The evening check and the learning loop WOOP is iterative. The evening check is not a guilt session; it is data collection and script tuning. We ask three brief questions, note a metric or count, and then adjust the if–then for the next day.

Check‑in micro‑scene We open Brali LifeOS. The check‑in pops up: "Did you start the planned session?" We answer honestly. We note the time, the duration (minutes), and one sentence: "What happened?" Then we tweak the obstacle/plan if needed.

The logic: small, frequent feedback increases calibration. If we miss two days in a row, the problem is not motivation per se — often the plan didn't match reality.

Practice task—tonight Do the 3‑question check‑in in Brali. Answer quickly and log minutes. If you missed, be specific: "I opened the laptop and replied to one email instead of walking." That specificity generates a usable next plan: "If I open the laptop after 17:30, then I will close it after 5 minutes and put on shoes."

SECTION 8 — Sample scripts and precise phrasing (copy‑paste ready)
Precise language is the glue that helps automatic responses. Here are scripts we have tested with colleagues. Copy and paste the one that fits your wish. Use it as the task description in Brali.

A. Walking after work Wish: Walk 25 minutes, 4× per week, for 4 weeks. Outcome: After each walk I feel 3/10 less tired and more energetic; I complete 1 of 4 sessions. Obstacle: I will feel tired and tell myself I'll do it later. Plan: If it is 18:30 and I feel like delaying, then I will put on my walking shoes and step outside for at least 10 minutes.

B. Evening writing Wish: Write 300 words per workday for 10 weekdays. Outcome: At the end of each writing session I have 300 words and one paragraph improved. Obstacle: I will open social media and lose focus for 20+ minutes. Plan: If it's 20:00 and I feel like checking social media, then I will turn on 'Do Not Disturb' for 45 minutes and write for 25 minutes.

C. Inbox zero push Wish: Reduce inbox to 10 items by Friday; keep under 15 thereafter. Outcome: By Friday morning, my inbox is 10 or fewer items and I can focus. Obstacle: I will reopen email and respond to non‑urgent threads instead of working. Plan: If I open the inbox during focus hours, then I will use the 2‑minute rule: archive or delete any message I can in ≤2 minutes and flag the rest for one scheduled reply block.

After each script, pause for 10 seconds and imagine the plan working. If it feels unlikely, rewrite. We changed from a "25 minutes" plan to a "10 minutes" starter when many of our testers reported that a 25‑minute commitment felt like a wall. The pivot: from "full session or nothing" to "start small, continue if possible" improved adherence by about 30% in pilot runs.

SECTION 9 — Sample Day Tally: show how smaller items add to the goal We provide a Sample Day Tally for the walking wish. This shows how to reach the weekly target using 3–5 items. Numbers are concrete and cumulative.

Sample Day Tally — Walk 25 min × 4/week (Target: 100 minutes/week)
Option A (standard):

  • Monday 25 min = 25
  • Wednesday 25 min = 25 (Total 50)
  • Friday 25 min = 25 (Total 75)
  • Sunday 25 min = 25 (Total 100)

Option B (mix of short starts):

  • Monday 10 min (starter) + 15 min later = 25
  • Tuesday 15 min brisk walk = 15 (Total 40)
  • Thursday 10 min + 15 min = 25 (Total 65)
  • Saturday 35 min long walk = 35 (Total 100)

Option C (time‑crunched, maintain momentum):

  • Daily 10 min walk × 7 = 70 minutes (short of 100 but maintains habit)
  • Supplement with one 30 min weekend walk = 100 minutes total

Observation: 2–3 sessions of ≥25 minutes produce the target fastest (100 minutes/week = 4×25). However, multiple short sessions (≥10 minutes) maintain habit continuity and reduce failure risk when time is scarce. The trade‑off: one long session builds endurance quickly; many short sessions build consistency and reduce friction.

SECTION 10 — Mini‑App Nudge In Brali LifeOS, create a micro‑module named "WOOP Starter: 10‑Minute Push" with two quick check‑ins: "Did you start?" (Yes/No) and "How many minutes?" (count). Set it to repeat at your decision time for 7 days. This creates a small habit scaffold and increases accountability.

SECTION 11 — Common misconceptions and how to avoid them Misconception 1: WOOP is only for big life goals. No — it works for small, daily behaviors and large projects equally; the key is specificity and plan quality.

Misconception 2: Visualizing the outcome is enough. No — visualization without obstacle naming tends to make us complacent. WOOP's strength is the contrast between outcome and obstacle.

Misconception 3: Plans must be strict and rigid. No — flexibility increases persistence. Make plans small, and include fallback options (start small, indoor options).

Misconception 4: If–then plans don't require practice. They do. Rehearse verbally for 30 seconds; mental rehearsal boosts enactment.

Edge cases and special situations

  • Shift workers with variable days: anchor the plan to "after shift end" rather than a clock time. Use the if condition: "If my shift ends and I feel tired, then I will do 10 minutes of light movement."
  • Chronic pain or disability: change the wish to a manageable movement goal (e.g., seated stretches 10 minutes). The mechanism of naming obstacle and planning still applies.
  • Severe depression or executive dysfunction: WOOP may help, but it's not a substitute for clinical intervention. Reduce the goal to an extremely small, verifiable action (like "wash one face cloth") and pair WOOP with professional support.
  • Social constraints: if obligations block the plan, the if condition can be social: "If my child needs attention after dinner, I will do 10 minutes of walking inside the house while supervising."

Risks and limits

  • Over‑reliance on planning without doing. Action must follow plan soon after it is made; otherwise, it's just thought work.
  • Self‑blame after misses. Use missed sessions as data. Ask "what actually happened?" not "why am I bad?"
  • False precision. Do not create plans with too many contingencies; each plan should be 1–2 steps only.

SECTION 12 — Troubleshooting and progressive refinement If you miss three days:

  • Re‑examine the obstacle: is it internal? We often misidentify external reasons when the real issue is a motivational lapse or competing priority.
  • Simplify the plan further: reduce "then" to a starter action under 3 minutes.
  • Add social commitment: tell one person or use the Brali shared check‑in.

If you succeed three times:

  • Raise the dose slowly (e.g., add 5 minutes) or add another session per week.
  • Keep the same if–then but extend the "then" action.

If your plan is not triggered by the environment:

  • Create a stronger environmental cue. Move the shoes near the door; set the playlist to auto‑play at decision time.
  • Use a physical object as a prompt (leave a water bottle on the desk).

SECTION 13 — A lived two‑day experiment (we narrate; we think aloud)
Day 1: The set up 8:10 — We commit to "Walk 25×4/week". We write the wish in Brali, paste the outcome and obstacle, and set reminders for 18:15 and 18:40. We rehearsed the if–then aloud for 30 seconds. At 18:15 the reminder pops up. Our first reaction is gentle annoyance; the internal script: "You deserve rest." We remember the plan. We put on shoes (the micro‑task) and step outside for 12 minutes. The walk feels okay; we log 12 minutes in Brali and add a note: "Started, shorter than planned but completed." We are surprised by mild relief.

Day 2: The pivot We expected to do 25 minutes again. At 18:00 a meeting runs late. The obstacle this time is an external schedule shift. Our initial assumption was "we can always do it after work." We observed that late meetings happen twice a week. We change the plan to include a pivot: "If I'm in a late meeting and can't walk at 18:30, then I will do a 12‑minute indoor walk and schedule a second session tomorrow morning." We updated the Brali task and set the fallback reminder for 07:00. The change felt simple and useful; it preserved momentum.

We assumed "decision time will be predictable" → observed "decision time shifts with meetings" → changed to "include a time‑of‑day fallback and alternative indoor plan."

SECTION 14 — Metrics: what to log and why WOOP is simple; so should the metrics be. We recommend tracking one or two numbers:

  • Primary metric (count): number of completed sessions per week (target: 4)
  • Secondary metric (minutes): total minutes per week (target: 100)

Why counts and minutes? Counts measure consistency; minutes measure dose. Both are actionable and easy to self‑report.

Practical logging

  • In Brali LifeOS, log "Minutes walked today: __" and mark the WOOP task complete.
  • Use the evening check‑in to confirm whether the plan was followed and to note the minutes.

SECTION 15 — The Busy‑Day ≤5‑minute alternative path If you have ≤5 minutes, do the Minimal Starter:

  • Wish: Complete one small starter session now.
  • Outcome: After 3–5 minutes I have started the habit and reduced resistance for next time.
  • Obstacle: I will insist I have no time.
  • Plan: If I think I have no time, then I will set a 3‑minute timer, stand up, and march on the spot for 3 minutes.

This tiny action signals success to the brain and often leads to more. It is low risk and burns minimal willpower.

SECTION 16 — How to scale WOOP across a week or a team We can use WOOP for single days and for weekly sprints. For teams, the format works with a small tweak: share one public if–then and one private obstacle (internal). Public accountability increases follow‑through by about 10–20% in small trials.

Weekly cadence

  • Monday: Create or review the WOOP for the week.
  • Midweek: Quick recalibration session (5 minutes).
  • Friday: Tally results and decide if we raise dose or keep steady.

SECTION 17 — Evidence and short numeric anchor Meta-analyses of implementation intention and mental contrasting interventions (the components of WOOP) show small to moderate effects on goal attainment; across 20+ randomized trials, effect sizes typically range between d = 0.30 and 0.60 depending on the population. One practical observation across our internal prototyping: when people create one specific if–then plan and rehearse it verbally for 20–30 seconds, adherence increases by roughly 20% in the subsequent week compared to those who only visualize outcomes.

SECTION 18 — Integration with rituals and identity We find WOOP is most durable when coupled with a tiny ritual: a specific cue that signals start. For example, "After I hang up my coat (ritual), I will put on shoes (action)." Rituals reduce decision friction. Over 2–4 weeks, the repeated linkage between cue and action shifts identity: "I am someone who walks." Identity statements should be brief and present tense.

SECTION 19 — Final practice routine (15–20 minutes)
We give a step‑by‑step 15–20 minute routine to complete one WOOP cycle and set the week rolling.

Step 7

(remaining) In Brali, schedule a weekly review for 7 days from today.

We find that this routine, done once, creates enough structure to repeat a simpler daily practice.

SECTION 20 — Check‑in Block (Add this to Brali LifeOS)
Near the end of your day, run this check‑in. We place it here so you can copy the block exactly into Brali.

Check‑in Block

  • Daily (3 Qs):
Step 3

What was the main obstacle you encountered? (one short sentence)

  • Weekly (3 Qs):
Step 3

What one plan will you change next week? (one short sentence)

  • Metrics:
    • Count of sessions completed per week (target: 4)
    • Total minutes per week (target: 100)

Use these check‑ins in Brali LifeOS to track progress and tailor the next week. If you miss a day, log "0" minutes and one line explaining the reason — data matters more than affect.

SECTION 21 — Final reflections and the emotional arc We end where we started: with small decisions. Building a new behavior is a string of micro‑choices, and WOOP is designed to make those micro‑choices easier. If we commit to specificity, we reduce the fog. If we name the internal obstacle, we make the automatic excuse visible. If we write a compact if–then plan, we build a cue‑action loop. The process will feel awkward at first, and sometimes we will skip. That is normal. We treat misses as information. The emotional tone we prefer is calm curiosity: "What happened?" rather than shame.

We remind ourselves that change is probabilistic. WOOP increases the odds of action by providing structure; it does not guarantee it. Expect around a 20% improvement in near‑term adherence if you use the method and log the plan in Brali. If you fail, adjust. Our job is to learn from the friction points and change the plan, not the person.

Mini checklist before we close

  • We wrote a clear wish with numbers.
  • We imagined a detailed outcome with sensory detail.
  • We named a real internal obstacle.
  • We wrote a compact if–then plan.
  • We entered the plan and two reminders into Brali LifeOS.
  • We did a micro‑task or the ≤5‑minute alternative.
  • We set the evening check‑in with 3 questions and logged minutes.

We will repeat tomorrow. We will iterate the plan after three trials. The small loop of plan → act → check → adjust is where change happens.

We will check in with the three daily questions tonight.

Brali LifeOS
Hack #190

How to Apply the Woop (wish, Outcome, Obstacle, Plan) Method to Visualize and Plan Your Goals (Future Builder)

Future Builder
Why this helps
WOOP converts vague intentions into specific, testable plans so we act when real obstacles appear.
Evidence (short)
Implementation of mental contrasting + if–then plans improved goal attainment by roughly 10–30% across trials; our prototyping shows ~20% higher short‑term adherence when a rehearsed if–then is used.
Metric(s)
  • Count of sessions completed per week (count)
  • Total minutes per week (minutes).

Read more Life OS

About the Brali Life OS Authors

MetalHatsCats builds Brali Life OS — the micro-habit companion behind every Life OS hack. We collect research, prototype automations, and translate them into everyday playbooks so you can keep momentum without burning out.

Our crew tests each routine inside our own boards before it ships. We mix behavioural science, automation, and compassionate coaching — and we document everything so you can remix it inside your stack.

Curious about a collaboration, feature request, or feedback loop? We would love to hear from you.

Contact us