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.

Why it works

Anti-goals should capture genuine values-based refusals, not engineering challenges. When an "I won’t accept" statement is actually "I can’t see how to avoid this," the right response is creative problem-solving, not elimination of the opportunity. Conflating the two categories narrows the option space unnecessarily and replaces deliberate design with premature foreclosure.

How to do it

1. For each anti-goal, ask: "Is this a refusal (I value its opposite) or a default (I haven’t found a way to avoid it)?"
2. Defaults belong in a problem-solving process, not a filter list.
3. True anti-goals survive the test: "Even if someone solved the logistical problem, I still would not accept this condition."
4. Keep only genuine refusals on the anti-goals list; move solvable constraints to a design brief.

Evidence

The distinction between values-based and capability-based constraints is supported by decision research on satisficing and constraint relaxation; conflating the two produces unnecessary option foreclosure. This specific application is conceptual rather than studied. Payne, Bettman & Johnson (1993) show that decision makers relax and reprioritise constraints adaptively as effort and stakes shift, underscoring that a constraint treated as fixed may in fact be a solvable default rather than a genuine refusal. (mechanistic)

The test between genuine refusal and solvable default is not always clear and may require iterative experimentation rather than a single reflection exercise.

Sources

• Payne, J. W., Bettman, J. R., & Johnson, E. J. (1993). The Adaptive Decision Maker. Cambridge: Cambridge University Press.

Common mistake

Labelling a constraint as an anti-goal because overcoming it feels hard, locking out an option that would be entirely acceptable if the practical challenge were solved.