Audit each schema's implicit assumptions, then cross-compare — shared undefined dependencies are your deepest gaps

Why This Is a Rule

Every schema — mental model, framework, or theory — takes certain things for granted. A schema about "effective feedback" assumes concepts like "psychological safety," "growth mindset," and "performance measurement" without defining them. A schema about "agile development" assumes "iterative improvement," "customer value," and "team autonomy." These assumptions are the schema's invisible prerequisites: the foundation it stands on without acknowledging.

When you cross-compare assumption lists across schemas, a pattern emerges: shared dependency gaps. Multiple schemas depend on the same foundational concept that none of them defines. "Psychological safety" appears as an assumed prerequisite in your feedback schema, your team leadership schema, and your innovation schema — but nowhere in your knowledge system is it actually defined and examined. This shared dependency gap is a high-leverage learning target: understanding it strengthens every schema that depends on it.

This technique also reveals fragile assumptions: concepts that multiple schemas assume but that may not hold in all contexts. If three schemas assume "rational actors" but your behavioral economics schema demonstrates systematic irrationality, you've found an assumption that silently undermines the others.

When This Fires

• During schema integration when combining frameworks from different domains
• When evaluating the robustness of a mental model — its assumptions are its vulnerability surface
• When looking for high-leverage learning targets (shared dependencies are the highest leverage)
• During periodic knowledge system audits when checking for implicit foundation gaps

Common Failure Mode

Listing only the assumptions you're aware of rather than the ones the schema actually makes. The hardest assumptions to surface are the ones so fundamental you don't recognize them as assumptions: "time is linear," "people respond to incentives," "complex systems are decomposable." To find these, ask: "In what context would this schema completely fail?" The answer reveals assumptions that are so baked in they're invisible.

The Protocol

(1) For a schema in your knowledge system, list everything it takes for granted without defining. Ask: "What must be true for this schema to work?" and "What concepts does it use without explaining?" (2) Repeat for other schemas you want to compare. (3) Cross-compare: which assumptions appear in multiple schemas? These shared dependencies are your highest-leverage gaps. (4) For each shared dependency: is it explicitly defined somewhere in your knowledge system? If not → create that definition. You've found a foundational concept that multiple frameworks depend on but none examines. (5) Check whether any shared assumption is questionable — if multiple schemas depend on an assumption that may not hold, you've found a systemic vulnerability.