Anti-Goals: Defining Success by What You Refuse to Accept
How defining what you don’t want sharpens what you actually pursue
What are anti-goals and how do they improve decisions?
Anti-goals, popularised by entrepreneur Andrew Wilkinson, are explicit statements of the outcomes, conditions, and trade-offs you refuse to accept — defined before deciding what to pursue. They complement positive goal-setting by creating a decision filter that eliminates technically "successful" outcomes that would make you miserable. The framework is a practitioner heuristic with no direct experimental study, but it applies well-supported principles from decision science and values-clarification.
Positive goal-setting asks "What do I want?" Anti-goals ask a harder question first: "What would make success feel like failure?" Andrew Wilkinson’s framework, derived from his experience building and selling companies, starts by listing the conditions of a nightmare outcome — and then uses those as filters before pursuing anything that looks attractive. The practices below operationalise this inversion across personal and professional decisions.
Practices
- Define your nightmare outcome before your ideal outcome
Write a vivid description of the life you don’t want — this clarifies the anti-goals that protect you from sleepwalking into it.
- Use anti-goals as a decision filter before evaluating opportunities
Run every major opportunity through your anti-goals list before calculating the upside.
- Name trade-off anti-goals: conditions that come bundled with attractive outcomes
Many desirable outcomes come packaged with specific costs — name the hidden costs as anti-goals before you commit.
- Set lifestyle anti-goals to protect daily experience, not just outcomes
The quality of your daily experience matters — define the daily conditions you refuse to accept, not just the outcomes.
- Apply anti-goals to relationships and collaborators
Naming the relational patterns you refuse to accept prevents you from optimising for the wrong things in who you work or live with.
- Review and update anti-goals annually as values evolve
Anti-goals based on your 28-year-old priorities may be wrong for your 38-year-old ones — review them explicitly.
- Distinguish true anti-goals from solvable constraints
Some "I won’t accept" conditions are actually design problems — not genuine anti-goals — and can be solved rather than ruled out.
How these practices connect
Every one of these practices treats a refusal as more decision-useful than a preference, because a specific 'I will not accept X' functions as a hard filter that runs before optimism bias and rationalization get a vote. Positive goals invite upside evaluation first, which is exactly where costs get discounted; anti-goals force the avoid-condition to be checked first, and only opportunities that survive it get evaluated for upside at all. The practices differ in WHERE that refusal gets applied — to the whole life, to a single decision, to a bundled trade-off, to daily texture, to relationships, or to the anti-goal list itself — but the underlying mechanism is the same reordering of refusal-before-upside.
Do I write my anti-goals before or after I know what I actually want?
Before. Nightmare-scenario-definition has you describe the outcome you refuse to accept before you define your ideal outcome, because imagining a future as already having happened (prospective hindsight) produces more specific, more action-guiding reasons than forward-looking planning does. A vague ideal goal tends to generate vague anti-goals; a vividly described nightmare generates concrete avoid-conditions like a headcount limit or an email cutoff time, which is what makes an anti-goal usable as a filter later. This ordering is also what feeds anti-goal-decision-filter — you need the specific list before you can run anything through it.
How is an anti-goal different from just being pessimistic about an opportunity?
Pessimism weighs the downside against the upside at the same time, which still leaves room for the upside to win the argument. An anti-goal filter is sequenced differently: anti-goal-decision-filter checks the opportunity against your refusal list before any upside calculation begins, so an opportunity that violates a stated anti-goal is eliminated before you ever get to 'but the potential is so good.' The mechanism it's countering is optimism bias activated by upside-first evaluation, not a general negative outlook.
Why would a good opportunity still get filtered out by an anti-goal?
Because many attractive outcomes come bundled with costs that aren't visible in the headline pitch. Trade-off-anti-goals names the hidden, packaged-in conditions of a desirable outcome — a high-income role that also demands specific lifestyle constraints, for instance — so the bundled cost gets evaluated instead of just the attractive attribute. When you run that named cost through anti-goal-decision-filter, an opportunity can fail even though its headline upside is real, because the filter is checking the whole package, not the part that got your attention.
What's the difference between a lifestyle anti-goal and a trade-off anti-goal?
Trade-off-anti-goals names costs bundled into a specific outcome or decision — the price tag attached to one choice. Lifestyle-anti-goals is broader: it defines the minimum acceptable texture of daily life across all your ongoing small choices — schedule, environment, relationships — regardless of which single outcome you're pursuing, because an outcome can be fully achieved while daily lived experience stays miserable. A trade-off anti-goal might surface once, at the point of a decision; a lifestyle anti-goal is meant to filter the accumulated small choices that happen every day, whether or not a decision is on the table.
Should I use anti-goals to evaluate people, not just decisions?
Yes — relationship-anti-goals applies the same refusal logic to who you work or live with, because skill and talent are highly salient in a pitch or first impression while relational patterns like honesty and reliability are harder to assess upfront and easy to discount. Naming a relational anti-goal ("I will not partner with someone who does X") forces attention onto the dimension most likely to cause suffering rather than the one most visible in the room. The common mistake is applying this only to partners or employees; the same asymmetry applies to clients, investors, and social circles.
Is every 'I won't accept this' actually an anti-goal?
No, and conflating the two categories is the specific failure anti-goals-vs-constraints names. A genuine anti-goal is a values-based refusal; a solvable constraint is a design problem disguised as a refusal — something you can't currently see how to avoid, not something you actually refuse on principle. Labeling a solvable constraint as an anti-goal forecloses an option prematurely, when the right response would have been creative problem-solving instead of elimination. The line between the two isn't always obvious and may need iterative testing rather than a single reflection pass to sort out.
Do anti-goals change over time, or are they set once?
They're meant to change. Annual-anti-goal-review treats the anti-goal list as a living document because values shift with life stage and accumulated experience of what actually helps or harms well-being — an anti-goal written at 28 may actively constrain a better path at 38. The mistake this practice is guarding against is treating the original list as sacred rather than as a hypothesis to keep testing against lived experience; what matters is deliberate, repeated revisitation, not the specific interval of doing it annually.
How do you choose between these?
Start from what's actually in front of you: facing a single opportunity or offer, run it through anti-goal-decision-filter and, if the offer bundles a cost with its upside, name that cost first with trade-off-anti-goals. If the friction is in ongoing daily life rather than a single decision, lifestyle-anti-goals is the fit because it filters recurring small choices, not one-time ones. If the friction is about a specific person — a collaborator, client, or partner — relationship-anti-goals targets the dimensions that are easy to overlook in a pitch. If you don't have a list yet, nightmare-scenario-definition is the starting point that produces one. And whenever a stated anti-goal starts to feel like it's blocking something that would otherwise work, check it against anti-goals-vs-constraints before treating the refusal as final — it may be a solvable problem, not a genuine limit. None of this depends on what kind of person you are; it depends on which of these five situations — a decision, a bundled trade-off, daily life, a relationship, or an aging list — you're actually in.
What these approaches do not settle
Anti-goal-decision-filter and annual-anti-goal-review are both labeled mechanistic rather than tested: they're reasonable applications of decision-heuristic and values-drift reasoning, but the anti-goals framing itself hasn't been directly studied as a decision tool or a review cadence, so the specific claim that filtering before upside evaluation (rather than after) changes outcomes is inferred, not measured. The evidence most directly supporting this page — prospective hindsight research behind nightmare-scenario-definition — backs the nightmare-first step specifically, not the broader anti-goals framework it's used to justify. And anti-goals-vs-constraints is honest that its own central distinction, genuine refusal versus solvable constraint, doesn't have a clean test; it says outright that sorting the two may take iterative experimentation rather than a single reflection exercise, which means the practice most other practices depend on for correct application is also the least resolved one here.
Practice this with IX Coach
Related concepts
- Essentialism, Made Practical
Less but better — the disciplined pursuit of less, trade-offs, and the mechanisms
- Values Clarification, Made Practical
Card sorts, ranking, and value-consistent action — with an honest read on the evidence
- Fear-Setting, Made Practical
Defining the worst case, the prevention, the repair, and the cost of inaction