Negate your root assumption and explore the implications…
State the negation of any root concept you identify and ask what you would do differently if the opposite were true, not to believe the negation but to break the structural lock that makes the original feel inevitable.
When This Fires
- After identifying a root assumption (Identify the deepest assumption in each decision domain…)
- When an assumption feels so obviously true that questioning it feels absurd
- During any strategic review where foundational premises need testing
- When you want to expand your option space beyond what your current assumptions allow
Common Failure Mode
Dismissing the negation immediately: "That's clearly wrong." The dismissal is the structural lock protecting itself. The negation doesn't need to be correct — it needs to be explored. "What if I'm wrong about this? What would I do differently?" If you can't answer because the alternative is unthinkable, the assumption has achieved dogma status and needs more scrutiny, not less.
The Protocol
After identifying a root assumption: (1) State the negation: "What if [opposite of root assumption]?" (2) Explore implications: "If the negation were true, which of my current decisions would I change? What would I do instead?" (3) The exploration often reveals that some decisions under the negation are actually better — indicating that your root assumption may be partially wrong or unnecessarily constraining. (4) The goal is not to adopt the negation but to break the structural lock and restore the assumption to choosable, testable status rather than inevitable-feeling truth.