Inversion
Instead of asking how this succeeds, what if you asked how it fails?
The idea
Avoiding known failure modes can be easier than designing perfection.
In the real world
Prevent data loss before optimizing dashboard colors.
Going deeper
Asking how to succeed produces an open-ended list that people disagree about. Asking how this fails produces a short, concrete list that people agree on almost immediately, because failure modes are specific and success is contested.
Eliminating known failures also has better returns early on. Preventing data loss, a broken signup and no support route raises the floor reliably; debating what would make the product excellent raises the ceiling speculatively. The two are complementary, and inversion is the one that is systematically underused because it feels less ambitious.
Where it stops applying
A product that only avoids failure is merely inoffensive. Inversion secures the baseline; it will not produce anything anyone loves.
Why it matters
Failure modes are usually easier to list and eliminate than success conditions are to design.
Try this today
List three ways the plan could fail.
Test yourself
A team debates which features would make a launch excellent. Asked instead what would make it a disaster, they immediately name data loss, a broken signup, and no way to contact support. Why was the second list easier?
Show the answer
Failure is concrete and bounded, while excellence is open-ended and contested. Removing known ways to fail raises the floor reliably; designing perfection often produces disagreement and no decision.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.