Assumption Mapping
A decomposition technique that extracts the hidden assumptions bundled inside a compound belief or plan, making each dependency explicit, testable, and independently evaluable.
Linked Lessons
Compound ideas hide dependencies
Extract Hidden Assumptions from a Compound Belief
Notice what you are not seeing
Run an Absence Audit on One Domain You Interact with Daily
Everyone operates on schemas
Map Your Hidden Assumptions in Obsidian
Inherited schemas versus chosen schemas
Map the Origins of a Core Belief in Miro
Schema awareness is the beginning of freedom
Map Your Hidden Decision Schema in Obsidian
Schemas have resolution limits
Map Your Schema's Blind Spots in Obsidian
Default schemas are invisible schemas
Map Your Morning Email Schema in Obsidian
Language encodes schemas
Map Your Domain Language in Obsidian
The cost of a bad schema
Map Your Untested Schema and Its Decision Impacts in Obsidian
Categories are constructed not discovered
Map the Hidden Purposes Behind Your Daily Categories in Miro
Root concepts anchor everything beneath them
Map Your Root Assumption in Obsidian
Failed predictions are data not failures
Map Your Failed Prediction to Find Schema Gaps in Obsidian
Peer review for personal schemas
Map Assumptions in Your Mental Model Using Miro
Validated schemas still have limits
Map the Boundaries of a Validated Schema in Miro
Schema debt from deferred updates
Map Your Career Schema Debt in Miro
Anomalies are evolution signals
Map Anomalies to Schema Assumptions in Miro
Proactive schema evolution
Test Your Decision-Making Schema in Obsidian
Schema dependencies
Map Your Belief Dependencies in Obsidian
Schemas about learning
Map Your Learning Beliefs in Obsidian
Schemas about other people
Map Your Assumptions About Three People in Obsidian
Evaluating schema sources
Map Schema Sources in Miro